►
From YouTube: Ethereum London Upgrade Community Call
Description
Announcement blog: https://medium.com/ethereum-cat-herders/ethereum-london-upgrade-community-call-fd8ddcda8249
PEEPanEIP videos:
------------------------------------
A Brief History of Ethereum's Future with Ben Edgington - https://youtu.be/FlFKZR_ofSo
Difficulty bomb & EIP-3554 with James Hancock - https://youtu.be/QwCPrw-4d98
EIP-1559: Fee market change with Tim Beiko, Barnabe Monnot, Micah Zoltu - https://youtu.be/AC1FS3LmoT4
EIP-3540 & EIP-3541 with Alex B., Paweł B., Andrei M. - https://youtu.be/E02THhW-yTE
EIP-3198: BASE FEE opcode with Ratan Rai Sur - https://youtu.be/QQ3NHtEaCLk
EIP-1559 with Tim Beiko - https://youtu.be/ZbSKo_x9RvU
Partial removal of refunds with Vitalik Buterin & Martin Swende - https://youtu.be/jqmM3xL6Ny8
London Mainnet Announcement EF blog - https://blog.ethereum.org/2021/07/15/london-mainnet-announcement/
Playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
How to claim POAP for the event?
All you have to do is a direct message (DM) to the POAP bot the "secret codeword"
Join Ethereum Cat Herders Discord ( https://discord.io/ethereumcatherders). Be sure your Discord account is over 7 days old.
Contact Ethereum Cat Herders
---------------------------------------------------
Discord: https://discord.io/ethereumcatherders
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
B
Yeah
hello
atm
community
idiom
blockchain
is
expecting
the
london
upgrade
to
go
live
on
the
mainland
in
less
than
three
days.
This
is
11th
major
network
upgrade
on
the
ddm
blockchain
and
I
believe
that
a
blockchain
is
decentralized
in
trees
when
every
milestone
is
celebrated
with
the
community.
So
here
we
are
welcome
to
the
london
upgrade
community
call
I'm
puja
ranjan
with
my
co-host,
hudson
jameson.
B
The
london
upgrade
includes
months
of
research
development
work,
including
many
hours
of
testing
and
implementing
five
different
proposals
in
ethereum
1.0
chain
in
the
next
60
minutes.
You
can
expect
a
quick
summary
of
these
proposals
by
the
champions
or
authors,
experience
of
researchers
and
eip
authors,
along
with
the
implementation,
ease
and
challenges
experienced
by
different
clients.
B
We
are
also
joined
by
some
of
your
favorite,
tooling
and
infrastructure
providers
to
share
a
quick
presentation
of
the
change
of
the
user
experience
that
you're
going
to
have
with
with
this
upgrade,
and
yes,
we
have
token
for
people
watching
the
stream.
The
code
will
be
shared
during
the
meeting,
so
strap
your
seat
belt.
On
the
fly
to
london.
A
B
C
Sure
yeah,
so
529
is
a
pretty
big
change
to
ethereum
hard
to
summarize
in
two
minutes,
but
at
a
high
level.
What
it
does
is.
It
makes
explicit
in
the
protocol
what
the
minimum
amount
for
a
transaction
should
be
so
right
now,
when
you
send
a
transaction
on
ethereum,
there's
no
notion
in
the
protocol
itself
of
what's
the
right
price
for
transactions.
It
leads
to
kind
of
bids
for
transactions
being
all
over
the
place.
C
For
every
transaction,
so
that's
kind
of
a
quick
summary
of
1559
eip
3198
is
basically
a
a
companion
to
1559,
which
returns
this
minimum
price
for
every
block
as
part
of
an
up
code,
and
it
just
makes
it
much
easier
for
smart
contracts
who
are
basically
looking
at
the
chain
to
generate
their
transactions,
to
figure
out.
What's
this
minimum
price,
so
it
makes
kind
of
the
functionality
from
1509
available
at
the
smart
contract
level.
A
A
C
E
Sure
so
that
eip,
the
essence
of
it,
is
that
we
modify
how
refunds
work
and
refunds
in
ethereum
are
basically
a
way
that
you,
you
use
some
gas
and
towards
the
end
of
transaction.
You
get
that
gas
refunded,
so
it's
still
available
in
the
block
and
you
yeah
you
not
pay
less
than
than
you
actually
spend
we're
changing
those
mechanics
in
three
ways.
We
remove
the
self-destruct
refund.
E
A
F
Hey
hudson,
hey
everyone:
3541
is
an
extremely
simple
eip,
which
shouldn't
really
have
any
effect
on
anyone.
It
only
disallows
the
creation
of
new
contracts,
which
start
with
the
0x
ef
byte,
and
this
byte
is
as
an
unassigned
instruction
today.
So
if
you
would
try
to
deploy
such
a
contract,
then
it
wouldn't
do
anything
anyway.
So
this
change
shouldn't
provide
any
any
anything
changing
to
anyone.
G
Hey
everybody,
the
ip3054
is
moving
the
ice
age
back.
It's
it's
a
literally
one
line
change
in
the
client.
So,
as
far
as
changes
goes,
it's
the
simplest
one.
We
can
possibly
do
and
it
moves
the
ice
age
back
to
around
december,
which
that,
at
the
time
we
targeted
for
we
probably
would
know
more
about
when
the
merge
would
happen
at
least
and
if
not
there
may
be
a
feature
fork
that
might
have
happened
or
might
not
happen,
but
it's
we
pushed
it
back
some
number
of
blocks.
E
F
B
Thank
you
james.
Thank
you,
everyone
so
for
people
watching
the
live
stream,
and
even
the
participants
of
this
call
to
make
this
movement
unforgettable.
We
have
web
token
for
you
to
claim
the
token
you
have
to
direct
message,
a
secret
codeword
to
a
board
available
on
discord.
The
process
is
also
available
in
the
description
section
of
the
youtube
stream.
A
Yeah
and
I
put
a
really
crude
microsoft-
paint
description
of
the
pope
code
and
how
to
get
it
in
the
live
stream.
So
zooms
participants,
you
can't
see
it,
but
the
code
is
ech,
london
and
again
yeah.
It
is
in
the
description
and
there's
a
pope
channel
in
our
discord.
It's
called
p
a
p
o
a
p,
but
don't
put
the
code
in
there
to
get
the
poe
app.
You
have
to
actually
dm
like
private
message.
The
poet
bought
so
be
sure
to
do
that.
B
Yeah
we
have
been
joined
by
a
new
contributor,
william
jean,
which
I
believe
is
also
an
intern
at
netherminecline.
So
lately
we
have
been
getting
a
lot
of
community
support.
Thank
you
so
much
for
joining
us
and
helping
with
your
contribution
on.
I
would
like
to
invite
banabe
mano
a
researcher
from
robust
incentive
groups
at
ethereum
foundation
to
share
his
experience
with
work
done,
especially
for
eip1559
and
any
interesting
piece
that
you
would
like
to
share
with
their
community.
I
I
I
was
really
drawn
by
the
problem.
This
idea
of
congestion,
this
idea
of
auction
trying
to
analyze
the
mechanism
there's
a
lot
of
theory
on
both
topics,
but
all
of
the
theory
kind
of
flies
out
the
window.
The
minute
you
are
in
the
blockchain
setting.
You
can't
trust
anyone.
Things
are
very
open.
You
have
mempool
shenanigans.
I
mean
there's
a
lot
of
things
going
on
in
the
dark
forest,
so
you
have
to
kind
of
pick
apart.
All
of
that
and
understand
it.
I
At
the
same
time,
from
a
research
point
of
view,
you
also
have
to
maybe
balance
some
of
the
expectations
around
the
upgrade
itself,
like
a
lot
of
people,
see
many
different
things
in
the
eip.
That
may
or
may
not
be
there.
So
you
you're
trying
to
kind
of
bring
clarity
to
a
topic
which
is
definitely
technical
and
and
fundamentally
changes.
Quite
a
lot
of
things
to
to
ethereum
and
how
it
works,
and
maybe
finally,
this
is
more
yeah
contrasting
how
research
is
done
in
ethereum?
B
Thank
you
very
much
for
those
people
who
have
missed
it
earlier.
We
have
recorded
a
very
informative
episode
on
vpn
e
on
one
five.
Five,
nine
with
timber
bonnie,
bae,
minor
and
marcus-
will
do
it
answers
many
questions
on
the
proposal
as
well
as
what
to
expect
after
the
merge.
So
it's
worth
watching
and
the
episode
number
is
37.
A
Okay,
so
it
looks
like
what
do
we
have
next
here?
Also,
I'm
troubleshooting
the
pope.
I
know
a
lot
of
y'all
are
getting
some
error
messages
and
it
looks
like
I
will
be
troubleshooting
this
as
we
go
along
the
client
perspective.
We're
going
to
talk
to
some
of
the
clients
who
are
implementing
this
london
upgrade
and
get
some
of
their
perspectives
on
some
of
the
changes
and
how
their
client
has
come
along.
Maybe
some
challenges
whatever
they
want
to
talk
about
with
it.
So,
let's
start
with
nethermind
thomas.
J
What
was
like
the
last
thing
from
our
perspective
is
like.
We
also
could
work
with
the
x-die
team
on
a
lot
of
testing.
They
helped
us
a
lot
with
the
verifying
key
ip1559
in
different
setups.
So
I
think
that,
thanks
to
introducing
this
in
that
mind,
we
will
have
the
eip159
and
other
upgrades
from
london
in
all
the
like
aura
and
other
networks
very
soon
after
the
mainnet.
A
K
H
K
K
It
doesn't
mean
specific,
particular
anything,
so
it's
just
a
some
sort
of
short
name
which
doesn't
mean
anything
and
can
be
pronounced
pretty
easily.
I
hope
anyway,
so
our
perspective
is
that
I
was
aware
of
this
eip
1559
since
the
very
beginning,
but
I
I
must
say
that
I
wasn't
so
much
turned
on
on
what
was
going
on
for
the
last
couple
of
years.
K
K
Ethereum
has
and
not
just
kind
of
copy
paste
it,
and
but
that
is
not
ready
yet
so,
although
the
the
I
don't
think
it
will
have
a
big
impact,
it
will
mean
that
for
some
time
the
transaction
pool
implementation
won't
be
correct,
but
some
people
might
have
seen
the
the
design
for
a
new
transaction
pool.
It's
actually
been
designed
before
we
implement
it,
so
it's
currently
being
implemented
so
yeah.
That's
that's
the
challenge,
but
often
than
that.
K
Prior
there
was
a
lot
of
discussions.
People
were
trying
to
introduce
versioning,
but
you
might
remember
we're
trying
to
introduce
the
versioning
into
the
evm,
but
there
was
never
a
successful
proposal
of
how
to
exactly
roll
it
out,
and
I
think
this
will
be
the
this
will
be
the
moment
to
roll
it
up
anyway.
So
that's
for
me,
it
seems
like
a
tiny
little
change,
but
for
me
I
think
it's
the
most
important
one
you
know
no
see
and
for
the
ip1559.
K
E
L
L
I
think
that
this
is
an
interesting
upgrade,
because
it's
one
of
the
most
rigorously
tested
upgrades,
maybe
we've
ever
done,
and
the
actual
implementation
is
not
something
that
took
me
a
very
long
time
to
do.
Maybe
one
to
two
weeks
to
implement
the
base
functionality
to
sync,
with
the
original
rhodes
testnet
and
we've
spent
almost
six
months.
Iterating
on
that
small
changes,
bug
fixes,
testing,
fuzzing
and,
I
think,
is
like
an
outside
contributor
for
the
sieve
not
being
on
the
guest
team.
L
E
There
are
logic
flow
changes,
basically
how
how
the
miner
should
operate
and
there
are
all
these
different
parts.
So,
in
the
end
we
set
up
the
1559
implementation
in,
I
guess
five
or
six
different
pr's.
I
mean
this
was
a
new
transaction
format,
new
signing
type
yeah.
So
it
was
a
huge
piece
of
work
regarding
weather
is
the
most
tested
one
I'm
not
so
sure?
E
many
other
changes
we
do
are
only
basically
in
the
ebm
and
are
easy
to
to
plus
test
the
client
versus
client
tbm
versus
dbm
and
as
for
me,
I'm
kind
of
like
in
the
same
state
of
mind
as
alexi.
I
think
that
3541
is
a
pretty
significant
heap
and
that
we
have
this
new,
basically
namespace
or
code
space.
M
Yeah
sure
I
mean
my
role
really
like
in
the
actual
implementation
was
quite
small.
I
basically
just
just
met
kind
of
wrote
the
code
before
he
ended
it
off
to
to
the
get
team.
I
just
wrote
some
code
before
I
ended
up
to
matt,
and
so,
but
that
was
really
only
on
the
on
the
like
the
transaction
pool
and
the
miner,
as
martin
just
said,
like
the
the
erp
touches.
M
So
many
different
areas,
but
but
like
maybe
just
to
briefly
say
then
like
just
to
illustrate
the
the
ap
process
right
and
how
why
it's
so
hard
to
to
bring
such
an
erp
to
minute.
I
think
I
think,
I'm
not
sure
when
the
apu
was
actually
first
but
it's
several
years
ago,
and
so
it
just
for
example,
my
role
in
this
sort
of
team
actually
reached
out
to
us
last.
M
I
think
december
something
just
because
there
were
some
concerns
for
the
erp
about
how
it
would
impact
like
all
aspects
of
transaction
sorting,
so
in
in
the
in
the
mempool
there's
a
lot
of
sorting
going
on
because
sometimes
like,
of
course,
once
the
the
memphis
reaches
maximum
capacity,
you
have
to
drop
off
some
transactions.
Also,
when
you're
mining
you
have
to
find
the
most
attractive
transactions
when
a
user
basically
wants
to
bump
that
transaction
with
a
higher
price.
You
also
have
to
like
have
some
rules
in
place
and
before
the
erp.
M
M
Looking
into
this,
they
would
very
easily
see
like
how
all
this
would
affect
and
how
they
can
can
take
that
into
their
clients,
but
in
erp,
usually
in
the
beginning,
is
in
a
stage
where
the
client
developers
don't
yet
have
the
time
to
look
into
it.
Right.
Like
last
december,
the
clients
actually
were
still
working
on
the
berlin
heart
walk,
and
so
you
you
need
people
that
basically,
like
can
at
least
look
into
it
a
little
bit
and
already
kind
of
like
pre-scout.
M
Is
this
an
issue
or
can,
or
can
this
basically
just
feasibly
go
on
so
this
was
basically
like
the
role
that
we
used
them
quilting
before
then
mad
later
on
did
all
the
of
the
break
and
implementation
help
with
get
as
well,
but
like
this
was
the
first
step
just
kind
of
like
have
someone
who
has
like
at
least
some
idea
of
how
that
works.
Look
at
it
first
just
say
like
this
kind
of
this
can
work,
and
so
this
is
basically
just
the
role
that
I
help
with.
H
A
N
Thanks
for
having
me
sorry,
I
can't
join
this
call
in
person,
so
I
have
to
have
to
record
this.
So
some
short
final
update
from
the
javascript
team
before
yeah
before
we
bring
one
five
f9
in
production
great,
so
the
javascript
team
is
mainly
sorry.
I
have
to
switch
this
lights
here
to
the
slides
here.
Yeah
this
we
are
maintaining
the
the
ethereum
js
libraries
richard
with
e-series,
is
also
in
in
our
team,
but
I've
seen
that
richard
is
actually
also
joining
the
call.
N
N
So
so
the
base
here
up
code
up
efp
gas,
gas
refund
reduction
and
this
restriction
on
the
other
xerox,
ef
bytes,
one
short
mention
there-
is
an
imminent
bug
fix
release
on
the
on
the
vm.
We
have
some
wrong
159
balance
check
pr
outstanding.
This
will
be
happening
in
the
next
one
to
two
days.
It's
it's
kind
of
like
it's,
it's
mid,
much
important.
So
it's
not!
It's
not
super
critical.
E
N
For,
for
this
hard
fork,
we've
seen
various
various
ecosystem
projects
really
release
early
and
in
time,
yeah,
and
I
think
that's
really
great
yeah
just
to
mention
mentioned
too
there's
this
remix,
for
example.
Now
it's
integrated
this
actually,
this
switch.
You
can
see
it
here
in
the
screenshot
for
for
the
different
virtual
machines.
N
N
N
M
A
That
was
the
ethereum
blockchain
speaking
to
us
through
the
ether.
So
next
up
thanks
thanks
so
much
for
that
ogre
and
they
wanted
to
do
a
short
clarification.
They
said
that
the
in
the
video
they
said
that
something
about
it
being
the
most
used
1559
library
and
they
meant
that
as
not
as
the
most
used
1559
library
ever.
But
the
libraries
we
provide
are
the
most
important
one
in
the
1559
context.
A
B
And
the
messages
will
try
to
get
them
the
link
which
is
needed
to
meet
the
channel
in
case
it
does
not
work
during
the
timeline.
So
the
time
to
claim
the
birth
is
till
this
meeting
is
live
so
make
sure
you
at
least
say
hello
in
the
channel.
So
we
know
to
reach
you
and
we'll
provide
you
the
link
after
the
call
right
after
the
call.
B
Moving
on
micah
and
lifeline
are
two
from
the
group
of
our
untiring
eip
editors,
who
contributed
in
process
specification
and
enforcement
in
the
past
year
and
a
half
I
don't
want
to
miss
exec
here.
I
understand
his
contribution
on
the
eap.
Editing
side
has
been
there
for
a
very,
very
long
time.
Thank
you
so
much
for
that,
but
I'll
be
curious
to
hear
what
difference.
D
Just
since
I
feel
like
I
missed
out,
everybody
else
got
to
say
what
their
favorite
eip
was,
and
I
didn't
so.
I'm
gonna
go
ahead
and
say
that
I'm
really
excited
about
three
five:
five,
four,
the
difficulty
bomb
delay.
I've
been
looking
forward
to
this
since
the
last
difficulty
bomb
delay
and
I'm
just
really
happy
it's
happening.
I
think
it's
it's
about
time.
L
D
D
Since
since
and
I
are
clearly
fighting
over
who
gets
to
not
talk
I'll
I'll,
go
ahead
and
concede
so
1559
and
31.98,
et
cetera,
et
cetera,
something
I've
learned
from
this
hard
fork.
Is
that
just
because
an
eip
has
lots
of
authors
doesn't
mean
that
there's
actually
anyone
championing
it.
So,
if
you're
going
to
write
an
eip,
I
strongly
encourage
having
a
champion
what
a
champion
means
is
it's
someone,
who's,
very
responsive
and
quick
to
merge
things.
D
One
of
the
problems
we
ran
into
at
the
ip1559,
I
think,
is
we
actually
had
like
a
dozen
authors
on
it,
but
the
problem
is
because
there's
a
dozen
authors,
there's
no
like
strong
ownership,
and
so
what
ends
up
happening
is
someone
spend
a
full
request
to
fix
something
like
a
typo
and
it'll
just
sit
outstanding
for
a
month,
and
and
this
isn't
any
one
individual's
fault?
It's
just
that.
I
think
when
you've
got
lots
of
authors
on
the
ip.
D
You
end
up
with
this
problem,
where
everybody
thinks
someone
else
is
gonna
take
care
of
it
or
everybody's
waiting
to
see.
If
everybody
else
is
okay
with
it,
and
you
don't
have
like
the
clear
leadership
who's,
someone
who
says
yes,
this
is
good.
Let's
merge
it
so
for
future
authors,
I
I
recommend
it's
okay,
to
have
lots
of
authors
of
less
people
involved
but
make
sure
someone's
designated
as
this
is
the
person
who's
kind
of
in
charge
of
shepherding
the
cip
through.
It
really
helps
get
your
eips
through
the
process
going
forward.
D
I
think
for
the
this
london
upgrade.
I
think
this
is
the
first
one
where
we're
fully
using
the
new
eth1
specs
repo.
So
that's
good
for
me.
Probably
no
one
else
cares,
but
I
like
it
because
I
don't
have
to
see
all
the
bull
requests
and
changes
to
the
like
the
specification
document
for
london
as
they
go
through,
which
frees
up
my
time.
So
I'm
a
big
fan
other
than
that
yeah.
That's
it.
I
think
things
are
going
to
go
smoothly.
L
L
That's
something
that
we've
been
trying
to
improve
for
the
last
eight
to
twelve
months,
and
I
hope
that
whenever
we
do
this
again
with
the
merge
and
there's
some
changes
to
end
points,
then
we'll
have
a
really
good
place
to
say.
This
is
now
exactly
how
the
endpoint
should
be.
All
clients
should
implement
this
way
and
we
don't
have
any
of
these
issues
where
some
clients
implement
something
as
an
integer
or
a
hex
or
different
things.
So
that's
kind
of
been
my
takes
is
like
from
the
more
edit
editor
position
on
the
fork.
C
How
do
we
expose
this
in
json
rpc
or
you
know,
what's
the
best
way
and
what
are
the
impacts
of
the
trade-offs
there?
So
I
think,
having
kind
of
a
two-step
process
where,
like
we,
you
know,
we
we
get
like
the
clients
running
in
consensus,
all
those
chains
implemented.
We
we
build
a
bunch
of
devnets
to
test
those
and
then
once
we're
confident
that,
like
the
actual
say,
merge,
spec
won't
change
that,
like
you
know,
then
it's
like
okay.
C
So
you
know
they'll
download
like
the
get
london
compatible
and
then
they
probably
won't
upgrade
until
the
next
fork
and
if
the
json
rpc
endpoints
are
are
kind
of
not
great
in
that
they
they
kind
of
become
cemented
in
you
know,
applications
have
workarounds
to
deal
with
them.
So
yeah,
I
think,
hopefully,
for
the
merge.
We
can
just
take
more
time
to
to
yeah
have
a
couple
like
iterations
on
it.
Based
on
on
the
yeah,
the
end
users
feedbacks.
H
B
O
Yeah,
so
just
to
go
right
into
it.
So
on
each
scan
we've
made
a
bunch
of
changes
you
if
you've
been
using
robstern
or
incomiagori,
you
would
have
seen
most
of
them
already.
So
if
you
go
on
the
transactions
page,
if
you
scroll
and
you
look
for
a
transaction
that
uses
the
transaction
type
two
one,
five,
five
nine
you'll
see
this
light
bulb
here.
That
indicates
it's
a
one,
four
five,
nine
transaction.
O
You'll
see
the
same
thing
as
well
that
you
saw
earlier
and
for
the
main
block
speech
that
if
you
go
from
the
from
the
dashboard
you'll
see
this
big
total
burnt
fee
amount
to
be
very,
very
clear.
This
is
just
like
a
brief
change
that
we're
making
and,
after
things
have
settled
down,
we'll
we'll
figure
out
a
more
comprehensive
ui
for
users
for
the
apis.
O
O
And
if
you
want
to
wait
for
a
hard
fork,
you
can
you
can
do
that
as
well
and
for
the
guest
tracker
page.
We
we
don't
have
it
on
the
test
nets,
so
we
can't
show
it,
but
we'll
have
some
minor
changes
with
these
numbers
shown
on
on
the
sort
of
header
here
and
over
here,
yeah,
so
you'll
see
that
when
the
hot
fog
goes
live.
Finally,
we
do
have
some
charts
that
a
lot
of
people
refer
to.
O
I
do
want
to
highlight
that
we
won't
have
it
ready
right
at
the
start,
when
the
half
goes
live
again,
because
we
want
to
wait
for
the
dust
to
settle
down,
but,
for
example,
if
your
friendly
neighborhood
maxi
comes
and
talks
about
how
the
ether
supply
isn't
showing
up
correctly,
I
can
highlight
to
them
that
each
scan
is
going
to
get
it
fixed,
hopefully
within
a
couple
days,
but
yeah.
It
won't
be
ready
immediately
on
time
when
the
halfway
goes
like
yeah.
So
that's
pretty
much
it
for
me.
B
P
Thanks
puja
hi
everyone
so
yeah,
like
puja
mentioned,
I
work
on
the
company's
hot
wallet
team
at
coinbase.
We
place
a
strong
emphasis
on
security,
so
98
of
our
customers.
Crypto
funds
are
placed
offline
in
cold
storage,
but
whenever
customers
make
crypto
deposits
or
withdrawals,
they
flow
through
our
hot
wallet
and
that's
the
infrastructure
that
I
work
on.
P
P
In
addition,
over
the
coming
week
or
two
we're
going
to
be
rolling
out
eip1559
transactions
for
customer
withdrawals,
we
want
to
make
sure
that
our
customers
are
able
to
take
advantage
of
the
fee
savings
that
come
with
eip1559
from
the
separation
between
the
max
fever,
gas
and
max
priority
fever.
Gas
we've
been
testing
these
extensively
on
test
nets,
for
each
sends
for
erc20
token
sends
for
contract
cows
and
so
on,
and
we
feel
very
ready
for
it
and
we're
very
thankful
for
all
of
the
surrounding
infrastructure.
P
I
definitely
want
to
thank
everyone
on
this
call
for
being
such
awesome
collaborators.
It
makes
a
lot
of
sense
to
me
why
ethereum
has
enjoyed
the
success
it
has
given
how
hard
working
smart
and
open-minded
everyone
is
at
coinbase.
We've
started
to
really
embrace
decentralization
into
all
of
our
working
processes,
so
yeah
I
really
have
enjoyed
working
with
ethereum
and
and
looking
forward
to
continuing
to
do
so.
B
Q
Yeah
so
sorry
to
say,
this
will
be
sort
of
like
a
non-update
update,
but,
as
we've
decided
to
wait
until
things
go,
live
to
get
more
data
on
how
the
the
spikes
will
play
out
on
main
net.
So
we've
internally
mapped
out
a
whole
bunch
of
scenarios,
but
we're
still
debating
on
the
best
ux,
based
on
what
we
think.
Users
will
most
likely
do.
Q
Essentially
we're
trying
to
minimize
showing
like
a
huge
range
on
the
on
the
multipliers
on
the
base
fee
and
instead
optimized
based
on
not
just
the
what
the
market
is
doing,
but
also
the
type
of
transaction
or
like
a
the
the
type
of
intent
that
a
user
has
so
we'll
be
working
on
that
shortly
after
the
release.
But
we
we
think
that
it
would
be
better
if
we
get
a
little
bit
more
data
on
on
the
spikes.
B
R
Cool
thanks
puja,
so
there's
not
really
a
lot
to
say
I'll.
Just
I've
got
a
few
notes
I'll
run
through
quickly,
but
basically
for
the
most
part,
nothing
needs
to
change.
There's
a
few
more
pieces
of
information
in
the
block
like
the
base
fee.
The
receipt
has
effective
gas
price
and
the
transactions
have
your
max
fee
and
max
priority
fee
at
a
high
level.
The
main
one
one
other
changes,
there's
a
new
a
new
feature
called
get
fee
data
on
providers
and
this
coalesces
gas
price
and
all
the
new
eip
1559
things.
R
So,
for
example,
in
v6
get
gas
prices
going
away
and
you'll
just
call
get
fee.
Data
and
gas
price
will
be
sitting
in
there
if
you're
on
a
network
that
does
not
support
1559
or
yeah.
That
sort
of
thing,
but
yes,
I'm
excited.
Basically,
nothing
needs
to
change.
Ethers
will
auto
detect
whether
1559
is
available
and
use
those
features
if
they're
there
most
awesomely
1559
just
works
like
the
quick
anecdote
I
wanted
to
give
was
robston
for
all
my
test
cases
it
actually
during
the
ci
makes
robston
transactions.
R
R
I
changed
nothing,
it
was.
It
was
beautiful,
like
I
just
sent
the
transaction
and
and
voila
it
arrived
on
time.
I
didn't
need
to
do
anything
weird,
so
the
only
thing
you
really
need
to
do
is
if
you're
currently
passing
in
a
gas
price,
don't
and
you're.
You
should
be
good
to
go.
You
can
all
you
can
obviously
override
max
base
max
max
fee
and
max
priority
fee.
A
All
right
thanks
richard,
so
what
we're
gonna
do
just
to
wrap
up
here.
We're
gonna
do
a
code
announcement
one
more
time.
The
code
is
london
hf.
If
you
go
into
the
ethereum
cat
herders
discord,
there
should
be
a
user
called
pope
dashbot
and-
and
if
you
just
dm
that
user
london
hf,
they
will
send
you
a
url
that
you
can
click
to
get
your
poe
app.
I
have
been
corrected
in
dms.
It
is
poep,
it
is
not
pope.
I
apologize
to
patricio
and
the
other
po
app
heads
out
there.
A
B
Right,
I
have
a
few
quick
announcement.
Last
week
on
penny,
we
recorded
a
special
episode
on
eip
3675.
That
is
a
great
consensus
to
proof
of
a
stake
with
mikhail
kalani.
The
recording
is
going
to
be
released
later
today.
If
you
are
interested
in
understanding
the
proposed
mechanism
and
understand
how
the
switch
is
going
to
happen,
you
wouldn't
want
to
miss
the
recording.
We
have
also
recorded
a
talk
by
vitalik
buterin
on
black
ass
limit.
Last
friday,
the
recording
will
be
coming
soon.
B
B
I
understand
we
need
to
wrap
up
now.
I
would
like
to
sincerely
thank
everyone,
client
development
team,
erp
editors,
researchers
and
especially
the
tooling
team
for
joining
the
call
and
sharing
what
ethereum
users
can
expect
with
the
london
upgrade.
Thank
you,
william
schwab,
and
the
poep
team
for
saving
us
today.
Now
we
have
new
app
code.
I
request
every
user
who
are
willing
to
get
the
token
claim
it
last
but
not
least,
a
huge
thank
to
the
loving
ethereum
community
for
watching
this
stream.
B
M
Well,
maybe
just
one
thing
that
I
wanted
to
say
is
for
anyone
listening
or
maybe
it
was
only
following
along
with
kind
of
things
like
somewhat
semi-regularly
like
you
might
have
actually
heard
that
both
alexa
and
martin
mentioned
that
they
personally
are
actually
more
excited
about
this
tiny
ap
that
you
might
not
even
have
heard
about
the
3541
than
the
the
big
5059,
and
I
just
wanted
to
like
say
maybe
like
in
the
lesson
here.
Is
that,
like
sure
these
mimi
ips
are
nice,
and
actually
I'm
personally
really
looking
forward
to
that
as
well?
M
But
there's
so
much
more
going
on
behind
the
scenes
and
like
specifically,
this
item
or
bridge
format,
is
one
of
these
examples
you
might
have
never
heard
about
it
like
we
have
like
two
of
the
auto
see
on
the
call
and
the
epson
team
and
like
if
that's
something
you
just
have
never
heard
about,
look,
maybe
look
into
it
a
little
bit.
It
might
just
be
that
five
years
from
now,
this
might
be
the
more
important
change
than
this
big
1559
that
everyone
is
talking
about.
M
A
B
That's
all
thank
you
so
much
hudson
for
co-hosting
and
for
the
rest
of
the
people
who
may
be
watching
it
later
on
reach
us
at
ethereum,
cathertis
discard
for
any
question
related
to
eip
the
process.
The
upgrade
or
anything
that
you
would
like
to
understand
or
learn
about
will
try
to
help
as
much
as
possible.
I
hope
the
london
upgrade
will
be
deployed
on
the
main
net
without
any
issue
and
on
that
name,
it's
time
to
conclude
today's
meeting
so
bye
for
now.
Thank
you
for
being
the
part
of
ethereum
family.