►
Description
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
A
We
have
the
gnosis
team
with
us
today,
which
I'm
very
excited
about.
They
are
going
to
be
teaching
us
about
the
best
practices
for
running
an
archive
node
in
the
gnosis
chain,
and
so
we
have
Ricky
here
who's
going
to
do
an
introduction,
and
let
us
know
a
bit
about
himself.
B
So
hi
guys
so
yeah
has
already
said
basically
I'm
involved
with
devops
at
niosis.
B
We
try
to
do
our
best
to
keep
niosis
blockchain
service
is
running
and
helping
out
other
teams
to
to
achieve
their
goals
with
projects
around
the
news's
chain.
Yep.
A
Wonderful
great
well,
let's
get
into
today's
conversation,
so
I'm
just
going
to
go
ahead
and
share
my
screen,
so
folks
can
see
the
presentation
that
we
have
just
bear
with
me.
One
moment.
C
A
A
Great
awesome
cool
well
also,
if
jackmo's
still
here,
but
if,
if
not
then
Ricky,
if
you
could
take
us
into
the
presentation,
that
would
be
fantastic.
B
B
This
is
something
that
hasn't
happened
at
the
yet
on
the
gnosis
Chain,
because,
as
you
know,
it's
it's
a
little
bit
different
from
ethereum.
B
We
run
on
a
different
algorithm
called
Aura
and
we
need
to
take
all
the
proper
consideration
and
we
are
doing
all
the
proper
tests
with
Shadow
Forks
Etc
in
order
to
do
the
merge
properly
and
we
hope
to
achieve
this-
I
mean
as
soon
as
possible,
because
the
merges
are
really
important
because
and
for
any
blockchain
really
because
I
mean
a
lot
of
Advantage
so
scaling
and
also
is
much
better
for
the
environment.
So
the
sooner
the
blockchain
will
get
there.
The
better
is
oh
yeah.
We
can.
B
We
can
continue
with
the
next
slide,
yeah,
okay,
how
to
run
an
archive
node
onions.
So
since
we
are
still
premiered,
we
will
focus
on
the
execution
layer.
So,
in
this
case,
with
nethermind,
you
know
there
are
different
kind
of
clients
that
you
could
use
in
order
to
to
run
the
execution
layer
on
a
blockchain,
and
we
will
focus
today
on
nethermind
and
we're
prepared
for
you
a
database
snapshot
that
is
hosted
and
yeah.
Basically,
since
we
need
to
provide
this
database
in
a
secure
way,
we
have
all
studied
behind
the
CDN.
B
So
in
this
way
you
bought
us-
and
you
will
will
basically
be
able
to
to
get
that
snapshot
that
possibly
quickly
and
also
in
a
way
that
is
secure
and
also
we
needed
to
create
downloader
app
due
to
some
limitation
of
the
CDN
that
will
not
allow
to
download
the
ADB.
That
is
more
than
30
gigabyte.
But
currently
our
database
is
around
two
terabyte.
So,
given
this
Baseline,
we
basically
needed
to
find
a
solution
that
was
a
user
friendly
for
you
and
it
was
also,
let's
say,
cost
effective
and
savior
for
us.
B
So,
let's
start
with
the
requirements
of
your
machine,
so
you
could
run
another
mind
in
any
in
any
news
we
possibly
will
with
Ubuntu,
because
it's
the
the
deals
that
is
mostly
used
for
running
anode,
then
CPU
to
course
Ram
8,
gig
disk.
It
should
be
a
higher
than
this.
So
in
order
to
in
order
to
be
able
to
to
get
the
the
database
and
running
properly,
so
we
usually
have
a
disk
of
around
at
least
three
terabyte
and
yeah.
B
B
A
B
Great
so
yeah
I
cannot
see
now
the
screen
I've
lost
it.
B
Okay,
okay,
so
hey
I,
I,
don't
know
why
sometimes
I
see
the
slide
and
other
times
it
disappear.
Maybe
there
is
some
issue.
B
B
I
can
actually
let
me
let
me
open
in
full
screen,
and
maybe
it's
my
browser.
Okay,
now
I
should
be
able
to
see
it
Okay.
So,
okay.
So
in
order
to
to
prepare
for
the
merge,
because,
yes,
we
are
not
yet
there,
but
if
we
are
prepared
this
better.
Basically,
what
are
the
client
provider
doing?
They
are
embedding
all
the
specification
for
the
chain,
so
the
the
Genesis
file
inside
and
changing
things
inside
the
the
actual
client.
B
So,
for
instance,
there
are
two
events
that
should
happen
in
order
for
the
merge
to
succeed.
First
is
the
Bellatrix
event
and
is
what
basically
ethereum
has
done
on
the
6th
of
September
and
then
a
a
terminal
at
the
terminal.
Total
difficulty
will
be
picked
up.
That
is
basically
the
point
in
time
where
the
consensus
layer
is
gonna
start
to
lead
the
the
charge.
Basically,
so
it's
gonna
start
to
send
in
information
to
the
to
talk
with
the
execution
layer
and
and
yeah
basically
is
gonna
pass.
B
The
execution
layer
is
gonna,
pass
the
ball
to
the
the
consensus
layer
and
we
will
start
to
talk
about
the
staking
and
not
anymore,
about
mining.
Basically,
so
can
you
use
CL
client,
I
I?
Will
try
also
to
to
to
answer
to
some
question.
Meanwhile,
can
we
use
an
ecl
client
or
is
Lighthouse
they
only
so
a
I.
We
are
testing
several
ones.
B
We
are
testing
Lighthouse
prism,
we
are
testing
load
star
and
techu
and
I
would
suggest
to
go
with
any
of
these
four
with
the
one
that
you
with
the
one
that
you
prefer
so
yeah,
but
I
personally,
like
the
the
the
couple,
never
mind
the
lighthouse
so
but
it's
just
a
personal
taste
when
merge,
ER
I
cannot
give
a
date
because
we
do
not
yet
know
it
and
I'm,
not
the
the
person
that
it
is
gonna
decide
when
it's
gonna
happen.
B
Okay,
so,
let's
see
make
sure
so
make
sure
you're
running
version
of
the
execution
layer,
client
that
supported
the
merge
yeah.
So
you
have
to
update
your
execution
layer
and
so,
for
instance,
I
think
we
never
mind
are
at
1.14.2,
and
this
is
the
latest
one
so
be
sure
that
the
execution
layer
is
up
to
date
and
then
make
sure
that
the
execution
layer
client
is
fully
synced.
B
This
is
really
really
important,
because
otherwise,
when
you
kick
off
the
consensus
layer
and
it's
gonna
start
to
talk
with
the
execution
layer,
basically
the
consensus
layer
should
have
already
a
good
overview
of
what
is
happening
in
in
the
blockchain.
So
the
execution
layer
must
be
synced,
and
this
is
really
important.
You
cannot
to
start
them,
maintain
them
without
the
execution
layer
being
already
synced.
B
E
B
C
B
Want
my
kids,
it's
on
okay,
perfect,
so
let's
continue
okay,
so
as
soon
as
the
execution
layer
is
synced.
What
you
have
to
do
you
have
to
so,
basically,
in
order
to
allow
the
execution
layer
and
the
consensus
layer
to
talk
in
a
secure
way.
B
B
Okay,
sorry
guys,
so,
let's
continue.
I
was
saying
that,
in
order
for
the
consensus
layer
and
execution
layer
to
talk,
there
should
be
a
security
mechanism
that
will
allow
them
to
talk
in
in
a
single
way.
Sorry
for
the
repetition.
In
this
case
a
the
client
have
chosen
to
use
a
Json
web
token.
This
could
be
generated
by
you
in
different
way.
B
B
It
is
basically
the
only
difference,
setup
that
you
will
have
post
merge
so
Json
web
token,
plus
opening
this
engine
airport
on
the
execution
layer
plus
pointing
and
use
the
same
Json
web
token
on
the
consensus
layer.
That's
it
so
get
prepared
for
the
merge,
okay,
so
yeah
we
can
go
to
the
next
slide.
Thank
you.
B
A
Right,
let's
get
into
questions
I
see
that
people
have
already
been
asking
questions
on
the
way
which
is
great
I'm.
Just
gonna
unmute
Giacomo
see,
if
he's
able
to
also
hop
into
the
conversation
and
yeah
Ricky
and
Jack
mode
for
free
to
answer
any
questions
and
everyone
else
feel
free.
C
B
Okay,
is
there
any
reason
why
I
can
use
a
standard,
HTTP
client
call
to
download
the
archive
snapshot?
So
yes,
there
is.
There
is
a
reason,
so,
as
I
was
saying
basically
for
security,
a
reason
since
it's
a
big
file
and
we
could
get
the
fluid
of
requests,
so
we
could
be
attacked
because
niosis
is
I
mean
sometimes
I
can
do.
Take
us
as
a
Target,
so
we
needed
to
secure
it
in
a
proper
way.
So
the
file
has
been
put
behind
the
CDN
and
unfortunately,
CDN
have
got
a
limitation.
B
In
this
case.
A
cloud
front
does
not
allow
you
to
download
the
file
cached
that
are
bigger
than
30
gig.
So,
in
order
to
achieve
a
full
download,
we
needed
to
provide
I
mean
it's
possible
also
to
do
with
code,
and
but
you
will
need
to
it-
wouldn't
been
a
user
friendly,
so
we
provided
the
download
manager,
and
so
this
download
manager
does
chunk
the
file
in
multiple
pieces
and
then,
after
you
have
downloaded
it,
it
merged
them
together.
So
it
was
just
to
facilitate
you
guys
to
download
it.
B
B
B
Hey
I
mean
we
we
could
we,
we
really
had
the
I'm
using
to
use
it
you're
right
guys.
We,
we
will
gather
all
this
feedback
and
provide
a
better
solution.
That
is
I
mean
that
is
good
for
you
for
the
community,
so
yeah.
We
are
learning
by
doing
at
the
moment,
so
yeah.
B
So,
actually,
you
can
start
from
a
specific
part,
I
I'm
answering
to
a
Chris
dottete.
If
you
add
a
dash
p
and
let's
say
you
want
to
start
on
a
part
230.,
you
can
restart
from
there.
B
I
know
I
know,
I
mean
I,
know
that
the
software
should
simplify
our
life,
but
really
that
the
tool
was
put
together
in
a
few
days.
So
it's
it's
not
any
anywhere
near
being
robust,
but
official
request.
We
will
take
it
in
consideration
and
we
will.
We
will
try
to
do
our
best
and
really
it's
a
public
repo
so
feel
free
to
rise
issue.
Also
there,
because
I
guess
they
would
be
taken,
I
mean
I.
I
will
leave
it
there
and
then
you
know
the
act
on
it.
Basically,
yeah.
B
B
B
Also
guys,
if,
for
any
one
of
you
that
runs
on
AWS
their
nodes,
it
could
be
good
to
I
mean
we,
we
could
even
share
the
EBS
snapshot
that
it
will
be
like
instantaneous.
So
you
will
never
know
the
running
in
a
few
minutes
really.
So
if
that
is
an
option
for
you,
we
can
take
it
in
consideration
and
share
with
you
an
EBS
snapshot
to
your
AWS
account.
So
yeah.
D
That's
awesome,
Ricky.
How
can
people
reach
out
for
that
like?
Is
there
a
is,
would
you
make
the
EBS
snapshot
broadly
available
and
people
just
need
the
EBS
snapshot
identifier,
or
would
you
share
it
with
specific
accounts,
I.
B
Mean,
let's
see
because
we
could
actually
think
on
this
with
the
graph
team
and
base
it
on
your
feedback.
We
can
find
that
the
best
solution
that
you
think
it's
suitable,
so
yeah.
D
B
Yes,
yes,
yes,
yes,
you
can
reach
out
to
me,
but
I
will
need
to
to
speak
with
other
team
and
yeah.
So
I
do
not
think
that
today
will
be
possible.
Maybe
tomorrow
we
can
have
something
set
up
so
yeah,
but
anyway,
as
soon
as
possible,
because
we
want
you
guys
to
run
your
nodes
as
soon
as
possible.
F
B
We
didn't
actually
talked
about
this,
but
also
really
guys
your
feedback
will
be
gold
in
this
case.
So,
based
on
your
needs,
we
can
decide
like
a
time
frame
which
we
are
gonna
upload.
The
new
snapshots
so
yeah.
B
Think
yeah
it
was
made
in
August.
It's
a
it's
quite
the
reason
that
so
you
really
by
using
that
snapshot,
you
should
be
able
to
be
up
to
speed
in
really
I
mean
yeah
really
quickly.
C
B
Hey
guys
thanks
a
lot
for
all
your
feedback,
because
you
are
helping
us
a
lot.
B
E
Yeah,
so
if
you,
if
you,
if
you
sing
from
scratch,
then
let's
say
the
current
size
of
the
database
of
the
Netherland
is
around
1.9
terabytes.
E
So
at
least,
if
you
think
from
scratch,
I
will
say
three
terabytes
yeah
no
less
than
two
terabytes
but
yeah.
If
you
download
the
the
copy
of
the
database
from
yeah
through
the
downloader
app,
then
yeah,
the
double
of
the
site,
so
yeah
around
five
terabytes
and
also
yeah
having
a
more
distributed
version
of
the
database
would
be
great.
So
if
you,
if
any
one
of
Yeah
Yeah
from
the
community,
should
start
a
torrent.
Also
please
reach
out,
and
let's
see
how
we
can
also
contribute
and
also
I,
know.
E
I
know
that
there
are
plans
to
yeah
for
the
Netherland
team
to
support
to
introduce
support
for
snapshot,
sync,
which
actually
is
only
supported
by
GIF
clients
on
mainnet,
so
hopefully
in
the
next
future.
Yeah
the
Netherland
client
will
support
snapshot
sync
as
well,
so
this
will
lower
the
amount
of
time
needed
to
get
up
to
speed
on
on
the
network.
E
Yeah,
a
snapshot
sync
is
basically
Chris
is
basically
instead
of
thinking
from
scratch
to
basically
download
the
copy
of
the
database
from
appear.
E
So
you
don't
have
to
go
through
the
downloader
app
in
the
case,
since
you
will
be
downloading
the
the
copy
of
the
database
yeah
that
that
would
be
automatically
handled
by
the
Netherland,
Clan,
client
or
well,
better
and
better,
say
the
the
client
and
the
specific
client
in
this
case,
guess
which
is
the
only
one
supporting
it
at
the
moment,
and
so
the
process
is
quite
straightforward,
since
you
don't
have
to
do
anything.
I
just
set
the
node
to
to
operate
on
Snap
sync
mode,
and
once
you
download
the
the
latest
snapshot.
E
Let's
say
this
depends
on
obviously
on
how
often
the
the
other
nodes
take
snapshots
on
their
end.
So
once
you
die,
you
have
downloaded
it.
Then
you
will
start
syncing
on
top
of
that.
The
snapshot
so
yeah
the
overall
the
overall
time
to
to
get
to
the
latest
Block
it's
as
you
can
understand.
There
is
really
little.
E
It
depends
on
on
how
it
is
configured,
because
if,
if
they
are
I
mean
if
it
really
depends
on
the
configuration,
because
if
these
snapshots,
yeah
probably
there
from
the
guest
team
and
the
Netherland
team,
will
also
try
more
more
information.
E
E
Okay,
are
there
any
any
other
questions
relate
to
yeah
how
to
run
yeah
nodes
on
Northeast
chain.
Otherwise,
if
there
are
more
questions
able,
please
could
you
collect
them
and
also
provide
them
with
that
to
us.
I
will
be
happy
to
to
answer
them
and
also
yeah.
E
We
also
got
a
lot
of
feedback
and
many
many
many
hints
and
points
for
improvement
that
would
make
yeah
our
lives
easier
many
times
many
okay,
so
such
as,
let's
say
the
SnapChat
thing,
yeah
having
a
snapshot
sink
for
archive
notes,
probably
would
be
also
interesting.
Let's
see
how
teams
can
Implement
that
but
yeah,
let's
start
with
telling
them
that
there
could
be
also
a
good
feature
to
include
in
their
nodes.
A
Yes,
we'll
definitely
message
over
any
questions
that
aren't
fully
answered
here
so
that
you
guys
can
come
back
to
them.
I
see
that
stake
stake.
Machine
is
typing.
A
Oh
Chris
is
typing
if
any
yeah,
as
as
we
mentioned,
this
is
kind
of
the
last
call
for
questions.
So,
if
you
guys
have
any
questions
either
in
the
chat
or
voice
feel
free
to
ask
away
I
feel
that
voices
quicker.
So
if
anyone
wants
to
unmute
feel
free
to.
C
E
D
Have
a
quick
question
so
we're
we're
seeing
that
Aragon
and
ericon
derivatives
like
akula
are
emerging
as
kind
of
the
next
generation
of
evm
execution
nodes,
and
it
looks
like
you
know.
Certainly
a
lot
of
the
ecosystem
is
recognizing
that.
D
Yeah,
a
lot
of
the
improvements
that
that
Aragon
brings
to
the
table
are
like
pretty
important
for
these
chains
to
continue
to
scale
like
particularly
with
things
like
State
bloat
and
yeah
I'm.
Wondering
like
how
the
gnosis
team
is
thinking
about
that
and
whether
there
is
an
intention
to
bring
Aragon
support
to
nurses
chain.
E
E
Really
soon
on
yeah
on
office
chain,
and
that
version
will
also
support,
support
The
Merchant
of
this
chain,
so
yeah
they
they
are
really
I
mean
the
air
gun
team
is
really
committed
to
yeah,
releasing
softwares
that
will
be
embracing,
also
noses
chain
and
yeah.
E
Not
this
chain
on
the
other
side
is
also
committed
to
help
everyone
or
never
mind
Eric
on
and
other
teams,
clients
and
then
developers
on
yeah
or
boarding
them
on
the
chain
and
helping
them
building
and
propose
any
any
kind
of
solutions
that
would
be
beneficial
for
for
everyone
and
for
the
whole
ecosystem,
so
yeah
to
do
to
answer
your
question.
Yes,
we
are
supporting
edible,
such
as
we
are
supporting
other
teams
and
clients
on
on
a
building
on
top
of
nurses
chain.
D
It
does
thank
you
so
much
and
super
excited
to
see
our
support.
Coming
for
nurses,
too
yeah.
E
And
thank
you
for
pointing
out
the
this.
Does
nothing
for
yeah
for
archive
notes.
Actually,
the
last
time
I'm
I
used,
yeah
I
said
and
a
full
note
to
to
think
of
nerves
and
snap
thing.
You
know
it
was
an
opening
video
one
and
then,
after
that,
I
I
didn't
I.
I
didn't
go
through
yeah,
the
latest
updates,
but
yeah.
E
Hopefully,
hopefully
this
you
know
this
snap
thing
for
archive
notes
could
be
probably
also
the
the
community
would
could
also
potentially
help
on
that,
and
you
know
with
yeah
proposing
features
and
so
on
so
yeah.
Let's
see
we
let's
see
first,
if
they
they
come
with
something
from
for
the
nurses
chain.
Let's
see
if
it's
just
a
full
node
a
Snapchat
thing,
and
if
that
works
first
and
then
let's
try
to
get
it
to
the
next
stage
and
also
enable
snap
sync
for
archive
notes.
E
Yeah,
unfortunately
open
your
video
is
well
actually
a
few.
A
few
providers
I
believe,
are
still
running
open
field
notes
not
on
an
ethereum
chain,
of
course,
but
yeah
on
on
other
ones,
but
yeah,
it's
deprecated.
So
if
you
have
any
any
opening
Freedom
notes
running
somewhere
on
your
machines,
taking
the
account
to
to
migrate
to
another
client.
D
I
guess
another
question
that
that's
maybe
a
little
bit
less
related,
but
I
think
is
maybe
somewhat
relevant
for
for
node
Runners,
so
I
understand
that
like
gnosis
chain
today,
you
know
is
obviously
you
know
just
an
execution
like
the
you
know.
It's
a
monolithic
chain
today
and
and
like
the
merge,
will
move
it
into.
D
You
know
the
the
kind
of
knows
to
speak
and
chain,
and
then
the
execution
client
will
be
separate
and
I
I
know
that
today,
obviously
you
guys
don't
use
proof
of
work,
you
have
a
custom
consensus
mechanism
and
I'm
wondering
about
you
know.
It
sounds
like
that
custom
consensus
mechanism
will
basically
be
deprecated
when
the
merge
happens
and
the
gnosis
beacon
chain
will
then
be
the
consensus
mechanism
for
gnosis
chain.
D
I
I'm,
conscious
that
if
I
remember
correctly,
the
nurses
Beacon
chain
has
block
times
that
are
half
that
of
the
ethereum
beacon
chain.
Is
that
right,
and
does
that
mean
like
we
can
expect
stake
growth
to
be?
You
know
roughly
twice
what
we
see
on
Main
I
guess
it
depends
on
utilization
as
well,
but
yeah.
Can
you
talk
a
bit
about
that
and
maybe
like
the
pre
and
post
gnosis.
E
So
that's
a
really
good
question
Chris.
So
as
of
now,
you
know
the
con.
The
current
consensus
algorithm
for
nurses,
Chinese
aura
and
this
algorithm
doesn't
doesn't
run
on
yeah.
It
doesn't
rely
on
proof
of
work
proofs,
but
instead
there's
a
set
of
validators
that
basically
are
enabled
to
validate
transactions
for
the
chains
or
kind
of
proof
of
stake,
with
some
yeah
minor
changes.
E
The
way
nurses
chain
will
work
after
the
merge
is
basically
the
consensus
layer
where
basically,
the
the
beacon
chain,
the
nose
is
Beacon
chain,
will
take
over
the
consensus,
part
and
yeah
validate
transactions
and
send
them
to
the
execution
layer
for
final
execution.
So
the
idea
is
to-
and
indeed
the
validators
that
yet
today
are
currently
validating
transactions
on
nurses
chain
will
become
worthless.
E
Once
we
merge
the
nurses
chain
with
the
beacon
chain,
since
the
consensus
layer
will
take
over
the
you
know,
the
the
consensus
for
the
for
the
chain,
so
noses
will
will
be
migrating
towards
yeah,
definitely
toward
the
proof
of
stake,
a
fully
proof
of
stake
a
chain
after
the
merge
and
also
there
are
plans.
Actually
there
are
some
discussions
around
how
and
when
and
we
we
should
get
rid
of
the
aura
consensus
in
which
way.
E
So
there
are
some
ongoing
tests
helped
by
the
community
and
by
nethermine
by
gnosis
and
other
parties.
That's
why
yeah
we
are
confident
we
can
make
the
match
really
soon,
but
still
we
we
must
be
cautious,
because
we
must
be
hundred
percent
sure
that
after
the
match
happens,
everything
will
be
working.
Fine,
so
yeah.
To
answer
your
question
and,
to
recap
yeah:
we
will
migrate
from
Aura
into
yeah.
E
Let's
say:
approval
stake,
consensus,
algorithm
and
nurses
chain
yeah
Beacon
chain;
sorry,
yes,
the
the
amount
of
so
basically
the
the
epochs
with
slots
slots
to
be
specific
are
half
of
the
half
of
the
timer.
If
you
compare
with
ethereum
ones,
so
it
means
that,
ideally,
the
change
should
be
two
times
faster,
so
that's
the
current
setup
and
yep.
E
So,
as
you
know,
it's
all
being
tested
yeah
the
beacon
chain
actually
is
already
available
and
anyone
can
can
join
it
and
run
validators
so
that
you
you
can
you
you
can
join
the
network
at
at
any
moment.
You
want
on
the
docs,
there
are
there's
a
guideline
explaining
how
to
deposit
genosis
chain
and
yeah
enable
your
validators
if
you
want
to
stay
in
the
start,
validating
transactions
on
the
Bitcoin
chain,
but
yeah
for
the
moment.
E
E
Actually,
I
don't
know
it's
around
13
15
I
guess
something
like
that.
E
Both
static
peer
configuration
prognosis
chain,
execution
nodes,
you
mean
like
setting
up
a
boon
notes.
What
do
you
mean
increase.
D
I
mean
I
I'm
sure
that
you
know,
like
the
X
guy
under
like
the
X-Type
configuration
that
nethermine
ships
with
specifies.
You
know
built-in
boot
nodes
and
so
on,
but
I'm
just
wondering
like
with
your
experience
operating
these
these
nodes,
you
know,
do
you,
do
you
pass
any
like
static
peer
configuration
like
if
you
run
maybe
five
nodes?
Do
you
specify
each?
You
know
each
of
the
nodes
as
peer
nodes
for
each
other,
or
do
you
kind
of
just
let
the
node
figure
it
all
out.
E
Yeah,
okay,
this
depends
on
how
fast
you
wanna
you
wanna,
learn
how
to
to
bring
up
and
and
start
thinking.
You
know
as
far
as
yeah,
based
on
my
experience,
you
shouldn't
take
more
than
a
couple
of
minutes
to
start
thinking
but
yeah,
even
though
even
so
I
saw,
let's
say
multiple
times
notes
unable
to
to
start
thinking,
because
no
peace
were
available.
So
probably
it's
just
because
you
know
the
algorithm
is
distributed.
E
The
routing
algorithm
requires
some
time
to
to
reach
out
to
yeah,
to
to
peace.
In
that
case
yeah.
If,
if
you
by
chance,
have
more
nodes
running-
or
at
least
you,
you
know,
someone
who
runs
nodes
and
you
can
ask
them
to
provide
you
with
the
the
enote.
E
Well,
the
the
yes,
the
E
note,
and
then
you
can
add
that
to
your
configuration,
at
least
for
sure,
you
know
that
at
one
peer
and
it
will
be
available
when
you
start
your
node,
so
yeah
for
most
of
the
configurations,
I
saw
I,
seen
no
static.
Ipa,
at
least
at
least,
was
was
needed
by
yeah
in
in
a
few
cases
when
nodes
were
not
bringing
up
yeah,
we
had
to
set
up
static,
IPS.
E
E
E
Chain,
actually,
there's
no
faucet,
since
basically
I
mean
the
faucet
will
be
someone
who
sends
you,
some
general
stockings
actually
actually
not
and
there's
no
faucet
for
the
beacon
chain.
Sorry.
E
Okay,
they're
not
I'm,
running
a
Tom
instructing
for
a
beer,
yeah,
also
yeah.
There
can
be
many
reasons
after
you
restart
the
node.
If
you
still,
if
you
are
still
experiencing
a
beating
issues,
probably
will
make
sense
to
to
specify
and
the
static
aesthetic,
IP
yeah.
F
E
Address
and
and
restart
the
node
again
and
see
whether
they,
whether
it
can
can
start
thinking
I,
know
at
least
on
open
ethereum.
You
could
specify
the
amount
of
peers,
the
minimum
amount
of
speeds
you
you
wanted
to
maintain
and
making
obviously
the
node
to
consume
more
run
resource,
since
he
had
to
do
more
discovery
on
the
network
and
not
sure
about
nethermine
whether
it
supports
that
that
feature,
but
in
case
they
they
do
I
will
say
you
can
also
increase
the
amount
of
the
amount
of
peers.
E
Yeah,
generally
speaking,
it
should
not
be
a
problem
to
find
out
peers.
It's
just
a
matter
of
time.
You
know
between
the
moment.
You
start
there
and
now
then,
when
the
node
finds
some
available
appears
but
yeah.
If
you,
if
you
are
aware
of
other
index
indexer
providers,
you
can
yourself
exchange
your
e-nodes
addresses
and
and
put
them
and
configure
them
on
on
your
node.
A
All
right
well,
as
I
mentioned
in
the
chat,
we're
at
the
top
of
the
hour,
so
we'll
just
wrap
up
with
final
questions
comments.
Anyone
feel
free
to
unmute
your
mic
or
type
in
the
chat
and
and
then
yeah
after
that,
we'll
wrap
up
today's
conversation.
A
That's
really
that's
really
nice
to
hear
Derek,
they're,
very
excited
for
indexing
nurses,
data
and
a
nice
meme
there
Chris
great
well
I'll,
take
this
opportunity
to
wrap
up
today's
conversation.
I
just
want
to
say
a
big
thank
you
to
Giacomo
and
Ricky
for
joining
us
for
today's
conversation,
answering
everyone's
questions
and
thank
you
all
for
attending
and
also
asking
your
questions
as
well.
A
So
as
we
normally
do
we're
going
to
have
a
workshop
again
next
week,
Tuesday
and
Thursday
so
be
sure
to
lock
into
the
calendar
so
that
you
can
stay
up
to
date
with
everything.
Thank
you
all
for
attending
and
we
look
forward
to
seeing
you
next
Tuesday
take
care.