►
Description
Topics covered
-----------------------------
0:51 - About the EIP-4345
1:55 - Guest’s introduction
3:38 - Difficulty calculation
9:07 - Bomb’s calculation
10:45 - Why do we have the difficulty bomb?
11:01 - Byzantium hardfork
11:22 - Constantinople
11:38 - Istanbul
11:50 - Muir Glacier
12:20 - Berlin
12:28 - London
12:39 - Arrow Glacier
13:36 - Chart
15:21 - Hardfork chart
15:40 - Why bomb is there in the first place - Monetary policy
16:31 - Adjustment of block reward (ETH)
17:00 - Forcing function
18:38 - Forcing function against core devs
19:12 - Open questions
21:00 - Questions - How would that look for the community where supposedly core devs are bribed but they are the only people with capabilities to push the bomb?
24:07 - What about the bomb as a way of preventing russification?
24:49 - Why will this not happen with proof of stake?
26:57 - How is it necessary relevant to the inclusion or exclusion of the difficulty bomb in proof of stake regardless the ability to earn money is the same?
29:50 - Hypothetically speaking if Google corrupts core devs, can we even tell?
32:19 - Decentralization on application layer
37:00 - What would be your proposed implementation of the bomb in proof of stake?
39:28 - With EIP-4488 in discussion, do you see a possibility of having any emergency upgrade before the Merge to push the difficulty bomb?
42:59 - Is it possible to have the setback of the offset without a proposal?
45:00 - Your experience as an author and if you have any suggestion to improve the present standardization process.
47:33 - T Jay’s message to the Ethereum community
Resources
------------------
EIP: https://eips.ethereum.org/EIPS/eip-4345
Discussions-To https://ethereum-magicians.org/t/eip-4345-difficulty-bomb-delay-to-may-2022/7209
PEEPanEIP #39: Difficulty bomb & EIP-3554 with James Hancock - https://youtu.be/QwCPrw-4d98
TrueBlocks project: https://github.com/TrueBlocks/
PEEPanEIP playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
Follow at Twitter
-----------------------------------------------
Thomas Jay Rush @tjayrush | Trueblocks @trueblocks | William Schwab @William94029369 | Alita Moore @AlitaMoore85 | Pooja Ranjan @poojaranjan19
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-herde...
Email: support@ethereumcatherders.com
Website: https://www.ethereumcatherders.com/
A
Ethereum
blockchain
is
going
to
deploy
its
last
network
upgrade
of
the
year
2021
in
less
than
24
hours.
From
now,
it's
exciting
to
follow
the
change
that
is
being
pushed
to
the
ethereum
mainland
with
arrow
glacier.
If
you
are
interested
to
learn
what
arrow
glacier
brings
to
the
user
of
the
ethereum
network
continue
watching.
A
The
difficulty
bomb
delay
with
the
co-author
of
the
proposal,
tj
rash,
eap.
4345,
is
a
standard
track
core
proposal
that
was
originally
proposed
by
timbeko
on
october
5th
to
initially
push
the
difficulty
bomb
till
may
2022
only
after
some
discussion
in
the
all
coder
meetings,
mostly
based
on
the
calculation
by
our
guest.
Today,
it
was
decided
to
push
the
ice
age
a
little
further
to
learn
more
about
the
proposal
and
learn
something
new
about
the
calculation
of
the
difficulty
bomb
in
the
ethereum
blockchain.
Let's
welcome
tj
rash
thanks
for
joining
us
t.j.
A
So
am
I
we
are
so
excited
to
learn
about
eip
4345,
but
before
we
get
technical,
we
generally
request
our
first
and
guest
to
give
an
introduction,
including
the
professional
history,
and
how
you
became
the
part
of
ethereum
ecosystem.
I
know
you
have
got
a
pretty
interesting
backstory
that
many
people
can
be
getting
inspiration
from
so
over
to
you.
B
A
That's
super
interesting:
it's
really
fascinating
and
I'm
sure
many
out
there
would
have
loved
the
transition
from
a
computer
scientist
a
poet
and
to
an
ethereum
researcher.
I
did
it
for
sure
talking
about
research.
I
understand
the
article
adventure
and
difficulty
bombing
played
a
significant
role
in
deciding
how
far
the
difficulty
bomb
should
be
pushed
for
the
arrow
glacier
upgrade
so
without
further
ado.
Let's
peep
in.
B
So
I'm
just
gonna
start:
I'm
gonna
just
go
through
I'll
go
rather
quickly,
but
I
wanted
to
use
the
math
of
the
thing,
even
though
it's
not
complicated
math.
It
really
explains
itself
well
when
we
look
at
the
math,
so
this
is
saying
that
the
difficulty
of
a
current
block
well,
first
of
all,
the
difficulty
is
used
to
adjust
the
amount
of
time
that
blocks
take
to
get
found
on
the
chain,
and
we
want
the
blocks
to
appear
every
14
seconds
or
every
13
seconds
and
be
consistent
in
how
often
they
appear.
B
So
the
difficulty
of
the
current
block
is
dependent
on
the
difficulty
of
the
of
the
previous
block,
it's
dependent
on
the
difficulty
of
the
previous
block,
plus
a
term
plus
another
term.
So
this
term,
I'm
going
to
call
adjustment
and
I'll
explain
that
in
a
minute
and
this
term
I'm
going
to
call
the
bomb
and
what
we're
interested
in
is
setting
back
the
bomb,
so
it
doesn't
overtake
the
whole
calculation
and
slow
the
chain
down.
B
So,
just
looking
at
this
piece
here,
I'm
going
to
just
look
at
this
piece
for
a
second
and
we
can
see
that
this
has
various
parts.
The
first
part
is
the
times
the
time
stamp
of
the
current
block
minus
the
timestamp
of
the
previous
block,
in
other
words,
how
many
seconds
the
block
took
to
appear
and
what
that
does
then
is
divide
by
10
and
take
the
floor
of
that
number,
and
then
it
subtracts
that
number
from
one
and
you
get
this
term
inside
of
the
adjustment
and
here's
a
table
of
that
data.
B
B
If
it's
more
than
20
seconds,
you
get
an
increasingly
large
negative
number
and
what
this
is?
It
just
calculates
into
a
direction
to
send
the
difficulty
calculation
either
up,
because
it's
too
slow.
You
want
it
to
go
up
or
it's
just
right,
so
you
want
it
to
leave
it
where
it
is,
or
it's
too
fast,
in
which
case
you
want
the
I
might
have
that
backwards
if
it,
if
the
block
is
too
slow,
you
want
the
difficulty
to
go
up
my
my
charts
backwards.
B
Exactly
the
opposite
of
what
I,
what
I
just
said:
slow
blocks
want
to
be
faster
and
fast
blocks
want
to
be
slower,
so
you
stay
right
at
14
seconds.
So
this
number
this
whole
term
right
here,
adjusts
it
either
up
or
down
depending
on
the
previous
block
time,
and
then
this
calcul.
This
piece
right
here
can
can
be
called
the
direction
of
the
of
the
adjustment,
and
you
can
then
see
that
this
piece
is
a
small
portion
of
the
previous
block
difficulty.
B
So
what
this
is
saying
is
that
the
current
block
is
the
previous
block's
difficulty,
plus
a
small
portion
of
that
difficulty,
added
or
subtracted
from
the
previous
difficulty
to
make
it
either
go
up
or
down,
and
I'm
going
to
call
this
whole
thing
the
adjustment
and,
if
I
hide
the
bomb
for
just
a
second,
this
is
what
bitcoin
has
in
its
difficulty
adjustment.
It
takes
the
previous
block
and
it
adjusts
it.
B
You
can
also
see
it
in
this
chart
where
it
stays
very
flat
until
the
bomb
starts
going
off.
So
the
thing
of
interest
in
the
difficulty
calculation
for
ethereum
is
the
bomb.
So
let's
focus
on
the
bomb
now
for
a
second,
and
if
you
look
at
this
calculation
here
predicting
when
a
block
is
going
to
occur,
is
very,
very
simple
because
you
just
have
to
add
14
seconds
times
the
number
of
blocks-
and
you
know
exactly
when
a
block
is
going
to
happen.
The
trouble
is
that
there's
fake
there's
the
bomb
calculation.
B
B
So
just
looking
at
some
numbers
here,
so
this
calculation
becomes.
The
difficulty
of
the
current
block
is
the
difficulty
of
the
previous
block,
plus
this
adjustment
plus
2,
raised
to
whatever
period
we're
in
so
just
looking
at
some
numbers
back
at
block
1
million,
the
real
block
was
1
million.
There
was
no
offset
so
the
fake
block
was
a
million
period
10
and
the
additional
part
from
the
bomb
was
only
10
1024.
B
B
So
now
the
bomb
is
starting
to
dominate
the
calculation
and
that's
exactly
what
the
bomb
is
supposed
to
do.
It's
supposed
to
slow
the
chain
down
and
the
reason
is
to
force
a
hard
fork.
We
want
to
force
a
hard
fork
and
the
the
chain
if
we
don't
fix
the
bomb,
the
chain
will
come
to
a
halt
over
time,
because
this
number
gets
astronomically
large.
B
B
B
B
Now
there
is
a
function
of
hashing
involved
here
too,
but
the
difficulty
calculation
never
allows
the
block
to
go
slower
really
than
10
than
13
seconds,
and
additional
hashing
only
makes
it
more
easy
to
get
back
to
13
seconds.
So
more
hashing
is
important,
but
only
once
the
block
really
only
once
the
bomb
really
starts
taking
effect,
so
we
can
kind
of
ignore
it
in
our
on
our
prediction.
B
So
this
is
just
a
chart
of
showing
the
real
block
number
here
and
then
the
fake
block.
This
is
where
we
offset
the
fate
block
back
and
you
can
kind
of
see
the
slowing
down
of
the
blocks
in
the
curvature
of
the
line
here,
because
it's
it
is
definitely
slowing
down,
but
then
it
goes
back
and
you
can
see
this
line,
which
is
now
the
the
periods.
B
I
call
the
line
of
no
return
or
something
like
that,
which
is
where
we
as
a
community
better
start
thinking
about
resetting
the
bomb
once
it
starts
getting
past
this
gray
dashed
line
here
and
so
for
london
in
the
summer
we
were
well
within
the
range
of
when
it
starts
affecting
it
and
now
we're
a
little
bit
further
along,
but
we're
still
well
within
the
range.
So
it's
a
good
time
to
set
it
back
now
and
here's
this
these
two
forks
right.
These
are
two
forks
right
here,
one
after
another.
B
That's
where
we
kind
of
misunderstood,
where
we
should
have
set
it
back
so,
and
this
also
shows
up
in
in
this
chart,
and
you
can
see
that
the
bomb
kind
of
takes
its
effect
and
as
soon
as
we
set
it
back.
This
yellow
line
is
the
difficulty
as
soon
as
we
set
it
back.
The
difficulty
drops
immediately
and
that's
true
here
and
you
can
see
that
we're.
Actually,
the
the
hashing
rate
is
growing
and
that's
why
the
difficulty
is
growing,
because
it's
trying
to
keep
this
line
as
flat
as
it
can
be.
B
So
that's
kind
of
just
an
explanation
of
how
I
figured
out
where
I
think
the
thing's
going
to
happen,
but
I
wanted
to
spend
two
minutes
and
just
talk
about
like.
Why
is
the
bomb
even
there
and
what
is
the
purpose
of
the
bomb
and
why
was
it
put
in
originally
and
and
all
that?
So
I
think
there's
basically
three
things
that
people
would
argue.
B
Another
reason
for
it
is
as
a
forcing
function,
and
this
was
right
in
from
the
very
beginning
when
vitalik
started,
writing
about
the
difficulty
bomb,
a
forcing
function
from
pow
to
pos,
and
if
you
think
about
this
change
from
the
perspective
of
a
minor
there's,
always
not
a
single
miner
in
the
world
who
would
upgrade
to
pos
because
their
business
literally
goes
away.
They
don't
have
a
business
if
there's
no
pow
if
they're
mining
a
pow
chain.
B
So
this
difficulty
bomb
destroys
the
old
chain
which
means
that
new.
If
the
miners
don't
upgrade
their
software
on
their
hardware
on
their
machines,
they'll
lose
out.
They'll
be
cut
off
from
the
chain.
So
it
was
a.
I
think
a
really
brilliant
idea
as
a
forcing
function
to
force
to
it
basically
takes
the
power
of
the
decision
making
away
from
the
miners
and
puts
it
in
the
hands
of
the
of
the
core
debts.
B
But
I
actually
think
that's
a
problem
as
well
and
another
reason
why
the
difficulty
bomb
was
put
in,
in
my
opinion,
was
because
of
back
in
the
day
there
was
this
huge
argument
in
bitcoin
about
the
size
of
a
block
and
the
community.
The
bitcoin
community
had
no
say
in
whether
or
not
that
got
changed
in
the
code,
because
the
core
devs
had
complete
control
over
the
source
code
and
they
didn't
have
to
change
anything.
So
another
thing
that
the
difficulty
bomb
does.
B
It
gives
the
community
a
forcing
function
against
the
core
depths,
because
the
core
devs
have
to
upgrade
the
software
or
the
chain
will
stop,
and
that
gives
the
community
a
chance
to
change
its
mind
about
who
the
core
dev
should
be
every
year.
So
I
think
that's
a
really
important
part
of
the
of
the
existence
of
the
bomb,
and
I
think
people
miss
that
sometimes
because
people
will
mostly
say
it's
a
it's
a
reason
to
shift
to
proof
of
stake.
B
But
I'm
going
to
ask
the
question
like
what
what,
if
our
core
devs
get
captured
by
big
data
or
by
google
or
by
microsoft,
or
they
all
get
bought
out
or
something
like
that?
What
is
the
community
going
to
do?
They're
going
to
go
with
the
core
devs,
if
there's
not
some
way
for
them
to
force
the
core
devs
to
do
what
they
want,
and
the
question
really
is:
who
has
the
power?
Should
the
power
be
the
miners?
B
Should
the
power
be
the
core
devs,
or
should
it
actually
be
the
community,
and
I
think
it
should
definitely
be
the
community?
And
for
that
reason
I'm
asking
the
question:
should
there
be
a
difficulty
bomb
in
the
pos
code?
I
don't
think
that
that
has
any
future
of
actually
getting
done,
but
I
think
we
should
actually
have
that
conversation
because
to
me
that
gives
the
community
a
way
to
force
the
devs
to
at
least
make
one
more
upgrade
to
the
software.
B
A
A
C
Actually
wanted
to
start
from
the
end,
if
I
could
about
what
you
were
saying
about
the
about
the
bomb
being
kind
of
coordination
mechanism
for
the
community
around
core
devs.
But
let's
say
that
somehow,
google
bribed
all
the
core
depths
tomorrow
and
at
the
end
of
the
day,
they're
still
really
the
only
people
at
the
experts
keys
to
modify
the
clients
to
actually
push
off
the
bomb,
no
like
how.
How
would
that
look
like
the
community
kind
of
forking
away
from
the
core
devs,
so
to
speak?.
B
Well,
I
would
say
first
of
all
for
the
difficulty
bomb
itself:
that's
not
really
true
the
line,
it's
literally
no
exaggeration,
one
line
of
code
to
change
to
diffuse
the
bomb,
so
just
for
the
difficulty
bomb
itself.
That's
not
really
true!
Anyone
can
you
know
if
if
we
could
fork
the
guest
code
and
change
that
one
line,
we
could
continue
on
with
that
chain.
B
C
B
B
So
it
diffuses
the
power
of
the
core
devs
of
bitcoin,
because
there's
only
one
repo
at
least
there's
multiple
repos
in
in
ethereum,
because
there's
multiple
clients.
So
that's
another
good
thing.
But
if
we
remove
that,
you
know
not
clear
to
me
what
we're
removing
and
whether
we're
actually
removing
you
know.
I
think
it's
important
that
we
think
about
why
we're
removing
the
difficulty
bob.
B
Now,
if
you
look
at
it
from
the
perspective
of
the
miners,
they're
happy
as
hell
that
it's
gone
and
the
core
devs
are
happy
that
it's
gone
because
they're
doing
a
hard
fork
tomorrow.
That
has
no
purpose
other
than
to
defuse
this
bomb.
So
it
seems
kind
of
silly
for
them
to
be
doing
this.
But
I
think
it's
important
actually.
C
What
about
the?
What
about
the
bomb
as
a
of
preventing
ossification-
and
I
I
think
you
kind
of
touched
on
this
when
you
refer
to
the
bitcoin
block
size
debates,
but
one
of
the
other
things
I've
heard
people
mention-
is
that
it
without
the
bomb?
It
becomes
a
little
bit
easy
to
get
complacent
and
not
merge
in
new
vips.
B
D
B
So
it
kind
of
takes
away
the
power
away
from
the
miners
and
the
reason
they
wanted
to
do.
That
is
because
they
want
to
be
able
to
switch
to
proof
of
stake
and,
if
you
think
about
the
proof
of
stake
from
the
perspective
of
a
minor
they're,
not
interested
in
that
at
all,
because
they
lose
their
business,
their
business
is
proof
of
work.
B
So
they
a
lot
of
people.
I
think
would
say
that
the
difficulty
bomb
was
only
a
way
to
force
proof
of
stake
to
get
switched
to,
and
I
think
that
the
core
devs
kind
of
look
at
the
difficulty
bomb
as
just
a
pain
in
the
butt,
for
no
real
good
reason,
and
they
don't
think
about
it
from
the
perspective
of
the
community.
B
That
says
that
I
think
what
the
court,
what
the
difficulty
bomb
is,
it's
a
promise
from
the
core
devs
to
the
community
that
they
will
upgrade
at
least
one
more
time,
and
I
don't
think
that
the
core
devs
feel
like
they
need
to
make
that
promise,
because
they're
going
to
do
that
anyway.
But
I
you
know,
I
like
to
look
in
the
future
and
think
about
google
sitting
over
there
wanting
to
capture
the
entire
chain
for
themselves.
So
I
want
that
in
there
I
don't
know.
B
B
D
More
so
just
our
miners
at
april,
because
you
were
saying
that
miners
switching
to
proof
of
stake,
or
they
wouldn't
want
to
do
that
because
of
the
fact
that
they
would
lose
their
business.
And
so
I'm
wondering
in
general,
if
that's
relevant
to
whether
or
not
the
difficulty
won't
be
included
into
proof
of
stake.
B
No,
I'm
more
saying
that
if
we
were
to
include
something
like
a
difficulty
bomb
in
proof
of
state,
what
would
be
doing
is
the
community
would
be
extracting
a
promise
from
the
core.
Devs
we've
already
eliminated
the
miners
with
proof
of
stake,
because
they
don't
really
have
a
they
don't
have
a
say
in
anything
really
in
proof
of
stake.
B
And
I
think
you
know
what
I'm
saying
is
probably
not
what
a
lot
of
people
would
say.
I
kind
of
don't
hear
people
say
what
I'm
saying
all
that
often,
but
it
just
feels
to
me,
like
that's
the
real
important
part
about
this.
This
difficulty
bomb
is
the
communities
it
gives
the
community
some
power.
It's
a
tiny
little
bit
of
power,
it's
not
very
much
power,
but
it's
more
than
zero.
C
So
maybe
just
to
dig
into
that
again,
if
I
could
and
kind
of
maybe
lead
the
conversation
into
decentralization
in
general.
So
I
remember
when
I
was
first
getting
into
the
space.
This
was
something
that
kind
of
worried
me,
which
is
any
significantly
complex
code
base
or
significantly
large
code
base,
especially
one
that
was
created
by
a
team.
In
the
first
place
it
gets
to
be
kind
of
inscrutable
when
you
have.
C
The
size
of
an
ethereum
client,
especially
one
of
the
theory
of
clients
that
has
a
lot
of
other
functionality.
I
mean
I
believe,
that
gef
still
ships
with
both
the
whisper
and
the
swarm
module
and
then
I
think,
they're
taking
it
out.
It
gets
very,
very
difficult
to
audit
and
it
made
me
wonder
for
all
the
talk
of
development
in
the
open
and
the
centralization.
B
B
B
I
think
there's
zero
chance
that
it
won't
get
corrupted
because
just
think
about
it,
it's
the
world's
you
know
the
world's
economic,
the
world's
economic
platform,
and
it's
not
going
to
get
corrupted
what
what
planet
would
that
ever
happen
on?
I
don't
know
any
planet
that
that
would
happen
on
seems
to
me
it's
absolutely
going
to
be
corrupted
and
I
think
we
need
to
engineer
that
into
our
expectation
and
make
sure
that
we're
diligently
watching
these
things,
because
otherwise
we're
going
to
have
a
really
bad
situation
on
our
hands.
B
C
I
think
it
was
benjamin
franklin
once
said
about
democracy,
that
there's
there's
no
one
who
wouldn't
sell
democracy
for
a
hot
meal,
and
for
us
I
I
wonder
if
there's
any
user,
who
would
descend
it
wouldn't
sacrifice
to
centralization
for
just
like
you
know
another
one.
Second,
less
latency,
I
know
yeah.
I.
B
Always
tell
people
what
we
want
to
get
to
eventually.
Is
you
can't
buy
a
computer
that
doesn't
have
a
node
running
on
that
computer
and
I
tell
people
that
computers
in
the
future
are
going
to
have
100
terabyte
hard
drives
and
99.9
terabytes
are
going
to
be
for
the
blockchain
data
and
nobody
will
care
if
it's
the
norm
it's
the
norm,
that's
for
sure
yeah
I
mean
you
know.
I
feel
like
to
think
that
it's
just
gonna
happen.
Magically
is
probably
not
a
good
way
to
plan
for
that
it
has
to
happen
on
purpose.
C
So
I
mean
you're
really
digging
in
here
to
the
bomb
as
a
form
of
coordination
as
it
put
like,
yet
something
that
pushes
it
just
creates
a
natural
kind
of
incentive
that
has
decentralization
kind
of
built
into
it.
Do
you
see
any
other
kind
of
protocol
layer
incentive
loops
that
you
think
really
need
to
either
be
talked
about
in
order
to
make
them
more
decentralized.
B
Well,
my
work
on
trublox
has
always
been
about
access
to
the
data
as
well.
You
know,
and
I
think
that
is
it's
kind
of
outside-
of
the
blockchain,
because
accessing
the
data
is
a
function
that
people
do
outside
of
the
chain.
I
mean
people
write
smart
contracts
with
need
which
need
access
to
the
data
inside
the
chain,
but
we
really
need
access
to
the
data
outside
the
chain
as
well,
and
that
to
me
is
is
wildly
centralized,
and
I
think
that
there's
a
whole
lot
of
things
that
we
should
be
paying
attention
to
there.
B
As
far
as
how
do
we?
How
do
we
ensure
that
access
to
the
data
off
chain
is
not
centralized,
because
that
I
see
as
a
much
easier
thing
actually
to
do
than
centralizing
the
chain
and
everything
I
see
is
leading
directly
towards
that?
I
mean,
notwithstanding
the
10
different
solutions
that
people
are
proposing,
including
my
own,
but
it's
a
that's,
probably
the
most
important
thing
I
see,
or
at
least
from
my
perspective.
C
C
D
C
Fine,
all
right
cool.
I
was
just
going
to
ask
what
you're,
referring
to
there
with
data
availability
is
due
to
the
difficulties
of
running
an
archive
node,
specifically
and
theoretically.
If
we
were
all
running
archive
notes,
we'd
be
able
to
know
the
entire
state
of
the
chain
from
genesis
locally,
but
most
of
us
can't
really
run
archive
nodes.
B
Well,
actually,
you
guys
should
all
switch
to
aragon,
I'm
just
making
a
plug
for
aragon.
There
they're
they're,
pretty
it's
not
hard.
It's
two
terabytes
big,
so
it's
much
better
than
12
terabytes
speak,
but
there's
actually
proposals
now
to
drop
historical
data
and
different
ways
of
accessing
that
historical
data.
So
it's
an
increasingly
important
question
as
well.
C
Sorry
about
that
zoom's
last
update
has
really
recognized
you're,
referring
to
how
you're,
referring
to
the
stateless
ethereum
initiatives
where,
like
we
wouldn't
have
to
all,
have
all
the
data
locally.
In
order
to
be
able
to
query
it
from
the
network
right,
okay,
yeah
yeah
see
that
yeah
lita
wait
wait
go
for
it
sure
so.
D
B
B
B
Of
a
fake
block
or
something
and
it's
in
the
code,
it's
it's
a
choice
of
the
core
developers
to
put
that
line
of
code
into
the
code.
It's
not
like
some
magical
formula,
it's
just
that
the
core
developers
have
to
put
it
in
and
it
just
slows
the
chain
down
over
time
unless
they
fork
yeah.
That's
the
same
exact
thing
that
the
current
difficulty
bomb
is.
You
could
remove
the
bomb
literally
with
a
one-line
change
to
the
code,
so.
C
A
Well,
I
think
the
core
idea
of
pos
moving
into
pos
is
to
get
rid
of
the
pure
w
consensus
mechanism,
maybe
because
of
that
we
have
not
considered
that
the
coder
may
not
have
considered
putting
difficulty
form
over
there.
But,
as
you
mentioned
in
like
one
of
your
slides
that
when,
when
this
difficulty
bomb
is
not
there,
the
block
time
will
be
fixed.
That
is
an
advantage
that
we
would
be
getting
accurate
timing
of
producing
block.
I
mean
everything
has
a
trade-off.
That
may
be
the
trade-off
here
that
we
are
dealing
with.
A
I
have
couple
of
more
questions
for
you
related
to
proposal.
I
understand
you
mentioned
about
the
merge
like
we
know
that
the
difficulty
bomb
would
not
be
there
and
there
are
high
chances
of
this
to
be
being
the
last,
the
arrow
glacier
being
the
last
difficulty
bomb
related,
upgrade
it's
a
hypothetical
situation,
I'm
just
trying
to
I'm
curious
and
I'm
just
trying
to
understand
here
recently
we
came
across
the
proposal.
A
A
B
B
B
A
B
Having
said
that,
I've
been
known
to
make
mistakes
in
my
life.
First
of
all,
just
say
it
that
way,
and
secondly,
you
know
it
may
be
that
I
think
that
the
bomb
never
comes
earlier
than
you
expected
to
come,
because
the
bombs
never
get
faster.
They
never
go
much
below
13
seconds.
On
average,
they
only
really
get
slower,
because
the
only
thing
that
happens
is
the
bomb
adds
to
the
difficulty,
so
they
get
slower
but
not
faster,
so
it
doesn't
really
come
early.
B
The
reason
it
came
early
is
because
we
set
it
back
incorrectly,
but
now
we're
kind
of
saying
we
know
exactly
how
far
we
set
it
back.
We
know
exactly
how
long
it's
going
to
take
so
it
doesn't
come
early.
Is
one
good
thing,
but
I
don't
think
when
you
I
didn't
realize
that
people
were
talking
about
another
hard
fork
before
the
merge.
I
didn't
hear
that.
A
There
is
one
more
question,
I'm
not
sure.
If
I
read
it
correctly
in
one
of
your
presentation,
I
think
I
I
I
saw
that
the
period
was
also
adjusted
in
london.
I
do
not
remember
any
difficulty
bomb
proposal
going
in
so
is
it
something
that
is
not
related
with
a
proposal,
and
it
can
be
done
on
the
client
side.
Independent
of
that
I.
B
A
A
But
that
was
really
interesting
fact
that,
with
this
discussion
with
this
calculation
that
you
have
showed
over
a
period
of
time
how
difficult
the
bomb
was
calculated,
we
actually
figured
out
and
key
factor
which
actually
decides
how
we
can
adjust
the
like
a
pushing
of
the
bomb.
That
is
like
really
very
important
question
for
co-developer
the
client
developer,
but
again
these
suggestions,
those
are
coming
up
from
researchers
like
you.
Thank
you.
B
A
A
B
B
Yeah,
well,
actually,
tim
biko,
I
believe,
is
his
last
name.
He
he
did
all
the
work.
I
didn't
do
anything
and
he
just
put
my
name
on
it,
because
I
did
the
calculation
behind
it
and
it
was
a
very
short
eip.
So
I
think
it
wasn't
too
hard
to
do.
I've
looked
at
a
lot
of
vips
in
my
life
and
one
of
the
reasons
why
I've
never
done
one
before
is
because
I
don't
have
that
much
energy
to
do
that.
Much
work.
A
Well,
not
a
problem,
I
mean
your
work
on.
The
research
part
also
has
helped
us
a
lot,
because
now
we
know
that
the
developers
have
better
inside
of
when
we
can
expect
the
difficulty
bomb
all
right.
I
think
I'm
done
with
all
the
questions
here
and
we
are
almost
close
to
the
time.
Just
final
call
for
anyone
on
the
call.
If
you
have
any
questions.
A
A
We
have
also
recorded
an
episode
on
difficulty
bomb
with
james
hancock
for
the
earlier
upgrade,
and
it's
it's
interesting
to
learn
about
the
proposal
and
how
the
difficult
why
the
difficulty
bomb
is
there
in
the
first
place,
and
here
tj.
I
just
remembered
the
proposal
that
went
into
the
earlier
upgrade
when
we
did
this
episode
with
james
hancock.
B
A
B
This
is
the
best
connection
I've
had
to
the
ethereum
community
directly,
I'm
just
going
to
say
I
love
you,
ethereum
community
you're,
the
best
group
of
people
on
the
planet,
earth
and
I'm
so
excited
to
be
part
of
the
ethereum
community.
I
loved
it
ever
since
the
the
first
weekend
that
I
fell
into
this
rabbit
hole.
B
A
Right,
I
agree
yeah.
Thank
you
yeah.
I
love
today's
conversation
yeah.
It
was
really
interesting
to
learn
what's
going
on
in
the
back
end
with
all
the
decisions
those
are
made
in
front
end
by
the
co-developers,
the
client
teams
and,
as
we
are
very
close
to
the
end
of
the
top,
I
would
like
to
thank
you
once
again
tj
for
sharing
this
presentation
and
talk
about
the
difficulty
bomb
and
eap
4345,
which
I
am
assuming
that
will
be
deployed
on
the
main
net
in
less
than
just
24
hours.
Yeah.
A
Please
check
out
the
description
section
for
guest
information
and
related
resources.
Link
there
sharing
is
caring.
If
you
care
about
this
proposal
and
care
about
the
blockchain.
Please
extend
your
support
by
sharing
this
video
and
yes,
do
not
forget
to
subscribe,
we'll
be
back
with
another
interesting
topic
till
then.
Keep
watching
keep
sharing
your
love
with
the
team.
Catherine
see
you
soon.