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:14.110 align:start position:0%
 
[Music]

00:00:14.110 --> 00:00:14.120 align:start position:0%
 
 

00:00:14.120 --> 00:00:17.330 align:start position:0%
 
thanks<00:00:15.120><c> for</c><00:00:15.360><c> coming</c><00:00:15.599><c> my</c><00:00:16.320><c> name</c><00:00:16.379><c> is</c><00:00:16.500><c> Vincent</c><00:00:16.980><c> I'm</c>

00:00:17.330 --> 00:00:17.340 align:start position:0%
thanks for coming my name is Vincent I'm
 

00:00:17.340 --> 00:00:19.430 align:start position:0%
thanks for coming my name is Vincent I'm
going<00:00:17.640><c> to</c><00:00:17.880><c> talk</c><00:00:18.420><c> about</c><00:00:18.600><c> standardized</c>

00:00:19.430 --> 00:00:19.440 align:start position:0%
going to talk about standardized
 

00:00:19.440 --> 00:00:22.370 align:start position:0%
going to talk about standardized
subgraphs<00:00:20.100><c> today</c><00:00:20.279><c> or</c><00:00:21.000><c> how</c><00:00:21.300><c> we</c><00:00:21.539><c> can</c><00:00:21.720><c> make</c><00:00:21.960><c> it</c><00:00:22.140><c> so</c>

00:00:22.370 --> 00:00:22.380 align:start position:0%
subgraphs today or how we can make it so
 

00:00:22.380 --> 00:00:25.250 align:start position:0%
subgraphs today or how we can make it so
much<00:00:22.560><c> easier</c><00:00:22.920><c> for</c><00:00:23.580><c> you</c><00:00:23.699><c> to</c><00:00:23.880><c> build</c><00:00:24.060><c> your</c><00:00:24.240><c> dats</c>

00:00:25.250 --> 00:00:25.260 align:start position:0%
much easier for you to build your dats
 

00:00:25.260 --> 00:00:27.890 align:start position:0%
much easier for you to build your dats
if<00:00:25.740><c> you</c><00:00:25.859><c> ever</c><00:00:26.039><c> built</c><00:00:26.519><c> a</c><00:00:26.699><c> dab</c><00:00:27.000><c> or</c><00:00:27.359><c> have</c><00:00:27.599><c> ever</c>

00:00:27.890 --> 00:00:27.900 align:start position:0%
if you ever built a dab or have ever
 

00:00:27.900 --> 00:00:30.290 align:start position:0%
if you ever built a dab or have ever
considered<00:00:28.439><c> building</c><00:00:28.740><c> a</c><00:00:29.039><c> DAV</c><00:00:29.279><c> one</c><00:00:30.000><c> of</c><00:00:30.180><c> the</c>

00:00:30.290 --> 00:00:30.300 align:start position:0%
considered building a DAV one of the
 

00:00:30.300 --> 00:00:32.150 align:start position:0%
considered building a DAV one of the
first<00:00:30.420><c> questions</c><00:00:30.779><c> that</c><00:00:31.199><c> comes</c><00:00:31.500><c> to</c><00:00:31.560><c> mind</c><00:00:31.740><c> is</c>

00:00:32.150 --> 00:00:32.160 align:start position:0%
first questions that comes to mind is
 

00:00:32.160 --> 00:00:35.209 align:start position:0%
first questions that comes to mind is
probably<00:00:32.540><c> where</c><00:00:33.540><c> do</c><00:00:33.660><c> you</c><00:00:33.780><c> find</c><00:00:33.960><c> the</c><00:00:34.200><c> data</c>

00:00:35.209 --> 00:00:35.219 align:start position:0%
probably where do you find the data
 

00:00:35.219 --> 00:00:38.030 align:start position:0%
probably where do you find the data
and<00:00:35.940><c> let</c><00:00:36.300><c> me</c><00:00:36.420><c> show</c><00:00:36.540><c> you</c><00:00:36.719><c> an</c><00:00:36.960><c> example</c><00:00:37.559><c> that</c>

00:00:38.030 --> 00:00:38.040 align:start position:0%
and let me show you an example that
 

00:00:38.040 --> 00:00:41.270 align:start position:0%
and let me show you an example that
component<00:00:38.820><c> Finance</c><00:00:39.300><c> has</c><00:00:39.840><c> been</c><00:00:40.020><c> working</c><00:00:40.320><c> on</c><00:00:40.620><c> so</c>

00:00:41.270 --> 00:00:41.280 align:start position:0%
component Finance has been working on so
 

00:00:41.280 --> 00:00:43.850 align:start position:0%
component Finance has been working on so
they're<00:00:41.879><c> trying</c><00:00:42.180><c> to</c><00:00:42.360><c> build</c><00:00:42.719><c> this</c><00:00:43.500><c> uh</c>

00:00:43.850 --> 00:00:43.860 align:start position:0%
they're trying to build this uh
 

00:00:43.860 --> 00:00:47.810 align:start position:0%
they're trying to build this uh
predicted<00:00:44.760><c> model</c><00:00:45.500><c> uh</c><00:00:46.500><c> to</c><00:00:46.739><c> for</c><00:00:46.980><c> people</c><00:00:47.219><c> to</c><00:00:47.640><c> look</c>

00:00:47.810 --> 00:00:47.820 align:start position:0%
predicted model uh to for people to look
 

00:00:47.820 --> 00:00:50.990 align:start position:0%
predicted model uh to for people to look
at<00:00:48.059><c> different</c><00:00:48.840><c> assets</c><00:00:49.260><c> like</c><00:00:49.559><c> if</c><00:00:50.219><c> in</c><00:00:50.640><c> this</c><00:00:50.820><c> case</c>

00:00:50.990 --> 00:00:51.000 align:start position:0%
at different assets like if in this case
 

00:00:51.000 --> 00:00:54.650 align:start position:0%
at different assets like if in this case
and<00:00:51.780><c> how</c><00:00:52.140><c> the</c><00:00:52.860><c> yield</c><00:00:53.039><c> will</c><00:00:53.280><c> be</c><00:00:53.460><c> in</c><00:00:53.579><c> the</c><00:00:53.760><c> future</c>

00:00:54.650 --> 00:00:54.660 align:start position:0%
and how the yield will be in the future
 

00:00:54.660 --> 00:00:57.650 align:start position:0%
and how the yield will be in the future
and<00:00:55.079><c> in</c><00:00:55.199><c> order</c><00:00:55.379><c> to</c><00:00:55.680><c> do</c><00:00:55.920><c> that</c><00:00:56.160><c> they</c><00:00:56.820><c> need</c><00:00:57.059><c> a</c><00:00:57.600><c> lot</c>

00:00:57.650 --> 00:00:57.660 align:start position:0%
and in order to do that they need a lot
 

00:00:57.660 --> 00:01:00.410 align:start position:0%
and in order to do that they need a lot
of<00:00:57.840><c> historical</c><00:00:58.440><c> data</c><00:00:59.100><c> historical</c><00:00:59.760><c> data</c><00:01:00.239><c> on</c>

00:01:00.410 --> 00:01:00.420 align:start position:0%
of historical data historical data on
 

00:01:00.420 --> 00:01:03.290 align:start position:0%
of historical data historical data on
interest<00:01:00.660><c> rate</c><00:01:00.960><c> on</c><00:01:01.620><c> total</c><00:01:02.100><c> deposit</c><00:01:02.579><c> from</c>

00:01:03.290 --> 00:01:03.300 align:start position:0%
interest rate on total deposit from
 

00:01:03.300 --> 00:01:05.570 align:start position:0%
interest rate on total deposit from
different<00:01:03.600><c> lending</c><00:01:04.199><c> protocols</c><00:01:04.860><c> across</c>

00:01:05.570 --> 00:01:05.580 align:start position:0%
different lending protocols across
 

00:01:05.580 --> 00:01:07.670 align:start position:0%
different lending protocols across
different<00:01:05.880><c> Networks</c>

00:01:07.670 --> 00:01:07.680 align:start position:0%
different Networks
 

00:01:07.680 --> 00:01:10.670 align:start position:0%
different Networks
and<00:01:08.580><c> this</c><00:01:09.360><c> is</c><00:01:09.479><c> a</c><00:01:09.720><c> small</c><00:01:10.020><c> example</c><00:01:10.439><c> to</c>

00:01:10.670 --> 00:01:10.680 align:start position:0%
and this is a small example to
 

00:01:10.680 --> 00:01:13.190 align:start position:0%
and this is a small example to
illustrate<00:01:11.220><c> where</c><00:01:11.760><c> you</c><00:01:11.939><c> might</c><00:01:12.119><c> go</c><00:01:12.540><c> to</c><00:01:12.659><c> find</c>

00:01:13.190 --> 00:01:13.200 align:start position:0%
illustrate where you might go to find
 

00:01:13.200 --> 00:01:15.289 align:start position:0%
illustrate where you might go to find
all<00:01:13.500><c> these</c><00:01:13.740><c> data</c><00:01:14.040><c> today</c><00:01:14.280><c> as</c><00:01:14.939><c> you</c><00:01:15.119><c> can</c><00:01:15.180><c> see</c>

00:01:15.289 --> 00:01:15.299 align:start position:0%
all these data today as you can see
 

00:01:15.299 --> 00:01:17.149 align:start position:0%
all these data today as you can see
there<00:01:15.659><c> are</c><00:01:15.780><c> many</c><00:01:16.020><c> different</c><00:01:16.320><c> data</c><00:01:16.860><c> sources</c>

00:01:17.149 --> 00:01:17.159 align:start position:0%
there are many different data sources
 

00:01:17.159 --> 00:01:19.429 align:start position:0%
there are many different data sources
that<00:01:17.460><c> you</c><00:01:17.580><c> need</c><00:01:17.700><c> to</c><00:01:17.820><c> hit</c><00:01:18.000><c> to</c><00:01:18.659><c> depending</c><00:01:19.140><c> on</c>

00:01:19.429 --> 00:01:19.439 align:start position:0%
that you need to hit to depending on
 

00:01:19.439 --> 00:01:21.350 align:start position:0%
that you need to hit to depending on
which<00:01:19.799><c> lending</c><00:01:20.280><c> protocol</c><00:01:20.580><c> you</c><00:01:20.880><c> you</c><00:01:21.060><c> want</c><00:01:21.240><c> to</c>

00:01:21.350 --> 00:01:21.360 align:start position:0%
which lending protocol you you want to
 

00:01:21.360 --> 00:01:23.630 align:start position:0%
which lending protocol you you want to
pull<00:01:21.540><c> data</c><00:01:21.960><c> from</c><00:01:22.080><c> if</c><00:01:22.680><c> you're</c><00:01:22.799><c> lucky</c><00:01:23.040><c> there's</c><00:01:23.520><c> a</c>

00:01:23.630 --> 00:01:23.640 align:start position:0%
pull data from if you're lucky there's a
 

00:01:23.640 --> 00:01:25.490 align:start position:0%
pull data from if you're lucky there's a
subgraph<00:01:24.060><c> that</c><00:01:24.360><c> you</c><00:01:24.479><c> can</c><00:01:24.540><c> already</c><00:01:24.720><c> use</c><00:01:25.080><c> that</c>

00:01:25.490 --> 00:01:25.500 align:start position:0%
subgraph that you can already use that
 

00:01:25.500 --> 00:01:28.010 align:start position:0%
subgraph that you can already use that
has<00:01:25.680><c> all</c><00:01:25.860><c> that</c><00:01:26.040><c> data</c><00:01:26.400><c> if</c><00:01:27.000><c> not</c><00:01:27.180><c> you</c><00:01:27.659><c> might</c><00:01:27.780><c> have</c>

00:01:28.010 --> 00:01:28.020 align:start position:0%
has all that data if not you might have
 

00:01:28.020 --> 00:01:31.789 align:start position:0%
has all that data if not you might have
to<00:01:28.259><c> like</c><00:01:28.560><c> work</c><00:01:29.040><c> with</c><00:01:29.340><c> Json</c><00:01:29.820><c> RPC</c><00:01:30.479><c> API</c><00:01:31.320><c> and</c><00:01:31.619><c> kind</c>

00:01:31.789 --> 00:01:31.799 align:start position:0%
to like work with Json RPC API and kind
 

00:01:31.799 --> 00:01:35.030 align:start position:0%
to like work with Json RPC API and kind
of<00:01:32.360><c> transform</c><00:01:33.360><c> and</c><00:01:34.080><c> aggregate</c><00:01:34.500><c> all</c><00:01:34.740><c> of</c><00:01:34.860><c> that</c>

00:01:35.030 --> 00:01:35.040 align:start position:0%
of transform and aggregate all of that
 

00:01:35.040 --> 00:01:36.590 align:start position:0%
of transform and aggregate all of that
data<00:01:35.400><c> yourself</c>

00:01:36.590 --> 00:01:36.600 align:start position:0%
data yourself
 

00:01:36.600 --> 00:01:38.990 align:start position:0%
data yourself
and<00:01:37.380><c> for</c><00:01:37.619><c> each</c><00:01:37.799><c> of</c><00:01:37.979><c> that</c><00:01:38.159><c> data</c><00:01:38.579><c> you</c><00:01:38.820><c> probably</c>

00:01:38.990 --> 00:01:39.000 align:start position:0%
and for each of that data you probably
 

00:01:39.000 --> 00:01:43.370 align:start position:0%
and for each of that data you probably
also<00:01:39.659><c> need</c><00:01:39.900><c> a</c><00:01:40.380><c> data</c><00:01:40.799><c> adapter</c><00:01:41.280><c> to</c><00:01:41.900><c> normalize</c><00:01:42.900><c> so</c>

00:01:43.370 --> 00:01:43.380 align:start position:0%
also need a data adapter to normalize so
 

00:01:43.380 --> 00:01:45.770 align:start position:0%
also need a data adapter to normalize so
that<00:01:43.560><c> your</c><00:01:43.740><c> application</c><00:01:44.220><c> can</c><00:01:44.520><c> use</c><00:01:44.759><c> it</c><00:01:45.000><c> so</c><00:01:45.479><c> the</c>

00:01:45.770 --> 00:01:45.780 align:start position:0%
that your application can use it so the
 

00:01:45.780 --> 00:01:47.929 align:start position:0%
that your application can use it so the
point<00:01:45.960><c> I</c><00:01:46.200><c> wanted</c><00:01:46.380><c> to</c><00:01:46.680><c> make</c><00:01:46.799><c> here</c><00:01:47.040><c> is</c><00:01:47.280><c> that</c><00:01:47.460><c> web3</c>

00:01:47.929 --> 00:01:47.939 align:start position:0%
point I wanted to make here is that web3
 

00:01:47.939 --> 00:01:51.050 align:start position:0%
point I wanted to make here is that web3
data<00:01:48.420><c> space</c><00:01:48.540><c> is</c><00:01:48.960><c> very</c><00:01:49.200><c> fragmented</c><00:01:49.939><c> there</c><00:01:50.939><c> are</c>

00:01:51.050 --> 00:01:51.060 align:start position:0%
data space is very fragmented there are
 

00:01:51.060 --> 00:01:52.730 align:start position:0%
data space is very fragmented there are
dozens<00:01:51.360><c> and</c><00:01:51.479><c> dozens</c><00:01:51.840><c> of</c><00:01:52.020><c> different</c><00:01:52.259><c> data</c>

00:01:52.730 --> 00:01:52.740 align:start position:0%
dozens and dozens of different data
 

00:01:52.740 --> 00:01:55.730 align:start position:0%
dozens and dozens of different data
source<00:01:52.979><c> that</c><00:01:53.220><c> focus</c><00:01:53.579><c> on</c><00:01:53.759><c> different</c><00:01:54.119><c> parts</c><00:01:54.740><c> of</c>

00:01:55.730 --> 00:01:55.740 align:start position:0%
source that focus on different parts of
 

00:01:55.740 --> 00:01:57.830 align:start position:0%
source that focus on different parts of
data<00:01:56.040><c> or</c><00:01:56.220><c> different</c><00:01:56.399><c> kind</c><00:01:56.640><c> of</c><00:01:56.820><c> data</c><00:01:57.180><c> if</c><00:01:57.720><c> you're</c>

00:01:57.830 --> 00:01:57.840 align:start position:0%
data or different kind of data if you're
 

00:01:57.840 --> 00:02:01.010 align:start position:0%
data or different kind of data if you're
working<00:01:58.079><c> with</c><00:01:58.380><c> raw</c><00:01:58.680><c> data</c><00:01:59.159><c> it</c><00:02:00.060><c> takes</c><00:02:00.299><c> a</c><00:02:00.720><c> lot</c><00:02:00.840><c> of</c>

00:02:01.010 --> 00:02:01.020 align:start position:0%
working with raw data it takes a lot of
 

00:02:01.020 --> 00:02:04.249 align:start position:0%
working with raw data it takes a lot of
effort<00:02:01.500><c> to</c><00:02:02.159><c> aggregate</c><00:02:02.759><c> transform</c><00:02:03.479><c> them</c><00:02:03.720><c> into</c>

00:02:04.249 --> 00:02:04.259 align:start position:0%
effort to aggregate transform them into
 

00:02:04.259 --> 00:02:06.109 align:start position:0%
effort to aggregate transform them into
something<00:02:04.560><c> that</c><00:02:04.860><c> you</c><00:02:05.040><c> can</c><00:02:05.159><c> use</c><00:02:05.399><c> for</c><00:02:05.880><c> example</c>

00:02:06.109 --> 00:02:06.119 align:start position:0%
something that you can use for example
 

00:02:06.119 --> 00:02:09.290 align:start position:0%
something that you can use for example
TVR<00:02:06.780><c> Revenue</c><00:02:07.200><c> those</c><00:02:07.920><c> all</c><00:02:08.459><c> require</c><00:02:08.640><c> a</c><00:02:09.060><c> lot</c><00:02:09.119><c> of</c>

00:02:09.290 --> 00:02:09.300 align:start position:0%
TVR Revenue those all require a lot of
 

00:02:09.300 --> 00:02:10.010 align:start position:0%
TVR Revenue those all require a lot of
work

00:02:10.010 --> 00:02:10.020 align:start position:0%
work
 

00:02:10.020 --> 00:02:12.770 align:start position:0%
work
uh<00:02:10.619><c> historical</c><00:02:11.099><c> data</c><00:02:11.520><c> is</c><00:02:11.819><c> often</c><00:02:12.239><c> difficult</c><00:02:12.540><c> to</c>

00:02:12.770 --> 00:02:12.780 align:start position:0%
uh historical data is often difficult to
 

00:02:12.780 --> 00:02:15.530 align:start position:0%
uh historical data is often difficult to
find<00:02:13.340><c> you</c><00:02:14.340><c> probably</c><00:02:14.520><c> need</c><00:02:14.700><c> an</c><00:02:14.879><c> archive</c><00:02:15.180><c> node</c>

00:02:15.530 --> 00:02:15.540 align:start position:0%
find you probably need an archive node
 

00:02:15.540 --> 00:02:17.530 align:start position:0%
find you probably need an archive node
and<00:02:15.720><c> those</c><00:02:15.959><c> are</c><00:02:16.140><c> often</c><00:02:16.500><c> difficult</c><00:02:16.800><c> to</c><00:02:17.040><c> access</c>

00:02:17.530 --> 00:02:17.540 align:start position:0%
and those are often difficult to access
 

00:02:17.540 --> 00:02:20.030 align:start position:0%
and those are often difficult to access
this<00:02:18.540><c> is</c><00:02:18.720><c> actually</c><00:02:18.959><c> a</c><00:02:19.319><c> problem</c><00:02:19.440><c> that</c><00:02:19.800><c> Missouri</c>

00:02:20.030 --> 00:02:20.040 align:start position:0%
this is actually a problem that Missouri
 

00:02:20.040 --> 00:02:22.910 align:start position:0%
this is actually a problem that Missouri
has<00:02:20.879><c> run</c><00:02:21.120><c> into</c><00:02:21.360><c> when</c><00:02:21.840><c> we</c><00:02:22.020><c> first</c><00:02:22.200><c> got</c><00:02:22.500><c> into</c><00:02:22.680><c> the</c>

00:02:22.910 --> 00:02:22.920 align:start position:0%
has run into when we first got into the
 

00:02:22.920 --> 00:02:24.949 align:start position:0%
has run into when we first got into the
Unchained<00:02:23.459><c> space</c><00:02:23.640><c> where</c><00:02:24.120><c> a</c><00:02:24.360><c> big</c><00:02:24.540><c> data</c>

00:02:24.949 --> 00:02:24.959 align:start position:0%
Unchained space where a big data
 

00:02:24.959 --> 00:02:27.170 align:start position:0%
Unchained space where a big data
provider<00:02:25.500><c> we're</c><00:02:25.920><c> trying</c><00:02:26.220><c> to</c><00:02:26.340><c> get</c><00:02:26.640><c> a</c><00:02:26.940><c> lot</c><00:02:27.060><c> of</c>

00:02:27.170 --> 00:02:27.180 align:start position:0%
provider we're trying to get a lot of
 

00:02:27.180 --> 00:02:29.930 align:start position:0%
provider we're trying to get a lot of
data<00:02:27.660><c> and</c><00:02:28.260><c> it</c><00:02:28.500><c> was</c><00:02:28.620><c> difficult</c><00:02:29.040><c> for</c><00:02:29.400><c> us</c><00:02:29.459><c> to</c><00:02:29.700><c> find</c>

00:02:29.930 --> 00:02:29.940 align:start position:0%
data and it was difficult for us to find
 

00:02:29.940 --> 00:02:30.830 align:start position:0%
data and it was difficult for us to find
those

00:02:30.830 --> 00:02:30.840 align:start position:0%
those
 

00:02:30.840 --> 00:02:33.830 align:start position:0%
those
so<00:02:31.260><c> we</c><00:02:31.379><c> decided</c><00:02:31.860><c> to</c><00:02:32.280><c> collaborate</c><00:02:33.180><c> with</c><00:02:33.660><c> the</c>

00:02:33.830 --> 00:02:33.840 align:start position:0%
so we decided to collaborate with the
 

00:02:33.840 --> 00:02:37.430 align:start position:0%
so we decided to collaborate with the
graph<00:02:34.140><c> to</c><00:02:34.860><c> work</c><00:02:35.099><c> on</c><00:02:35.660><c> standardizing</c><00:02:36.660><c> subgraphs</c>

00:02:37.430 --> 00:02:37.440 align:start position:0%
graph to work on standardizing subgraphs
 

00:02:37.440 --> 00:02:39.530 align:start position:0%
graph to work on standardizing subgraphs
so<00:02:37.739><c> that</c><00:02:37.920><c> we</c><00:02:38.160><c> solve</c><00:02:38.520><c> this</c><00:02:38.640><c> problem</c><00:02:38.940><c> for</c>

00:02:39.530 --> 00:02:39.540 align:start position:0%
so that we solve this problem for
 

00:02:39.540 --> 00:02:41.110 align:start position:0%
so that we solve this problem for
everyone<00:02:39.720><c> in</c><00:02:40.200><c> the</c><00:02:40.319><c> space</c>

00:02:41.110 --> 00:02:41.120 align:start position:0%
everyone in the space
 

00:02:41.120 --> 00:02:43.729 align:start position:0%
everyone in the space
specifically<00:02:42.120><c> the</c><00:02:42.480><c> way</c><00:02:42.599><c> that</c><00:02:42.959><c> we</c><00:02:43.379><c> we</c>

00:02:43.729 --> 00:02:43.739 align:start position:0%
specifically the way that we we
 

00:02:43.739 --> 00:02:45.949 align:start position:0%
specifically the way that we we
standardize<00:02:44.340><c> these</c><00:02:44.879><c> subgraphs</c><00:02:45.420><c> is</c><00:02:45.660><c> that</c><00:02:45.840><c> we</c>

00:02:45.949 --> 00:02:45.959 align:start position:0%
standardize these subgraphs is that we
 

00:02:45.959 --> 00:02:48.770 align:start position:0%
standardize these subgraphs is that we
would<00:02:46.140><c> look</c><00:02:46.319><c> at</c><00:02:46.860><c> all</c><00:02:47.160><c> of</c><00:02:47.340><c> the</c><00:02:47.819><c> protocols</c><00:02:48.360><c> in</c><00:02:48.660><c> a</c>

00:02:48.770 --> 00:02:48.780 align:start position:0%
would look at all of the protocols in a
 

00:02:48.780 --> 00:02:51.229 align:start position:0%
would look at all of the protocols in a
specific<00:02:49.080><c> category</c><00:02:49.739><c> say</c><00:02:50.220><c> lending</c><00:02:50.640><c> protocols</c>

00:02:51.229 --> 00:02:51.239 align:start position:0%
specific category say lending protocols
 

00:02:51.239 --> 00:02:53.449 align:start position:0%
specific category say lending protocols
and<00:02:51.599><c> we</c><00:02:51.720><c> pick</c><00:02:51.959><c> out</c><00:02:52.140><c> all</c><00:02:52.440><c> of</c><00:02:52.560><c> the</c><00:02:52.800><c> commonalities</c>

00:02:53.449 --> 00:02:53.459 align:start position:0%
and we pick out all of the commonalities
 

00:02:53.459 --> 00:02:55.910 align:start position:0%
and we pick out all of the commonalities
and<00:02:53.879><c> differences</c><00:02:54.360><c> among</c><00:02:55.080><c> these</c><00:02:55.379><c> protocols</c>

00:02:55.910 --> 00:02:55.920 align:start position:0%
and differences among these protocols
 

00:02:55.920 --> 00:02:58.369 align:start position:0%
and differences among these protocols
and<00:02:56.519><c> see</c><00:02:56.700><c> and</c><00:02:57.120><c> come</c><00:02:57.300><c> up</c><00:02:57.420><c> with</c><00:02:57.780><c> the</c><00:02:57.959><c> unified</c>

00:02:58.369 --> 00:02:58.379 align:start position:0%
and see and come up with the unified
 

00:02:58.379 --> 00:03:01.430 align:start position:0%
and see and come up with the unified
data<00:02:59.040><c> model</c><00:02:59.220><c> that</c><00:02:59.879><c> would</c><00:03:00.060><c> apply</c><00:03:00.660><c> to</c><00:03:01.080><c> all</c><00:03:01.319><c> of</c>

00:03:01.430 --> 00:03:01.440 align:start position:0%
data model that would apply to all of
 

00:03:01.440 --> 00:03:03.830 align:start position:0%
data model that would apply to all of
these<00:03:01.739><c> and</c><00:03:02.220><c> then</c><00:03:02.340><c> we</c><00:03:02.580><c> transformed</c><00:03:03.180><c> that</c><00:03:03.360><c> into</c>

00:03:03.830 --> 00:03:03.840 align:start position:0%
these and then we transformed that into
 

00:03:03.840 --> 00:03:07.130 align:start position:0%
these and then we transformed that into
a<00:03:04.200><c> common</c><00:03:04.519><c> subgraph</c><00:03:05.519><c> schema</c><00:03:06.120><c> in</c><00:03:06.660><c> which</c><00:03:06.780><c> we</c>

00:03:07.130 --> 00:03:07.140 align:start position:0%
a common subgraph schema in which we
 

00:03:07.140 --> 00:03:10.070 align:start position:0%
a common subgraph schema in which we
built<00:03:07.620><c> all</c><00:03:07.980><c> of</c><00:03:08.099><c> our</c><00:03:08.340><c> subgraphs</c><00:03:09.000><c> again</c><00:03:09.239><c> so</c><00:03:09.900><c> for</c>

00:03:10.070 --> 00:03:10.080 align:start position:0%
built all of our subgraphs again so for
 

00:03:10.080 --> 00:03:11.690 align:start position:0%
built all of our subgraphs again so for
each<00:03:10.319><c> of</c><00:03:10.440><c> the</c><00:03:10.620><c> lending</c><00:03:10.980><c> protocols</c><00:03:11.519><c> we</c>

00:03:11.690 --> 00:03:11.700 align:start position:0%
each of the lending protocols we
 

00:03:11.700 --> 00:03:13.790 align:start position:0%
each of the lending protocols we
integrate<00:03:12.120><c> we</c><00:03:12.659><c> use</c><00:03:12.840><c> that</c><00:03:13.200><c> standardized</c>

00:03:13.790 --> 00:03:13.800 align:start position:0%
integrate we use that standardized
 

00:03:13.800 --> 00:03:16.430 align:start position:0%
integrate we use that standardized
schema<00:03:14.280><c> so</c><00:03:14.819><c> that</c><00:03:15.060><c> you</c><00:03:15.720><c> can</c><00:03:15.840><c> use</c><00:03:16.019><c> the</c><00:03:16.319><c> same</c>

00:03:16.430 --> 00:03:16.440 align:start position:0%
schema so that you can use the same
 

00:03:16.440 --> 00:03:18.710 align:start position:0%
schema so that you can use the same
query<00:03:16.800><c> you</c><00:03:17.159><c> can</c><00:03:17.280><c> use</c><00:03:17.459><c> the</c><00:03:17.760><c> same</c><00:03:17.879><c> data</c><00:03:18.300><c> adapter</c>

00:03:18.710 --> 00:03:18.720 align:start position:0%
query you can use the same data adapter
 

00:03:18.720 --> 00:03:22.190 align:start position:0%
query you can use the same data adapter
to<00:03:19.379><c> fetch</c><00:03:19.920><c> all</c><00:03:20.099><c> of</c><00:03:20.220><c> that</c><00:03:20.459><c> data</c><00:03:20.819><c> and</c><00:03:21.420><c> now</c>

00:03:22.190 --> 00:03:22.200 align:start position:0%
to fetch all of that data and now
 

00:03:22.200 --> 00:03:24.290 align:start position:0%
to fetch all of that data and now
instead<00:03:22.980><c> of</c><00:03:23.099><c> going</c><00:03:23.280><c> to</c><00:03:23.580><c> all</c><00:03:23.879><c> of</c><00:03:24.060><c> these</c>

00:03:24.290 --> 00:03:24.300 align:start position:0%
instead of going to all of these
 

00:03:24.300 --> 00:03:26.089 align:start position:0%
instead of going to all of these
different<00:03:24.480><c> data</c><00:03:25.019><c> sources</c><00:03:25.260><c> to</c><00:03:25.500><c> fetch</c><00:03:25.860><c> that</c>

00:03:26.089 --> 00:03:26.099 align:start position:0%
different data sources to fetch that
 

00:03:26.099 --> 00:03:29.089 align:start position:0%
different data sources to fetch that
that<00:03:26.459><c> data</c><00:03:26.819><c> you</c><00:03:27.360><c> just</c><00:03:27.540><c> need</c><00:03:27.720><c> to</c><00:03:27.900><c> hit</c><00:03:28.560><c> one</c>

00:03:29.089 --> 00:03:29.099 align:start position:0%
that data you just need to hit one
 

00:03:29.099 --> 00:03:31.910 align:start position:0%
that data you just need to hit one
single<00:03:29.879><c> decentralized</c><00:03:30.659><c> data</c><00:03:31.319><c> source</c><00:03:31.560><c> that's</c>

00:03:31.910 --> 00:03:31.920 align:start position:0%
single decentralized data source that's
 

00:03:31.920 --> 00:03:33.949 align:start position:0%
single decentralized data source that's
the<00:03:32.159><c> graph</c><00:03:32.400><c> and</c><00:03:32.760><c> you'll</c><00:03:32.940><c> be</c><00:03:33.060><c> able</c><00:03:33.239><c> to</c><00:03:33.360><c> find</c><00:03:33.659><c> all</c>

00:03:33.949 --> 00:03:33.959 align:start position:0%
the graph and you'll be able to find all
 

00:03:33.959 --> 00:03:35.750 align:start position:0%
the graph and you'll be able to find all
of<00:03:34.080><c> the</c><00:03:34.260><c> data</c><00:03:34.500><c> you</c><00:03:34.680><c> need</c><00:03:34.860><c> including</c><00:03:35.459><c> the</c>

00:03:35.750 --> 00:03:35.760 align:start position:0%
of the data you need including the
 

00:03:35.760 --> 00:03:38.509 align:start position:0%
of the data you need including the
historical<00:03:36.180><c> ones</c><00:03:36.540><c> so</c><00:03:37.140><c> uh</c><00:03:37.379><c> here's</c><00:03:37.800><c> an</c><00:03:37.980><c> example</c>

00:03:38.509 --> 00:03:38.519 align:start position:0%
historical ones so uh here's an example
 

00:03:38.519 --> 00:03:40.910 align:start position:0%
historical ones so uh here's an example
uh<00:03:39.360><c> product</c><00:03:39.659><c> or</c><00:03:40.080><c> here's</c><00:03:40.379><c> actually</c><00:03:40.560><c> a</c><00:03:40.799><c> product</c>

00:03:40.910 --> 00:03:40.920 align:start position:0%
uh product or here's actually a product
 

00:03:40.920 --> 00:03:43.430 align:start position:0%
uh product or here's actually a product
that<00:03:41.220><c> mazari</c><00:03:41.819><c> has</c><00:03:41.940><c> built</c><00:03:42.299><c> on</c><00:03:42.659><c> top</c><00:03:42.780><c> of</c><00:03:42.959><c> all</c><00:03:43.260><c> of</c>

00:03:43.430 --> 00:03:43.440 align:start position:0%
that mazari has built on top of all of
 

00:03:43.440 --> 00:03:45.770 align:start position:0%
that mazari has built on top of all of
the<00:03:43.879><c> standardized</c><00:03:44.879><c> subgraphs</c><00:03:45.420><c> that</c><00:03:45.540><c> we</c><00:03:45.659><c> have</c>

00:03:45.770 --> 00:03:45.780 align:start position:0%
the standardized subgraphs that we have
 

00:03:45.780 --> 00:03:48.830 align:start position:0%
the standardized subgraphs that we have
built<00:03:46.140><c> as</c><00:03:47.040><c> you</c><00:03:47.159><c> can</c><00:03:47.280><c> see</c><00:03:47.459><c> here</c><00:03:47.760><c> we're</c><00:03:48.480><c> showing</c>

00:03:48.830 --> 00:03:48.840 align:start position:0%
built as you can see here we're showing
 

00:03:48.840 --> 00:03:50.990 align:start position:0%
built as you can see here we're showing
there's<00:03:49.560><c> a</c><00:03:49.799><c> lot</c><00:03:49.920><c> more</c><00:03:50.099><c> metrics</c><00:03:50.700><c> that</c><00:03:50.879><c> we're</c>

00:03:50.990 --> 00:03:51.000 align:start position:0%
there's a lot more metrics that we're
 

00:03:51.000 --> 00:03:52.910 align:start position:0%
there's a lot more metrics that we're
showing<00:03:51.420><c> uh</c><00:03:52.019><c> that</c><00:03:52.319><c> we</c><00:03:52.440><c> are</c><00:03:52.560><c> we</c><00:03:52.739><c> have</c>

00:03:52.910 --> 00:03:52.920 align:start position:0%
showing uh that we are we have
 

00:03:52.920 --> 00:03:55.190 align:start position:0%
showing uh that we are we have
integrated<00:03:53.340><c> it's</c><00:03:54.060><c> not</c><00:03:54.239><c> in</c><00:03:54.480><c> this</c><00:03:54.659><c> in</c><00:03:55.080><c> this</c>

00:03:55.190 --> 00:03:55.200 align:start position:0%
integrated it's not in this in this
 

00:03:55.200 --> 00:03:57.410 align:start position:0%
integrated it's not in this in this
slide<00:03:55.500><c> but</c><00:03:55.739><c> you</c><00:03:56.040><c> can</c>

00:03:57.410 --> 00:03:57.420 align:start position:0%
slide but you can
 

00:03:57.420 --> 00:04:00.589 align:start position:0%
slide but you can
check<00:03:57.900><c> it</c><00:03:58.140><c> out</c><00:03:58.260><c> using</c><00:03:58.920><c> the</c><00:03:59.040><c> URL</c><00:03:59.400><c> there</c><00:03:59.700><c> so</c><00:04:00.299><c> to</c>

00:04:00.589 --> 00:04:00.599 align:start position:0%
check it out using the URL there so to
 

00:04:00.599 --> 00:04:03.250 align:start position:0%
check it out using the URL there so to
give<00:04:00.780><c> you</c><00:04:00.959><c> a</c><00:04:01.260><c> sense</c><00:04:01.440><c> of</c><00:04:01.980><c> where</c><00:04:02.340><c> we</c><00:04:02.519><c> are</c><00:04:02.700><c> today</c>

00:04:03.250 --> 00:04:03.260 align:start position:0%
give you a sense of where we are today
 

00:04:03.260 --> 00:04:06.110 align:start position:0%
give you a sense of where we are today
on<00:04:04.260><c> on</c><00:04:04.500><c> the</c><00:04:04.739><c> subgraph</c><00:04:05.099><c> standardization</c><00:04:05.760><c> work</c>

00:04:06.110 --> 00:04:06.120 align:start position:0%
on on the subgraph standardization work
 

00:04:06.120 --> 00:04:09.050 align:start position:0%
on on the subgraph standardization work
we<00:04:06.780><c> have</c><00:04:06.959><c> index</c><00:04:07.620><c> data</c><00:04:08.040><c> from</c><00:04:08.400><c> 60</c><00:04:08.700><c> different</c>

00:04:09.050 --> 00:04:09.060 align:start position:0%
we have index data from 60 different
 

00:04:09.060 --> 00:04:11.809 align:start position:0%
we have index data from 60 different
protocols<00:04:09.840><c> across</c><00:04:10.680><c> 20</c><00:04:10.920><c> different</c><00:04:11.280><c> networks</c>

00:04:11.809 --> 00:04:11.819 align:start position:0%
protocols across 20 different networks
 

00:04:11.819 --> 00:04:15.949 align:start position:0%
protocols across 20 different networks
surfacing<00:04:12.780><c> over</c><00:04:13.080><c> 500</c><00:04:13.980><c> unique</c><00:04:14.700><c> metrics</c><00:04:15.239><c> across</c>

00:04:15.949 --> 00:04:15.959 align:start position:0%
surfacing over 500 unique metrics across
 

00:04:15.959 --> 00:04:18.289 align:start position:0%
surfacing over 500 unique metrics across
all<00:04:16.199><c> of</c><00:04:16.320><c> the</c><00:04:16.500><c> different</c><00:04:16.680><c> protocol</c><00:04:17.100><c> types</c><00:04:17.639><c> and</c>

00:04:18.289 --> 00:04:18.299 align:start position:0%
all of the different protocol types and
 

00:04:18.299 --> 00:04:19.370 align:start position:0%
all of the different protocol types and
we<00:04:18.540><c> have</c>

00:04:19.370 --> 00:04:19.380 align:start position:0%
we have
 

00:04:19.380 --> 00:04:22.670 align:start position:0%
we have
indexed<00:04:20.280><c> over</c><00:04:20.699><c> a</c><00:04:21.000><c> billion</c><00:04:21.359><c> data</c><00:04:21.840><c> points</c><00:04:22.199><c> that</c>

00:04:22.670 --> 00:04:22.680 align:start position:0%
indexed over a billion data points that
 

00:04:22.680 --> 00:04:25.370 align:start position:0%
indexed over a billion data points that
you<00:04:22.860><c> can</c><00:04:22.979><c> use</c><00:04:23.220><c> in</c><00:04:23.639><c> your</c><00:04:23.820><c> Dev</c><00:04:24.060><c> directly</c><00:04:24.720><c> so</c><00:04:25.199><c> that</c>

00:04:25.370 --> 00:04:25.380 align:start position:0%
you can use in your Dev directly so that
 

00:04:25.380 --> 00:04:27.350 align:start position:0%
you can use in your Dev directly so that
you<00:04:25.560><c> don't</c><00:04:25.680><c> have</c><00:04:25.800><c> to</c><00:04:25.979><c> do</c><00:04:26.160><c> that</c><00:04:26.340><c> work</c>

00:04:27.350 --> 00:04:27.360 align:start position:0%
you don't have to do that work
 

00:04:27.360 --> 00:04:30.770 align:start position:0%
you don't have to do that work
and<00:04:28.139><c> the</c><00:04:28.500><c> way</c><00:04:28.620><c> that</c><00:04:28.979><c> we</c><00:04:29.220><c> are</c><00:04:29.400><c> seeing</c><00:04:30.240><c> kind</c><00:04:30.660><c> of</c>

00:04:30.770 --> 00:04:30.780 align:start position:0%
and the way that we are seeing kind of
 

00:04:30.780 --> 00:04:33.350 align:start position:0%
and the way that we are seeing kind of
how<00:04:30.960><c> the</c><00:04:31.139><c> future</c><00:04:31.320><c> will</c><00:04:31.680><c> evolve</c><00:04:32.160><c> is</c><00:04:32.400><c> that</c><00:04:32.699><c> today</c>

00:04:33.350 --> 00:04:33.360 align:start position:0%
how the future will evolve is that today
 

00:04:33.360 --> 00:04:36.650 align:start position:0%
how the future will evolve is that today
you're<00:04:33.900><c> spending</c><00:04:34.500><c> a</c><00:04:35.160><c> lot</c><00:04:35.280><c> of</c><00:04:35.400><c> effort</c><00:04:35.880><c> on</c><00:04:36.479><c> kind</c>

00:04:36.650 --> 00:04:36.660 align:start position:0%
you're spending a lot of effort on kind
 

00:04:36.660 --> 00:04:38.390 align:start position:0%
you're spending a lot of effort on kind
of<00:04:36.780><c> the</c><00:04:37.020><c> data</c><00:04:37.320><c> Plumbing</c><00:04:37.740><c> on</c><00:04:37.979><c> the</c><00:04:38.100><c> data</c>

00:04:38.390 --> 00:04:38.400 align:start position:0%
of the data Plumbing on the data
 

00:04:38.400 --> 00:04:41.629 align:start position:0%
of the data Plumbing on the data
aggregation<00:04:38.880><c> part</c><00:04:39.240><c> and</c><00:04:40.020><c> very</c><00:04:40.380><c> little</c><00:04:40.560><c> uh</c><00:04:41.400><c> on</c>

00:04:41.629 --> 00:04:41.639 align:start position:0%
aggregation part and very little uh on
 

00:04:41.639 --> 00:04:45.110 align:start position:0%
aggregation part and very little uh on
the<00:04:41.820><c> application</c><00:04:42.660><c> logic</c><00:04:43.259><c> but</c><00:04:44.220><c> with</c><00:04:44.759><c> the</c>

00:04:45.110 --> 00:04:45.120 align:start position:0%
the application logic but with the
 

00:04:45.120 --> 00:04:47.629 align:start position:0%
the application logic but with the
subgraph<00:04:45.479><c> that</c><00:04:45.840><c> we</c><00:04:46.020><c> have</c><00:04:46.139><c> built</c><00:04:46.580><c> you</c><00:04:47.580><c> know</c>

00:04:47.629 --> 00:04:47.639 align:start position:0%
subgraph that we have built you know
 

00:04:47.639 --> 00:04:49.249 align:start position:0%
subgraph that we have built you know
it's<00:04:47.820><c> already</c><00:04:48.000><c> done</c><00:04:48.300><c> for</c><00:04:48.540><c> you</c><00:04:48.660><c> you</c><00:04:48.900><c> can</c><00:04:49.080><c> just</c>

00:04:49.249 --> 00:04:49.259 align:start position:0%
it's already done for you you can just
 

00:04:49.259 --> 00:04:52.909 align:start position:0%
it's already done for you you can just
use<00:04:49.500><c> that</c><00:04:49.740><c> so</c><00:04:50.699><c> you</c><00:04:50.940><c> can</c><00:04:51.120><c> focus</c><00:04:51.780><c> more</c><00:04:52.259><c> on</c><00:04:52.680><c> your</c>

00:04:52.909 --> 00:04:52.919 align:start position:0%
use that so you can focus more on your
 

00:04:52.919 --> 00:04:55.310 align:start position:0%
use that so you can focus more on your
application<00:04:53.400><c> logic</c><00:04:53.940><c> as</c><00:04:54.240><c> adaptive</c><00:04:54.840><c> developer</c>

00:04:55.310 --> 00:04:55.320 align:start position:0%
application logic as adaptive developer
 

00:04:55.320 --> 00:04:58.730 align:start position:0%
application logic as adaptive developer
yeah<00:04:56.280><c> so</c><00:04:56.520><c> all</c><00:04:56.759><c> of</c><00:04:56.880><c> the</c><00:04:57.060><c> work</c><00:04:57.180><c> we</c><00:04:57.479><c> do</c><00:04:57.660><c> is</c><00:04:58.080><c> open</c>

00:04:58.730 --> 00:04:58.740 align:start position:0%
yeah so all of the work we do is open
 

00:04:58.740 --> 00:05:01.010 align:start position:0%
yeah so all of the work we do is open
source<00:04:59.160><c> it's</c><00:04:59.400><c> public</c><00:04:59.699><c> here's</c><00:05:00.600><c> the</c><00:05:00.720><c> GitHub</c>

00:05:01.010 --> 00:05:01.020 align:start position:0%
source it's public here's the GitHub
 

00:05:01.020 --> 00:05:02.990 align:start position:0%
source it's public here's the GitHub
repo<00:05:01.500><c> for</c><00:05:01.800><c> all</c><00:05:01.979><c> of</c><00:05:02.160><c> our</c><00:05:02.340><c> standardized</c>

00:05:02.990 --> 00:05:03.000 align:start position:0%
repo for all of our standardized
 

00:05:03.000 --> 00:05:05.930 align:start position:0%
repo for all of our standardized
subgraphs<00:05:03.960><c> if</c><00:05:04.440><c> you're</c><00:05:04.620><c> a</c><00:05:04.860><c> dab</c><00:05:05.220><c> Builder</c><00:05:05.639><c> or</c>

00:05:05.930 --> 00:05:05.940 align:start position:0%
subgraphs if you're a dab Builder or
 

00:05:05.940 --> 00:05:08.930 align:start position:0%
subgraphs if you're a dab Builder or
data<00:05:06.360><c> scientist</c><00:05:06.800><c> data</c><00:05:07.800><c> analyst</c><00:05:08.160><c> we</c><00:05:08.520><c> if</c><00:05:08.820><c> you</c>

00:05:08.930 --> 00:05:08.940 align:start position:0%
data scientist data analyst we if you
 

00:05:08.940 --> 00:05:11.050 align:start position:0%
data scientist data analyst we if you
work<00:05:09.120><c> with</c><00:05:09.300><c> a</c><00:05:09.479><c> protocol</c><00:05:09.840><c> team</c>

00:05:11.050 --> 00:05:11.060 align:start position:0%
work with a protocol team
 

00:05:11.060 --> 00:05:14.570 align:start position:0%
work with a protocol team
we<00:05:12.060><c> are</c><00:05:12.600><c> we're</c><00:05:13.259><c> more</c><00:05:13.500><c> than</c><00:05:13.620><c> happy</c><00:05:13.919><c> to</c>

00:05:14.570 --> 00:05:14.580 align:start position:0%
we are we're more than happy to
 

00:05:14.580 --> 00:05:17.090 align:start position:0%
we are we're more than happy to
integrate<00:05:15.360><c> your</c><00:05:15.600><c> protocol</c><00:05:15.960><c> into</c><00:05:16.800><c> our</c>

00:05:17.090 --> 00:05:17.100 align:start position:0%
integrate your protocol into our
 

00:05:17.100 --> 00:05:19.969 align:start position:0%
integrate your protocol into our
standard<00:05:17.580><c> so</c><00:05:18.419><c> feel</c><00:05:18.960><c> free</c><00:05:19.139><c> to</c><00:05:19.259><c> reach</c><00:05:19.560><c> out</c><00:05:19.680><c> to</c><00:05:19.800><c> me</c>

00:05:19.969 --> 00:05:19.979 align:start position:0%
standard so feel free to reach out to me
 

00:05:19.979 --> 00:05:22.670 align:start position:0%
standard so feel free to reach out to me
after<00:05:20.280><c> the</c><00:05:20.580><c> talk</c><00:05:20.759><c> and</c><00:05:21.720><c> if</c><00:05:22.020><c> you're</c><00:05:22.139><c> a</c><00:05:22.320><c> subgraph</c>

00:05:22.670 --> 00:05:22.680 align:start position:0%
after the talk and if you're a subgraph
 

00:05:22.680 --> 00:05:25.070 align:start position:0%
after the talk and if you're a subgraph
developer<00:05:23.400><c> or</c><00:05:23.699><c> a</c><00:05:23.880><c> Ross</c><00:05:24.300><c> developer</c><00:05:24.720><c> that's</c>

00:05:25.070 --> 00:05:25.080 align:start position:0%
developer or a Ross developer that's
 

00:05:25.080 --> 00:05:28.370 align:start position:0%
developer or a Ross developer that's
that<00:05:25.800><c> interested</c><00:05:26.280><c> in</c><00:05:26.400><c> in</c><00:05:26.699><c> this</c><00:05:26.880><c> data</c><00:05:27.180><c> stage</c><00:05:27.660><c> uh</c>

00:05:28.370 --> 00:05:28.380 align:start position:0%
that interested in in this data stage uh
 

00:05:28.380 --> 00:05:30.230 align:start position:0%
that interested in in this data stage uh
feel<00:05:28.620><c> free</c><00:05:28.800><c> to</c><00:05:28.979><c> scan</c><00:05:29.340><c> that</c><00:05:29.520><c> QR</c><00:05:29.820><c> code</c><00:05:30.000><c> there</c>

00:05:30.230 --> 00:05:30.240 align:start position:0%
feel free to scan that QR code there
 

00:05:30.240 --> 00:05:32.330 align:start position:0%
feel free to scan that QR code there
that<00:05:30.660><c> will</c><00:05:30.840><c> take</c><00:05:31.020><c> you</c><00:05:31.199><c> to</c><00:05:31.380><c> our</c><00:05:31.560><c> careers</c><00:05:31.979><c> page</c>

00:05:32.330 --> 00:05:32.340 align:start position:0%
that will take you to our careers page
 

00:05:32.340 --> 00:05:36.290 align:start position:0%
that will take you to our careers page
and<00:05:33.120><c> we</c><00:05:33.479><c> are</c><00:05:33.600><c> always</c><00:05:33.780><c> hiring</c><00:05:34.259><c> Yep</c><00:05:35.039><c> this</c><00:05:35.520><c> is</c><00:05:35.639><c> my</c>

00:05:36.290 --> 00:05:36.300 align:start position:0%
and we are always hiring Yep this is my
 

00:05:36.300 --> 00:05:38.990 align:start position:0%
and we are always hiring Yep this is my
talk<00:05:36.600><c> and</c><00:05:37.259><c> thank</c><00:05:37.680><c> you</c><00:05:37.800><c> for</c><00:05:37.919><c> coming</c><00:05:38.039><c> he's</c>

00:05:38.990 --> 00:05:39.000 align:start position:0%
talk and thank you for coming he's
 

00:05:39.000 --> 00:05:40.990 align:start position:0%
talk and thank you for coming he's
aggregated<00:05:39.419><c> subgraph</c><00:05:40.020><c> is</c><00:05:40.199><c> more</c>

00:05:40.990 --> 00:05:41.000 align:start position:0%
aggregated subgraph is more
 

00:05:41.000 --> 00:05:43.610 align:start position:0%
aggregated subgraph is more
is<00:05:42.000><c> there</c><00:05:42.180><c> assumptions</c><00:05:42.720><c> of</c><00:05:42.900><c> trust</c><00:05:43.199><c> when</c><00:05:43.440><c> you</c>

00:05:43.610 --> 00:05:43.620 align:start position:0%
is there assumptions of trust when you
 

00:05:43.620 --> 00:05:45.529 align:start position:0%
is there assumptions of trust when you
use<00:05:43.919><c> the</c><00:05:44.160><c> aggregate</c><00:05:44.699><c> it's</c><00:05:44.880><c> a</c><00:05:45.000><c> graph</c><00:05:45.180><c> compared</c>

00:05:45.529 --> 00:05:45.539 align:start position:0%
use the aggregate it's a graph compared
 

00:05:45.539 --> 00:05:47.450 align:start position:0%
use the aggregate it's a graph compared
to<00:05:45.660><c> this</c><00:05:45.840><c> I</c><00:05:46.139><c> have</c><00:05:46.320><c> a</c><00:05:46.380><c> subgrapher</c><00:05:46.919><c> compound</c><00:05:47.280><c> sub</c>

00:05:47.450 --> 00:05:47.460 align:start position:0%
to this I have a subgrapher compound sub
 

00:05:47.460 --> 00:05:50.930 align:start position:0%
to this I have a subgrapher compound sub
graph<00:05:47.820><c> yep</c><00:05:48.419><c> so</c><00:05:49.080><c> uh</c><00:05:49.740><c> all</c><00:05:49.979><c> of</c><00:05:50.160><c> our</c><00:05:50.340><c> subgraph</c>

00:05:50.930 --> 00:05:50.940 align:start position:0%
graph yep so uh all of our subgraph
 

00:05:50.940 --> 00:05:54.050 align:start position:0%
graph yep so uh all of our subgraph
source<00:05:51.360><c> code</c><00:05:51.479><c> is</c><00:05:52.080><c> uh</c><00:05:52.500><c> open</c><00:05:52.680><c> source</c><00:05:53.160><c> uh</c><00:05:53.699><c> There</c>

00:05:54.050 --> 00:05:54.060 align:start position:0%
source code is uh open source uh There
 

00:05:54.060 --> 00:05:55.909 align:start position:0%
source code is uh open source uh There
Was<00:05:54.180><c> You</c><00:05:54.419><c> know</c><00:05:54.479><c> the</c><00:05:54.660><c> GitHub</c><00:05:55.080><c> repo</c><00:05:55.440><c> we</c><00:05:55.560><c> showed</c>

00:05:55.909 --> 00:05:55.919 align:start position:0%
Was You know the GitHub repo we showed
 

00:05:55.919 --> 00:05:58.790 align:start position:0%
Was You know the GitHub repo we showed
so<00:05:56.400><c> we</c><00:05:56.699><c> we</c><00:05:57.240><c> uh</c><00:05:57.600><c> describe</c><00:05:58.139><c> all</c><00:05:58.440><c> of</c><00:05:58.620><c> the</c>

00:05:58.790 --> 00:05:58.800 align:start position:0%
so we we uh describe all of the
 

00:05:58.800 --> 00:06:01.490 align:start position:0%
so we we uh describe all of the
methodology<00:05:59.280><c> of</c><00:06:00.240><c> our</c><00:06:00.479><c> kind</c><00:06:00.900><c> of</c><00:06:01.020><c> you</c><00:06:01.259><c> know</c><00:06:01.320><c> the</c>

00:06:01.490 --> 00:06:01.500 align:start position:0%
methodology of our kind of you know the
 

00:06:01.500 --> 00:06:04.610 align:start position:0%
methodology of our kind of you know the
computation<00:06:01.919><c> for</c><00:06:02.220><c> for</c><00:06:02.600><c> metrics</c><00:06:03.600><c> in</c><00:06:04.020><c> detail</c><00:06:04.259><c> in</c>

00:06:04.610 --> 00:06:04.620 align:start position:0%
computation for for metrics in detail in
 

00:06:04.620 --> 00:06:07.129 align:start position:0%
computation for for metrics in detail in
the<00:06:04.740><c> repo</c><00:06:05.100><c> and</c><00:06:05.699><c> of</c><00:06:06.060><c> course</c><00:06:06.180><c> you</c><00:06:06.479><c> can</c><00:06:06.539><c> go</c><00:06:06.840><c> into</c>

00:06:07.129 --> 00:06:07.139 align:start position:0%
the repo and of course you can go into
 

00:06:07.139 --> 00:06:09.529 align:start position:0%
the repo and of course you can go into
the<00:06:07.620><c> the</c><00:06:07.919><c> source</c><00:06:08.280><c> code</c><00:06:08.400><c> to</c><00:06:08.639><c> look</c><00:06:08.759><c> at</c><00:06:08.940><c> exactly</c>

00:06:09.529 --> 00:06:09.539 align:start position:0%
the the source code to look at exactly
 

00:06:09.539 --> 00:06:12.350 align:start position:0%
the the source code to look at exactly
how<00:06:10.020><c> different</c><00:06:10.380><c> numbers</c><00:06:10.740><c> are</c><00:06:11.100><c> integrated</c><00:06:11.580><c> and</c>

00:06:12.350 --> 00:06:12.360 align:start position:0%
how different numbers are integrated and
 

00:06:12.360 --> 00:06:14.749 align:start position:0%
how different numbers are integrated and
the<00:06:12.780><c> graph</c><00:06:13.020><c> is</c><00:06:13.440><c> also</c><00:06:13.800><c> working</c><00:06:14.039><c> on</c><00:06:14.340><c> uh</c>

00:06:14.749 --> 00:06:14.759 align:start position:0%
the graph is also working on uh
 

00:06:14.759 --> 00:06:16.969 align:start position:0%
the graph is also working on uh
something<00:06:15.000><c> called</c><00:06:15.300><c> verifiable</c><00:06:16.080><c> queries</c><00:06:16.560><c> that</c>

00:06:16.969 --> 00:06:16.979 align:start position:0%
something called verifiable queries that
 

00:06:16.979 --> 00:06:20.090 align:start position:0%
something called verifiable queries that
will<00:06:17.340><c> put</c><00:06:17.880><c> that</c><00:06:18.180><c> trust</c><00:06:18.539><c> into</c><00:06:19.080><c> the</c><00:06:19.440><c> data</c><00:06:19.740><c> that</c>

00:06:20.090 --> 00:06:20.100 align:start position:0%
will put that trust into the data that
 

00:06:20.100 --> 00:06:21.650 align:start position:0%
will put that trust into the data that
it<00:06:20.220><c> indexes</c>

00:06:21.650 --> 00:06:21.660 align:start position:0%
it indexes
 

00:06:21.660 --> 00:06:24.409 align:start position:0%
it indexes
what's<00:06:22.259><c> the</c><00:06:22.620><c> approximate</c><00:06:23.280><c> delay</c><00:06:23.699><c> before</c><00:06:24.180><c> the</c>

00:06:24.409 --> 00:06:24.419 align:start position:0%
what's the approximate delay before the
 

00:06:24.419 --> 00:06:25.969 align:start position:0%
what's the approximate delay before the
data<00:06:24.720><c> is</c><00:06:24.780><c> available</c><00:06:24.960><c> I</c><00:06:25.380><c> mean</c><00:06:25.500><c> if</c><00:06:25.620><c> we</c><00:06:25.740><c> want</c><00:06:25.919><c> to</c>

00:06:25.969 --> 00:06:25.979 align:start position:0%
data is available I mean if we want to
 

00:06:25.979 --> 00:06:27.469 align:start position:0%
data is available I mean if we want to
do<00:06:26.100><c> something</c><00:06:26.160><c> real</c><00:06:26.580><c> time</c><00:06:26.699><c> it's</c><00:06:27.000><c> in</c><00:06:27.120><c> real</c><00:06:27.300><c> time</c>

00:06:27.469 --> 00:06:27.479 align:start position:0%
do something real time it's in real time
 

00:06:27.479 --> 00:06:30.170 align:start position:0%
do something real time it's in real time
yeah<00:06:27.840><c> so</c><00:06:28.080><c> it's</c><00:06:28.319><c> block</c><00:06:28.560><c> by</c><00:06:28.800><c> block</c><00:06:28.979><c> okay</c><00:06:29.280><c> but</c><00:06:29.580><c> on</c>

00:06:30.170 --> 00:06:30.180 align:start position:0%
yeah so it's block by block okay but on
 

00:06:30.180 --> 00:06:32.210 align:start position:0%
yeah so it's block by block okay but on
the<00:06:30.360><c> order</c><00:06:30.479><c> there's</c><00:06:30.660><c> got</c><00:06:30.840><c> to</c><00:06:30.960><c> be</c><00:06:31.020><c> some</c><00:06:31.139><c> like</c><00:06:32.039><c> 15</c>

00:06:32.210 --> 00:06:32.220 align:start position:0%
the order there's got to be some like 15
 

00:06:32.220 --> 00:06:33.950 align:start position:0%
the order there's got to be some like 15
seconds<00:06:32.639><c> to</c><00:06:33.060><c> like</c><00:06:33.360><c> two</c><00:06:33.539><c> minutes</c><00:06:33.660><c> okay</c>

00:06:33.950 --> 00:06:33.960 align:start position:0%
seconds to like two minutes okay
 

00:06:33.960 --> 00:06:37.160 align:start position:0%
seconds to like two minutes okay
depending<00:06:34.319><c> on</c><00:06:34.440><c> the</c><00:06:34.620><c> Chain</c><00:06:34.740><c> perfect</c>