►
From YouTube: The Graph - Q2 2023 Quarterly Participant Update
Description
The Graph ecosystem is thriving and innovating at lightspeed, with achievements like Substreams, scaling on Arbitrum with L2, and much more.
The latest Graph Participant Update covers highlights from Q2 2023 of The Graph ecosystem, including key stats, announcements and milestones. Watch the recording and learn about all the building and innovating happening within The Graph community!
The Graph is the indexing and query layer of web3. Anyone can build and publish open APIs, called subgraphs, making data easily accessible.
Follow The Graph on social media
Twitter: https://twitter.com/graphprotocol
Instagram: https://instagram.com/graphprotocol
LinkedIn: https://www.linkedin.com/company/thegraph/
GitHub: https://github.com/graphprotocol
Website: https://thegraph.com
B
B
First,
we
are
making
public
data
available
and
accessible
to
all,
and
secondly,
we're
here
to
ensure
that
the
graph
network
is
the
future
of
this
decentralized
internet
that
we're
all
building,
and
we
are
very
much
laser
focused
on
execution
around
the
graph
Network
to
make
this
possible,
and
so
my
role
is
really
much
very
much
about
ensuring
the
strategy
gets
executed
on
in
an
expeditious
way,
and
that's
really
what
I'm
focused
on
full
time.
So,
with
this
change
in
my
role,
I
will
be
handing
over
the
reporting
duties
for
this
call
to
Kyle
and
Max.
B
C
C
What's
crazy
is
the
graph
has
officially
served
over
one
trillion
queries,
and
this
is
a
massive
achievement
for
the
entire
ecosystem,
from
the
foundation
to
the
court
of
teams
to
to
all
of
you
in
the
community.
All
playing
a
key
part
in
this
and,
what's
incredible,
is
the
graph
ecosystem
launched
the
hosted
service
less
than
four
years
ago
in
2019,
and
then
we
celebrated
the
Milestone
of
1
billion
queries
per
month
in
the
summer
of
2020,
and
now
the
Technology's
averaging
around
1
billion
queries
every
single
day
and
for
context
on
that
Google.
C
Four
years
after
launch
was
averaging
around
200
million
queries
per
day.
Again,
the
graph
is
averaging
around
1
billion
per
day
and
has
seen
many
weeks
consistently
every
once
in
a
while,
depending
on
the
market
and
where
things
are
going
in
activity
where
the
Technologies
queried
closer
to
one
and
a
half
to
two
billion
queries
per
day.
So
the
numbers
are
pretty
staggering
when
you
think
about
it.
I'd
say
one
caveat
here
is
that
less
than
one
percent
of
all
graph
ecosystem
query
volume
has
come
from
the
decentralized
network.
C
So
there's
still
a
lot
of
very
important
work
to
do
to
get
that
moved
over
away
from
the
hosted
service
and
we'll
talk
about
some
big
ideas
on
this
later
in
the
presentation,
and
even
when,
when
all
dapps
on
the
hosted
service
move
over
to
the
network,
it
won't
likely
be
an
equivalent
one-to-one
volume
moving
over
since
people
when
they
move
over
to
the
network
are
already
finding
innovative
ways
to
decrease
volume
once
they
start
to
pay
and
therefore
minimize
overall
costs,
which
is
to
be
expected.
We'll
talk
a
little
more
about
this
as
well.
C
Another
major
milestone
for
the
network
is
that
we
saw
the
1
000
subgraph
published,
and
the
rate
at
which
subgraphs
are
moving
over
is
is
just
speeding
up,
and
that's
probably
mostly
due
to
and
the
feedback
we're
getting.
Is
it's
mostly
due
to
depth
seeing
how
much
more
powerful
the
network
is
with
quality
of
service
metrics
that
are
consistently
surpassing
the
hosted
service
and
they
have
been
now
for
a
year
or
more?
C
Here's
a
summary
of
growth
across
Network,
subgraphs,
indexers
and
delegators,
as
well
as
number
of
queries
and
query
fees.
The
new
subgraphs
on
the
network
continue
to
rise
fast.
The
protocol
did
see
a
drop
in
indexers
queries
and
query
fees
and
it
just
set
up
some
context
up
front.
There
are
three
main
reasons
why
query
volume
and
fees
went
down
which
I'll
discuss
in
the
next
slide,
but
what's
important
here
is
that
it's
not
because
people
are
leaving
a
network,
but
let's
dive
in
to
understand
why
so
the
growth
is
never
a
straight
line.
C
It's
really
important
to
understand
why
we're
seeing
these
fluctuations,
a
40
drop
in
48
drop
in
query
fees
is
something
we
take
extremely
seriously.
We
dug
into
heavily.
The
first
thing
we
saw
is
that
overall,
web
3
user
activity
is
down
across
the
board,
which
is
understandable
and
something
many
of
us
have
seen
in
the
multiple
ups
and
downs
in
this
industry.
Still
we
we
couldn't
chalk
it
up
to
that.
C
We
really
needed
to
dive
in
and
understand
if
this
was
due
to
an
outflow
of
dapps
moving
away
from
the
network,
and
we
actually
saw
the
opposite.
We
saw
only
one
dap
move
away
from
the
network
and
it's
adapt
that
we've
been
in
very
close
touch
with
well
before
upgrading
to
the
network,
and
we
knew
they
were
moving
back
to
the
hosted
until
they
optimized
their
query
volume.
They
were
a
little
worried
about
cost
because
they
had
very
high
query
volume
and
then
they've
adapted
pulling
over
to
hosted
just
to
make
sure
they
minimize
it.
C
So
the
DAP
has
since
optimized
the
volume
is
already
planning
to
move
back
to
the
network
this
quarter,
so
that
would
be
a
great
win.
A
good
example
or
case
study,
of
how
people
have
a
say
and
just
to
clarify
what
optimization
means
for
everyone.
When
subgraphs
are
on
the
hosted
service,
they
can
and
often
do
query
data
just
constantly
and
they
haven't
had
to
worry
about
cost,
but
as
dapps
move
to
the
network,
they
realize
they're,
often
over
querying
and
retrieving
data
that
doesn't
always
need
to
be
updated
every
fraction
of
a
second.
C
So
they
work
to
make
their
query
volume
more
efficient,
still
within
the
graph
ecosystem,
just
making
sure
they're
only
getting
and
paying
for
what
they
need
and
therefore
save
on
cost
and
optimization
of
query
volume
is
something
we're
seeing
across
multiple
subgraphs,
which
is
playing
a
part
in
the
volume
and
query
drops,
but
the
ability
to
optimize
here.
It's
really
important
to
emphasize
it's
a
feature.
It's
a
feature,
not
a
bug
for
data
consumers,
and
this
alone
is
making
the
network
an
incredibly
sticky
product.
C
Another
important
factor
in
lower
query
fees
was
due
to
a
Gateway
configuration
change
to
reduce
parallel
or
simultaneous
request
to
multiple
indexers
for
any
given
subgraph.
Therefore,
improving
query
prices
for
data
consumers
actually
using
the
network
and
to
put
that,
in
other
words,
the
price
per
query,
has
gone
down
to
make
sure
people
aren't
paying
for
more
than
what
they
need,
making
the
network
more
affordable
for
everyone
which,
in
the
end,
is
a
good
thing.
What's
what's
really
important
on
the?
C
Why
of
the
network
here
is
that
in
web
2
pricing
models
across
all
Industries
people
are
complete
price
takers.
They
take
it
or
leave
it
and
have
little
to
no
say
in
what
price
they
pay
on
the
decentralized
network.
Dapps
have
some
control,
and
this
completely
changes
the
Dynamics
and
creates
a
data
economy
where
everyone
has
a
say
so
we're
excited
to
see
people
adapt
in
any
way
that
they
can
to
stay
on
the
network,
which
is
simply
the
more
performant
data
solution.
C
It's
great
that
the
nap
the
graph
Network's
a
sticky
product-
and
these
are
just
a
couple
examples
why
now
taking
a
look
at
the
decrease
in
the
number
of
indexers?
This
was
expected.
As
the
mips
program
came
to
an
end
in
Q2,
we
assumed
that
not
all
would
stay
on
after
it
ended.
Still
mips
was
successful
since
before
the
program
was
announced,
there
were
for
you
within
180
indexers,
and
none
of
them
were
able
to
serve
queries
on
anything
other
than
ethereum.
C
And
and
though
we
always
need
to
analyze
the
negatives,
we
also
have
to
look
at
the
positives
positives
that
we
saw
for
the
quota
as
well,
so
alluding
to
what
I
mentioned
of
the
graph
Network
being
sticky.
When
you
look
back
at
the
beginning
of
the
year,
there
were
only
around
140
monthly
active
data,
consumers,
which
is
a
combination
of
dapps
querying
known
subgraphs,
and
then
third-party
data
consumers
querying
subgraphs.
They
don't
maintain
two
quarters
later.
C
This
is
jumped
to
190,
so
over
30
percent
in
two
quarters
and
many
dapps
use
more
than
just
one
subcrafts
subgraph,
sometimes
many
more
so
it's
important
to
see
how
many
subgraphs
are
actively
queried,
just
not
active
data
consumers,
and
so
more
than
270
subgraphs
have
more
than
a
thousand
queries
per
month.
But
there
are
a
number
of
subgraphs
queried
below
that
amount
as
well.
C
So
the
number
is
right
around
300
or
so,
as
opposed
to
270
of
just
actively
queried
per
day,
and
these
data
consumers
are
active
across
multiple
chains,
live
on
the
network
and
I'd
say
a
likely
indicator
for
subsequent
growth.
Here
is
the
number
of
subgraphs
being
published
so
out
of
those
1
000
Plus
subgraphs
on
the
network.
There
is
a
long
list
of
dapps
that
I
mentioned
have
published
and
curated.
C
Metrics
aside
from
unbeatable
uptime,
due
to
hundreds
of
indexers
being
ready
to
serve
queries
at
any
time,
median
latency
continues
to
get
faster
right
now
at
78
milliseconds
for
Q2
and
for
some
context
there,
a
response
time
of
100
milliseconds
is
perceived
as
instantaneous,
so
seeing
the
network
below
that
Mark
shows
how
well
the
network
is
performing,
especially
versus
the
hosted
service
and,
of
course,
query.
Success
rate
is
also
key,
as
it
doesn't
matter
how
fast
something's
served
if
it's
a
failed
query
and
decentralized
network
is
also
outperforming
the
hosted
service
there
as
well.
C
It's
it's
it's
proving
to
the
world
that
decentralized
technology
is
simply
the
more
performant
solution
and
it
has
been
for
a
year
or
more,
but
performance
isn't
the
only
thing
that
matters
it's
all
about.
It's
also
about
the
experience
people
have
when
using
the
text.
So
let's
shift
gears
here
and
we'll
focus
on
some
user
and
developer
experience,
improvements
which
actually
saw
some
really
big
advancements
in
Q2
I'd,
say
one
of
the
most
highly
anticipated
functionalities
that
recently
went
into
beta
is
subscriptions
and
subscriptions
get
the
graph
one
step
closer
to
a
traditional
SAS
experience.
C
While
still
being
able
to
leverage
the
decentralized
network
for
just
the
best
performance
and
and
unbreakable
data,
and
with
subscriptions
data,
consumers
can
use
usdc
to
pay
monthly
and
Abstract
the
need
to
interact
with
GRT
for
billing.
While
everything
still
gets
converted
to
GRT
that
gets
paid
out
to
network
participants,
so
data
consumers
no
longer
need
to
manually
refill
their
billing
need
to
worry
about
it
running
out
and
then
having
to
go
and
log
in
and
even
then
the
existing
pay-as-you-go
billing
process
is
still
available.
C
And
Beyond
just
enhancing
the
experience
for
data
consumers,
the
graph.com
landing
page
got
a
massive
upgrade.
That's
been
in
the
works
for
many
months.
It
was
a
huge
cross-team
effort
across
the
ecosystem
to
launch.
The
website
now
has
simpler
to
understand
wording
for
both
Technical
and
non-technical
people
alike,
which
is
important
to
not
only
get
people
building
but
to
onboard
participants
like
delegators
in
order
to
scale
the
network.
C
It
has
simpler
and
faster
navigation,
so
one
click
goes
to
exactly
where
you
need
to
be
right.
When
you
go
to
the
site,
getting
people,
learning,
building
and
participating
faster
and-
and
it
just
looks
beautiful,
I
highly
recommend
you
go
check
it
out
for
yourself.
Caroline
dropped
a
link
in
the
chat.
C
And
then
last
but
not
least,
new
chains
continue
to
go
live
on
the
network.
There
are
now
seven
chains
live
being
used
in
production,
with
polygon
and
Phantom
being
the
most
recent
additions
at
this.
These
two
chains
alone
have
unblocked
thousands
of
subgraphs
with
tens
of
millions
in
Daily
query
volume
on
the
network
and
optimism's
up
next
and
is
close
to
going
live
as
well
and
then
for
future
Integrations.
C
The
graph
Foundation
is
working
on
the
graph
Improvement
proposal
process
to
speed
up
Integrations,
which
Eva
will
discuss
in
a
bit,
but
these
are
all
very
exciting
from,
even
though
we
see
some
downside
on
on
growth,
there
is
justification.
We
understand
what
it
is,
we're
aware
of
it
and
we're
working
hard
to
make
sure
every
level
we
could
pull
continues.
Growth
trending
up
into
the
right,
but
I'll
stop
here,
I'm,
going
to
pass
the
mic
back,
but
first
I'm
going
to
take
a
couple
seconds
to
give
taking
a
proper
intro.
C
So
one
of
the
best
decisions
I've
made
my
life
but
I'd,
say
there
are
leaders,
they're
Leaders
with
vision
and
their
leaders
that
can
execute
and
they
are
rarely
the
same
person.
But
taking
has
a
rare
of
ability
to
do
both
and
has
been
one
of
the
few
leaders
that
I've
ever
seen
with
that
superpower
and
probably
two
and
a
half
decades
across
three
major
industries
and
I.
C
B
B
We
can
go
to
the
next
slide,
so
this
is
kind
of
our
our
secret
plan
that
we've
been
executing
on.
If,
if
you
will
McKenzie
is
famous
for
their
kind
of
three
Horizons
is
what
they
call
them,
but
we're
calling
them
zones
and
you'll
see
why,
in
a
moment,
but
with
that
it's
kind
of
the
short
term,
the
medium
term
and
the
long-term
goal
of
the
business
and
so
Zone
one,
it
was
very
much
this
network
infrastructure
Zone.
B
B
I
think
we
can
kind
of
check
this
off
and
and
view
it
as
done,
and
we
very
much
needed
engineering
leaders
during
this
Zone,
but
now
we're
entering
a
different
phase
and
this
phase
is
zone
two,
and
this
is
very
much
the
hand-to-hand
combat
phase,
and
this
is
where
we
are
today,
and
it's
really
about
executing
on
what's
in
front
of
us,
with
the
graphs,
decentralized
Network
and
really
focusing
on
getting
these
hosted
service
subgraphs
upgraded
to
the
decentralized
network.
Now
that
the
infrastructure
is
ready.
B
This
is
obviously
a
huge
hill
to
climb
in
zone
two,
and
you
know
once
we
do
that
we
can
enter
enter
zone
three
but
zone.
Two
very
much
needs
great
Business,
Leaders
and
I'm
excited
to
join
many
great
Business
Leaders
across
the
ecosystem
like
Kyle,
Eva,
Martin,
Matthew
of
streaming
fast,
and
so
many
others,
and
so
with
that
you
know
it's
only
been
a
little
over
a
month
and
we've
already
made
waves
on
our
progress
to
the
decentralized
network,
and
that
upgrade
and
again
it's
really
not
about
me.
B
It's
really
about
empowering
the
incredible
people
across
the
different
companies
and
ecosystem,
and
so
with
that
we're
very
much
laser
focused
on
the
network.
So
let's
talk
a
little
bit
about
zone
three
before
we
move
to
the
next
slide,
we
can
stay
at
the
the
previous
side
so
zone
three.
This
is
very
much
where
you
need
is
building
as
an
example,
he's
building
Geo
a
web
3
browser
on
the
graph
kind
of
playing
3D
chess,
expanding
the
graph.
B
It's
all
about
demand
generation
and
data
acquisition,
and
once
we
Edge
a
node
help
to
complete
zone
two.
This
will
free
us
up
to
kind
of
be
a
new
ecosystem
participant
and
ideally
join.
You
need
in
that
third
Zone,
with
data
acquisition
and
kind
of
further
growing
the
graph
and
my
goal
as
as
CEO
is
to
kind
of
get
us
to
zone
three
as
quickly
as
possible.
I
set
a
100-day
plan,
we've
been
executing
on
that
and
we're
very
much
laser
focused
on
getting
that
hosted
service
traffic
upgraded
to
the
network.
B
D
B
That
won't
transfer
to
the
network
one
to
one.
As
we
have
seen,
the
queries
will
be
optimized,
but
it
really
is
have
go
time
to
get
that
traffic
over,
and
so
let's
talk
a
little
bit
about
the
hosted
service.
What
is
the
hosted
service?
Why
does
it
exist?
So
once
upon
a
time
there
was
no
way
to
query
a
blockchain
developers
were
attempting
to
spin
up
indexers
internally
in
a
centralized
way.
They
had
a
lot
of
downtime.
B
They
put
a
lot
of
engineering
hours
and
costs
into
this,
but
it
was
centralized
and
a
lot
of
times
it
wasn't
reliable.
So
it
was
extremely
difficult
to
query
blockchains
that
existed
and
because
of
this
there
weren't
really
many
use
cases
in
the
crypto
space
so
enter
the
graphs
hosted
service.
We
served
indexing
and
querying
for
subgraphs
we
innovated
and
coined
the
term
subgraphs,
which
are
open
apis
and
we
were
serving
them
in
a
hosted
capacity,
though
it
was
permissionless
to
spin
up
a
subgraph
on
the
hosted
service.
B
So
because
of
this
core
piece
of
the
tech
stack,
emerging
use,
cases
emerged
so
D5
summer,
then
nfts,
Dows
and
so
much
more
right,
web3
kind
of
exploded
in
many
different
directions,
and
it
continues
to-
and
you
know
we
have
to
be
honest
in
that-
we're
hosting
a
lot
of
that
web
3
traffic
and
usage,
which
isn't
the
goal
that
isn't
the
mission
and
and
we've
been
doing
it.
We've
been
subsidizing
that
for
developers
and
entrepreneurs
across
the
ecosystem,
but
now
that
the
network
is
ready,
the
decentralized
network
is
ready.
B
It's
time
for
those
sub
graphs
to
all
move
over,
and
we
really
stopped
to
our
mission
on
creating
a
decentralized
open
data
layer
for
web
3,
and
we
launched
the
decentralized
network
two
and
a
half
years
ago
and
we
launched
it
with
one
subgraph
and
as
Kyle
mentioned
today,
there
are
over
a
thousand
soap
graphs.
But
back
then
you
know
this
was
true.
Innovation.
There
wasn't
anything
to
fork
or
copy.
The
graph
was
kind
of
the
first
of
its
kind
in
this
category.
B
So
if
we
fast
forward
to
today,
we
can
see
that
the
network
very
much
is
flourishing
in
many
different
directions
with
thousand
subgraphs.
Those
users
are
paying
for
queries
in
GRT,
there's
tens
of
thousands
of
developers
building
on
and
experimenting
with
the
network,
and
these
are
really
the
entrepreneurs
building
building
this
future
that
we're
just
simply
enabling
there's
also
200
plus
indexers,
that
are
serving
queries.
So
you
know
these
are
different
companies
and
different
jurisdictions,
all
around
the
world
that
are
kind
of
the
backbone
of
the
web.
B
If
you
look
at
web
2,
it
has
you
know
one
company,
that's
really
organizing
a
lot
of
the
data
and
that's
Google
and
Google.
You
know
whether
they
intended
it
this
way
or
not.
They
have
the
ability
to
alter
the
data
or
simply
not
organize
the
data
that
all
of
us
rely
on
with
the
traditional
web
and
you
know
be
it
internal
or
external
forces.
Google
is
kind
of
pushed
to
alter
that
data
or
not
organize
data,
and
it's
not
because
Google's
evil.
B
But
now
it's
time
for
the
remaining
tens
of
thousands
of
sub
graphs
to
move
over
to
the
the
decentralized
network
or
upgrades
the
network.
If
you
will,
the
question
has
really
been
how
to
best
do
that
in
a
very
smooth
and
seamless
manner.
Think
like
as
easy
as
upgrading
an
iOS
update
on
your
phone
and
that's
really
been
the
big
question
over
the
past
month
and
a
half
that
I've
served
as
as
CEO
and
what's
exciting
is
that
we
we
have
a
plan,
so
we
can
go
to
the
next
slide.
B
So
we've
entered
into
a
new
era
of
the
graph
and
there
are
really
three
phases
to
this
master
plan
which
are
shown
here
so
the
sunrise,
and
this
is
really
how
the
graph
eats
all
data
and
how
we
make
sure
that
web3
wins
through
executing
on
on
these
three
pillars:
the
sunrise.
This
is
how
we
will
upgrade
all
traffic
to
the
network.
B
We
have
a
plan,
we're
actually
we've
begun
executing
on
a
portion
of
that
plan,
we're
scoping
out
the
remaining
engineering
work
and
then,
at
that
point
we
will
be
able
to
kind
of
share
that
master
plan.
With
all
of
you,
we've
been
speaking
to
community
members,
you
know
large
and
small
daps,
delegators,
indexers
kind
of
fine-tuning
this
plan
and
the
communication
strategy
around
it,
and
we
would
love
to
hear
from
you.
B
So
we'll
have
more
to
share
on
this
in
the
coming
weeks,
but
I
know
many
of
you
on.
This
call
have
asked
for
a
simplified
token
economics
and-
and
we
really
want
to
deliver
on
that-
so
we'll
continue
chatting
to
the
community
to
collect
feedback
and
kind
of
coordinating
these
columns,
and
we
want
to
make
sure
that
the
best
ideas
rise
to
the
top.
We
we
believe
in
kind
of
an
idea
of
meritocracy.
B
So
if
you
have
good
ideas,
we
want
to
hear
them
and
it's
really
our
responsibility
to
serve
you
and
and
the
other
community
members.
So
with
that
we
can
double
click
into
our
Q3
priorities.
If
we
want
to
go
to
the
next
slide,
so
this
is
what
we're
really
kind
of
excited
about
in
the
short
term,
so
the
first
is
solving
four
of
the
top
Network
blockers.
We've
actually
already
solved
two
of
the
four
for
this
quarter.
B
This
is
really
just
about
smoothing
the
process
and
making
it
easier
for
developers
and
entrepreneurs
and
third-party
data
queries
to
use
and
leverage
the
graphs
network
and
with
that,
the
ones
that
we've
completed
are
substreams
powered
subgraphs
on
ethereum
on
the
graph
Network
that
is
live
today
and
as
Kyle
mentioned
billing
2.0
with
subscriptions
in
beta.
This
is
something
developers
have
been
asking
for
for
a
long
time.
So
it's
been
great
to
execute
on
that.
B
Polygon
went
live
on
the
network
at
the
end
of
last
quarter,
so
that
was
something
that
a
lot
of
developers
were
were
also
asking
about,
but
we're
not
counting
that
for
this
quarter
and
it's
been
nice
to
just
kind
of
continue
making
Making
Waves
and
knocking
these
blockers
out.
The
next
day
is
launching
the
layer,
2
transfer
tools,
so
we're
very
close
on
this,
but
that's
in
scope
for
the
next
couple
weeks
in
the
quarter
and
then
lastly,
really
just
upgrading
subgraphs
to
the
network.
B
I
know
five
to
ten
percent
might
seem
a
bit
small,
but
there's
engineering
work.
That's
going
to
allow
this
pace
to
pick
up
towards
the
the
end
of
the
quarter
and
into
Q4.
So
with
that
we're
very
much
laser,
focused
and
I
will
pass
it
over
to
Alex
CTO
of
streaming
fast.
Who
will
discuss
the
innovations
that
they've
been
making
when
it
comes
to
fire
hose
and
sub
streams.
D
D
Name
is
Alexander
and
I'm
going
to
give
you
a
quick
update
from
the
streaming
fast
perspective
and
our
our
contributions
to
the
ecosystem.
You
can
go
to
the
next
slide
there,
so
we've
observed
from
some
indexers
by
shifting
their
back
end
to
fire
hose
in
the
graph
node
there.
They
saw
a
decrease
in
their
RPC
cost
by
90,
that's
9-0,
so
that
was
pretty
exciting.
It
was
the
first
integration
we
did
coming
into
the
graph.
D
That's
that
thing
here
and
we
are
currently
also
working
with
the
go
ethereum
team
to
integrate
a
new
in
extended
Tracer
that
they
built
in
collaboration
with
our
team
and
which
it
was
inspired
by
our
work
on
the
fire
hose
and
we're
currently
porting
that
Tracer
to
arbitrum,
and
that
will
be
helpful
for
any
Geth
based
chain
and
then
we're
going
to
continue
rolling
out
there.
But.
C
D
Working
with
a
dozen
other
chains
to
build
a
native
fire
hose
integration
and
make
make
them
the
graph
ready
out
of
the
box
and
when
fire
hose
is
integrated
boom,
they
also
get
substream
support
for
free
and
so
a
few
important
Milestones.
Regarding
substance,
let's
say
in
the
last
few
months
was
the
General
availability
of
substreams
in
March
and,
more
recently,
the
release
of
substreams
based
subgraphs
on
the
network,
which
means
that
sub
graphs.
D
You
know
queryable
using
the
the
query
interface
that
you
people
are
used
to
and
it's
current
tokenomics
and
all
that
can
be
powered
by
substreams
and
deployed
to
the
network.
So
I,
you
know
I've
personally
observed
72
times
the
performance,
so
that's
seven
thousand
two
hundred
percent
performance
increase
on
the
uni
swap
V3
substreams
based
subgraph
that
we
wrote,
which
is
an
equivalent
to
the
original
subgraph
one
to
one,
and
we
know
some
use
cases
go
well
beyond
that.
Leveraging
the
power
of
parallelization.
D
And
maybe
a
last
note
there
we
made
we
met
with
a
few
large
depths
that
are
getting
more
and
more
excited.
Some
have
dug
deep
into
sub
streams.
Some
have
made
started,
making
sub
streams
their
main
backends
for
their
data
pipelines
and
that
opening
to
new
technology
is
received
for
them
as
the
breadth
of
fresh
air,
as
some
reasons
why
some
had
dismissed
the
graph
at
some
point
are
sort
of
Vanishing,
because
we're
opening
up
the
valve
of
new
data
service
as
Tegan
was
saying.
E
Cool
yeah,
so
I'll
catch
up,
everyone
on
the
r
d
efforts
and
some
of
the
wider
ecosystem
work
with
the
foundation,
so
you
might
have
remembered
last
quarter.
There
was
a
few
different
things
on
this
roadmap
because
we've
shipped
them,
so
you
know
those
being
substance:
powered
subgraphs.
Some
of
the
billing
features
looking
forward
to
this
quarter
in
the
next.
We're
really
focused
on
scaling,
so
we've
got
some
final
improvements
to
make
on
scalar
our
efficient
payment
system
currently
being
audited,
as
Tegan
mentioned,
we're
also
working
on
L2
migration
in
full
swing.
E
So
we
have
a
few
gips
like
L2
transfer
tools
to
actually
help
indexers
move
over
to
the
arbitrary
Network
and
then
we'll
be
moving
over
all
query
volume.
We've
got
a
lot
going
on
on
the
research
side,
so
making
these
data
services
verifiable
and
when
I
say
data
services,
I
mean
subgraph,
substreams
and
also
future
new
data
services
that
the
graph
will
be
serving
as
we
really
solidify
our
role
as
a
Marketplace
of
data,
we'll
also
be
adding
new
data
sources.
E
So
things
like
our
weave
ipf
us
even
off-chain
data,
increasing
the
scope
of
what
the
graph
can
actually
index
and
then
also
integrating
that
with
substreams
directly
for
efficient
querying
we're
continuing
multi-chain
expansion.
I'll
speak
a
bit
more
about
that
in
the
next
slide,
and
we've
got
a
ton
of
rfps,
so
we're
really
looking
to
grow
the
substream
ecosystem.
E
So,
as
Kyle
I
believe
mentioned,
we
finished
mips
and
if
you
remember,
mips,
was
a
multi-chain
incentive
program
similar
to
an
incentivized
testnet
for
indexers.
With
that
program.
Over
the
last
nine
months
we
launched
seven
new
chains
so
really
excited
about
the
force
behind
the
web.
3
Community
as
every
chains
Community
came
together,
we're
seeing
a
lot
of
node
operators,
let's
say
in
the
gnosis
ecosystem,
become
an
indexer
and
really
create
synergies
between
both.
So
that's
part
of
our
growth
strategy
going
forward
is
really
capitalizing
on
all
the
existing
node
operators.
E
For
these
chains
as
a
next
step,
we
are
finishing
things
up
with
optimism
and
then
we'll
be
moving
to
a
permissionless
process,
and
this
means
that
for
the
first
time
in
history,
any
chain
that
wants
to
be
supported
by
the
graph
can
do
so
by
their
own
volition,
so
really
exciting
moment.
This
means
that
you
know
folks
can
post
on
the
Forum.
They
can
go
through.
E
The
testing
process
make
sure
their
their
chain
is
up
to
Snuff
and
then
work
with
the
core
Dev
teams,
and
then
their
chain
will
be
on
the
network
so
really
exciting
time.
As
We
Know,
especially
in
the
bear
Market,
there's
quite
a
few
new
chains
coming
up-
and
this
also
means
things
like
l3s
new
types
of
L2,
so
not
necessarily
new
L1
chains,
but
really
making
sure
we
support
all
types
of
data
being
indexed.
E
So
you
know
something
like
the
unit
swap
sub
graph
going
from
two
two
months
of
syncing,
because
it
was
so
large
and
complex,
there's
so
much
data.
It's
the
most
highly
used
smart
contract
on
ethereum
to
20
hours
really
shows
what
the
power
of
the
graph
is,
as
we
start
to
scale
web3
itself
so
really
excited
to
see
dapps,
actually
even
transition
in
the
way
that
they're
thinking
about
data.
E
Now
that
we
know
the
graph
is
so
performant
next
slide
and
and
really
to
summarize,
you
know
what
substring-powered
subgraphs
do
is
they
are
boosting
the
power
of
subgraphs.
So
we
wanted
to
just
share
a
little
snippet
of
some
of
our
internal
stats
on
the
documentation,
so
substring-powered
subgraphs
were
launched
third
week
of
July
and
in
that
first
10
days
or
so,
we
already
saw
nearly
100
I
believe
over
over
nearly
200,
actually,
users
actually
visit
and
start
building
substreams.
E
We
had
I
believe
over
20
new
sub
streams
that
were
actually
built
and
deployed
within
the
first
five
days,
so
really
exciting
that
people
are
catching
up
our
biggest
hurdle
right
now
and
where
we
could
use
your
help
is
actually
spreading
the
word
and
educating
more
developers.
We
know
rust.
Engineers
are
sparse,
but
any
any
that
you
know
of
we'd
love
to
get
them
on
board.
E
And
wanted
to
wrap
this
up
with
the
gips
that
are
in
process
so
world
of
data
services,
that's
Gip
42
is
ongoing
as
we're
continuing
to
work
on
adding
new
data
services.
So
you'll
see
more
this
year.
Query
fee
rebates
is
one
of
the
gips
to
make
things
a
lot
more
efficient
for
indexers.
So
we're
really
thinking
about
how
to
make
sure
profitability
for
indexers
is
taken
into
account.
L2
indexing
rewards.
E
You
know,
there's
a
lot
going
on
here,
but
this
is
the
migration
of
the
rewards
from
L1
to
L2.
So
the
end
state
is
that
indexers
can
earn
a
hundred
percent
of
their
indexing
rewards
on
L2
the
new
arbitrum
launch,
but
for
now
we're
doing
this
incrementally
to
make
sure
that
things
are
secure
and
also
indexers
feel
comfortable
with
the
process.
C
Just
to
give
some
well-deserved
thank
yous
to
people
that
have
helped
in
all
sorts
of
ways
across
the
ecosystem.
Thank
you
so
much
to
Jeff
from
chapter
one
for
connecting
us
with
an
amazing
head
of
talent
to
Jenna
from
coin
fund,
for
including
the
ecosystems
open
roles
in
their
hot
jobs,
feature
Tish
Liang
from
Ledger
Prime
for
the
hiring
suggestions
Jr
for
multi-coin,
for
all
the
amazing
help
on
com
strategy
and
Michael
and
Craig
from
reciprocal.
C
Thank
you
so
much
for
all
the
incredible
strategy
support
as
well
as
Ali
from
the
teams,
the
hiring
recommendations
to
John
Choi
for
help
on
strategy
and
Korea
and,
of
course,
last
but
not
least,
thank
you
to
all
the
amazing
graph
Guardians
for
what
you
do
every
single
day
and
really
just
helping
educate
the
world
on
the
graph
Network
and
then
helping
it
build
out
to
the
next
level
and
then
to
close
it
out.
We
want
to
make
sure
everyone
knows
how
you
can
help.
So.
C
First
we'd
really
appreciate
your
feedback
on
the
sunrise
plan
that
Tegan
mentioned,
as
well
as
com
strategy.
So
please
reach
out.
If
you'd
like
to
hear
more
about
it
and
give
feedback
next,
we
ask
all
of
you
to
delegate
your
GRT
to
help
continue
to
scale
and
secure
the
decentralized
network.
Every
GRT
delegate
helps
increase
the
ability
of
indexers
to
sync
up
and
serve
more
queries
to
data
consumers
on
the
decentralized
network.
Third,
we
are
hiring
from
some
key
roles
in
the
ecosystem.
C
Please
pass
them
our
way,
so
we
can
make
sure
we
try
to
get
them
access
to
the
edge
of
node
House
of
web
3,
which
has
now
a
solid
number
of
Founders
Builders
and
more
attending
the
Space
daily.
Please
invite
your
community
to
be
a
graph
Advocate,
whether
they've
been
in
the
industry
for
a
while
or
are
new
and
just
want
to
break
into
web3.
C
It's
been
a
really
good
red
pill
for
getting
people
into
the
graph
ecosystem
and
from
graph
Advocates
that
have
even
become
full-time
hires,
so
it's
a
great
way
to
get
involved
and,
as
always
reach
out
with
your
advice,
feedback
and
anything
else.
You
think
we
can
benefit
from.
We
take
feedback
very
seriously.
It
can
work
really
fast
to
incorporate
it.
So
please
keep
it
coming
and
we
appreciate
any
and
all
of
it.
So
that's
it
for
now.
I'll
pass
it
over
to
Caroline
to
go
over
any
questions
that
have
come
up
within
the
call.
A
C
I
could
probably
take
that
one,
so
web
3
usage
has
gone
down
across
the
board.
There
was
a
good
drop
commensurate
on
the
hosted
Service
as
well
as
the
network,
so
it's
not
like
the
net
the
hosted
Services
going
up
while
the
network
is
going
down
like
I
mentioned
in
the
beginning,
there's
about
a
billion
queries
per
day
right
now
unhosted,
but
we
have
seen
up
to
one
and
a
half
to
two
billion,
so
it
could
just
be
activity
across
all
chains
in
the
ecosystem
across
the
board.
C
C
The
team
is
hyper,
focused,
we've
cut
and
obviously
I'm
experiencing
this
personally,
we've
cut
so
much
of
other
responsibilities,
and
now
it's
all
about
the
North
Star,
it's
all
about
our
near-term
goals
and
that's
what
we
should
be
concentrating
on
so
on
the
unblocking
of
the
team
getting
into
the
momentum
swing
around
executing
I,
think
Tegan
and
other
team
members
have
done
a
really
good
job
of
helping
rework.
What
has
been
some
in
the
past.
C
F
Yeah
happy
to
chime
in
hi
everybody,
I'm,
Rodrigo,
cuello,
Chief,
Spirit
officer
at
Edge,
node,
so
I
will
add
an
echo
to
what
Kyle
said
here
just
to
give
some
more
color
on
this.
We
do
a
an
internal
quarterly
survey
amongst
all
of
our
team
members
on
engagement.
So
we
ask
about
12
questions
and
they're
rated
on
a
scale,
and
people
are
able
to
add
comments
and
we
ask
questions
along
along
certain
parameters
like
well-being,
leadership,
responsibilities,
psychological
safety,
Etc,
so
we're
in
the
midst
of
a
survey.
F
Now
it
ends
on
Friday,
so
we
have
about
half
of
people
respondents
of
their
responses
in
so
what
I
can
say
is
that
we
are
up
across
the
board.
We
were
able
to
compare
quarter
to
quarter
and
we
track
these
over
time.
So
we
can
see
how
things
are
trending
and
what
I
can
say
so
far
is
that
across
multiple
Dimensions,
primarily
around
leadership
responsibilities
and
role,
Clarity,
our
scores
are
up
dramatically.
C
Yeah
I'd
say
that
we
will
share
more
public
information
on
this
soon,
but
if
you're
interested,
let's
just
book
a
call,
let's
talk
through
it,
walk
through
it
and
and
get
direct
feedback.
I
think
that'd
be
the
best
way
until
everything's
made
fully
public
and
we're
building
out
in
the
open
which
we
want
to
be.
E
I
can
take
that
one.
So
that's
a
great
question.
I
would
say
it's
a
bit
nuanced
because
we're
in
the
process
of
building
out
this
data
Marketplace.
So
obviously
we
have
sub
graphs
as
the
product
right
now
we
have
that
Demand
on
both
the
hosted
service
and
the
network.
We
also
have
that
Supply
actually
being
able
to
serve
those
queries
in
that
data,
but
our
goal
really
is
to
make
the
graph
much
more
modular.
E
So
not
only
core
developers
today
can
add
new
data
services,
but
anybody
can
so
there
are
a
few
new
data
services,
we're
already
working
on
things
like
substance
powered
subgraphs.
Next,
we'll
be
focusing
on
getting
substreams
and
fire
hose
on
the
network.
Even
getting
new
data
services
on
the
network.
You'll
you'll
hear
more
about
that
soon
and
really
the
goal
is
at
that
point.
E
Then
it's
about
getting
the
current
web
2
volume
that
exists
right
like
there
are
people
requesting
things
like
you
know,
fire
hose
or
raw
blockchain
data
outside
of
the
graph,
and
so
it's
just
shifting
that
current
existing
demand
to
the
graph
Network
in
terms
of
the
supply.
You
know
once
these
data
services
are
deployed,
meaning
it's
either
their
core
devs
or
maybe
some
other.
You
know
developer
in
the
future
that
deploys
these.
E
It's
just
getting
indexers
to
actually
run
the
back
end
stack
and
that
will
largely
be
based
on
fire
hose
in
the
existing
graph,
node
infrastructure.
So
for
indexers
it
will
become
a
choice
of
Economics
of
perhaps
loyalty
to
the
chain
or
the
type
of
data
Community.
Maybe
they
only
want
to
serve
data
scientists,
for
example,
but
we're
really
confident
that,
because
what
we're
building
out
is
just
you
know,
implementations
in
the
decentralized
fashion
for
demand
that
already
exists,
but
our
Tech
is
stronger.
E
A
C
Yeah
ZK
sync
is
currently
live
on
the
hosted
we
we'd
support
them
in
testnet
and
we're
live,
I
think,
first
or
second
day
of
mainnet,
and
we
are
in
discussions
with
them.
They're
really
excited
about
unlocking
substreams
for
Builders,
so
we're
we're
talking
through
a
fire
hose
integration
now
and
that's
exciting,
because
the
builders
across
all
chains,
not
just
CK
sync,
are
asking
the
chains
to
get
substreams
unlocked.
So
it's
a
really
fun
thing
to
see
and
work
through
with
all
the
different
ecosystems.