►
Description
Topics covered
-----------------------------
00:47 - Introduction
1:09 - What will be covered?
2:25 - Guest’s intro
3:24 - Why is the Merge important? What can you expect from the Merge?
6:01 - Timeline of the Merge (1/2)
8:15 - Hyperledger Besu
11:42 - From Eth1 Client to Execution Engine
13:47 - Bonsai
16:10 - Snapsync
17:01 - Risks of the Merge
18:32 - Client Diversity
19:52 - Testing the Merge
22:56 - What’s on the horizon for Besu?
23:00 - Opportunities in a post-Merge world
28:28 - Why run a minority client?
30:00 - How to contribute?
31:09 - Thank you (Resources & links)
33:00 - How was your client integration & devnet testing experience?
34:12 - Experience of Amphora testnet
35:00 - Client diversity
39:39 - Any special preparation for Ropsten/Sepolia testnet or Mainnet forking?
Resources:
-----------------
Slides: https://docs.google.com/presentation/d/1d1-2x1sWUkJz1Qx6gyzgr4K4ZJ5Y3HMms8sbOrD_Z10/edit#slide=id.g12d423b4a7a_4_114
Follow at Twitter
-----------------------------------------------
Sajida Zouarhi @sajidazouarhi | Pooja Ranjan @poojaranjan19
PEEPanEIP playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
The Merge playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqoLxXqZqT4hcYhoHoP6w12
Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2
Contact Ethereum Cat Herders
---------------------------------------------------
Discord: https://discord.io/EthCatHerders
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
GitHub: https://github.com/ethereum-cat-herders
Website: https://www.ethereumcatherders.com/
A
Thank
you
for
joining
us
thanks
puja
thanks
for
having
me
today.
Hyperledger
besu
is
an
execution
layer,
client
of
ethereum
blockchain,
designed
to
be
enterprise
friendly
for
both
public
and
private
permission
network.
It
can
also
be
used
on
a
test
network
such
as
robston
guardly,
and,
I
suppose
sepolia
too,
we'll
get
to
know
more
about
it.
B
B
We'll
have
the
two
different
chains
merging
into
what
we
call
ethereum
two,
but
that
will
just
be
ethereum
main
net
in
the
future,
so
the
proof
of
work
chain
and
the
beacon
chain.
The
merge
will
happen
when
we
hit
the
terminal,
total
difficulty
that
will
be
set
and
the
consensus
logic
is
going
to
happen
on
the
consensus
layer.
A
B
B
Ultrasound
money
already,
you
know
introduced
by
eip
1559,
but
now
we've
staked
it
and
the
locked
supply.
It's
going
to
be
even
more
interesting.
In
terms
of
just
crypto
economics
and
supply
constraints,
I
think
yeah.
I
think
we
can
also
mention
that
the
fact
that
we're
able
to
do
this
in
a
seamless
manner,
with
little
friction
for
developers
and
up
runners
is
pretty
nice.
B
So
talking
about
roadmap
here
is
a
timeline
of
the
merge.
I
have
been
very
careful
not
to
specify
any
dates,
so
I
think
we
are
using
the
community
not
to
get
too
attached
to
dates.
So
I
really
liked
superfiz
step-by-step
presentation
of
the
timeline
here,
because
it's
more
about
the
logic
of
how
we
will
get
to
the
merge
as
a
community.
B
B
So
that's
going
to
happen
on
the
proof
of
work
side,
but
also
on
the
proof
of
authority
side
and
then
the
consensus
layer
is
going
to
prepare
for
the
merge
as
well
and
then
the
merge
ultimately
will
happen
when
that
will
be.
I
have
no
idea,
but
hopefully
not
too
far
from
now
so
talking
about
this
next
important
milestone.
I
don't
really
know
when
this
video
is
going
to
be
released,
so
it
might
be
after
we
we
go
through
the
bellatrix
upgrade
but
yeah.
B
So
there
is
a
new
beacon
chain
that
was
created
just
for
robsten.
So
that's
pretty
nice.
That
means
that
we're
gonna
be
able
to
test
the
merge.
For
the
first
time
on
a
test
net
that
has
been
around
for
years
now,
this
reminds
me
a
lot
of
the
excitement
that
we
had
during
the
infrared
interrupt
week
was
the
first
time
as
a
community
that
we
went
from
a
proof-of-work
to
a
proof-of-stake
transition.
B
It
was
pretty
cool.
It
was
also
interesting
to
see
how
much
we
were
able
to
accomplish
in
a
week
probably
months
worth
of
work,
so
yeah
pretty
excited
to
see,
what's
going
to
happen
on
eruption
and
if
everything
goes
smoothly,
we
just
keep
up
with
the
timeline.
I
just
showed
before
it's
a
good
opportunity
for
testers
to
actually
go
through
the
merge
and
see
how
things
look
like
for
their
apps
and
services
in
the
post-merge
world.
B
B
B
So
the
six
systems
that
you
can
find
in
bezu
as
a
client
and
they
are
common
to
other
clients-
actually
are
here.
So
the
evm
engine
is
just
a
virtual
stack
that
is
embedded
in
each
ethereum
full
nodes.
It's
responsible
for
executing
the
byte
code,
which
is
just
higher
level
languages
like
solidity
compiled,
and
this
is
where
we
deploy
and
execute
smart
contracts.
B
B
So
it's
really
a
method
to
review
and
confirm
what
data
to
add
to
the
record
peer-to-peer
communication.
It's
pretty
standard,
it's
just
nodes
talking
to
each
other.
Json-Rpc
communication
is
pretty
pretty
interesting.
I've
mentioned
it
a
bit
before,
but
it's
basically
what
that
needs
to
leverage
on-chain
data.
So
if
you
have
to
query
unchained
data,
you
will
go
through
these
apis
and
this
is
what
dex's
or
wallets
uses.
So
it's
very
important.
B
The
data
storage
is
mainly
trees
in
blockchain,
specifically
merkel,
patricia
trees
and
for
busy.
We
use
roxdb,
actually
I'll
talk
a
bit
more
about
storage
with
bonsai
in
a
couple
of
slides,
so
pretty
cool
improvement
that
we
have.
I
don't
think
I
need
to
go
through
block
production
first,
because
it's
mining
second,
because
I
think
most
people
know
how
it
works,
but
yeah.
Basically,
you
bash
some
transaction
from
the
mempool.
You,
you
know
generate
a
certificate
propagate
it
to
other
peers.
People
just
check
if
everything
is
valid.
B
If
so,
it's
added
to
the
blockchain,
so
those
are
historically
the
main
systems
of
what
we
know
as
an
ethereum
client
functions
today,
but
in
the
future
in
the
near
future,
we
will
have
a
change
so
post
merge.
As
you
can
see,
on
these
slides
on
the
left
side.
You
have
what
we
know
as
ethereum
client
today
with.
B
System
in
this
monolith
and
then
post
merge,
you
can
see
two
different
modules.
The
one
is
the
consensus
layer,
client
and
the
second
one
is
the
execution
layer.
Client.
You
can
see
here
that
the
mining
has
been
dropped
and
it's
really
the
consensus
that
the
consistent
layer,
client
that
is
driving
the
blockchain
forward,
so
how
yeah?
How
do
they
communicate?
Just
let's
zoom
in
here
a
bit
between
the
consensus
layer
and
the
execution
layer.
There
is
some
new
piece
of
technology
very
important
that
is
called
the
engine
api.
B
B
B
Bonsai,
so
I
mentioned
bonsai
a
bit
before
the
very
good
news
is
that
it's
now
available
for
general
use.
We
were
able
to
remove
the
experimental
flag
sometimes
ago.
Now
it's
a
pretty
big
change
of
paradigm
regarding
state
storage
for
bezu.
Basically,
we
were
so.
Basically
the
strategy
was
a
forest
of
trees.
A
B
B
So
if
I'm
comparing,
for
example,
get
to
bezoo
a
get
strategy,
around
snapshot
is
to
take
a
fixed
point
in
time
and
then
with
the
def
log,
you
reconstruct
current
values,
but
with
a
a
bonsai
approach
with
bizu
you're
gonna
start
with
the
current
point
in
time
and
then
use
the
d
flock
to
construct
historical
values.
So
it's
very
interesting
if
you're
looking
at
using
data
around
the
head.
B
But
if
you
want
to
reproduce
historical
states,
bonsai
is
definitely
not
the
best
strategy,
but
for
stakers
it's
interesting
because
it
means
less
state
pros
and
easier
maintenance
of
the
sticking
infrastructure
over
time.
So,
as
you
can
see
on
the
diagram
here,
we
were
pretty
happy
with
the
result
and
the
improvement
it
brought
to
the
to
the
users
and
something
else
we
have
coming.
That
is
still
in
the
testing
phase,
but
I
just
wanted
to
mention
it
is
snapsync.
B
B
The
networking
load
bezos
is
going
to
be
able
to
sync
the
world
state,
much
faster
in
the
latest
test
that
we
have,
even
though
it's
still
very
preliminary,
we
went
from
more
than
24
hours
to
less
than
six
hours
and
even
three
hours
on
some
machines
on
mac
m1
for
a
full
download
on
the
main
of
the
main
network
states.
So
that's
we're
looking
at
a
80
85
percent
reduction,
so
yeah
stay
tuned
for
the
blog
posts
and
confirmation
of
all
this
nice
data,
so
testing
the
merge.
B
It's
important,
I
think,
for
people
to
understand
the
risks
to
get
motivated
to
test
the
merge.
I
feel
like
a
lot
of
the
communities
relying
on
the
core
devs
to
do
that,
but
it's
actually
a
collective
effort,
and
now
I
was
just
stressing
in
this
article
I
wrote
for
the
devs
behind
the
merge
series
using
this
image
of
you
know
the
airplane
engine
that
we
need
to
change
while
flying.
B
Currently
there
is
a
lot
of
assets
stored
in
defy
alone
on
ethereum,
plus
the
it
stakes
on
the
beacon
chain.
That
number
is
a
bit
big
now
due
to
recent
crypto
market
conditions,
but
you
get
an
idea
and
more
than
500
000
daily
active
users
worldwide
on
ethereum.
So
that's
basically
most
of
the
emerging
web
3
industry
that
is
supported
by
ethereum
at
the
moment.
B
So
it's
important
that
everybody
everyone
contributes
to
and
we
need
all
a
pair
of
eyes
on
this
and
just
echoing
welcomes
to
it
here.
This
is
an
existential
risk.
What
we're
doing
right
now
is
a
major
engineering
challenge,
specifically
something
that
I
was
looking
at
is
client
diversity,
so
super
majority
of
a
client
is
bad
and
we
know
that
because,
obviously,
if
you
have
a
super
majority,
if
there
is
an
issue
with
that,
client
is
going
to
affect
all
the
network.
B
B
Actually
dank
had
did
a
very
nice
article
where
he
runs
through
different
scenarios
of
what
would
happen
if
an
execution
client
that
has
this
amount
of
network
shares
has
an
issue
so
yeah
a
bit
this
topic,
but
that's
probably
the
type
of
of
things
that
we
need
to
realize
how
urgent
this
matter
is
and
not
only
do
we
need
diversity
at
the
client
level,
but
also
at
the
language
level.
Most
of
smart
contracts
today
are
written
in
solidity.
B
90
viper
is
is
still
a
minority
language,
and
so
it's
it's
just
important
to
have
diversity
at
every
level
to
reach
global
resiliency,
so
testing
the
merge.
I
said
I
was
gonna,
share
some
tools,
so
here
you
can
find
some
interesting
links
from
marius,
but
also
paris.
They
did,
if
I'm
not
mistaking
a
video
with
you
as
well
a
while
ago,
where
they
go
into
details.
B
B
B
So
in
this
slide,
I
actually
put
a
list
in
the
mega
merge
resources
that
mario
havel
did
and
it
has
all
the
links
to
tools
launch
pads
that
people
can,
you
know,
go
through
and
join
the
test
nets
start
testing,
and
you
can
also
find
some
scenarios
that
you
can
try
at
home.
I
compiled
in
the
merge
testing
leaderboards,
so
I'm
interesting
data,
it's
usually
fresh
because
of
how
the
page
is
set
up,
so
you
can
go
there
to
have
the
latest
information
on
the
merge
testing
calls.
B
So
to
echo
what
tim
said
here,
protocol
layer
testing
is
not
application
level
testing
everything
that
I've
mentioned
basically
are
things
that
people
can
do
and
they
don't
have
to
be
core
devs
or
you
know,
protocol
software
engineer
whatever
you
can
go
ahead
and
just
make
some
transactions
deploy,
adapt
or
smart
contracts
and
just
start
trying
some
stuff
yeah.
I
guess
this
is.
This
is
well
put
client.
A
B
B
So
the
merge
in
itself
is
pushing
us
to
seeing
of
modularizing
bezu
it's
going
to
be
easier
on
the
maintenance
and
it's
going
to
allow
also
more
people
to
contribute,
as
I
mentioned
before,
I
do
not
believe
that
the
future
is
going
to
be
on
the
private
and
permission
side
and
either
way
like
the
gap
is
just
growing.
So
everything
that
is
meaningful
or
interesting
that
has
happened
on
ethereum
lately
has
not
impacted
the
enterprise
side
enterprise.
They
don't
care
about
eip1559.
B
And
so,
if
someone
needs
to
go
through
that
learning
curve
of
going
through
almost
the
whole
code
base
just
to
make
a
small
change,
it's
not
going
to
be
motivating.
So
we
have
a
lot
of
friction
at
the
moment
and
we
believe
that
modularizing
can
really
improve
the
contribution
experience
and,
as
I
mentioned,
unlocking
opportunities
I
mentioned
here
mev,
because
it's
a
great
example,
but
I
could
mention
actually
the
evm
extraction
that
was
done
by
dano
ferran,
so
one
great
contributor
that
we
have
on
hyperledger
bizu.
That
is
not
that
consensus.
B
So
that's
perfect
example
of
how
big
of
an
impact
you
can
have
on
a
project
on
an
open
source
project.
He
extracted
the
evm
as
a
standalone
library,
and
that
has
unlocked
many
opportunities.
It's
now
being
reused
in
other
projects.
It
can
also
be
reused
by
rollup
solution
that
wants
an
evm
so
so
yeah.
So
there
is
a
lot
there's
a
lot
that
can
be
done
so
new
rules
and
business
models.
I
I
touched
on
that.
I
guess
new
tech
that
will
leverage
ethereum
protocol
as
layer,
1
premium
settlement
area.
B
So
what
I
mean
by
that
is
we're.
We've
been
looking
at
things
currently
based
on
the
status
quo,
but
post
merge,
new
roles
are
going
to
appear
and
what
we,
what
we
would
expect
today,
ethereum
to
do,
is
going
to
be
done
by
other
technologies
that
have
that
are
being
developed
at
the
moment
or
that
we
maybe
don't
know
what
they
are
and
so
people.
B
So
there
is
a
lot
of
space
for
people
that
want
to
discover,
invent
and
contribute
to
the
roadmap
here,
and
I
just
think,
that's
pretty
exciting
and
that
should
bring
more
people
to
core
developments.
Hopefully
it.
I
just
think
it's
great
to
come
to
a
project
and
understand
that
not
everything
has
been
done
or
decided
yet
from
a
technical
standpoint,
and
you
can
still
impact
the.
B
And
the
decision
from
a
technical
standpoint,
so
that's
the
message
here
and
so
yeah
link
to
that
opening
innovation
is
going
to
grow.
There
was
the
client
incentive
program
that
was
launched
by
df,
which
was
amazing
and
unheard
of
there's
the
protocol
guild
also
that
is
assembling
and
trying
to
find
a
way
to
to
reward
core
development
work.
It's
just
interesting
because
I
think
we've
understood
now
that
a
lot
of
the
industry
is
based
on
protocol
and
core
developments.
B
Yet
it's
the
place
where
we
sometimes
struggle
the
most
to
find
revenue
streams
that
make
sense.
So
if
you
look
at
how
much
you
can
make
in
defy
or
in
mev
running
a
searcher
sandwiching
people,
it
can
be
a
bit
depressing
when
you're
a
core
dev
implementing
the
iep
making
sure
all
that
work
for
everyone-
and
you
know
just
having
a
salary
which
is
great.
You
know
like
it's.
You
have
a
job,
that's
that's
fine,
but
yeah.
I
think
it's
important
to
not
let
that
gap
grow
too
white.
B
So
hyperledger,
basically,
is
a
minority
client,
and
this
is
why
it's
important
to
run
it
and
it's
also
interesting
to
contribute
to
it,
because
we
do
not
have
the
same
pressure
as
gets.
I'm
just
gonna
say
it
kudos
to
the
get
team
honestly,
but
that
also
means
that
we
have
maybe
more
space
sometimes
to
try
stuff,
even
if
the
trade-off
with
stability
is
in
favor
of
innovation
or
testing
some
experimental
things,
and
so
that's
a
very
interesting
learning
space.
B
The
other
thing
is
just
link
to
what
I
said
earlier
about
client
diversity.
We
need
to
encourage
minority
clients
we
need
to
to
keep
working
on
them.
The
hyperledger
bizoo
committee
is
is
actually
pretty
strong.
I
I
put
here
some
numbers
just
for
people
to
show
because
it
might
not
be
evident
from
from
what
there
is
online
and
we
have
been
seeing
a
an
increase
in
contributor
participation.
B
The
code
base
is
is
huge.
There
is
a
lot
of
engineering
challenges,
modularization
being
one
of
them.
We've
been
talking
a
lot
and
getting
inspired
by
aragon
and
they've,
been
very
open
about
modularization,
and
so
there's
there's
just
a
lot
of
challenges
that
I
think
some
students
or
people
in
software
looking
to
maybe
change
their
job
or
contribute
part-time
to
an
open
source
project
might
find
interesting.
B
B
For
that
we'll
see
if
we
can,
if
we
can
kick
start
that
in
the
next
couple
of
months
and
yeah,
so
if
you
are
interested
in
all
of
these
topics,
testing
the
merge
being
one
of
them,
I
put
the
direct
link
here
to
the
basically
a
twitter
feed
that
is
going
to
send
you
on
the
latest
news
regarding
testing
the
merge.
You
can
obviously
read
it
to
news
by
editing
done.
B
You
can
join
the
merge
community
call
if
you
want
those
are
public
if
you're
looking
to
try
the
merge
on
test
net
on
rupture
10,
the
latest
bazel
release
is
supporting
this
eruption
ttd.
So
you
can
just
click
here
and
and
download
it
I'll
be
at
hcc
in
july.
So
for
those
of
you
who'll,
be
there
I'll.
I
guess
I'll
see
you
and
yeah.
If
you
need
to
reach
out
to
me,
my
dms
are
open
on
twitter
and
you
can
reach
out
with
telegram
or
email,
and
that's
it
for
me.
A
Thank
you
so
much
for
sharing
all
this
information.
This
presentation
was
quite
informative
and
I'm
sure
it's
going
to
help
many
node
operators
to
know
their
client
sharing
about
bonsai
and
snap
sync
was
really
cool,
like
the
bonsai
is
a
really
cool
feature
that
is
coming
up,
because
this
is
much
special.
I
have
a
few
more
questions
related
to
it.
Those
are
mostly
related
to
your
experience,
maybe
as
a
client
developer
and
even
for
client
manager.
A
A
B
Well,
it's
interesting
because,
as
you
mentioned,
it
was
it
can
look
lighter
than
others,
but
it's
actually
not
because
you
have
to
play
along
with
other
clients.
So
the
whole
interoperability
angle
here
was
really
the
challenge,
and
so
most
of
the
issues
that
we
have
was.
You
know
like
how
is
bezu
running
with
these
consensus
clients.
Oh,
we
were
basically
looking
at
all
the
pairs
that
we
have:
bezu,
teku
or
bezu,
prism,
bezu,
loadstar,
etc,
and
so
yeah.
B
A
That
is
an
important
point
when
we
are
getting
too
much.
It
is
important
that
interoperability
should
be
considered
in
mind.
Talking
about
that.
I
remember
one
of
the
biggest
interrupt
session
of
m
forum,
so
I
would
like
to
learn
a
little
bit
about
the
experience
in
person
meeting
for
launching
a
test
net
or
performing
a
test
net.
Do
you
think
it
is
anyway
helpful
than
doing
it
asynchronously
living
in
different
part
of
the
world?
B
A
A
All
right,
I
see
you
have
covered
most
of
the
point.
I
have
one
final
question
on
the
client
diversity
part
you
mentioned.
Client
diversity
is
important
and
as
in
the
slide,
it
was
obvious
like
we
are
able
to
get
it
on
the
cl
clients,
but
it
is
still
far
on
the
el
side.
What
do
you
think
the
role
of
basic
could
be
here,
like
you
mentioned,
that
we
are
basically
trying
to
move
more
towards
the
ethereum
main
net
than
enterprise
level,
so
we'll
definitely
expect
more
user
to
join
in.
A
B
Yes,
so
I
mean
there
is
different
ways
to
go
about
it.
First,
it's
bizu
is
a
minority
client.
So
the
obvious
role
that
bizu
can
play
here
is
try
to
get
as
much
as
many
users
as
possible,
and
that
is
how
we
contribute
to
client
diversity
as
well,
by
communicating
more
sharing
more
about
what
we
are
doing.
You
know
just
trying
to
be
more
present
for
the
community
so
that
they
reach
out
to
us.
B
They
tried
the
software
and
just
be
there
to
support
the
people
on
discord
that
are
going
through
the
steps
and
the
tutorials.
So
that's
one
thing:
the
other
thing
is
increasing
our
performances,
and
so
that's
why
we've
been
doing
big
strides
at
that.
So
bonsai
is
obviously
a
big
win
for
the
team
snapseeing,
when
it's
going
to
be
ready,
is
going
to
be
a
huge
improvement
and
so
little
by
little
we're
solving
most
of
the
bottlenecks
that
we've
been
seeing.
B
There
has
been
lots
of
tech
depth
and
I
think
something
that
is
different
for
bezu
compared
to
other
clients,
is
that
we
we
started
with
a
very
wide
scope,
and
so,
and
so,
even
though
we
focus
now
on
main
nets
getting
reads
or
just
in
a
clean
way.
Separating
the
main
net
part
from
the
private
permission.
Part
is
going
to
be
a
lot
of
work,
because
a
lot
of
things
are
actually
connected.
B
So
this
is
what
I
meant
by
big
engineering
challenges,
and
so
yes,
the
other
thing
is
the
bounty
program
that
I
mentioned.
I
think
if
people
want
to
contribute
more
to
bezu.
Obviously
new
ideas
are
going
to
come.
It's
important
also
to
have
new
like
fresh
ideas
and
fresh
pair
of
eyes,
on
what
we're
doing,
and
so
that's
also
how
we
reach
diversity
and
this
time
at
the
contributors
level.
B
As
I
mentioned,
diversity
needs
to
happen
at
every
level,
and
so,
if
there
is
only
one
big
company
developing
a
software,
it's
going
like
even
if
bezou
is
part
of
the
hyperledger
project,
it's
currently
mainly
consensus
developing
it.
So
if
we
really
want
to
reach
diversity
here,
we
need
to
have
a
lot
of
organization
contributing
to
bezu,
and
so
that's
something
that
I
would
be
really
happy
to
see.
A
That
is
interesting
to
know.
Yes,
I
think,
even
for
client
diversity,
we
don't
need
to
present
user
getting
migrated
from
one
client
to
another,
but
we
can
also
engage
more
new
users
to
join
in
the
network
and
when
we
are
having
this
new
features
like
bonsai,
I'm
hopeful
that
many
people
will
consider
running
full
nodes.
B
Yes
and
the
fact
also
that
we
have
teku
pretty
close
in
terms
of
you-
know
many
things
from
a
technology
standpoint
you
know
take
when
these
were
both
java
clients.
They
share
engineers
historically,
so
the
people
that
were
part
of
the
creation
of
bizu
also
were
part
of
the
creation
of
teku,
and
so
a
lot
of
time.
When
we
talk
about
big
who
so
baseblasteku,
we
think
about
ways,
we
can
make
the
experience
easier
like
what
about
allowing
people
to
just
run
a
combo
in
a
well.
B
A
Is
quite
interesting
I
mean
I
I
don't
know
I
may
have
missed
it
earlier,
but
this
is
a
great
client
combination
for
both
like
el
ncl.
It
is
highly
recommended
that
if
you
want
to
be
a
part
of
the
proof
of
stake
network,
you
run
both
the
clients.
So
if
we
have
a
client
combination
which
are
using
the
same
language,
I
think
it
will
be
easier
for
the
user.
A
B
B
So
I
I
mentioned
that,
and
there
is
a
link
in
the
slide
around
testing
the
merge,
tooling,
so
yeah,
a
big
goal
that
we
have
is
just
to
pass
the
test
that
the
community
is
sharing
and
we're
trying
to
set
the
bar
quite
high
and
make
sure
that
all
client
teams
are
passing
that
before
before
moving
forward.
And
so
this
way
we
know
that
we're
going
into
this
well
prepared
and
we
can
assess
if
the
robsten
test
network
goes
well.
Then
that's
great.
A
B
It's
it's
a
really
a
community
effort.
It's
it
was
yeah
incredible
and
mariusz
that
I
mentioned
has
been
doing
lots
of
work
and
education
around
testing
the
merge
with
pari
running
the
test
test
nets.
Doing
the
fuzzing
mikhail
has
been
the
main
architect
behind
the
engine.
Api
specification,
so
yeah
I
just
I
just
feel
like
there
was
a
lot
of
very
interesting
phase
and
it's
a
pretty
great
story,
so
we're
just
very
excited
and
impatient
to
get
to
the
merge.
At
this
point.
B
A
Understand
that,
yes,
the
excitement
is
there,
I
am,
I
mean
community-
is
definitely
excited
with
ven
merge
all
the
time,
and
we
know
that
even
it
is
for
developers
because
they
are
bringing
this
big
change
to
their
client
team.
It
is
important
for
them
as
well.
Yes,
well,
I
think
I
have
a
very
good
news
for
all
the
viewers
of
people
need
channel
that
we
are
going
to
have
this
information
about
merge
being
shared
by
different
client
teams.
A
B
A
A
A
A
Thank
you,
sachita
for
taking
out
time
and
talking
about
diesel
the
execution
layer
client
for
ethereum.
On
this
note,
thanks
to
all
our
youtube
viewers
for
watching.
I
hope
this
talk
helped.
You
learn
something
new
about
bezu.
Should
you
have
any
question,
leave
a
comment
or
reach
us
at
eat.
Cathartist
call
check
out
description
for
links
to
useful
resources
and
guest
twitter
to
follow.
We
have
got
more
to
share
with
mud
special
talk
coming
up
stay
tuned.
Keep
sharing
your
love
with
the
ethereum
categories,
have
a
good
one.
Everyone.