►
Description
Topics covered
----------------------------
00:49 - Client introduction
1:20 - Guest’s introduction
3:16 - Nethermind History
5:08 - Nethermind core team
6:20 - Nethermind - the company
8:25 - April 2021 - Rayonism + Ray Tracing
10:00 - October 2021 - Amphora Interop
11:37 - 2021-2022
13:55 - EIP-5133 (June 2022)
15:34 - People of the Merge
25:55 - About Nethermind client
29:37 - Post-merge and Onwards
30:31 - Get in touch
30:45 - Q&A
31:20 - Why Nethermind doesn’t support mining?
34:00 - Is there any plan for a beacon chain client?
36:31 - Posmoni- does it work with a specific combination or open for all?
38:54 - Syncing issue post Gray glacier upgrade
40:39 - What are config issues? What are common pitfalls where a client node runner needs to be careful about?
44:18 - Nethermind performance during interop sessions
47:40 - Preferred or best EL & CL client combo
49:27 - Thoughts on Client diversity. How will Nethermind increase network share post merge?
52:38 - Where can we find resources for running Nethermind nodes?
54:25 - Any message for the Ethereum community?
Resources:
-----------------
TheMerge playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqoLxXqZqT4hcYhoHoP6w12
KnowYourClient - https://www.youtube.com/playlist?list=PL4cwHXAawZxoruie1hmYWJfiakpYivXft
PEEPanEIP playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2
Follow at Twitter
-----------------------------------------------
Tomasz K. Stańczak @tkstanczak | Pooja Ranjan @poojaranjan19
Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herde...
Contact Ethereum Cat Herders
---------------------------------------------------
Discord: https://discord.io/ethereumcatherders
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
GitHub: https://github.com/ethereum-cat-herde...
Email: support@ethereumcatherders.com
Website: https://www.ethereumcatherders.com/
A
With
multiple
options
to
pick
a
client
for
node
running
ethereum
is
the
most
decentralized
blockchain
network.
The
merge
upgrade
makes
it
mandatory
to
run
an
execution
client
to
participate
as
a
validator.
We
hope
today's
talk
will
help.
You
learn
about
execution,
client
provider.
That
may
become
your
favorite
client
for
note,
running.
A
So
nethermine
is
an
ethereum
execution
client,
as
per
the
website
description.
It
is
built
on.net,
core
and
nethermine.
Clients
runs
on
linux
windows,
mac
os
and
supports
click
aura
it
hash
and
proof
of
stake
consensus
algorithm.
It
is
a
robust
client
for
ethereum
node
operators
built
for
performance
and
versatility,
we'll
get
to
learn
more
about
nethermine.
In
this
episode
with
thomas
thank
you
for
joining
us
tomas.
B
Thank
you
once
again
welcome
everyone,
so
I'll
be
talking
about
nethermind
and
emerge.
I
think
that
much
of
it
will
be
about
the
the
roads
to
the
merge,
how
we
participated
in
testing,
how
we
started
all
the
important
events
and
important
people
internally
at
nethermine,
and
that
worked
on
this
quite
extensive
set
of
changes
and
lots
and
lots
of
testing.
B
So
thanks
everyone
for
for
listening-
and
let
me
start
by
some
introduction
of
myself
of
the
team
company
and
tell
you
a
bit
more
of
a
story.
So
my
name
is
thomas
kaitenstein.
I
started
a
nether
mind
project
five
years
ago
now
and
altogether,
so
I'm
I'm
wearing
more
and
more
hats.
Nowadays,
every
every
few
months
there
is
something
new,
interesting
that
contributes
to
the
ethereum
ecosystem
as
a
whole.
B
That's
that
I
got
interested
in
so
I
keep
leading
the
nether
mind
as
a
company,
and
nowadays,
under
my
client
is,
is
a
part
of
it
important
and
big
part
of
it,
but
part
because
there's
much
more,
I'm
also
making
flashbots
so
working
on
product
management.
Architecture
of
some
of
the
mev
infrastructure
related
components
at
flashbots
and,
as
you
will
see,
this
is
all
relevant
for
the
merge
as
well.
B
B
We
we
enter
into
collaboration
with
multiple
partners,
just
to
name
noses,
flashbeds
starkware
and
many
more
energyweb,
so
the
first
crypto
winter
for
fernand
was
extremely
tough.
I
think
that,
maybe
in
a
few
hundred
years,
when
they
cut
me
through,
they
will
see
there's
like
marks
in
the
winters
and
summers.
You
know
it
will
be
probably
very,
very
visible.
B
B
These
were
three
people
that
were
dedicated,
dedicating
full-time
of
theirs
to
the
merge,
but
nowadays
it's
maybe
around
15
people
on
the
core
team
who
work
on
the
merge
in
various
ways
like
contributing
with
with
fixes
testing,
just
communicating
with
the
community,
supporting
for
research
building,
infrastructure,
testing
and
so
on.
So
infrastructure
part
in
the
merge
is
massive.
B
The
broader
core
team
at
friend
of
mine
is
around
25
people
and
they
work
also
on
projects
like
energy
web
noses,
juno
voyager.
So
all
the
things
that
are
related
to
protocol
engineer,
nederman
is
a
company.
Nowadays,
it's
over
160
people
and
practically
all
of
them
contribute
and
work
on
ethereum.
So,
as
a
company,
we
remain
loyal
to
ethereum
and
we
barely
touch
other
chains.
B
We
touch
them
like
when
running
some
validators
infrastructure
when
comparing
and
investigating
running,
like
due
diligence
and
some
research,
but
all
our
building
nowadays
is
mostly
related
to
ethereum
in
the
sense
of
we
attach
the
layer
twos
that
contribute
to
ethereum.
We
touch
side
chains
with
dutch
ethereum
itself.
B
That
would
not
be
possible.
I
mean
we
only
survived
this
death
crypto
winters,
because
because
people
were
there,
people
listened
and
and
helped
us
to
to
make
ethereum
succeed
as
well
and
also
super
important
for
us.
Since
last
year,
since
last
april,
we
got
200
internships
at
nethermines,
where
people
stayed
up
to
three
months
and
chose
any
projects
they
wanted
to
work
on
and
contributed
to
many
and
including
various
mev
projects.
Hackathons
related
sorry,
the
merge
projects
hackathons
related
to
the
merge.
Some
of
them
were
binding,
both
mev
and
merge.
B
Global
scaling,
ethereum,
which
was
part
of
this
ryan,
is
like
the
same
event
at
which
the
orionis
was
running
and
for
ryan.
Is
we
also
recorded
the
the
set
of
tutorials
that
were
showing
how
how
to
run
the
early
stages
of
the
merge?
They
were
all
based
on
on
some
of
the
tutorials
that
were
built
by
proto,
lambda
and
wukash
recorded
some
that
you
can
watch
nowadays
on
youtube.
B
Although
much
of
that
information
is
now
outdated
still
still
there,
there
are
some
things,
a
few
hundred
views,
so
I
think
that
many
people
learned
a
lot
how
to
configure
any
client
solutions
from
from
those
recordings
then
fast
forwards
to
october
2021,
and
thanks
to
the
sponsors
that
brought
everyone
together
to
fantastic
on-site.
That's
in
greece.
It
was
a
foreign
interrupt
with
this
famous
picture
of
the
first
major
success
of
people
running
everything
together.
B
B
We
are
just
running
between
the
tables
and
trying
and
pushing
each
other
to
to
to
drive
it
harder
to
see
if
it
works
and-
and
it
was
just
like
first
first
good
memory,
success
and
very
important
event
for
everyone
to
to
understand
it
for
the
next
few
months,
whenever
you'll
be
reaching
out
to
to
others,
you
just
ask
for
for
help
or
ask
for
discussion.
You
will
no
longer
think
of
just
some
random
people
on
the
in
the
internet,
but
you'll.
B
This
is
our
a
merge
or
something
that's
we're
still
waiting
for
the
big
one
or
maybe
like
two
last
big
ones,
with
the
girly
finalizing
all
the
testnets
transition
and
the
maintenance
merge,
and
I
I
think
we
should
not
be
telling
the
dates,
but
recently,
obviously
it's
quite
public
that
the
most
most
likely
dates
are
somewhere
mid
september.
That's
what
the
core
deaths
were
targeting
officially
publicly.
B
Obviously
we'll
see
how
it
goes.
We
have
to
be
absolutely
sure
that
everything
is
ready,
that
the
community
is
ready,
that
the
configurations
are
ready
and
that
there'll
be
no
mistakes.
We
still
see
problems
when
running
shadow
forks.
They
are
getting
better
and
better
each
time,
but
they
are
not
perfect.
So
obviously
we
want
to
be
absolutely
sure
to
see
some
shadow
forks
that
go
without
any
issues
whatsoever
and
then
we
are
confidently
going
through
the
merge
process
on
the
maintenance.
B
So
you
see
the
list
of
all
the
changes
we're
starting
with
kintsugi,
the
beautiful
name
reflecting
the
I
think,
the
japanese
artist
of
fixing
broken
broken
containers
faces
and
and
then
coming
back
with
the
names
of
like
kiln
and
they
and
then
building
the
first
merge
definites,
curly
shadow,
forex
maintenance,
shadow
forex.
Now,
nowadays
we
have
the
eighth
shadow
frog
of
the
maintenance
and
we
went
through
robson
and
zepalia
right.
Sebolia
was
as
a
time
and
I'm
speaking
was
yesterday.
B
All
right
so
also
another
mind.
Team
was
involved
a
bit
more
in
defining
the
ip5133.
So
obviously
this
is
just
a
formality,
but
I
think
it
was
fantastic.
It
didn't
mind
that
we
got
some
of
the
people
at
internship
involved
into
writing
the
spec
for
the
for
the
eip
for
testing
called
the
python
scripts
for
writing
some
nice
data
model.
B
For,
for
this
final
difficulty
bomb
delay,
writing
finally,
a
quite
a
good
analysis
of
of
what
exactly
we
should
expect
like
what
kind
of
delay
we
should
expect
so
like
congrats
to
all
of
those
fantastically
talented
people
and
their
minds.
That's
that's
come
for
the
internship
and
immediately
just
get
included
in
the
ip
and
got
their
aip
approved
and
then
go
for
the
hardware.
B
B
So
I'm
providing
here
a
list
of
people
that
participated
in
the
merge
from
that
of
mine
side,
and
there
are
many
more
than
those
that
you
would
see
on
the
screen.
I
read
those
names
for
those
of
you
who
cannot
read
slides
why?
I
think
it's
super
important
apart
from
obviously
recognizing
their
contributions.
B
I
think
the
merge
process
in
the
last
year
brought
to
light
a
lot,
a
lot
of
new
core
devs
that
they
were
like
starting
a
new
generation.
I
mean
like
through
the
for
the
crypto
winter.
We
had
this
all
these
people
who
participated
in
the
previous
forex,
we're
preparing
that
and
then
somehow
the
merge
and
and
the
amount
of
work
that
was
needed,
give
opportunity
to
many
people
to
just
like
show
how
skillful
they
are
and
how
much
they
can
meet
the
execution
layer,
clients,
development
in
the
future.
B
So
since
I'm
fora,
marek
moroccinski
was
leading
the
the
merge
and
engineering
at
that
mine,
matteo
chandrayevsky
was
running
all
day
like
leading
the
infrastructure
testing.
Setting
up
things
also
testing
our
infrastructure,
with,
with
a
movie
boost,
preparing
running
all
the
validators.
On
our
side,
sarah
liu
was
testing
preparing
post
merch
thing.
So,
if
you
think
about
what
is
a
post-merchant
problem,
the
synchronization
was
always
one
of
the
hardest
items
on
the
engineering
list
for
any
core
development
effort
on
the
execution
layer,
clients.
B
You
have
to
be
fast.
It's
extremely
complex
process
of
downloading
a
lot
of
data
from
multiple
network
peers
in
parallel,
verifying
everything
is
correct,
building
quite
significant,
sizeable
databases
locally
and
also
trying
to
stay
up
to
date
with
all
the
innovations
from
other
teams,
so
like
it's
really
the
trace
between
different
teams,
but
also
race
against
time
of
the
growing
state
that
makes
synchronization
such
a
challenging
thing.
So,
like
probably,
if
you
had
only
one
client,
we
would
be
10
times
worse,
but
also
synchronization
would
be
easier
process.
You
wouldn't
have
to
rush
it.
B
So
sarah
spent
a
lot
of
time
on
the
past.
Merge
sync.
So
how
we
synchronize
the
clients
equally
effectively
and
safely
after
after
the
merge
happens,
then
wukash
rosemay
was
leading
a
lot
of
development
at
nethermine
for
a
long
long
time
already
before
it
emerged
and
during
the
merge
first
he
he
really
kick-started
everything.
B
B
We
have
great
people
from
from
the
infra
and
core
team,
like
miguel
tenorio,
who
is
nowadays
building
a
tool
called
one
click,
and
this
is
for
a
very
easy
setup
for
solo
validators
to
to
run
the
entire
entire
deployment
of
the
validator,
the
beacon
chain,
client
and
the
execution.
So
all
the
consensus
layers,
pieces
and
the
execution
layer
together
like
this
complexity
of
setting
up
everything,
is
growing
a
bit
right.
B
So
if
you
want
to
be
a
solo
value,
data
running
execution
player,
you
have
three
or
four
components
and
then
maybe
you
want
to
run
an
evb
boost
as
well.
Deploying
all
of
that
together
configuration
has
a
major
effort,
so
so
miguel
is
working
on
one
click
and
then
we
have
jorge
menderos
who
is
working
on
something
that's
pretty
important
for
us.
We
work
together
with
noses
chain
to
push
for
the
opportunity
to
to
run
the
merge
on
noses
chain,
which
is
the
network
with
significant
value
on
the
network.
B
So
it's
a
mainnet
knows
this
maintenance
of
a
of
a
side
chain
of
ethereum
that
will
transition
to
the
same
format
as
ethereum
with
its
own
set
of
validators,
and
that
effort
can
help
a
lot
to
verify
like
how
post-merge
workings
of
the
of
the
entire
network.
Look
when
you
actually
have
value
and
when
something
can
be
attacked
because
of
the
potential
value
extraction.
B
Also,
it
puts
a
lot
of
pressure
on
us.
I
think,
because
another
mind
is
nowadays
the
only
client,
that's
that
will
support
noses
during
the
transition
and
well
like
there's
there's
no
chance
that
if,
if
we
fail,
then
someone
will
take
over
so
it
has
to
be
properly
tested
now.
Well,
everything
has
to
be
properly
tested,
but
here,
like
there's,
there's
no
security
from
the
from
the
client
diversity.
After
the
merge,
the
the
other
clients
will
join
and
the
noses
chain
will
be
multi-clients
again.
B
What
are
people
of
the
merch
for
nethermine?
So
all
the
community
members
that
were
testing
helping
us
fix
things
contributing
like
sending
prs.
That's
extremely
motivating,
always
that
people
are
there
and
they
try
and
use
the
anonymity
notes.
I
think
nowadays
we
have
around
three
percent
of
the
of
the
notes
on
the
mainnet,
and
this
is
growing.
So
I
really
really
encourage
you
to
to
try
another
minds
to
talk
to
us.
B
That
will
be
very
important.
Obviously,
for
the
merge
itself,
like
the
withdrawals
of
the
deposits,
all
the
ips
that
come
in
shanghai
and
then
account
abstraction
feels
like
next
to
vertical
trees
is
one
of
those
really
big
items
that
are
that
are
long-term
dream
of
what
we
can
deliver
to
improve
ethereum.
B
So
so
please
listen
to
whatever
kristoff
is
sharing
at
the
conference.
That's
that's!
It's
interesting
jared
doro,
so
he
has
been
with
the
ethereum
cat
herders
for
a
long
time
was
helping
us
a
lot
with
the
q,
a
to
all
the
tests
internally
running
the
networks,
verifying
everything
works
well,
daniel
zaradak
came
and
delivered
like
super
fast
as
snap
sync
client
that
nowadays
allows
the
nethermine
client
to
practically
spend
three
hours
in
sync
and
then
be
ready
to
process
the
blocks
on
the
mainnet.
So
it's
massive
improvement.
B
B
Of
course,
thanks
to
amazing
effort
from
the
guev
team,
that's
that
we
build
on
top
of
like
we
use
the
spec
and
and
gaff
delivers
the
servers
for
that.
So
fantastic
nikita
yakov.
So
he
was
working
on
the
authorization
so
we're
using
now
the
jwt
for
the
off
between
the
between
the
consensus
layer,
clients
and
execution
layer
clients.
B
A
B
Is
growing
like
it's
particularly
recently
another
mind,
we,
we
brought
around
10
to
new
members,
sorry
10
new
team
members
to
the
core
team
that
will
work
specifically.
On
the
another
mind,
ethereum
client-
and
this
is
also
thanks
to
the
thanks
to
the
grant
from
knows
this
chain
to
work
on
improvements
that
are
needed
for
noses.
B
So
I
think
there'll
be
lots,
lots
lots
delivered
soon
and
in
the
next
months
and
years
and
last
we
see
lots
of
people
on
the
internship
that
already
mentioned
that
worked
on
ray
tracing
on
the
hackathons.
The
merge
testing
infra
eap513,
thanks
for
listening
to
that
lease,
because
those
people
really
really
deserve
that.
I
mean
they
were
pushing
really
long
hours
to
get
that
on
time
and
they
keep
doing
that
with
this,
like
september,
calendar
date
looming
over
all
right.
B
So
maybe
a
few
more
things
about
that.
My
client,
a
bit
of
summary
of
what
I
may
have
already
mentioned
so
nowadays
with
snapsync.
So
if
you
launch
it,
this
is
a
default
sync
and
it
brings
in
around
three
hours,
possibly
obviously
depending
on
the
machine
setup.
But
this
is
without
like
two
heavy
requirements:
free
three
hours
to
being
operational
mainnet,
the
plugins
ecosystem.
B
That's
on
on
nethermite
is
used
nowadays
by
many
of
the,
like
any
researchers
who
just
write
ability
to
to
access
the
mampo
and
the
block
production
and
simulation
very
quickly
for
the
plugins
to
netmind
the
mev
support
that
is
built
in
so
the
same
way
as
there
is
mev
gaff.
So
there
is
version
of
netamine
that
allows
for
simulation
like
nanomine.
Doesn't
support
mining
and
proof
of
work
never
has,
but
it
has
the
mev
support
and
it
can
be
used
for
any
block.
B
Builder's
post
merge
and
it
was
used
also
for
for
the
other
chain.
Sidechain
technology
we
have
full
pruning,
so
the
only
necessary
state
is
being
stored
with
full
pruning
which
actually
occasionally
can
clean
the
database.
It
makes
a
copy
of
the
database
pushes
everything
there
that
is
needed
and
deletes
the
old
database
and
can
run
like
once
per
week.
For
example,
generally
in
the
minds
was
always
loved
for
the
low
disk
requirements.
It
can
skip
a
lot
of
blog
bodies
and
receipts
from
the
past.
B
So
so
much
of
that
is
coming
down
to
any
user
of
another
might
know
and
obviously
aura
positive
support
nowadays,
with
open,
ethereum
not
being
supported
anymore.
We
remain
as
the
only
implementation
they're
supporting
those
chains
account
abstraction
that
I
mentioned
from
christoph
and
and
his
team
like
jorge
and
jorge,
also
worked
on
this,
and
this
was
delivered
by
nethermine,
not
only
for
an
intermediate
client,
but
also
for
the
gaf
client.
B
B
So
here
it
is
like
one
by
one.
So,
first
the
merge.
This
is
one
one
goal
for
us
now
and
practically
being
compatible
with
all
consensus,
clients
supporting
the
merge
and
full
history
before
the
merge,
then
deploying
those
tools
that
I
mentioned:
one
click
post
money
for
all
the
solos
takers
and
anybody
who's
monitoring
the
network.
We
run
a
lot
of
infrastructure
ourselves,
so
these
are
tools
that
we
can
use
in
some
occasions
like
some
of
them
are
more
for
stalls
take
care.
Some
of
them
are
for
larger
operators.
B
Then
the
snacks
substance
server
will
be
coming
the
state
snapshots
and
all
the
increases
that
will
lead
to
a
much
better
leaner,
faster
clients
and-
and
I
think,
we're
just
keeping
this
race
going
between
all
of
the
execution
layer,
clients
which
is
much
much
needed
for
innovation
improvements,
so
yeah
invitation
to
stay
in
touch.
Please
reach
out
to
us
to
anybody
from
the
team
and
that's
from
me
and
I'm
open
to
any
questions
from
from
puja
from
community.
A
A
I
have
a
few
question
that
I
have
collected
from
the
community,
though
the
presentation
was
thorough
enough
and
it
shared
a
lot
of
information.
So
my
first
question
is
out
of
curiosity.
You
did
mention
that
nethermine
does
not
support
mining.
I
know.
Nethermind
is
currently
involved
with
ethereum
research,
the
account
abstraction,
maybe
workly,
and
everything
that
you
mentioned.
Then
why
not
mining.
B
I
thought
it
would
be
a
lot
of
work
and
potentially
additional
effort
on
on
building
up
this
relationships
with
miners,
and
I
think
that's
what
I
was
afraid
of.
That's
that
you
will
not
be
used.
So
that's
why
I
never
got
priority.
We
always
had
a
bounty
open
on
git
going
to
build
it,
and
I
think,
for
a
long
long
time
like
we
pushed
there
initially
some
relatively
small
amount
of
eight
eve
and
then
he
grew
to
like
significant
amount,
but
nobody
picked
it
up
so
like
we
just
withdrew
it
later.
B
When
we
realized
that
the
merge
is
happening
already,
so
I
decided
to
no
longer
think
of
miami.
Well,
I
looking
back.
If
I
knew,
I
would
probably
build,
smiling
much
much
earlier
and
maybe
pick
up
the
time
when
parity
was
being
decommissioned,
especially
as
this
like
the
dream
of
something
like
mev
was
in
my
head
for
for
a
long
time.
So
so
a
lot
to
see
nowadays
flashbacks
running
with
another
mind
notes.
So
it
was
missed,
opportunity
and
and
a
great
pain
yeah.
So
you
know
like
we
had
to.
A
B
Yes
again,
they
we
started
working
on
beacon,
chain,
client,
just
probably
a
few
months
after
everyone
else
started.
I
think
it's
a
known
story
that
I
I
missed
a
meeting
initializing
like
all
the
work
on
ethereum
two
and
then
later
I
was
so
busy
working
on
the
ethereum
one
that
I
have
enough
time
ready
to
attend
all
the
meetings
early
meetings,
so
it
was
a
bit
on
one
side
missed
opportunity.
On
the
other
hand,
I
think
that
this
would
be
too
much
for
the
size
of
the
team
that
we
had
there.
B
We
built
a
lot
like
we.
We
worked
with
sly
grython,
who
started
the
net
implementation
of
the
of
the
beacon
chain,
and,
and
we
tried
to
bring
it,
we
tried
to
bring
it
under
one
umbrella
of
the
none
of
my
notes.
Working
together.
It
was
a
bit
too
much
effort.
Only
like
again,
we
couldn't
cover
that
and
I
couldn't
work
with
sly
for
so
long
nowadays.
B
A
That's
interesting,
I
mean
it
is
always
a
good.
If
there
there
was
some
opportunity
missed,
we
are
definitely
doing
something
better
on
the
other
side,
maybe
and
account
abstraction
all.
These
are
good
features
which
neither
mind
is
currently
broke.
I
mean
like
supporting
and
hopefully
will
be
adopted
soon
by
the
community.
A
B
Yes,
this
is
open
for
all,
so
it's
it's
a
tool
that
allows
you
to
just
quickly
select
everything
that
you
want
to
have
deployed,
and
this
pushes
it,
and
here
it
goes
it
runs.
So
we
just
consider
that
this
configuration
effort
nowadays
is
one
of
the
big
risks
and
having
a
tool.
That's
that's
simple
enough
to
just
say:
okay,
this
is
what
I
want
from
for
consensus
layer.
This
is
what
I
want
for
execution
layer.
I
want
to
run
an
ev
boost
and
I
want
it
to
like
make
everything
secure,
safe
and
ready.
B
A
B
Otherwise
we
have
the
risks
to
the
decentralization
of
the
network,
so
this
has
to
be
provided
and
we
spend
a
lot
a
lot
of
time.
I
mean
when
I
say
we
I
don't
mean
now
here
nanomind,
but
more,
the
core
development
and
research
teams
that
work
on
ethereum
together
on
thinking
of
how
how
mev
will
affect
the
network,
how
it
should
be,
how
the
network
should
be
built
to
to
be
resilient
to
any
risks
provided
by
me.
A
That's
good,
that's
interesting.
I
hope
this
will
also
help
in
like
client
diversity.
Now
people
have
choice
to
pick
up
and
there
is
a
tool
which
supports
like
with
one
click.
You
can
pick
any
of
combination,
that's
really
for
sure
all
right.
My
next
question
is
related
to
syncing.
Now
you
mentioned
about
snapsync.
That
is
a
default
method
with
the
present
effects
of
nethermine.
A
B
So
I
mean
the
sinking
issues
appear
here
and
there
in
various
combinations.
I
mean,
as
I
say
this
is
this-
is
over
and
over
a
challenge
to
to
have
everything
perfect.
I
think
that
the
ones
that
you
are
referring
to
might
be
related
to
the
just
incorrect
configuration
once
again
like
there
were
situations
when
the
users
were
upgrading
the
binaries
of
the
of
nanomine,
but
not
upgrading
the
config
file.
B
They
changed
spec,
so
called
chainspec
that
defines
some
parameters
are
extremely
important
for
the
correct
chain
behavior,
so
we
provide
documentation
and
whenever,
whenever
it
happens
that
the
users
don't
upgrade
something,
I
still
think
it's
our
fault
that
they.
This
is
not
clear.
The
documentation
doesn't
cover
it
or
maybe
that
the
the
client
doesn't
pick
it
up
and
doesn't
say
like
okay,
it
looks
it
looks
wrong
to
me
so
work
on
this.
We
we
introduced
a
lot
of
checks
like
this.
B
A
That's
good
to
know,
and
you
partially
answered
my
next
question,
which
is
about
the
config
issue,
so
in
the
sepolia
test
net
merge
like
it
generally
is
considered
to
be
good.
However,
it
was
reported
that
there
were
some
config
issues
if
you
can
maybe
for
our
listeners
that
talk
a
little
bit
about
what
are
the
config
issues
and
what
are
the
a
common
pitfall
where
a
client
node
runner
needs
to
be
careful
about?
Is
there
anything
that
could
be
done
to
avoid
this
in
future?.
B
This
doesn't
really
give
enough
time
to
inform
everyone
properly
of
how
to
configure
that
then
also,
there
is
a
bit
of
like
a
thing
of
confusion
or
maybe
like
tiredness
with
those
forks
happening.
Too
often,
I
think
the
teams
that
are
preparing
the
infrastructure
now
every
every
two
or
three
weeks
have
to
reconfigure
and
there
are
changes
in
between.
So
there
is
no
stable
configuration
approach
where
they
already
get
used
to
the
same
thing
over
and
over
again.
Instead,
they
just
like
there's
some
minor
changes
here.
B
That's
why
I
believe
that
this
leads
time
before
the
mainnet
merge
as
important
to
us
spends
time.
It's
important
to
spend
time
then
for
as
much
education
for
the
operators
as
possible
like
it
will
be
in
the
end,
all
in
the
hands
of
infrastructure
operators,
among
them
lots
of
solo
stakers
to
properly
configure
everything
update
everything
upgrade.
B
I
think
it
was
good
opportunity
to
to
force
everyone
to
upgrade
through
the
greyclassier
to
to
make
sure
that
people
know
okay.
They
feel
confident
with
this
process
and
and
start
preparing
them
for
the
mainnet,
and
it's
it's
a
lot,
so
the
more
we
educate
the
better
result
will
have
at
the
main
time.
I
think
everyone
should
should
really
take
it
into
account
that
it's,
it
might
be,
not
the
clients,
implementations
and
the
the
actual
development
that
will
lead
to
problems.
B
There
will
be
actual
users
that
will
not
have
enough
knowledge
or
confidence
to
properly
configure
everything
and
and
don't
feel
a
bit
of
stress
just
before
the
merge
right,
because
I
think
that
for
everyone,
who's
running
a
solo
staker.
Even
if
the
merge
is
success,
if
their
node
is
failing,
they
don't
see
it
as
a
success
like
they'll
be
very
unhappy.
A
That
is
good,
like
yeah.
I
understand
success.
Definition
may
vary
from
person
to
person.
We
are
talking
about
a
very
big
community
here,
so
we
can
probably
say
it.
It
is
a
good
success
for
separate
tests,
but
for
people
whom,
for
whom
it
did
not
work
out,
may
not
be
that
successful.
I
hope
this
is
not
there
in
the
case
of
mainnet,
because
that's
where
the
real
money
is
involved,
all
right
talking
about
the
test
nets.
Let's
take
a
few
steps
back.
A
Would
you
like
to
maybe
talk
about
netherman's
performance
during
that
interrupt
session,
like
I'm
asking
for
another
mind,
because
it
is
considered
to
be
one
of
the
minority
client
as
on
the
date
and
like
how
did
it
perform
in
comparison
to
the
majority
plans?
Were
there
any
significant
difference
to
be
observed.
B
B
So
some
some
of
the
execution
layer,
clients
started
maybe
a
month
or
two
months
later
and
and
it
created
this
like
perspective
perception
of
us
doing
better.
But
I
think
it's
really.
It
was
a
lot
of
circumstances
that
could
lead
it
to
them.
So
we
were
doing
well
at
m4.
I
think
so.
Geth
was
much
better
prepared
at
that
time.
Like
majority
of
testing
was
happening
with
geth,
I
think
mario's
van
der
veeden
and
the
team
and
gaff
did
amazing
work
of
of
preparing.
B
I
remember
guillaume,
was
doing
a
lot
of
effort
for
the
for
the
merge
and
I
think
I
could
say
that
from
the
execution
clients,
maybe
we
were
just
like
behind
gaff
on
the
preparation
side,
but
it's
really
hard
to
say
like
to
quantify
it's
like
who
is
better.
We
did
well
in
the
sense
that
we
went
through
all
the
processes.
I
don't
think
that
anyone
was
perfectly
stable
and
like
synchronization
going
for
the
merge
we
we
did
went
through
the
for
the
sync
for
this.
Like
devnet
the
merge
on
the
m4.
B
There
was
lots
of
stress
and
like
trying
to
guess,
what's
happening
and
rewriting
the
code
base.
I
spent
a
lot
of
time
coding
their
own
silence
and
trying,
like
I
don't
code
that
often
anymore
for
the
last
year
so
like
it
was
like
probably
one
of
the
biggest
coding
sessions
for
me,
then
yeah
everyone
was
putting
a
lot
of
effort
and
then
and
then
since
then,
we
like
constantly
code
and
improves.
A
Yeah,
I
would
agree,
I
mean
like
it's
really
difficult
to
quantify,
although
we
can
we
observed
like
in
the
kenzuki
when
it
was
three
ways
that
get
based
on
another
mind,
all
were
in
the
same
line
and
I
believe
nethermine
was
kind
of
savior
there
right
for
that
split
like
it
helped.
So
I'm
happy
to
know
that
there
were
not
major
differences
between
the
minority
client
and
the
majority
climb.
As
we
said
now.
A
Talking
about
that,
the
combination.
Do
you
think
there
is
any
perfect
or
near
to
perfect
el
ncl
combo,
though
I
have
heard
a
lot
of
good
words
about
another
mind.
I
have
interviewed
many
other
clients
on
consensus
layer.
They
were
talking
all
good
points,
so
if
there
is
any
preferred-
or
you
think
is
the
best
one.
B
Yeah,
I
remember
in
the
past
when
I
was
choosing
like
among
different
clients
for
for
a
particular
purpose.
When
I
was
downloading
some
applications
very
often,
I
would
just
simply
choose
something
that
was
less
popular,
because
I
wanted
to
go
against
the
stream
or
something
that
had
a
nice
logo
or
a
nice
name,
so
everyone
will
have
their
their
own
perfect
combination
and
it
might
be
different
for
everyone.
So
that
would
be
great,
like
if
people
feel
start
to
feel
like
it's
a
bit
of
just
a
commodity,
almost
like
any
choice.
B
If
they,
if
they
feel
super,
super
confident
that
whatever
they
choose,
it
will
be
staple
stable
and
good,
but
it
may
have
some
slightly
different
flavor
for
them.
The
delivers
may
be
like
a
one
or
two
niche
things
that
just
scatters
nicely
to
10
20
percent
of
the
of
the
users
because
yeah,
I
think
like.
If
you
have
20
25
combinations,
then
you
simply
want
around,
like
four
percent
of
the
of
the
network,
to
run
particular
combinations.
So
really
this
would
be
the
the
perfect
spread
of
this
usage.
B
A
B
We
should
see
at
the
situation
when
all
the
operators
or
validators
have
to
choose
between
the
execution,
clients
they'll
be
choosing
different
ones,
because
they
will
have
to
spread
it
to
make
sure
that
they
are
safe,
safer
during
some
potential.
Slashing
events
like
we've
seen
the
failures
of
majority
clients
in
the
past
and
if
they
would
stay
at
80
percent,
this
would
be
problematic.
B
A
Yes,
of
course
I
mean
there
are
a
lot
of
opportunities
coming
up
post
much,
so
we
should
be
looking
forward
to
it.
I
know
we
are
very
close
to
time.
I
have
one
question
that
may
be
very
useful
for
new
people.
Where
can
one
find
resources
for
running
execution,
client
nether,
mind
and
if
it
is
available
in
with
different
cl
client
combinations?
That
would
be
great.
B
That's
looking
now
at
the
slide,
that's
displayed
all
the
time,
so
it's
not
hello
at
nevermind.com.
It's
that
I
am
so
they
if
you
wanted
to
send
us
an
email,
the
all
the
all
the
information
is
their
plus
on
various
medium
articles
that
we
provide
that
we
write.
So
we
it's
like
it's.
It's
always
a
challenge
to
find
fantastic
technical
writers.
You
have
them
come
and
go
and
move
and
really
care
about
like
what
they
build
and
they
have
all
the
different.
You
know
like
plans
for
future.
B
So
if
you
are
super
knowledgeable
about
ethereum,
you
want
to
write
about
ethereum
there's
like
super
hard
things
like
how
to
how
to
deploy
everything,
how
to
run
everything
that
we
always
invite.
People
like
we
look
for
more
technical
writers
on
the
team
and
the
team
is
preparing
all
those
articles
so
like
when
we
deploy
one
click.
We
provide
the
explanation
of
how
to
run
one
click
so
for
sure,
for
sure,
if
you
go
to
github
one
click
for
nanomind,
you
will
see
the
materials
of
how
to
launch
and
deploy
different
different
client
combinations.
B
Well,
thank
you
so
much
for
for
staying
with
us
for
for
driving
us
through
all
those
times
and
allowing
us
to
grow.
So
it's
amazing
and
yeah.
It's
just
all
the
time
saying.
Thank
you.
Thank
you
and
we'll
be
we'll
continue.
We'll
continue
just
doing
everything
we
can
to
make
it
your
massive
success.
You
always
peter
when
things
are
tough,
when
things
are
getting
better,
you
know
like
the
team
is
growing
and
the
team
is
always
staying
with
you.
A
And
on
this
note,
thanks
to
everyone
watching
or
listening
to
this
special
episode
on
the
merge,
should
you
have
any
question:
leave
a
comment
or
reach
us
at
eath
cat
herders
discord,
check
out
descriptions
for
links
to
useful
resources
and
guest
twitter
to
follow.
We
have
got
more
mud,
special
talks
coming
up
so
stay
tuned
and
keep
sharing
your
love
with
the
kingdom.
Catheters
have
a
good
one.
Everyone.