►
From YouTube: PEEPanEIP #113: EIP-7044: Perpetually Valid Signed Voluntary Exits #shorts #ethereum #staking
Description
Resources:
-----------------
EIP-7044 - https://eips.ethereum.org/EIPS/eip-7044
Slides - https://hackmd.io/@dapplion/EIP-7044-PEEP-AN-EIP
PEEPanEIP - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
Dencun - https://www.youtube.com/playlist?list=PL4cwHXAawZxpnKFDl1KzGOKqwux5JaLlv
Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2
YT Shorts1: https://youtube.com/shorts/2sMH3Sf9BK8
YT Shorts 2: https://youtube.com/shorts/2d-32GZqnco?feature=share
Clip: https://youtu.be/6gFiyj9ZDkc
Follow at Twitter
--------------------------
dapplion @dapplion | Pooja Ranjan @poojaranjan19
Topics covered
-------------------------
0:43 - Skip intro
2:10 - dapplion’s introduction
3:38 - Presentation EIP7044
4:04 - What’s a Voluntary exit?
4:28 - Staking models
5:12 - Single entity stakers
5:22 - Third party staking services
5:47 - Validating entity can keep the funds hostage
6:12 - Withdrawal entity should be able to recall funds
6:29 - With pre-signed voluntary exit
6:48 - Upcoming EIP7002 will allow trigger exeit from Execution layer
7:09 - Pre-signing voluntary exit has a catch
7:43 - Domain Separation
A
Validators
are
the
key
stakeholders
of
the
ethereum
proof
of
a
stake
world
after
the
chapel
upgrade
eat
or
rewards
withdrawal
is
successfully
enabled
ethereum
Clan
developers
are
now
suggesting
Improvement
proposals
to
overcome
some
of
the
complexities
of
staking
operations.
We
hope
to
have
a
few
proposals
deployed
with
Duncan
with
the
next
plan.
Network
upgrade
if
you
are
a
validator
or
generally
interested
in
following
proposed
changes
to
the
ethereum
consistence
change
stay
with
us.
A
Hey
everyone:
this
is
p
penny
episode,
113
I'm,
your
host,
Putra
ranjan,
welcoming
you
to
the
10
gun
special
episode.
Today
we
will
follow
our
denim
eip7044,
but
virtually
valid
signed
voluntary
exit.
As
many
of
you
know,
Janet
is
the
name
of
the
consensus
layer
upgrade,
so
this
proposal
will
perhaps
propose
changes
relevant
to
consensus.
Client,
Developers
7044
was
documented
on
May
18
2023.
Currently,
it
is
in
draft
status
to
provide
an
overview
of
this
proposal
and
propose
changes.
We
are
joined
by
lion.
A
Most
of
our
listeners
don't
know
that
I
reached
out
to
line
in
October
2021
to
be
on
this
talk
show
to
talk
regarding
the
merge
at
the
time,
but
due
to
schedule
conflict,
it
didn't
work
out
after
a
couple
of
years.
Here
we
are
having
Lion
on
deep
and
E
so
excited.
To
finally,
have
you
with
us:
may
we
begin
with
a
brief
introduction,
sharing
your
professional
background,
how
you
joined
ethereum,
and
how
do
you
feel
about
the
blockchain
space
in
general?.
B
Yes,
for
sure
so
excited
to
be
here,
so
I
came
from
another
space
background
and
at
some
point
it
felt
really
corporate
and
that
was
like
late
2017
ethereum
was
popping.
So
that's
an
article
technical
World
felt
really
exciting
to
me.
So
I,
just
chip
I've
had
done
everything
just
to
try
ethereum
at
the
time.
I
didn't
do
much,
but
I
was
very
lucky
to
find
a
meet-up
in
Barcelona,
where
I
met
Griff,
green
and
Jordan
and
from
day
one
they
took
me
under
my
wing.
B
I
moved
into
a
hacker
house
and
from
that
on,
I
have
only
contributed
to
like
ethereum
work
and
search
projects,
and
it's
been
a
while
right.
I
went
from
drop
notes,
discovered,
Lord,
started,
doing
covets
and
then
protocols
acne
really
hard,
and
it's
been
an
amazing
journey.
I
think
the
level
of
technical
friends
and
professionalism
exceptionalism
here
is
is
fantastic,
so
I
wouldn't
call
it
anyone
to
try
it
out.
Try
the
the
protocol
Fellowship
programs,
it's
fantastic,
and
it's
a
very
welcoming
community.
A
B
Hello,
so
yeah
I'm
gonna
talk
today
about
EAP
7044
perpetually
valid,
sign
voluntary
exits,
where
the
goal
of
this
VIP
is
to
improve
stinging
operations
on
splitted
credentials
with
minimal
protocol
changes
so
compared
to
everything
that's
coming
to
the
net.
This
EIP
is
rather
small
and
has
low
impact,
but
its
complexity
is
so
trivial
that
we
felt
it
was
worth
it
to
put
it
in
the
box.
So
just
to
start
the
story
motivate
what
we
are
doing.
B
Let's
talk
about
what's
a
voluntary
exit,
so
an
ethereum
validator
has
its
life
cycle
started
when
it
sends
a
deposit
message
and
it
becomes
active
after
performing
its
duties
at
some
point,
it
will
decide
to
exit
from
the
chain
and
that's
when
it
submits
this
message,
voluntary
exit
it
will
put
into
the
exit
queue
and
after
some
time
it
will
be
fully
withdrawn.
So
in
the
big
contain
there
are
the
concept
of
two
different
credentials:
the
with
rock
dimensions
and
the
validating
credentials.
B
The
evaluated
credentials
are
those
ones
that
are
used
on
a
day-to-day
basis
to
sign
attestation
sign
blocks
and
because
they
are
needed
continuously,
they
are
considered
hot.
They
have
to
be
kept
in
a
more
insecure
situation,
usually
in
memory,
so
we
chose
to
add
a
second
set
of
credentials
which
are
the
withdrawals
which
control,
ultimately
the
state
funds.
These
allow
to
have
a
much
higher
level
of
security
in
the
withdrawal
credentials
usually
kept
in
cold
storage
and
in
some
cases
they
are
never
even
created.
It's
only
an
address
such
as
the
0x01.
B
So
in
today,
situation
without
doing
anything
when
the
withdrawal
say
the
owner
of
the
funds
submits
These
funds
to
the
chain
through
the
deposit.
It
delegates
control
of
these
funds
elevating
key,
while
the
ultimate
recipient
of
this
funds
is
the
withdrawal
credentials.
The
evaluating
key
has
the
capacity
to
keep
fans
hostage
because
the
authority
to
trigger
an
exit
relies
on
the
validated
key.
This
is
not
ideal.
What
we
would
like
to
see
is
a
situation
where
the
withdraw
credential
retains
both
control
of
the
funds
and
the
authority
to
claim
them
back.
B
So
it
should
have
some
mechanism
to
trigger
this
exit
from
its
own.
What
you
can
do
today
is
you
can
prepare,
or
you
can
expect
the
the
party
that
you
will
delegate
the
funds
to
to
sign
these
voluntary
exits
ahead
of
time.
Then
you
should
be
the
funds
and
whenever
you
want
to
claim
the
sandbox,
you
can
just
send
this
message
to
the
network.
However,
doing
this
today,
it's
not
trivial,
it
has
a
complication
with
this.
B
Aip
will
address
and
I
will
explain
in
a
second,
but
I
want
to
mention
that
there
is
an
AP
coming
called
702,
which
it
will
allow
to
trigger
exits,
also
from
the
exhibition
layer
and
crucially,
from
the
withdrawal
credentials.
So
for
the
case,
what
are
the
credentials
are
an
execution
layer
address.
Dcip
is
the
right
solution,
but
the
one
we're
talking
today
deals
with
the
Legacy
BLS
credentials.
So,
as
I
said,
you
could
technically
today
pre-sign
these
voluntary
exits,
but
there
is
a
catch.
B
Let's
explain
why
so
a
voluntary
exit
is
a
very,
very
simple
message
where
you
just
Express
the
intent
that,
after
the
epoch
specified
to
the
message
the
evaluator
can
be
withdrawn.
This
is
enforced
in
the
block
through
this
condition,
and
what
it
also
means
is
that
the
epoch
at
which
is
sign
is
the
one
that
decides
at
which
the
signature
domain
is
set.
B
So,
let's
explain
in
the
beacon
chain,
every
single
message
is
signed
with
a
different
domain
separation.
That's
used
to
make
sure
that
signatures
are
guaranteed
to
never
collide
with
each
other,
and
the
domain
separation
has
three
levels.
First,
one
is
the
chain
Genesis,
so
the
fork,
the
validators
that
are
in
the
Genesis
you
compute
the
root
and
that
uniquely
didn't
defies
Every
Chain,
so
mainnet
has
one
go
early
has
another.
Then
every
single
message
has
another
domain
and
the
fourth
version.
B
What
it
does
is
uniquely
identify
every
Fork
every
hard
Fork,
so
phase
one
has
one
Altair
pelatrix
Etc.
As
you
can
see,
there
is
a
pattern
here.
We
for
convention
choose
for
maintenance
to
just
have
an
increasing
nonce
on
the
living
byte.
So
if
you
want
to
assign
messages,
we
go
here,
the
Genesis
change
analysis
is
known.
It
will
never
change.
The
message.
Type
is
known,
it
will
never
change,
and
the
four
version
is
the
thing
that
changes
and
kind
of
breaks
this
pre-sign
situation,
but
you
can
see
here.
B
Oh
it
is
increases
okay,
so
I'm
just
gonna
sign
for
each
one
of
these.
The
problem
is
that
there
is
no
rule
to
enforce
that.
We
will
continue
this
pattern
of
non-increasing
in
the
future,
so
we
could
have
a
better
solution.
I
want
also
to
note
of
why
this
is
even
possible.
Why
don't
you
just
sign
the
message
for
Genesis
and
then
use
it
forever?
Well,
the
catch
is
that
the
spec
defines
a
very
specific
rule
on
how
these
four
versions
are
accessible
on
chain.
B
From
the
point
of
view
of
the
spec,
all
this
information
is
not
known.
Only
the
last
two
are
available
for
usage.
That's
because
the
spec
enforces
a
rule
where
it
can
really
only
use
information
available
in
the
state
to
perform
blog
processing,
so
the
state
only
holds
the
current
and
the
previous
Forks.
B
That's
why
a
message
signed
for
Bellatrix
will
not
be
able
to
be
validated
in
the
net,
because
the
oldest
Fork
that
is
available
is
Capella.
So
just
to
contrast,
the
deposit
message,
which
is
another
life
cycle
regulator,
message,
is
perpetually
valid.
The
sign
BLS
execution
chain,
which
is
a
new
message
that
we
introduced
in
Capella
to
allow
people
to
switch
from
0x01
credentials
to
zero
zero
one.
They
are
all
perpetually
valid,
except
for
the
same
voluntary
exit,
which
is
exactly
what
this
EIP
wants
to
fix.
B
But
you
will
ask:
why
are
simulated
exits
not
perpetually
valid
from
from
the
start?
Well,
the
reason
when
we
started
the
chain
there
was
this
consideration
where,
in
the
case
of
a
very
long
contentious,
Fork,
consider
a
situation
like
the
Dow
or
messages
that
are
assigned
for
cork
a
if
we
lock
the
the
signature
domain,
they
will
be
replayable
in
the
other
chain.
So
this
is
definitely
an
issue.
B
0X01
dzip
is
the
way
to
go,
and
if
this
will
be
actually
the
one
that
will
be
used
by
Lido
and
rocketpool
and
they
have
been
waiting
for
this
one
for
a
while,
but
for
our
Europe
status
is
included
in
the
net.
So
far
here
I'm
linking
the
Lost
implementation,
that's
because
of
the
client,
I'm
leading
but
I'm
sure
other
ones
are
already
done
or
to
follow
and
yeah.
That's
all.
Thank
you.
So
much
for
your
attention
and
I'm
the
lion
in
all
socials.
A
Short
and
sweet
nice
presentation,
I,
hope
people
remember
the
concept
of
withdrawal
credentials
from
the
talk
which
we
recorded
at
the
time
of
Chapel.
We
did
have
a
conversation
on
clwp,
a
proposal
that
was
suggested
to
update
the
withdrawal
credential
moving
on
to
the
next
section,
which
is
a
question
and
answer.
I
would
like
to
start
with
the
proposal.
Out
of
curiosity,
keeping
signed
voluntary
exit
valid
up
to
only
two
upgrades
for
Block
inclusion
was
that
the
part
of
initial
Beacon
chain
specs
in
2020
or
something
that
was
included
in
later,
upgrade
that.
B
A
Like
we
were
at
very
initial
phase
right,
so
we
just
wanted
to
be
careful
right,
so
it's
okay,
we
can
always
improve
it.
My
next
question
is
about
the
advantage.
At
the
time
of
Chapel
upgrade.
It
was
suggested
to
update
the
withdrawal
key
credential
either
using
the
BLS
signature
or
clwp
proposal.
I,
don't
have
a
data
for
the
withdrawal
credential
update,
but
do
you
see
a
use
case
of
eip7044
if,
hypothetically
speaking,
100
of
existing
validator
would
have
got
their
withdrawal,
credential,
updated.
A
B
A
A
A
B
I
would
say
in
consensus,
who
has
the
ultimate
Authority
at
the
end,
to
decide?
What's
that
and
what's
not
is
the
the
consensus
spec
repo
if
something
is
merged
and
there
are
consensus,
spec
tests,
you
are
required
to
have
that
running,
because
that's
the
expectation
that
any
client
should
pass
all
tests
if
they
want
to
run
on
mainnet
I.
Think
the
fact
that
now
we
have
to
do
eaps
is
a
bit
of
a
hassle,
and
now
we
have
to
do
more
things,
but
I
think
it
makes
sense,
because
it
makes
the
whole
process
more
homogeneous.
A
I
would
agree
because
I
believe
that
EAP
documentation
is
a
document
that
we
are
creating
for
Community
to
follow
like
they
should
know
what
we
are
proposing.
Change
to
the
ethereum
main
net
over
here
I
mean,
of
course,
the
interested
parties.
Only
not
everybody
cares
about
protocol
specification
talking
about
the
same
thing,
the
duplication
of
effort
with
respect
to
documentation.
The
EAP
suggests
that
test
cases
are
work
in
progress
within
the
standard
consensus
layer
test.
However,
I
do
not
see
the
link
to
the
consensus
layer.
A
B
But
I
think
client
teams
has
been
coordinating
well,
that
there
is
a
list
of
eaps
that
we
agree
to
put
on
a
busy
Fork.
Usually
we
cut
a
version
of
the
spec
tests
such
that.
If
you
pass
spec
test,
then
you
are
good
for
definite,
so
I
will
check
on
that
specific
release.
If
this
is
included-
and
there
are
tests,
then
you
should
run
it.
A
But
yeah
we
do
have
a
call
scheduled
with
paretosh
to
talk
about
the
tests,
and
you
know,
proposals
getting
on
javanets
later
on
in
August,
I
guess
yeah.
So
definitely
we'll
get
to
know
more
about
it
all
right!
There's
one
other
thing
that
you
mentioned
about
security
consideration.
Are
there
any
security
concerns
that
client
teams
or
user?
Perhaps
the
validators
may
be
aware
of.
B
So,
first
of
all,
this
is
a
backwards
compatible
change.
There
is
nothing
that
has
to
be
aware
of
that
would
break
today
only
with
the
minor
asterisk
of
a
future
consideration.
If
you
did
this
strategy
of
pre-signing
exits,
you
should
be
aware
that
any
exit
after
capella
would
not
be
valid,
but
the
one
at
capella
would
be
valid.
So
if
someone
has
designed
a
system
like
the
one
I
was
talking
about
like
a
Denman
switch,
they
should
just
update
the
strategy
to
broadcast
the
one
sign
for
capella
for
perpetuity.
B
That's
the
only
really
important
consideration
in
terms
of
usability
for
security
as
I
was
talking
about.
If
there
is
a
contentious
work,
then
whoever
is
handling.
The
second
Fork
should
consider
this
Edge
case
and
Implement
a
bit
of
consensus
code
to
make
sure
that
exits
are
not
replayable.
Otherwise,
it
would
be
much
difficult
for
users
to
stay
active
on
both
chains,
which
is
also
a
big
asterisk,
like
we
have
never
had
such
a
splits.
We
don't
know
what
will
happen
so
here
there
are
the
case.
B
A
Is
good
to
know,
my
next
question
is
again
with
respect
to
the
documentation
of
The
Proposal.
So
generally,
when
we
are
documenting
a
proposal,
we
add
a
link
to
discussion,
which
is
called
like
a
discussion
tool
thread
that
we
generally
created
Fellowship
of
ethereum
magician.
While
looking
into
this
proposal,
I
found
this
thread
was
mostly
empty.
You
could
not
find
much
on
the
EIP
pull
request
either
I'm
wondering.
Where
can
the
community
follow
the
discussion
with
respect
to
eap7044.
B
So
I
think
there
was
a
month's
discussion
like
as
I
said.
This
is
a
very
tiny
thing
that
we
believed
makes
made
sense.
I
think
it
was
briefly
discussed
in
a
consensus,
call
and
Mikhail
and
he
saw
express
interest,
and
that
was
about
it
because
it
it
doesn't
have
it's
it's
a
very
small
size,
it's
practically
in
a
religious
complexity
with
no
considerable
security
issues,
so
it
was
just
done
basically
in
an
afternoon.
This
is
why
I
think
it
doesn't
have
much
grounds
to
allow
for
controversy.
Yeah.
A
B
A
Definitely
we
would
like
to
share
the
link
of
discussion
with
the
recording,
so
people
interested
may
come
and
share
their
feedback.
Okay.
My
next
question
is
with
respect
to
the
status
I
understand.
The
EIP
process
is
relatively
new
for
CLT,
so
I'm,
assuming
this
is
already
in
the
consensus.
Spec
included.
This
perhaps
will
be
a
right
time
to
move
into
the
review
status.
A
B
As
I
say,
I'm,
not
that
intimately
familiar
with
the
exact
details
of
preparep
process,
but
I
trust,
my
EAP
editors
and
I
know
they
will.
Let
me
know,
when
is
the
right
time
to
do
so
so
yeah
as
I
said
coming
mostly
from
consensus,
we
still
Focus,
probably
too
much
on
the
consensus
pack,
so
yeah
I
will
try
to
educate
myself
and
others
more
on
the
exact
details.
A
All
right
for
making
this
proposal
like
moving
to
the
next
status,
there's
nothing
much
needed.
You
can
simply
create
a
pull
request
in
which
you
can
make
one
small
change
from
draft
to
review,
and
that
would
be
all
okay.
It's
always
a
good
idea
to
have
it
in
review,
while
it
is
actually
in
review
Because
unless
it
is
there.
Even
the
community
believes
that
this
proposal
is
not
ready
to
provide
feedback
so.
A
B
Sure
so,
as
I
say
like
doing,
this,
AP
definitely
came
as
an
as
an
extra
hurdle
that
we
had
to
do
before
we
had
this
merger.
Probably
the
CIP
would
have
been
through
line
PR
in
the
consensus
specs,
and
we
will
be
done
with
it
and
forget
about
it.
Definitely,
this
VIP
has
some
over
ahead,
but
coming
from
a
person,
that's
not
non-technical.
I
could
see
how
the
consensus
pack
would
feel
that
intimidating
as
this
repo
with
code
and
things.
B
So
it's
not
the
most
inviting
place
for
external
feedback
so
now
that
the
beacon
chain
has
merged
with
execution
chain
and
as
we
inherited
all
the
users
and
all
the
community
that
lay
on
the
other
side,
which
is
arguably
much
greater
than
in
the
consensus
bank
site
I,
think
it's
it's
good
that
we
allow
for
these
other
forums.
My
Hope
Is,
that
with
time
the
overhead
of
doing
this
would
be
lower,
but
we
will
get
there.
B
I
think
the
most
important
now
is
Let's
Be
uniformed,
let's
make
a
consistent
process
and
we
can
work
on
it
in
the
future.
Another
important
point
is
the
execution
site
will
get
executable
specs
soon,
hopefully
that's
very
exciting.
So
then
the
Symmetry
between
the
two
layers
will
be
much
greater
and
then
we
can
see
what
can
we
do
around
that
because
at
the
end,
I
think
stacking
with
code
is
the
best
and
then
having
the
AP?
Has
this
minimal
document
that
touches
everything
but
technicalities
to
cover
all
the
other
considerations?
A
Thank
you
for
this
great
feedback.
Yes,
we
do
expect
execution
specs
to
be
ready
soon.
Recently
we
have
started
the
workshop
for
eels
for
people
to
understand
the
execution
specs
and
how
they
can
perhaps
start
running
their
own
node
with
that
people
interested
in
following
Workshop
can
find
it
on
ethereum
cat
hurdles
YouTube
or
it's
an
initiative
by
Sam
Wilson,
who
has
been
leading
the
execution
specs
for
quite
some
time
here.
Is
there
any
success
or
roadblocker
story
that
you
would
like
to
share
with
our
listeners?
That's.
B
B
B
Now
that
I'm
working
more
on
on
Research
side
than
just
doing
doing
these
APS,
it's
very
it's
very
nice
and
refreshing,
like
the
the
research
community
in
ethereum,
is
growing
so
fast
and
with
so
talented
people,
and
we
have
so
many
challenges
ahead.
Then
I
think
I
think
we'll
never
get
bored,
and
hopefully
we
can
deliver
an
amazing
ethereum.
A
Done
my
hopes
aligns
with
yours.
I
have
heard
a
few
stories
about
these
meetups
like
in-person,
meetups
I
hope
that
team
will
have
another
good
time
at
Istanbul,
which
is
the
next
land
later
all
right.
We
are
coming
close
to
concluding
today's
talk.
Do
you
have
any
message
for
the
validators
community.
B
Don't
be
afraid
to
stake,
solo
sticking
is
much
simpler
than
you
think,
and
you
would
get
even
more
rewards
than
going
through
another
entity,
and
there
is
also
always
the
altruistic
component
of
participating
in
the
chain,
but
it's
really
important
and
now
having
the
explosive
growth
of
Lido.
It's
super
important
to
have
a
counterbalance
in
power
and
even
though
I
think,
recent
reports
show
that
solo
stickers
represent
six
percent
six
percent
of
the
many
billions
of
persecuting
ethereum.
B
It's
it's
still
a
huge
chunk
and
in
the
case
of
a
problem
that
would
be
what
save
ethereum
from
extreme
their
risks.
So
yeah
don't
be
afraid.
Joint
forums
join
ease,
taker,
tap
notes,
all
the
forums.
It's
not
that
hard
and
we
are
working
hard.
There
are
proposals
to
lower
the
32
East
limits,
and
even
if
you
want
to
do
that
today,
you
can
use
I,
think
rocket,
pool
even
allows
a
smaller
limit,
so
yeah
don't
be
afraid.
We
will
have
you.
B
A
Right
perhaps
this
is
something
that
we
need
to
like
promote
just
like
the
client
diversity
that
we
would
like
to
change
this
percentage
from
six
percent
to
something
really
significant,
so
we
can
balance
the
stickers
on
the
network
yep
very
well,
that
line
we
thank
you
for
joining
us
on
T
Penny
and
talking
about
upcoming
changes
with
eip7044.
We
look
forward
to
seeing
the
proposal
on
the
test
net
and
finally,
on
the
main
net,
with
Denco
upgrade
for.
A
On
this
note,
thank
you
to
all
our
YouTube
viewers
for
watching
and
podcast
subscribers
for
listening
to
this
special
episode
on
Den
con.
Should
you
have
any
question
on
this
or
any
other
topic?
Let
us
know
at
each
Catholics,
Discord
check
out
descriptions
for
more
info,
we'll
be
back
with
another
interesting
talk
until
next
time.
Keep
watching
keep
listening
and
keep
sharing
your
love
with
ethereum
caterers
cheers.