►
Description
In his talk, Ryan Selkis, the founder and CEO of Messari, discusses a shared vision for Open Data and announced Messari as the new, first-ever core subgraph developer, after receiving a $12.5 million grant. Messari is a data and research platform with two components: Market Intelligence which comprises Tools, Analytics, and Data fees and Protocol Service Divisions, working to standardize information flows to different communities.
Read more about Messari’s role as core subgraph developer and the mission to build and standardize subgraphs:
https://messari.io/article/the-graph-foundation-awards-messari-usd12-5mm-in-first-ever-core-subgraph-developer-grant-to-build-and-standardize-subgraphs
Watch more Graph Day 2022 talks, panels, and announcements here: https://www.youtube.com/playlist?list=PLTqyKgxaGF3SWt8ipQw-Ul9HQvmxulbUu
Keep up with The Graph on social media!
0:00 Intro
0:42 About Messari
2:00 Open Crypto Data
5:00 Strong standards and broad coverage
7:13 3 Month Recap
8:35 Messari is first core subgraph developer
13:00 Q & A
Twitter: https://twitter.com/graphprotocol?s=20
Instagram: https://instagram.com/graphprotocol
LinkedIn: https://www.linkedin.com/company/thegraph
GitHub: https://github.com/graphprotocol
Website: https://thegraph.com
A
Yeah
all
right
in
the
front
row
I
like
that.
Thank
you.
Thank
you.
Thank
you.
Thank
you.
Thank
you
all
right,
so
I'm
here
today
with
an
important
announcement
for
those
of
you
that
don't
know
me,
I'm
ryan
selkis,
I'm
the
founder,
ceo
of
missouri,
and
I'm
here
today
to
officially
announce
my
candidacy
for
the
u.s.
That's
a
different
presentation.
A
No,
no,
no,
no,
I'm
having
too
much
fun
working
with
folks
like
edge
and
node
and
the
graph
foundation.
So
I
am
here
today
to
talk
about
open
data
and
an
exciting
new
partnership
that
we
have
with
the
graph
that
I'm
going
to
share
in
just
a
few
minutes,
but
first
a
little
bit
about
missouri.
For
those
of
you
that
don't
know
us
we're
data
and
research
platform
and
really
we've
got
two
components
of
the
business.
A
We've
got
market
intelligence,
which
is
basically
just
tools.
Analytics
data
feeds
that
help
investment
funds,
infrastructure
companies.
You
know
trad
fi,
come
up
the
learning
curve
with
crypto
and
actually
you
know,
learn
about
support
these
assets
and
get
comfortable
with
the
complexity
of
this
new
space
and
then
on
the
other
side.
There's
the
protocols
themselves.
A
We
call
it
our
protocol
services,
division
and
we've
worked
with
hundreds
of
these
entities
over
time
and
what
we're
really
trying
to
do
is
we're
trying
to
standardize
the
information
flows
that
are
coming
from
them
to
their
communities
and,
in
many
cases
we're
almost
serving
like
an
outsourced
investor
relations
function.
So
we've
got
market
intelligence.
We've
got
protocol
services,
some
people
have
said
if
you're
using
the
x
for
y
comparison,
it's
like
a
bloomberg
for
crypto,
but
when
we
started
we
actually
were
going
a
little
more
boring
and
uninteresting
and
trying
to
think
about.
A
A
We
had
a
common
vision
around
that
and
I
think
you
know-
we've
been
working
in
our
own
ways
on
open
data
for
the
past
four
and
a
half
years.
But
if
you
look
at
the
massari
platform,
we've
basically
done
almost
everything,
except
for
on-chain
data,
which
is
a
little
bit
ironic.
We've
been
very
patient
in
terms
of
building
in
protocol
metrics
and
really
robust
on-chain
data
capabilities
into
our
platform,
we'll
track
off
chain
events,
we'll
track
markets,
data
we'll
track.
A
You
know
all
these
other
kind
of
miscellaneous
building
blocks
that
give
people
a
composite
view
of
what's
going
on
with
these
different
assets,
but
we
haven't
really
kind
of
pierced
the
veil
and
spun
up
our
own
infrastructure.
Yet,
and
one
of
the
reasons
for
that
is:
we've
been
waiting
for
other
middleware
other
infrastructure,
like
the
graph
that
are
focused
on
just
this
on
a
full-time
basis,
to
really
become
a
little
bit
more
reliable
and
robust
without
creating
upstream
supplier
risk
for
us
and
our
users
right,
you
don't
want
to
get
rugged.
A
You're
going
to
hear
this
afternoon
really
have
10xed
or
100x
the
reliability
of
the
graph
as
a
protocol,
and
it's
something
that
we
believe
that
we
can
build
on
now
in
a
very
reliable
way
in
an
open
way.
The
last
bit
is
well
structured
right.
So
basically,
there's
been
this
tension
between
protocols
like
the
graph
that
are
working
to
make
this
information
publicly
available
and
allow
for
anyone
to
build
on
top
and
then
the
more
private
on-chain
data
platforms
like
nansen,
like
glass,
node,
coinmetrics,
amber
data.
A
These
are
great
businesses,
but
they
basically
had
to
make
a
decision
we're
incurring
all
these
costs
to
spin
up
these
nodes.
Obviously,
we're
going
to
pay
all
this
and
we're
going
to
charge
a
pretty
penny
for
it,
so
that
enterprises
can
actually
have
on-chain
insights,
but
then
there's
very
limited,
that's
left
to
the
general
public
and
there's
nothing
wrong
with
that,
but
that's
just
kind
of
how
the
industry
has
evolved
right
now.
So
we've
had
the
open
data
vision.
A
We
really
believe
in
the
the
reliability
of
the
graph
of
the
protocol.
Now,
how
do
we
get
to
the
well-structured
component
to
complete
the
trifecta
and
we
met
with
the
edge
and
node
team
and
the
graph
foundation
team
in
february
this
year
at
east
denver,
where
we
all
got
coveted
afterwards,
or
at
least
I
did
like
half
my
team-
and
I
guess
all
of
you
did
as
well
from
from
that
laughter.
But
we
were
talking
about
okay.
A
Are
there
ways
that
missouri
could
play
a
role
here
in
curating
subgraphs,
because
right
now
there's
a
quality
control
issue,
because
it
is
an
open
protocol.
Anyone
can
spin
up
a
subgraph
and
that's
great
unless
you're
trying
to
use
it,
and
we
are
a
power
user
of
these
data
sets
as
a
company.
They
need
to
meet
certain
performance
standards.
They
need
to
meet
certain
quality
standards
for
us
to
be
able
to
pull
data
and
ingest
it
into
our
platform
and
then
kind
of
spit
it
back
out
for
our
end
users.
A
So
we
talked
about
you
know,
look
we've
got
500
enterprise
customers,
the
who's
who,
on
the
fun
side
on
the
exchange
side
kind
of
throughout
the
industry.
Globally,
we
work
with
hundreds
of
protocols
already
we're
very
strongly
incentivized
to
get
this
right
and
to
build
sub-graph
infrastructure.
But
we
just
want
to
understand
like
how
we
can
better
collaborate,
and
we
could
do
this
in
a
sustainable
open
way,
instead
of
just
creating
private
subgraphs
using
the
graph
protocol.
A
The
other
thing
is,
our
work
is
going
to
be
very
visible
because
it's
going
to
be
something
that
people
can
access
through
our
analytics
tools
and
in
many
cases
that's
either
free
or
a
very
low
tier
30
a
month.
This
isn't
an
advertisement
for
I'm
sorry,
but
just
to
kind
of
show.
This
is
relatively
accessible
versus
some
of
those
other
enterprise
customers
or
enterprise
services
that
I
showed
in
the
previous
slide
and
then
finally,
we've
already
managed
communities
at
scale.
A
We've
done
this
with
our
analyst
program,
we've
worked
with
well
over
a
hundred
contract
and
volunteer
analysts
through
our
missouri
hub
that
you
know
helped
us
rate.
You
know
our
research
capabilities
and
output
and
then
ultimately
create
a
really
really
strong
alumni
network
that
ultimately
got
placed
at
some
of
the
big
protocols.
A
Funds
funds
like
coinbase
ventures
grayscale,
and
we
thought
okay.
If
we
already
have
these
incentives
to
build
for
both
sides
of
our
customer
base,
we
know
that
this
is
going
to
be
very
visible
for,
like
qa
in
terms
of
the
outputs
of
the
subgraph
and
we've
already
managed
communities
at
scale.
On
the
analyst
side
could
we
do
the
same
thing
on
the
developer
side
and
for
the
past
few
months?
A
That's
exactly
what
we've
done,
so
our
team
has
worked
relentlessly
over
the
last
three
months
to
start
to
come
up
with
a
new
schema
for
subgraphs
on
a
per
sector
basis,
so
trying
to
batch
like
for
like
when
you're
talking
about
dex
subgraphs.
If
you're
talking
about
lending
protocol
subgraphs
create
a
little
bit
of
a
more
robust
scheme
or
reliable
schema
that
other
people
are
going
to
be
able
to
build
on
in
a
predictable
way
and
you'll
be
able
to
have
consistent
quality
across
the
different
subgraphs
that
you
see
in
the
ecosystem.
A
We've
deployed,
20
subgraphs
we've
got
another
25
in
queue
and
we've
got
25
active
contracts
of
graph
developers
now.
So
this
is
something
that
we
want
to
incentivize
at
scale
and
the
mission
that
we
have
and
that
we
talked
about
after
a
couple
months
of
iterating
on
this
project
is
you
know
we
want
to
make
sub
graph
scaling
and
then
quality
control
of
the
subgraphs
themselves.
A
Essentially,
the
front
end
of
the
graph
community
turned
it
into
a
first-class
citizen
in
core
development,
and
so
the
real
reason
I'm
here
today
is
to
announce
something
that
I'm
very
excited
about.
Our
team's
been
working
on
and
it's
really
the
culmination
of
a
four-year
relationship
with
the
folks
at
edunode
and
the
broader
graph
community.
A
A
It
says
here
you
know:
200
high
quality,
subgraphs
we're
in
a
bear
market.
So
maybe
it
is
just
200,
but
we
obviously
think
that
there's
going
to
be
thousands,
tens
of
thousands
of
different
protocols
that
are
going
to
need
to
be
indexed
and
we're
need
to
need
to
create
high
quality
sub
graphs.
For
so
this
is
a
starting
point
for
us.
A
A
The
most
exciting
thing
here
is
again
it's
a
culmination
of
a
long
relationship
that
we've
had
with
multiple
members
of
the
the
graph
foundation
and
edge
and
node
team,
and
I
think
this
is
going
to
be
a
really
exciting
positive
sum:
development
for
the
rest
of
the
industry.
Anything
that
can
be
built
in
public
should
and
ultimately
will
be
built
in
public
if
the
incentives
are
well
aligned
within
crypto
and-
and
I
think
the
the
graph
community
and
all
the
different
core
developers
that
have
already
received
you
heard
this
morning.
A
A
We
are
going
to
be
incorporating
this
hopefully
into
in
in
many
of
our
communities,
whether
that's
on
the
analyst
side,
whether
that's
on
the
subgraph
developer
side
and
this
community,
but
we
ultimately
want
to
be
able
to
not
only
play
a
leading
role
in
the
subgraph
developer
ecosystem,
but
hopefully
help
people
build
credentials
even
if
they're
just
a
contributor
to
a
dow-
and
this
is,
I
think,
one
of
the
one
of
the
most
exciting
things,
especially
because
the
music
you
can
tell
that.
I
I
picked
that
music.
A
A
B
A
Across
across
yeah
florent,
where
are
you
there?
He
is
laurent
vincent
missouri
team.
Just
stand
up
real
quickly,
we're
rolling
deep
this
week,
so
they're
all
in
the
same
row
back
here
so
flag.
These
guys
down
laurent
vincent
make
sure
that
you
find
this
guy
after
the
presentation.
I'm
sure,
if
there's
other
folks
that
that
have
similar
questions
or
concerns
make
sure
you
try
to
get
these
guys
right
outside
after
the
presentation,
but
we
do
want
to
get
to
200.
So
thank
you
for
asking
that,
and
hopefully
we
can.
A
A
A
We
can
certainly
get
in
touch
easy
easily
we're
not
only
working
with
sub
graph
developers
on
a
contract
basis,
but
when
it
comes
to
the
the
groups
that
are
setting
standards
like
we're
not
going
to
pretend
that
we're
the
only
voice
in
the
room-
that's
just
dictating
from
on
high
how
these
should
be
structured.
So
there's
a
couple
of
other
kind
of
working
groups
right
now
that
we're
going
to
be
a
meaningful
contributor
to
and
help
catalyze
and
lead
for
now.
A
Are
we
going
to
work
on
substreams,
yes,
and
that's
one
of
the
things
that
we
were
very
excited
about
when
we
caught
up
in
february?
It
was
kind
of
the
tipping
point
to
be
honest
for
our
decision
to
really
go
all
in
on
on
the
graph,
and
and
again
I
can't
I
can't
say
enough:
we
we're
very
patient
as
a
company.
A
It's
killed
me
to
not
have
on-chain
data
for
years,
but
it's
also
allowed
us
to
not
go
down
any
dry
holes
and
just
waste
a
ton
of
developer
resources.
You
know
we
so
we've
been
patient
in
terms
of
waiting
and
the
infrastructure.
That's
been
built
from
some
of
the
other
core
developers
last
year,
especially
substreams
included,
were
a
big
reason
that
we've
we've
we've
made
this
hard
turn
and
have
begun
to
go
all
in
on
this.
A
A
A
The
sub
graph
development
standards?
So
I
think
it's
it's
developing
a
common
scheme.
I'm
not
going
to
be
able
to
give
you
the
technical
answer.
That's
going
to
be
for
our
team
up
here,
I'm
just
the
monkey
that
they
send
on
stage
to
say
words,
but
the
the
schema
development
that
we're
doing
and
some
of
the
documentation
on
different
types
of
assets,
I
think,
is
really
important.
So
you
look
at
something
like
v3.
A
So
one
of
the
things
that
we
want
to
do
is
make
this
very,
very
easy
for
community
subgraph
developers
to
contribute
for
us
to
maintain
and
upgrade
them
over
time
and
make
sure
there's
continuity
for
some
of
these
subgraphs
in
terms
of
maintenance.
That's
been
a
big
problem,
as
someone
will
create
and
then
not
maintain
or
not
make
a
fix,
and
one
of
the
ways
that
we
think
that
we
can
do
that
really
effectively
is
if
we
can
onboard
more
of
the
protocols
themselves
to
work
with
us.
A
A
So
the
question
was
about
composability
of
based
on
better
subgraph
standards.
What
does
that
mean
for
composability
of
different
different
applications?
I
won't
give
away
too
much
because
we
do
have
our
conference
coming
up
in
september.
Mainnet
new
york,
21st
through
23rd
of
september
and
we're
gonna
have
a
lot
of
product
announcements
that
event.
A
But
I
think
the
short
answer
is
this
is
going
to
create
just
a
tremendous
explosion
of
different
types
of
applications,
information
and
data
applications
that
I
think
are
going
to
make
it
easier
for
developers
to
make
it
obviously
easier
for
end
users
and
investors
to
navigate
these
different
segments,
and
you
know
the
one
thing
that
we
learned
and
heard
repeatedly
when
we
were
kind
of
diligencing.
Should
we
really
kind
of
go
all
in
and
is
now
the
right
time?
Is
we
love
the
graph?
We
love
the
graph.
A
We
love
the
graph
but
navigating
the
the
sub
graphs
and
making
sure
that
when
we
actually
use
it
as
our
back
end,
it's
just
it's.
We
we
can't
even
get.
We
can
barely
get
the
one
nine
much
less
like
you
know
three,
four,
five
nines
in
terms
of
reliability,
so
I
think
when
we
get
to
one
nine,
two
nines
and
then
ultimately,
you
know
this
becomes
as
reliable
as
a
centralized
information
service.