►
From YouTube: The Graph - Q3 2022 Quarterly Graph Participant Update
Description
The Graph ecosystem continues to iterate to support the decentralized web.
The latest Graph Participant Update covers highlights from Q3 2022 of The Graph, including key stats, announcements and milestones. Watch the recording and learn about all the building and innovating happening within The Graph Ecosystem!
The Graph is an indexing protocol for querying networks like Ethereum and IPFS. Anyone can build and publish open APIs, called subgraphs, making data easily accessible.
Follow The Graph on social media
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
All
right,
let's
jump
in
so
thank
you,
everyone
for
joining
today's
graph,
quarterly
participant
update.
We
are
super
excited
to
share
everything.
That's
happened
in
in
Q3.
Just
a
quick
reminder.
This
is
a
recorded
call.
It
will
be
shared
publicly
so
with
that
feel
free
to
make
any
content
during
today's
presentation
and
ask
any
questions
in
the
link
that
Caroline
shared
in
the
zoom
chat.
A
So
just
a
quick
disclaimer.
There
are
no
forward-looking
statements
in
this
presentation
and
if
you
intend
to
purchase
DRT
make
sure
you
only
purchase
the
amount
that
you
do
intend
to
use
in
the
network
as
it
is
a
utility
work
token.
So
with
that,
what's
the
purpose
of
this
update,
so
we
want
to
provide
summaries
on
the
work.
A
So
with
that,
let's
take
a
look
at
the
highlights
from
Q3.
I
know
we're
we're
almost
to
the
half
of
Q4
and
there's
been
a
lot
of
exciting
updates
in
Q4
already,
but
in
Q3
we
can
see
that
there
were
106
new
subgraphs
on
the
graphs,
decentralized
Network.
These
are
all
ethereum
based
subgraphs
and
there
was
a
24
increase
from
last
quarter.
A
But
with
that
we
can
look
at
the
query.
Fee
increase
at
282,
000,
GRT,
query
fees,
that's
a
51
increase
from
last
quarter.
So
what
this
signifies
is
that
a
lot
of
the
applications
that
are
moving
to
the
graphs
decentralized
network
have
have
a
more
traction,
they're
they're,
seeing
more
queries
on
their
applications
and
with
that
the
mips
program
launched
and
15
52
new
inductors
spun
up
thus
far
on
the
graphs,
decentralized
Network,
and
we
saw
over
a
hundred
or
sorry
over
1800
applications
for
the
mips
program.
A
So
there
are
now
over
500
new
subgraphs
that
have
been
published
to
the
graphs
decentralized
Network,
which
is
exciting
to
see
the
ramp
up
there,
and
with
that
query
fees
are
continuing
to
grow
so
with
migrations.
More
queries
are
on
the
decentralized
networks
and
what's
been
interesting
in
the
blockchain
space,
is
that
everyone
is
really
focused
on
rights
like
writing
to
the
blockchain,
whereas
the
graph
is
really
focused
on
reads
and
when
you
post
a
Twitter,
a
tweet
as
an
example
that
tweet
is
one
right,
but
if
you
get
250
likes.
A
That's
an
example
of
the
the
reads
on
that
tweet.
So
with
this,
this
is
a
double
click
into
the
indexers
on
the
network.
So
this
chart
shows
just
the
growth
rate
in
indexers,
so
there
are
now
over
200
indexers
on
the
graph
Network
and
those
inductors
are
the
ones
serving
those
queries
for
the
applications,
and
this
is
very
important
as
we
go
multi-chain
to
have
many
different
indexers
on
all
of
the
chains
that
are
going
to
spin
up
on
the
graphs,
decentralized
Network
Beyond
ethereum.
A
When
we
look
to
delegation
there
are
now
over
10
000
delegators
on
the
graph
Network,
so
delegators
help
secure
the
graph
Network.
They
also
help
indexers
increase
the
stake
that
they
have,
and
so,
if
you
were
one
of
the
first
10
000
delegators,
congratulations,
if
you
have
interest
in
delegating-
and
you
don't
know
how
to
get
started,
feel
free
to
reach
out
to
us.
We're
always
happy
to
help.
And
it's
just
a
couple
clicks.
A
So
when
it
comes
to
these
improvements,
gas
fees
are
are
hindrance
to
the
decentralized
network
today.
So
when
you
curate,
when
you
index,
when
you
delegate,
you
have
to
pay
gas
costs
in
ethereum,
but
also
when
you
publish
a
subgraph
to
the
network,
you
incur
gas
costs
as
well.
So
the
solution
is
moving
to
Arbitron.
There's
a
Gip,
that's
going
through
the
process
for
this,
and
this
will
reduce
costs.
We
assume
at
around
95
percent
and
also
what
this
unlocks
is.
A
Advanced
tasks
when
it
comes
to
earned
programs
like
coinbase
or
like
CMC,
so
that
you
can
actually
get
users
participating
in
the
network
which
is
all
about.
You
know
all
all
what
we're
focused
on
here
and
when
I
was
at
web
Summit.
So
many
people
came
up
to
me
and
they
said
they
actually
earned
learned
about
the
graph
through
a
coinbase
earn
or
through
a
CMC
earn.
So
we're
excited
to
ramp
up
the
tasks
there
to
really
get
people
participating
in
the
network.
A
A
second
piece
is
on
the
Fiat
on-ramp
some
projects.
They
just
want
to
pay
for
queries
with
a
credit
card,
and
let
all
the
grtps
happen
in
the
background.
So
this
is
a
piece
around
improving
that
that
building
experience
and
they
also
want
reoccurring
payments
so
that
they
don't
have
to
think
about
it,
and
so
that's
the
second
solution
is
just
getting
subscriptions
on
the
decentralized
network.
A
So
all
of
these
things
are
are
a
work
in
progress
currently
when
it
comes
to
the
quality
of
service,
so
we're
actually
seeing
this
on
par
and
better
than
the
hosted
service,
which
is
great
and
we're
continuing
to
make
efforts
to
really
improve
the
quality
of
service
on
the
decentralized
network
and
then
going
cross
chains.
So
gnosis
was
announced
as
the
next
chain
on
the
graph's
decentralized
network.
This
is
exciting
because
it
will
unlock
the
sub
graphs
that
are
building
on
gnosis
to
be
able
to
migrate
to
the
decentralized
network
decentralize
their
their
indexing.
A
A
query
layer
and
we've
been
in
conversations
with
many
of
the
applications
on
gnosis
already
and
no
gnosis
is,
is
doing
a
lot
behind
the
programs
that
are
running
as
well,
which
has
been
great
just
in
partnership
with
gnosis,
and
if
you
have
opinions
on
the
next
chains
that
you
want
to
see
on
the
decentralized
network,
we
would
love
to
hear
from
you
there's.
You
know
many
different
chains
that
we
could
unlock
next
and
in
the
likes
of
polygon
or
Arbitron
or
optimism.
A
So
we
would
love
to
hear
from
you
to
see
who
you
think
should
be
unlocked
next,
so
protocol
metrics
and
data
apps,
so
Missouri
has
been
working
on
a
lot
of
products
internally.
Mazari
is
now
a
core
developer
and
they
all
of
their
data
is
powered
by
the
graph.
They
really
wanted
to
build
on
something
that's
positive,
some
as
opposed
to
zero
sum
building
on
essentialized
analytics
platform
that
no
one
really
benefits
from
other
than
that
centralized
company.
A
So
this
is
really
exciting
and
they
have
really
great
really
great
products
that
they're
working
on
internally
and
they're
standardizing
the
sub
graphs,
so
that
everyone
can
use
really
great
subgraphs.
So
if
you
are
an
application
within
the
web
3
space
and
you
need
help
building
a
top-notch
subgraph
talk
to
Missouri,
they
can
add
features
for
you
and
if
you
know,
anyone
that
is
building
that
could
leverage
Missouri's
help.
Let
let
the
team
know
Vincent,
is
great
in
leading
that
charge
and
with
this
I
will
pass
it
over
to
Eva
Bayland
who's.
B
Awesome,
thank
you
so
much
Tegan
you
can
go
to
the
next
slide
cool,
so
would
like
to
discuss
a
bit
more
about
what
technical
progress
we've
been
making.
So
these
three
gips
we
have
here
are
what
we
focused
on
the
last
few
months
and
we'll
be
in
production
very
soon,
the
first
one
being
that
layer,
two
integration
has
taken
mentioned
so
enabling
that
arbitrary
bridge
and
deploying
on
arbitrim
to
scale
for
all
participants.
The
next
one
is
what
we
call
an
Epoch
block
Oracle,
which
is
a
component
that
unblocks
multi-chain
Integrations
on
the
network.
B
So
right
now,
we've
started
with
gnosis
chain
in
this
Epoch
block.
Oracle
enables
gnosis
chain
to
be
supported
on
mainnet.
So
right
now
the
mips
program
has
been
on
for
several
weeks
and
we've
got
over
350
gnosis
indexers,
meaning
they're
running
gnosis
chain,
as
well
as
graph
node
that
are
testing
out
the
infrastructure
figuring
out.
How
to
you
know,
work
with
gnosis
as
a
new
chain,
and
once
this
Epoch
block
Oracle
passes
we'll
be
able
to
support
new
chains
as
well.
B
The
third
one
here,
oh
sorry,
the
third
one
here
is
just
curation
improvements.
So
we've
gotten
a
lot
of
feedback
from
users,
both
developers
and
just
random
curators,
that
the
bonding
curve
we
had
was
a
little
too
aggressive,
and
so
it
was
impacting
user
experience
so
sort
of
related
to
some
of
the
improvements
that
Tegan
mentioned
related
to
billing.
Curation
improvements
will
really
improve
the
devex
to
make
sure
that
migration
is
much
more
seamless.
B
There
really
is
no
rush
here
on
developers
and
we're
really
trying
to
ensure
that
every
dab
feels
safe
and
that
they
have
all
the
support
needed
throughout
their
migration
or
development
process,
expanding
multi-chain
so
again,
hoping
that
all
chains
are
migrated
over
the
next
several
months
and
we're
already
seeing
the
steam
pick
up
even
in
this
first
cycle,
with
noses
change.
So
we
expect
that
to
speed
up
over
every
chain
that
we
roll
out
substreams
based
subgraphs,
you
might
have
heard
a
bit
about
this.
B
Substreams
is
new
technology
that
will
make
it
much
faster
to
sync
the
subgraphs
that
everyone
knows
and
loves
today.
So
this
should
really
improve
syncing
speed
anywhere
between
10
and
100x,
depending
on
the
subgraph.
So
looking
for
that
to
come
into
production
very
soon,
miss
sorry
continuing
to
do
their
work
on
standardized
subgraphs,
and
this
goes
beyond
just
the
Missouri
app.
It
really
enables
data
standardization
throughout
the
ecosystem.
B
So
what
we
see
a
lot
of
is
teams
using
the
same
subgraphs
for
different
reasons,
and
the
goal
is
to
standardize
across
protocols
so
that
way,
lending
subgraphs
all
look
the
same.
You
know
the
definition
of
TBL
is
the
same
Etc,
and
this
should
Elevate
web
3
past.
Just
you
know,
being
standards
for
apis
graph.
B
Client
updates,
there's
quite
a
few
exciting
features
here
that
the
guild
has
been
working
on,
so
a
bunch
of
new
features
for
subgraph
developers
to
improve
their
experience
with
graphql
and,
lastly,
continuing
the
devex
improvements
that
we
mentioned,
hashtag
flatten
the
curve.
That's
the
bonding
curve
on
our
curation.
B
I'll
go
over
these
a
bit
quicker,
but
to
maybe
dive
into
what
substreams
are
I
know
that
we've
talked
a
lot
about
this.
Basically
they're
parallelized
data
streams
of
raw
data,
so
it
makes
it
much
easier
to
get
raw
data
like
state
that
you
know
could
unlock
other
use
cases,
but
also
just
make
syncing
subgraphs
much
faster
since
you're.
Just
updating
per
block,
much
faster
than
you
would
be
otherwise.
B
I
want
to
go
over,
maybe
just
one
of
these
which
is
graph
cast.
So
this
is
a
gossip
Network,
that's
being
developed
by
one
of
our
core
devs
graph
Ops,
and
the
goal
here
was
really
to
unblock
efficiency
between
indexers,
but
really
this
technology.
In
theory
could
be
be
used
between
other
protocols
so
expanding
past.
The
graph
other
protocols
that
might
have
you
know,
communication
between
their
node
operators
could
gain
from
a
lot
of
what
we're
working
on
going
over
what
we've
achieved
to
date
with
mips.
B
So
we
have
75
million
GRT
allocated
to
this
program.
This
will
be
divvied
up
per
chain
as
well
as
per
indexer
as
they
participate
in
different
chains.
We're
seeing
that
some
indexers
have
preferences,
for
example,
some
love
gnosis.
They
want
to
run
gnosis,
others
might
not
feel
like
they
want
to
run
certain
chains,
for
whatever
other
trade-offs
are
important
to
them.
B
So
far,
like
I
said,
we
have
over
360
indexers
syncing
gnosis,
which
is
amazing
and
we're
continuing
to
collaborate
with
gnosis,
with
some
really
exciting
announcements
coming
soon,
as
well
as
announcing
the
new
chain
which
should
unlock
a
whole
other
sort
of
community
that
we're
tapping
into
we've
gotten
really
close
with
gnosis
over
the
last
few
months.
But
we're
excited
to
expand.
B
A
lot
of
what
they're
also
doing
is
figuring
out
where
the
gaps
in
our
ecosystem,
so,
for
example,
The
Advocates
spun
up
this
initiative
of
approaching
other
protocol
teams
to
have
subgraph
querying
docs
integrated
into
those
protocol
websites.
So,
for
example,
ens
right
now.
If
you
go
to
their
website,
you
can
see
how
to
query
a
subgraph,
and
that
was
work
that
was
all
managed
by
The
Advocate
style.
So
we're
really
seeing
the
fruits
of
sort
of
this
labor
of
building
a
wider
network
of
contributors
globally.
B
That
then
come
up
with
their
own
idea
is
of
how
to
contribute
on
subgraph
dial.
This
one
is
still
a
little
early,
but
our
goal
is
that
we
give
out
bounties
and
grants,
so
other
teams
and
individuals
can
feel
like
they
can
help
actually
help
those
daps
migrate.
So,
instead
of
the
core
developers
working
on
those
themselves,
we
can
have
other
subgraph
developers
hold
their
hands.
A
Thank
you
so
much
Eva
great
and
then
one
thing
I
want
to
double
click
into
is
just
that.
You
know
the
graph
is
here
to
provide
core
infrastructure
for
the
future
of
the
web.
We
are
very
much
playing
a
long
game.
We
want
this
infrastructure
to
be
used
100
plus
years
and
into
the
future,
and
we
want
to
enable
applications
to
be
permanent
and
in
order
for
these
applications
to
be
permanent,
you
need
a
decentralized
web.
A
A
No
such
chain,
we
really
want
to
get
that
lit
up
on
the
decentralized
network
and
start
migrating
subgraphs
that
are
building
on
gnosis
onto
the
decentralized
network
from
the
hosted.
We
also
plan
to
announce
the
next
Network
chain
integration,
so
that
will
be
exciting
again.
We
would
love
to
hear
from
you
if
you
think
that
should
be
polygon,
arbitrum
optimism.
We
would
love
to
hear
your
opinions
there.
A
We
are
migrating
the
graph
to
arbitrum
so
that
we
can
reduce
gas
costs
and
we're
really
focused
on
improving
the
developer,
experience
user
experience,
latency
billing
and
we
plan
to
get
a
Fiat,
on-ramp,
Network
integration,
hopefully
by
next
quarter,
and
we're
really
just
focused
on
as
an
entire
ecosystem,
migrations
and
getting
subgraphs
supported
on
the
decentralized
network
and
we've
really
leaned
in
here.
We
fully
white
Club
the
process
so
that
it's
very,
very
easy
for
developers
and
Founders
and
entrepreneurs
to
migrate
their
subgraphs
onto
the
network.
A
So
with
this,
how
you
can
help?
So
we
would
love
to
hear
from
you
on
how
the
graph
network
is
is
going
any
data
that
you
need.
You're
you're
welcome
to
reach
out
to
us
all.
Most
of
it
is
public
on
the
the
graph
network,
but
we're
always
happy
to
provide
that
to
you
and
if
you
want
to
share
your
your
copies
in
advance
with
us,
we
would
love
to
to
help
and
then
also
just
introducing
us
to
any
teams
that
need
help
with
migration.
A
B
A
We
are
also
hiring
so
we're
hiring
the
the
graph
Foundation
is
hiring
for
a
CFO.
We
at
genot
are
hiring
for
a
senior
product
manager,
developer
relations,
a
site,
reliability,
engineer
graph
Ops
is
hiring
a
rust
engineer
and
streaming
fast
back
on
engineering
go
if
there
are
any
speaking
opportunities
or
workshops
to
help
educate
on
the
graph,
Network
or
subsequently
web3.
We
are
always
happy
to
lean
in
there
so
feel
free
to
send
any
opportunities
our
way
at
Edge
node.
A
We
just
launched
the
house
of
web
3
in
San
Francisco,
which
is
a
co-creation
space
for
anyone
to
come
and
and
work
from
and
be
a
part
of
and
post
events
at.
So
let
me
know
if
you
want
information
there
and,
of
course,
delegate
on
the
graph
to
help
secure
the
network,
if
you're
not
already
doing
so
and
again
always
happy
to
help
there.
A
A
few
thank
yous
before
we
get
to
q,
a
I
want
to
say
thank
you
so
much
to
the
subgraph
Dao
members
who
are
working
hard
on
Outreach
and
migration
support
to
help
the
core
developer
teams
scale
that
effort.
It's
really
been
great,
seeing
them
lean
in
there
also
thank
you
to
Michael
and
Craig
from
reciprocal
Ventures
for
all
the
support
and
strategy
guidance.
A
Thank
you
to
John
for
connecting
us
with
Talent
we
actually
hired
George
from
Edge
and
node,
based
on
John's
recommendation
and
a
big
thank
you
to
The
grapp
Advocates,
who
host
events
around
the
world
and
help
educate
at
Graf
booths
and,
of
course,
thank
you
to
the
graph
Council
for
the
continued
focus
on
strategy
and
and
pushing
the
protocol
forward.
So
with
that,
I'll
pass
it
over
to
Kyle
to
read
through
the
Q
a
questions.
C
All
right,
I'm
live.
You
can
hear
me
awesome,
sorry
for
that.
We
had
a
few
questions
to
start
out,
taking
on
the
hosted
service,
deprecation
exit
criteria
and
I'll
consolidate
those
into
really
one
or
two
here.
So
any
idea,
what
the
exit
criteria
benchmarks
will
look
like
to
pick
up
the
hosted
service
deprecation
again
and
then
also
win
the
deprecation
starts
again.
Will
it
eventually
be
a
timeline
once
more
or
will
the
will
it
look
very
different
in
general
and
future?
Have
we
thought
through
that
yeah.
A
So
we're
actually
moving
away
from
the
timeline
to
the
exit
criteria
area,
so
keep
an
eye
on
the
exit
criteria.
I
actually
shared
a
tweet
recently.
That
is
pretty
exciting,
just
in
terms
of
the
progress
that
we've
made
in
Q4
already,
but
the
criteria
is
really
around
quality
of
service,
latency,
developer,
experience,
user
experience
and
billing,
and
we
lay
this
all
out
and
it's
all
laid
out
in
the
graph
blog
and
then
Brandon
also
put
out
a
tweet
kind
of
double
clicking
into
all
of
it
and
also
looking
back
on.
A
You
know
the
journey
to
where
we
are
today.
But
one
thing
you
know
here:
oftentimes
people
will
say:
oh
decentralization,
doesn't
matter
users
don't
care
about
decentralization,
and
you
know
maybe
users
don't
care,
but
they
don't
need.
They
shouldn't
need
to
care,
because
the
infrastructure
and
the
applications
should
be
decentralized.
We
should
care
and
there's
a
good
analogy
between
Tesla
and
what
the
graph
is
doing.
A
So
before
people
said
you
know
no
one's
ever
going
to
buy
an
electric
car,
but
then
Tesla
kind
of
leveled,
the
playing
field
and
made
it
cheaper
to
buy
an
electric
car
and
everyone
adopted
and
many
people
have
adopted.
The
electric
car
and
I
think
the
graph
is
doing
similar
with
decentralization
we're
going
to
make
it
better,
faster,
cheaper
and
it's
just
a
no-brainer
to
use
decentralized
infrastructure.
And
so
that's
the
journey
that
we're
on
currently.
A
C
C
Yeah,
and
that
actually
relates
to
our
SEC,
our
next
question,
which
I'll
say
and
then
and
add
some
more.
But
would
you
share
some
more
about
GRT
volatility
for
developers
and
how
that's
being
addressed
so
the
the
Fiat
on-ramp,
the
recurring
billing
and
payments
the
subscriptions
are
all
to
enable
people
to
have
a
SAS
front-end
experience,
while
still
leveraging
the
decentralized
power
of
a
decentralized
network
in
the
back
end.
C
So
what
we're
trying
to
do
is
make
sure
people
don't
need
to
when
one
of
the
price
volatility
experiences
so
far
is
holding
GRT
and,
as
GRT
goes
up
and
down,
because
queries
are
priced
in
USD
that
can
affect
their
purchasing
power
if
they
hold
one
or
two
months
of
GRT
and
with
a
subscription
or
recurring
payments.
Essentially,
when
an
invoice
comes
out,
they
would
pay
with
USD
credit
card
ACH,
whatever
it
may
be,
and
that
automatically
transitions
to
GRT
in
the
back
end,
which
will
abstract
all
of
that.
What
will
still
enable
the
work?
C
A
C
Last
question
I
think
we
have
here
is
just
understanding
what
the
mips
program
is
my
great
migration
infrastructure
program.
So
if
we
can
dive
in
on
what
that
is,
why
why
it
is
there
and
we
could
always
go
into
numbers
too,
on
what
that
looks
like
from
the
foundation
Eva,
you
probably
take
that
yeah.
B
For
sure,
so
mips
is
migration.
Infrastructure
providers
and
it's
basically
an
incentivized
program
similar
to
an
incentivized
test
net
to
have
our
indexers
start
supporting
new
chains
on
the
network,
so
right
now
or
prior
to
mips,
launch.
We
only
supported
ethereum
gnosis
chain
was
the
first
chain
that
we're
doing
and
we
have
a
cycle
per
chain.
So
really
it's
just
about
getting
these
indexers.
B
B
The
indexers
have
been
testing
over
the
last
few
weeks,
and
this
means
that
we're
kind
of
moving
towards
being
able
to
migrate
all
the
subgraphs
for
those
chains.
So,
for
example,
we
started
with
gnosis
first
because
they
were
very
aligned,
there's
quite
a
few
subrop
users,
but
we'll
be
rolling
out
every
chain
subsequently,
and
our
goal
is
that
we
don't
need
to
have
sort
of
this
hand
holding
experience
per
chain.
B
It's
just
the
first
few
that,
because
this
is
brand
new
for
our
indexers,
but
hopefully
we'll
be
able
to
do
this
much
quicker
and
eventually
this
will
just
be
sort
of
the
community
submitting
gips,
saying
hey.
We
want
to
support
this
new
chain,
the
council
and
the
community,
then
passing
it
and
those
indexers
then
just
running
those
notes,
and
at
that
point
all
the
subgraphs
that
are
supported
for
that
chain
can
be
migrated
to
yeah.
A
I
think
it's
worth
mentioning
too.
This
is
a
similar
process.
As
early
days
of
the
hosted
service
we
started
out
with
just
ethereum.
We
started
out
with
a
handful
of
developers,
we
really
iterated
for
them,
and
then
we
saw
kind
of
escape
velocity
and
in
terms
of
new
subgraphs
being
created
in
terms
of
new
chains
being
added
and
I.
Think
the
decentralized
network
is
very
similar
as
we
onboard
new
chains.
That
process
becomes
a
lot
easier
over
time.
B
And
then,
in
terms
of
rewards,
we've
allocated
75
million
GRT
for
the
entirety
of
this
program,
so
50
million
GRT
is
being
awarded
to
indexers
as
grants
and
they're
basically
competing
at
the
per
chain
level.
We
even
have
a
leaderboard
that
you
can
check
out
on
our
website
currently
for
the
gnosis
indexers
and
then
25
million
GRT
has
been
allocated
as
migration
grants
to
all
the
subgraphs
and
daf
Developers
for
these
multi-chain
subgraphs
to
really
make
sure
that
their
process
is
smooth.
C
C
Just
reach
out
to
me
directly
Simone,
a
senior
solution,
engineer
and
I
are
helping
run
this
program,
making
sure
everyone's
comfortable
on
the
process,
the
scripting,
understanding,
everything
and
making
sure
people
are
technical
enough
to
walk
folks
through
the
whole
migration
process.
So
happy
to
reach
out
to
me
happy
to
take
a
call
zoom
and
we
can
hop
into
a
chat
and
then
I'll.
Add
you
to
the
subgraphed
out
Discord,
if
you're
still
interested.
B
A
Foreign
great
well
thanks
everyone
for
joining.
We
appreciate
it
feel
free
to
reach
out
we're
happy
to
set
up
one-on-one
calls
anytime
to
answer
any
other
questions
that
you
may
have,
and
we
will
share
this
recording
with
you
so
feel
free
to
share
that
to
your
your
communities.
Thank
you.
So
much
see
you
all
soon.