►
From YouTube: Building a Post-Merge World
Description
Visit the https://archive.devcon.org/ to gain access to the entire library of Devcon talks with the ease of filtering, playlists, personalized suggestions, decentralized access on IPFS and more.
https://archive.devcon.org/archive/watch/6/building-a-post-merge-world/index
This panel seeks to motivate builders to develop post-Merge tools and infrastructure in various domains (e.g. staking, consensus clients, Layer 2s, hardware), discuss the gaps in the ecosystem, and explore how we can move forward after The Merge.
Speaker(s): Diego Losada, Nixorokish, Kris Kaczor, Paul Hauner
Track: Opportunity & Global Impact
Keywords: The Merge,Developer infrastructure,Staking
Follow us: https://twitter.com/efdevcon, https://twitter.com/ethereum
Learn more about devcon: https://www.devcon.org/
Learn more about ethereum: https://ethereum.org/
Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.
Devcon 6 was held in Bogotá, Colombia on Oct 11 - 14, 2022.
Devcon is organized and presented by the Ethereum Foundation, with the support of our sponsors. To find out more, please visit https://ethereum.foundation/
A
A
Thank
you
so
much
all
of
you
folks
for
coming,
and
especially
thank
you
so
much
for
our
panelists
that
you
made
it
here
and
I'm
very
excited
to
have
many
interesting
people
on
the
stage
here
today.
So
yeah,
let's
get
into
it,
I
would
say:
let's
start
with
a
round
of
introductions.
So
please
tell
us
what
project
are
you
from
what
you
work
on
within
the
project
and
we
are
at
Defcon
so
mention?
Maybe
your
favorite
cute
animal
or
something
like
that.
B
Sure
my
name
is
Paul
hauna
co-founder
of
Sigma
Prime,
which
is
the
company
that
maintains
Lighthouse.
Also
I,
guess
a
co-founder
of
Lighthouse
I've
been
working
on
ethereum
staking
since
about
2018
was
involved
in
founding
Lighthouse
of
written
a
good
chunk
of
the
code
on
that
and
now
in
the
day-to-day
I'm
kind
of
I
guess
overseeing
project
managing
still
engineering
as
much
as
I
can
my
favorite
animal
is
a
quokka
Australian
animal
I.
C
D
Our
main
goal
is
contribute
to
the
decentralization
of
of
the
film
Network
by
providing
some
kind
of
images
for
for
these
kind
of
devices
like
Raspberry,
Pi
or
rock
5,
and
turn
them
into
a
fully
film
node.
Pretty
much
automatically
in
this
way,
I
make
it
easy
for
for
regular
users
from
users
to
run
a
full
node
in
these
low
power
and
resource
constraint
devices,
and
so
this
way
we
can
facilitate
this
for,
for
people
to
run,
to
run
all
set
home
in
values.
E
My
name
is
Nick
zorkish
I
am
I
work
at
East
acre
at
Staker
is
a
completely
volunteer,
run
organization
and
we
facilitate
Community
Education
and
staking
encourage
people
to
stake.
We
provide
guidance
and
do
technical
support
for
stakers,
so
we're
just
connecting
stakers
to
the
appropriate
protocols
that
they
can
use
to
stake.
Oh
my
favorite
animal
can
I
be
boring
into
say
a
cat.
F
A
Think
it's
kind
of
right,
ethereum,
culture
Vibe,
but
there
are
so
many
cat
people
here
and
I
mean
kids
are
great
source
of
entropy
right
I
mean
it's
also,
something
which
is
which
is
important
like
cryptography,
okay.
Anyway.
Thank
you
so
much
for
the
introductions
and
I'm
Mario
I'm
from
ethereum
Foundation
protocol
support
and
yeah.
So
the
merch,
something
which
I've
been
also
contributing
to
which
is.
D
A
Celebrated
a
lot
to
merge
so
like
we
are
over
all
the
celebrations
and
now
I
think
it's
time
to
discuss.
What's
next,
because
the
merge
the
merge
was
just
the
beginning,
there
is
no
time
to
rest
and
we
need
to
build
right
and
yeah,
so
maybe,
let's
start
with
some
Reflections.
So
how?
How
is
the
merge
for
you
for
your
project,
but
especially
what
it
changed?
D
Okay,
yeah,
for
in
from
our
side,
we
were
running
nulls
on
Raspberry
Pi's.
We
have
several
several
boards
and
after
the
match,
we
were
facing
two
too
many
issues.
First
of
all,
we
we've
seen
from
some
clients
some
issues
with
performance
and
later
we
realized
that
the
Raspberry
Pi
was
a
little
tight
because
the
hardware
requirements
after
the
merge
rise
a
little.
So
this
is
a
device
from
2019
and
it's
a
little
old
and
we
are
struggling
to
get
notes
in
sync
with
a
Raspberry
Pi.
D
We
really
achieved
this
with
Geth
and
and
nimbusbat.
It's
it's
becoming
a
little
harder
for
us
to
to
keep
up
with
the
chain
on
a
Raspberry
Pi.
But
hopefully
there
is
a
new
device
coming
up
this
this
month
called
rock
5.
That
is
much
more
powerful
and
actually
we
are
validating
with
this
with
this
device
and
we
so
it
is
a
really
powerful
device,
and
it's
it's
running
great.
D
C
Okay,
I
guess
that's
my
turn.
Okay,
so,
as
I
said,
probably
I'm
the
the
least
experienced
person
here
in
in
terms
of
if
POS
but
like
just
barely
like
one
month
ago,
I
always
pinned
up
about
you
know
fpos
nodes
to
to
prepare
for
the
merge
everything
went
smooth,
so
my
experience
with
the
merge
itself
was
was
really
great,
but
in
my
previous
life,
I
was
a
defy
engineer.
I
worked
at
maker,
Dao
and
now
I've
started
running
a
survey
within
my
colleagues.
C
You
know
blockchain
Engineers
Define
Engineers
like
do
you
know
how,
if
Works
after
POS
and
the
answers
are
no,
they
don't
have
a
clue
and
I
I
know
like
50
about
I.
Think
the
word
after
POS
I
think
the
biggest
challenge
now
is
like
education
there's
a
lot
of
like
you
know,
talks
about
if
2.0
whatever,
but
they
are
outdated
because
you
know
this
respect
changed
so
much
and
yeah.
That's
that's
a
huge
challenge.
I
think
right
now.
B
B
It
was
a
little
bit
of
a
known
event,
actually,
which
is
kind
of
what
we
wanted.
It
went
better
than
any
of
our
tests.
So
yeah
it's
been.
It's
been
interesting.
Just
trying
to
figure
out
what's
doing
a
post,
merge
world.
There's
there's
plenty
to
do,
but
yeah
it's
picking,
picking
up
the
pieces,
doing
a
lot
of
monitoring
analysis,
keeping
the
lights
on
yeah.
A
Thank
you
so
much
for
all
the
answers
we
well.
We
touched
many
important
topics
there
and
I
would
start
with
with
the
node
requirement
so
or
also
complexity
of
running
nodes
right.
So
now,
after
the
merge,
we
need
a
bit
more
complex
setup
before
I
was
doing
workshops
for
running
nodes,
which
is
like
download
and
run
this
right.
Maybe
a
specific
comment:
now
you
need
to
download
two
things.
A
You
need
to
figure
out
the
JWT
path
and,
and
also
the
hardware
requirements,
went
up
like
a
huge
good
restroom,
an
arm
on
for
for
being
able
to
validate
on
on
armed
devices,
but
so
what?
What
is
your
take
on
this?
What
do
you?
What
do
you
think
is
now?
How
can
we
tackle
this
challenge
of
not
just
the
node
requirements?
A
It's
more
like
the
protocol
topic,
but
especially
especially
the
complexity
of
running
basically
different
piece
of
software
at
the
same
time,
in
terms
of
validators
is
very
important
because
we
want
easy,
homesteaking
experience
so
yeah.
How
can
we
achieve
this?
What
what
is
happening
there
and
with
l2s
by
the
way?
It's
also.
It
also
touches
this
because,
especially
with
optimistic
relapse,
we
want
to
be
able
to
run
altu
node.
We
want
to
be
able
to
create
fraud
proofs
and
should
be
also
easy
experience,
so
yeah.
D
D
What
we've
seen
in
in
particularly
in
our
Discord
channel
list
people
that
as
they
cannot
get
in
sync
the
notes
and
they
are
struggling
with
with
constitutional
execution
layer
they
they
were
stressed
because
they
validator
were
on
offline
and
and
that's
something
that
concerned
us
because
yeah,
if
you
cannot
get
your
validator
online,
it's
it's
a
problem
because
people
get
the
stress,
I
mean
for
us.
It's
not
a
problem
because
we
are
in
I.T,
maybe
15,
20
years.
D
We
are
used
to
it,
but
regular
users
are
not,
and
my
main
concern
is
well.
If
there
are
no
much
difference
between
running
at
home,
a
validator
at
home.
Why
I
don't
go
to
a
pool
I
take
my
32
weeks,
send
it
to
two
upon
and
then
and
that's
it
I.
Don't
take
this
responsibility.
I
don't
get
stressed.
So
that's
a
concern
in
terms
of
of
centralization,
of
a
staking
yeah
and
I
think
that
it
could
be
really
great
if
there's
some
way
of
incentivizing.
D
E
A
little
bit
of
history
on
me,
I
I
got
into
East
acre
because
I
started
staking
and
when
I
ran
a
validator
I
saw
a
lot
of
comments
in
the
subreddit
that
I
was
using
to
set
it
up
that,
like.
Oh,
you
have
to
be
really
good
with
command
line.
To
do
this,
you
have
to
have
Linux
experience,
you
have
to
be
a
developer
and
I
was
like
I
am
none
of
those
things.
I
I
successfully
set
up
a
validator,
and
so
I
started
commenting
in
there
and
being
like
no.
E
This
can
be
done
by
anyone.
There
are
lots
of
tools
to
reduce
the
complexity
of
it
and
we
do
need
to
like
support
those
tools,
support
those
tools
more
so
that
they
are
well
fleshed
out
and
have
good
documentation
and
e-staker
aims
to
maximize
the
decentralization
of
the
network,
which
means
that
we
want
people
not
depositing
their
32
Ethan,
all
in
a
centralized
exchange,
for
example,
and
so
we
really
just
need
people
to.
B
Yeah
I'd
Echo
that
I
think
the
I
think
the
clients
generally
are
not
particularly
good
at
making
things
usable
for
non-developers
I
think
the
the
way
that
we
hire
is
usually
for
people
who
are
more
systems
programmers.
So
people
who
are
like
kind
of
thinking
about
you
know
like
what
it.
What
are
the
bits
look
like
coming
out
of
your
networking
interface
and
we're?
B
So
we
really
like
we
do
our
best
to
try
and
make
it
so
that
it's
like
it's
straightforward
and
it's
clean
and
that
usually
leads
to
it
being
simple,
but
I
think
it's
really
a
place
where
the
community
needs
to
come
in
and
help
is
when
it
comes
to
usability
so
like
at
Staker,
with
like
supporting
with
people
how
to
use
things
and
I
know.
There's
like
nice
nose
and
some
other
initiatives
out
there
to
make
it
so
that
you
can
kind
of
wrap.
E
E
If
you
think
about
it,
the
amount
of
people
who
are
like
comfortable
with
maintaining
a
node
on
a
command
line
interface,
who
are
also
interested
in
ethereum,
is
such
a
teeny
tiny
amount
of
the
world
and
who
has
32e.
That's
like
already
a
teeny
tiny
amount
of
the
world
yeah.
So
if
we,
if
we
try
to
keep
it
at
the
people
who
can
like
run
a
validator
a
32
week,
validator
with
100
Effectiveness
you're
going
to
get
a
very
centralized
set
of
operators.
A
Yeah
thanks
so
much
right,
so
I
noticed
this
totally
on
the
workshops
when
I'm
setting
up
help
somebody
to
step
node
and
the
command
line
comes
in
and
wall
just
get
scared.
Like
that's
that's
crazy
thing.
Why
would
I
use
this
Devils
whatever
come
online?
Yeah?
That's
that's
too
much
for
most
of
the
people
and
I
really
very
much
appreciate
tools
which
make
it
easy
also
to
remote
arm
I
mean
just
flushing
it
and
and
running
it's
it's.
It's.
D
There
are
a
lot
of
options
like
tab,
download
or
that
make
is
half
of
these
great
interface
web
web
menu,
or
this
two
clicks
and
you
have
a
node,
so
yeah
I
mean
there
are
other
solutions
that
command
line.
Our
our
project
is
yeah.
It's
focused
on
on
this
kind
of
of
devices
or
low
devices,
but
overall
there
are
other
places
that
make
it
easy
for
users
to
to
run
another
or
validate
so
yeah.
A
D
B
C
I
I
was
totally
not
sure
if
it's
gonna
work,
if
it's
like
correctly
configured
because
it's
like
it's
it's
it's
it's
been
working
but
I
wasn't
sure
if,
like
that,
you
know,
engine
RPC
works
correctly,
like
I
I.
Think
after
merch,
it's
like
gonna
be
easy
to
realize
that
it
doesn't
work
because
it's
not
going
to
be
syncing.
But
you
know
during
the
merch
I
was
like:
okay,
I
have
totally
it's
gonna
work
like
we're,
not
staking.
So
it's
not.
C
It
doesn't
take
a
huge
deal,
but
there
is
a
kind
of
stressful
and
you
know
like
now.
We
have
like
you,
know
this
modular
to
to
part
of
the
clients
and,
in
the
future,
we're
going
to
have
new
module
new
layers
like
I,
don't
know:
data
availability
layer
on
top
of
eip4844,
and
it's
going
to
be
even
harder
for
people
to
to
run
all
that
stuff.
So
yeah
again
we're.
C
A
It
wasn't
clear,
yeah
and
but
I
I
was
I,
had
trouble
explaining
it
like.
You
realize
how
much,
how
much
complexity
I'm
adding
to
the
documentation
there,
but
like
so
so,
just
to
sum
it
up
what
I
believe
we
agree
on
it's
very
useful
to
have
the
automatized
setup
tools
which
minimizes
the
the
technical
requirements,
also
because,
like
I'm
not
sure
whether
I
set
up
correctly
or
I,
leave
some
secular
security
hole
there
and
so
on,
and
also
the
education.
A
It's
really
important,
huge
kudos
to
each
taker
for
that
and
now
so,
regarding
upcoming
stuff.
Now,
like
the
merge
opened,
many
doors
opened
many
interesting
possibilities
and,
like
generally
before
for
844,
we
already
mentioned
one
thing,
but
but
are
there
any,
maybe
okay
other
than
that,
or
even
even
including
this?
What
are
you
now
excited
for,
or
maybe
afraid
of
what
are
the
biggest
biggest
upcoming
things
for
for
ethereum,
which
will
influence
you?
That's.
C
Yeah
and
I
I
found
it
quite
strange,
especially
for,
like
you
know,
this
big
staking
pose
like
and
I'm
excited
that
this
is
gonna,
be
fixed,
I,
think
in
the
in
the
future,
even
in
your
future,
I'm,
not
sure
here,
but
that
was
something
unexpected
to
me
and
also
like
you
know,
the
the
reasoning
behind
like
you
cannot
do.
This
right
now
was
also
pretty
interesting
to
to
learn.
B
Thank
you
so
coming
up
soon
in
the
protocol
will
be
withdrawals
which
I
think
are
pretty
exciting.
So
there's
an
EAP
out
there.
That
is
pretty
well
supported
by
the
teams
and
it
seems
like
that's
going
to
happen
so
that'll
be
automatic
withdrawals
to
the
execution
change.
So
it
means
that
if
you've
already
withdrawn
or
if
you
do
withdrawn,
then
at
some
point
your
eighth
is
just
going
to
appear
as
in
your
F1
address
and
you
can
claim
it
and
then
for
people
who
are
still
validating
once
you
get
over
32f.
B
Maybe
once
every
couple
of
months
or
something
like
this
it'll
be
just
kind
of
dropped
into
the
execution
chain
and
you
can
get
at
it,
so
that'll
be
pretty
exciting.
I.
Think
I,
think
the
panel
is
on
inspiring
people
to
build
things
is
that
is
that
right,
yeah,
okay,
so
the
what's
interesting
with
that
is
that
it'll
dump
the
F
into
a
an
address,
but
it
won't
trigger
any
code.
It
won't
do
code
execution
so
typically
like
in
ethereum.
B
A
B
B
So
I,
don't
know
how
far
I
want
to
go
into
it
here,
but
yeah
that'll.
So
what
once
users
have
done
is
kind
of
one
soft
action,
then
yeah,
the
the
withdrawals
are
going
to
be
automatic
and
they
just
land
in
there,
which
I
think
is
really
cool,
because
it's
less
for
people
to
do
it's
less
stuff
happening
on
the
network.
It's
cool.
C
B
E
B
E
And
so
there's
going
to
be
a
lot
of
opportunity
to
shift
things
around
and
maybe
address
some
of
the
centralization
risks
that
have
been
brought
up
and
so
I'm
excited
for
that
and
I'm
excited
for
any
documentation.
That's
going
to
be
written
up
prior
to
that
in
about
how
to
withdraw
correctly
and
what
protocols
are
the
best
protocols
to
deposit
into
if
you're
not
running
a
full
validator
at
that
point,
or
there
could
be
people
who
have
stacked
32
Ethan
that
time
and
want
to
run
a
full
validator.
D
D
This
is,
it
feels
feels
right,
I
mean
yeah,
we
didn't
propose
a
block
yet,
but
we
are
still
waiting
so
and
on
the
other
hand,
I
I
am
very
interested
in
in
two
use
cases
that
I
I
hope
that
once
the
merge
went
through
and
and
l2s
are
thriving,
that's
they
were
part
of
of
the
initial
ethim
Design,
This,
web3
and
sorry.
It
starts
decentralization.
It
was
swarm
protocol
we
have
ipfs
as
well
and
and
decentralized
messaging.
D
D
A
Thank
you
so
much
for
the
answers
so
yeah.
We
tackled
a
few
important
things
here
and
there
is
actually
a
big
discussion
in
the
community
right
now.
So
what
should
be
the
priority,
whether
it's
for
844,
whether
it's
with
roles,
whether
we
should
try
to
put
them
together
in
Shanghai
or
separate,
and
so
your
voice
of
communities
folks?
So
what
do
you
think
has
the
priority
for
you?
What
is
considering?
Maybe
the
complexity
and
whatnot?
C
D
A
A
B
I
think
I
think
it's
the
the
numbers
haven't
been
chosen
for
4844,
but
it's
looking
on
the
order
of
maybe
like
200
to
400
gig
extra
disk
space
there'll
be
some
more
Network
usage
as
well,
so
we're
very
sensitive
to
these
things
and
we
really
don't
want
to
set
them
high.
So
I'm
I'm,
one
of
the
guys
that
wants
load
values,
so
yeah,
less
less
usage,
but
yeah
we're
still
figuring
it
out,
but
there'll
be
an
impact
on
disk
and
it'll,
be
impact
on
network.
D
E
E
B
Yeah
sure
I
thought
I
should
let
everyone
else
speak
before
a
client
have
talked
to
to
hear
what
people
want,
because
that's
what
we
should
be
driven
by,
and
so
the
question
of,
withdrawals
or
4844
for
me
personally,
I
am
prioritizing
withdrawals
I
feel
like
the
merge
is
not
really
done
until
withdrawals
are
complete
because
I
think
that
we're
kind
of
we
did
the
beacon
chain
on
this
promise.
That
will
let
you
withdraw
one
day
and
the
longer
we
do
that.
It
just
feels
a
little
dishonest
to
me.
B
So,
in
my
opinion,
the
next
Vlog
withdrawals
have
to
happen,
and
then
it's
a
question
about
whether
or
not
4844
comes
with
it.
Yeah
I
think
myself
and
the
other
developers
kind
of
flip
back
and
forth
between
like
yeah
yeah,
we
can
do
4844.
No,
no,
we
can't
do
four,
eight
four
four,
so
yeah
I'm
not
sure
what
like
we've
we've
had
a
bunch
of
meetings
on
it
this
week,
making
progress,
checking
it
out,
be
cool
if
it
came
in
not
explicitly
for
it
or
against
it.
A
Yeah,
thank
you
yeah,
so
like
considering,
the
topic
should
be
like
what
to
build
after
the
merge
right.
I
think
we
mentioned
many
great
things.
I
mean
contributions
on
the
protocol
level
to
withdrawals
to
First
for
for
the
testing
and
the
stake
infrastructure.
The
education
there
is
so
many
things
to
do
right
now.
A
F
B
I
have
been
a
little
disappointed
with
how
Mev
has
gone
since
the
merge
I
think
it's,
it's
probably
not
anyone's
fault,
perhaps
of
the
way
that
we
we
coordinate.
The
merge
but
I
think
that
Mev
has
kind
of
showed
up,
not
in
the
same
Readiness
State
as
the
clients
have
so
there's
been
some
problems
with
Mev
booths
that
have
been
a
little
disappointing.
B
B
We've
also
seen
some
problems
with
other
Builders,
where
they've
that
they've
been
unable
to
produce
blocks
and
they
can
get
themselves
in
a
position
where
the
validator
is
already
committed
to
a
block,
and
then
they
fail
to
actually
follow
up
on
their
part
and
produce
it,
which
means
the
validator
can't
actually
produce
its
own
block.
So
we've
seen
missed
proposals
due
to
Mev
we're
seeing
a
lot
of
late
blocks
due
to
Mev.
B
So
yeah
and
I've
also
seen
some
of
these
scenarios,
where
Mev
like
MVP
boost
or
Mev
Builders,
have
problems,
and
they
don't
alert
the
community
quick
enough.
They
don't
come
out
with
an
announcement
saying
hey
like
we
have
a
problem
and
we're
not
critical.
So
please
just
turn
us
off
until
we
fix
it.
I
haven't
seen
that
from
them,
so
yeah
I'm
I'm,
actually
a
little
bit
unhappy
with
Mev
in
the
state
of
it.
I
think
it'll
get
there.
D
I'm
particularly
concerned
with
censorship,
because
some
some
relays
that
are
running
on
on
countries
like
USA,
that
you
know
some
regulator,
says
now
that
tornado
cash
is
legal.
So
this
these
Builders
will
not
include
this.
These
blocks
with
sorry
these
transactions
with
through
tornado
cash-
and
this
bothers
me
because
if
we
are
using
Med
with,
for
example,
a
flash
boot
are,
we
are
we
as
a
sensory
in
transactions,
maybe
so,
if
we
are
using
their
their
layers,
so
it's
it's
a
little
concerning
yes,.
A
Thank
you
so
much
for
the
question
by
the
way
it
was.
It
was
my
last
question.
The
censorship
I
wanted
to
drop
the
negative
bump
on
the
end
right,
but
yeah.
So
like
the
the
like,
you
also
mentioned
it
like.
There
are
because
of
the
Mev
booths
because
of
the
this
relays.
The
values
are
currently
censoring
blocks
and
it's
over
40
right
now
of
blocks
which
are
over
compliant.
So
no
good,
and
there
is
a
the
PBS
which
is
I
would
say
just
the
meme
right
now.
A
It's
just
like
yeah
there
will
be
ppas
will
solve
it
in
the
future.
But,
like
the
problem
is
that
the
the
longer
we
wait,
the
harder
it
might
be
to
solve
right
so
Paul?
Thank
you
so
much
for
mentioning
or
like
encouraging
people
actually
not
to
run
the
Mev
boost
or
I
would
say
you
can
use
non-sensoring
relays.
There
are
these
options,
do
you
have
do
you
have
any
other?
Other
sorry.
B
So
I,
as
in
what
I
said
about,
including
in
the
consensus,
client,
yeah,
yeah,
so
the
so
what
so?
Before
the
merge
we
had
Mev
Geth,
which
was
like
if
you
wanted
to
do
Mev
stuff,
you
needed
to
run
this
Fork
of
Geth
in
order
to
like
to
do
this
stuff
and
a
lot
of
people
were
running
it,
which
meant
that
a
lot
of
people
are
running
a
fork
of
a
consensus
client
by
a
team
that
is
not
considered
to
be
client
developers.
So
I
thought
that
was
not
great.
B
So
what
we
did
with
the
consensus
clients
was
was
to
add,
was
to
get
flashbots
to
to
instead
create
a
separate
service,
and
then
we
support
an
API
to
talk
to
it.
So
what
this
means
is
that,
like
flashbots,
no
longer
needs
to
to
Fork
all
these
against
census
clients
and
then
like
either,
do
a
lot
of
work
or
jeopardize
client
diversity,
and
it
also
meant
that
now
the
consensus
clients
choose
when
to
use
these
Builders,
these
Mev
Builders.
B
So
we
have
like
fail-safes
in
there
to
say
like
if
the
chain
is
unhealthy
in
a
particular
way.
Then,
let's
just
like
cut
Mev
because
it
could
be
the
problem
for
it.
So
at
the
moment,
like
the
protocol
doesn't
support
it.
The
implementations
kind
of
acknowledge
that
it
exists
and
try
to
and
try
to
do
it
safely.
I,
like
my
the
way
that
I
think
about
it,
is
like
drug
use
like
it'd,
be
great
if
it
didn't
happen,
but
it's
going
to
so,
let's
make,
let's
make
it
safe.
A
Anything
to
add
folks,
if
not
I,
think
we
are
yeah.
We
are
passed
over
time
and
I
would
like
to
say
a
huge
thank
you
not
just
for
attending
this
panel,
but
especially
for
all
the
work
that
you
do
in
your
project.
It's
it's.
What
pushes
ethereum
well
to
succeed
right,
so
thank
you
so
much
again
for
your
work
for
being
here
and
yeah.
Thank
you
so
much
for
attending
the
panel.
Thank
you.