►
From YouTube: Merge Implementers' Call 3
Description
A
A
A
With
the
orionis
updates
from
client
updates,
then
go
to
the
update
on
the
first
devnet.
A
Client
updates
I'll
start
from
tekku
side,
so
taco
is
like
ready
for.
A
The
first
devnet
launch
it's
been
tested
with
bazoo
nethermind
and
catalyst.
A
And
yeah,
so
that's
that's
it
we're
excited
to
see
it
in
the.
A
In
the
first
devnet
and
see
how
the
things
are
going-
and
I
didn't
try
like
interrupt
it
with.
A
Other
clients,
but
just
try
to
run
it
on
a
couple
of
machines.
Yep
went
well,
so
let
us
see.
A
A
B
I
can
I
can
take
a
lighthouse,
not
a
whole
lot
to
report.
On
our
end,
we
got
interrupt
going.
B
With
nethermine
now
so
we're
now
working
with
gas
and
nethermind
yeah
we're
ready
for
the.
B
Devnet,
I
believe,
we're
still
not
calling
the
finalized
endpoint,
but
we
can.
B
Probably
throw
that
in
pretty
quickly,
I
think
that's!
That's
it
for
us.
A
Yep
great
prismatic,
yeah
hey
there,
so
I
think
we're
pretty
much
ready.
We
spent
the.
C
Last
few
days,
debugging
hashu
root
for
the
transactions
field
and
then
to
proto.
C
C
D
We're
ready
so
we've
been
testing
with
geth,
with
catalyst
and
and
so
far
it's
been
the.
D
Interop's
been
solid,
so
yeah
looking
forward
to
see
see
if
this
works,
how
this
works
tomorrow.
A
Great
okay,
so
yeah,
I
guess
we
can
go
to
eat
one
clients
who
wants
to
be
first.
E
I
can
go
first,
so
nothing
major.
We
will
be
releasing
a
hot
fix.
E
For
what
lighthouse
submitted
to
us
a
small
issue
in
the
contracts
in
the
response,
but.
E
Nothing
major
we'll
be
releasing
it
today,
so
we
will
have
a
newest
release
and
us
docker
today.
A
What
is
this
issue
about
like
the
issue?
Is
that
the
response
wasn't
serialized
correctly.
E
I'm
really
confused
why
it
happened
because
it
worked
fine
for
me,
it's
just
to
simplify.
F
It
the
response
is
instead
of
success.
Instead,
it
was
saying
value
and
lighthouse
said
that
it
is.
F
B
Yeah,
so
we
we
don't
let
an
error
on
that
endpoint!
Stop
us
from
progressing,
so
we
it.
B
So
lighthouse,
just
kind
of
logs,
an
error
that
that
we
didn't
find.
B
The
feel
we
expected
in
the
response
and
the
success
that
the
call
works
well
in.
B
E
I
don't
think
that
release
would
hurt
anything,
so
we
will
be
more
more
stable
and
if
you.
A
Okay,
then,
who
wants
to
speak
from
go
ethereum
from
catalyst?
Is
anybody
from
go
theorem
here.
A
H
To
join
the
the
friday
test
net,
it's
still
pretty
early
because
we
just
recently
got
it.
H
You
know
stable
and
right
now
it's
just
a
rainism
branch,
npr.
G
Any
short-lived
transient
test
nets
with
multiple
like
different
consensus
engines,
driving.
I
I
I
I
I
Yeah,
this
is
actually
great,
I
think,
yeah
and
very
exciting,
to
see
what
we'll
have
tomorrow.
I
Sure
so
we
have
a
configuration
up.
Yesterday
we
had
an
initial
configuration,
but
we
changed
it.
A.
A
Great,
so
I
would
like
suggest
to
jump
on
the
discord.
A
A
On
this
first
devnet
to
to
understand
who
runs
what-
and
it
would
be
great
if
we
have
like.
A
Any
any
interrupt
disability,
I
believe,
with
four
different
epm2
clients
and
three
different.
I
If
your
month,
clients,
you
have
to
test
at
least
12
combinations,
I
think,
or
at
least
we'll
try.
G
What's
the
precise
time
it's
starting
again
12
for
you
to
see
12
yeah,
I
need
to
see
yep.
A
Okay,
I
see
peter
just
joined
peter.
Do
you
want
to
give
any
updates
on
the
cut.
A
G
Mainly
in
the
context
of
this
trans,
short-lived
merged,
devnet,
that'll
start
tomorrow,.
A
Okay,
probably
not
okay,
I'll
ask
later:
okay,
let's
just
go
to
research
updates.
A
There
is
like
the
first
update
I
I've
made
to
the
fork
choice,
rule
section
of
the
design.
A
Document
of
the
execution
layer,
design
document
this
this
update
is
just
to
remove
the.
A
New
block
that
that
is
coming
from
consensus
societies,
really
it
does
not
mean.
I
I
mean
this.
A
A
Valid
and
depending
on
the
implementation
of
consensus,
side
of
consensus,
layer.
A
In
the
in
that
regard,
in
this
case,
the
new
hat
won't
be
issued
for
this
particular
block.
J
Being
proof
of
work
to
be
in
transition
mode?
No,
it's
not
about
transition,
but
it's.
A
The
chain
to
this
new
block,
which
might
not,
which
dependent
on
the
implementation
might
not.
A
G
J
Basically,
if
the
client's
implementation
sent
the
execution
block
to
the
execution,
client.
G
A
The
withdrawal
mechanism,
and
this
this
is
what
we
will
probably
take
into
a
kind
of
spec
for.
A
To
deploy
the
withdrawal
test
that
so
dmitry,
do
you
want
to
speak
about
it.
K
K
K
Should
resist
it,
so
we
will
not.
We
will
not
see
visceral
messages
one
per
day
per
every.
K
G
There
and
we
don't
go
through
them
now,
but
I
just
want
to
make
sure
you
solve
them.
G
A
Just
take
a
look
like
like
in
the
next
week,
so
with
your
questions
on
discord.
A
Sorry
anything
I
was
just
going
to
mention
that
we
are
going
to
attempt
to
turn
on
the.
G
So
that
might
not
actually
be
very
useful,
but
we
can
talk
about
that.
I
guess
in
a
few
days.
G
Because
most
of
the
changes
are
extremely
minimal
yeah.
What
do
you
mean
by
diversion.
A
What
has
emerged?
Oh
I
and
I'm
not
certain
if
this
is
the
case,
but
the
has
the
ryanism
spec.
G
From
the
is
that
just
pointing
to
dev
currently,
or
is
that
pointing
to
a
particular
commit
on
the.
G
A
Okay,
thanks
yep,
I
think
we're
done
with
research
updates.
Let's
go
to
spec
discussion.
A
A
I
think
we
can
get
back
to
this
to
this,
like
in
a
couple
of
weeks.
C
Regarding
the
merge
spec,
I
look
at
the
merge
spec
and
I
think
the
merge
shoe
ideally
be.
C
C
G
G
But
once
they
stabilize
and
once
there's
like
a
very
concrete
order,
like
merge,
will
go.
G
To
mainnet,
first,
which
I
think
we
all
generally
agree
on,
we
would
see
like
charting,
be
rebased.