►
Description
Resources:
EIP - https://eips.ethereum.org/EIPS/eip-3085
Discussion - https://github.com/ethereum/EIPs/issues/3086
Presentation - https://docs.google.com/presentation/d/1OIDgsIPUSRYBAOt8wNY7RgRJh-g_o9Rswu_YBtrGfZk/edit#slide=id.p
Topics:
0:57 - Introduction
3:14 - What is RPC API? Overview EIP-3085
6:10 - Related work (EIP-2015)
9:20 - Demo at Metamask implementation
10:33 - Under the hood
12:22 - Security Consideration
16:50 - Next steps
18:10 - Q&A
15:15 - How is it different in Metamask?
20:00 - Why doing an EIP for this vs. just implementing this into the Metamask?
22:10 - Most concerning security vulnerability on this EIP that can be a major hindrance in delivering this EIP?
26:28 - How do you view the process of trying to educate users?
29:40 - Value in L2 chains?
30:40 - Are there applications for RPC methods for nodes, not just wallet UI?
33:35 - Why you decided to have url field as “string arrays” in the name for the block explorer and RPC fields instead of “icon url”?
36:05 - Thoughts on Websocket support (wssUrl)?
37:13 - What is the difference between ChainId & Network Id? And why is it recommended to use chainId instead of networkId?
40:00 - Does it support all networks by entering the chainId?
42:15 - Dependency of EIP-3085 on EIP-3091?
45:20 - Creating a thread at Fellowship of Ethereum magicians?
Follow at Twitter:
Erik Marks @rekmarks | William Schwab @William94029369 | Alita Moore @AlitaMoore85 | Brent Allsop @Brent_Allsop | Pooja Ranjan @poojaranjan19
Follow PEEPanEIP earlier episodes at https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2
Contact Ethereum Cat Herders
Discord: https://discord.gg/tzYmDmF
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
GitHub: https://github.com/ethereum-cat-herders/PM
Email: support@ethereumcatherders.com
Website: https://www.ethereumcatherders.com/
A
A
B
B
When
I
had
my
crypto
aha
moment
where
I
was
like
this
is
interesting.
Material
and
ethereum
especially,
is
interesting
to
me
because
you
know
for
all
of
the
reasons
that
developers
are
usually
more
interested
in
ethereum
than
say,
bitcoin
and
yeah.
That's
that's
my
background
and
in
in
terms
of
my
current
work
at
metamask.
B
So
obviously
there
is
this
eip
that
I'm
presenting
on
today
at
3085
and
then
also
metamask
snaps,
our
plug-in
system,
which
had
a
bit
of
a
rough
2020
in
terms
of
our
ability
to
allocate
resources
to
it,
but
we're
fully
back
on
track.
Now
in
the
past,
I
was
a.
I
ended
up
being
a
significant
contributor
to
eip
1193,
which
specifies
the
ethereum
javascript
provider
api.
So
that's
window.ethereum
its
interface
for
all.
B
You
dev
developers
out
there
and
then
I'm
also
currently,
the
sort
of
steward
of
1102
opt-in
account
exposure,
which
specifies
an
rpc
method
for
requesting
accounts
from
from
wallets.
So
before
we
dive
into
eip
3085
and
what
what
this
is.
There
was
a
request
from
william
schwab,
who's
on
the
call
to
talk
a
little
bit
about
the
rpc
api
and
what
is
like,
what
is
it
what's
the
status
of
it
so
there's
basically,
json
rpc
is
what
applications
users
ultimately
use
in
order
to
talk
to
ethereum
clients.
B
There
is
an
a
url
that
we
use
in
order
to
talk
to
our
ethereum
at
node
service,
which
is
infira,
which
is
also
part
of
consensus,
which
metamask
is
part
of,
and
then
the
ethereum
clients
specify
a
json
rpc
interface
with
a
lot
with
various
different
methods
that
you
use
to
send
transactions,
get
the
latest
block
number
all
like.
Basically,
any
action
you
can
take,
read
or
write.
B
It
can,
basically
only
you
know,
run
one
chain
at
a
time
like
you
can't
do
both
you
know,
maynet
and
and
something
else
in
an
in
ethereum
client
software
simultaneously.
But
a
wallet
of
course
can
talk
to
multiple
different
chains
at
one
time,
and
so
we
defined
this
method
wallet
at
ethereum
chain
that
we
hope
will
make
it
simpler
for
adapts
to
create
requests
to
add
different
layer,
two
chains
to
wallet
applications
and
thereby
promote
the
adoption
of
layer,
two
networks,
so
I'll
pause.
B
B
So
2015
is
basically
wallet
at
aetherium
chain,
but
with
additional
functionality
for
updating
a
wallet's
representation
of
a
chain
and
we'll
get
to
exactly
what
I
mean
by
a
wallet's
representation
of
a
chain
in
a
little
bit.
But
while
it
add
aetherium
chain
is
strictly
about,
you
know,
you
identify
a
chain
by
its
a
chain
id
and
some
meta
metadata,
and
then
you
add
it
to
the
wallet
so
that
the
wallet
can
like
service.
B
That
chain
and
service
requests
to
that
chain
and
like
read
the
chain
state
and
so
forth,
update
ethereum
chain
allows
you
to
do
some
additional
stuff
like
say,
add
another
rpc
endpoint
that
you
that
the
user
can
use
in
order
to
access
the
chain,
and
so
so
that
one's
that
one's
a
little.
That
was
a
little
different
and
then
during
the
specification
of
add
aetherium
chain
and
then
the
implementation
of
ad
ethereum
chain
in
metamask.
B
We
basically
uncovered
the
need
or
realize
that
there's
a
need
for
two
more
rpc
methods
that
will
be
defined
in
two
separate,
separate
vips.
The
first
is,
while
it
has
ethereum
chain,
so
that
is
so
that
if
you're
adapt
developer-
and
you
want
to,
you
know,
ask
a
user
to
add
a
particular
chain.
You
know
it
would
be
nice
to
be
able
to
ask
like
does
the
user
have
this
chain?
B
Or
do
I
need
to
like
show
a
button
that
they
should
add
it
or
like
stuff
like
that,
then
switch
ethereum
chain
is
basically,
as
we
implemented
support
for
this
method
in
metamask,
which
should
be
shipping
any
day
now
version
9.1.0
of
the
metamask
extension
will
have
the
first
working
implementation
of
at
ethereum
chain.
You
know
we.
Basically,
we
basically
ended
up
creating
all
of
the
functionality
for
an
rpc
method
that
just
switches
the
currently
selected
chain
in
the
wallet.
B
If
the
wallet
has
a
concept
thereof,
so
we're
just
going
to
go
ahead
and
people
have
been
asking
us
to
do
that
for
a
long
time,
so
we're
just
going
to
end
up
creating
an
eip
for
that
method
as
well
and
yeah.
So
that
is
a
bit
about
what
the
method
is
and
then
rather
than
me,
just
talking
about
it.
I
have
a
demo
of
how
this
looks
in
practice
in
the
metamask
implementation,
and
so
I'm
going
to
play
this
video
and
talk
through
what
happens.
B
B
Let's
see
if
I
can
switch
this
slide
so
under
the
hood
what's
happening
here,
is
that
we
are
using
the
ethereum
javascript
provider
api.
So
this
is
exactly
actually
what
the
on
the
left
here.
That's
what
the
what
the
actual
code
that
calls
the
method
it
looks
like
in
the
webpage,
and
this
is
per
eip1193,
the
javascript
provider
api
and
then
the
interface
for
this
request.
B
But
even
there
for
some
networks,
like
usually
the
native
currency,
is
just
basically
eth
with
a
different
name.
But
for
some
networks
like
say
optimisms
network,
their
native
currency
is
eth,
but
it's
an
erc20.
So
it
functions
a
little
bit.
So
it
functions
a
little
bit
differently
but
yeah.
So
that's
what
it
looks
like
under
the
hood
and
then
there
are
a
lot
of
security
considerations
like
that.
B
It's
the
it's
the
id
that
is
used
as
part
of
signing
transactions
before
they're
submitted
to
the
actual
blockchain.
So
it's
extremely
important
to
get
the
chain
id
right
and
minimally.
You
will
always
need
that
because,
like
there
is
no
chain
without
a
chain
id
effectively,
then
the
specification
is
pretty
loose
with
requiring
other
parameters,
because
it's
possible
that
a
wallet
could
implement
this
method
and
have
like
a
predefined
list
of
chains
to
choose
from.
B
B
Could
you
know,
submit
any
information
to
the
wallet
and
you
know
create
like
it
could
say
that
it
could
give
you
the
xdi
chain
id,
and
it
could
give
you
the
chain
name
of
a
bunch
of
like
of
like
a
completely
different
chain
and
trick
the
user
in
that
way.
So
the
reason
the
security
consider
consideration
section
is
very
long
is
like
you
know:
how
do
you
make
this
method
reasonably
safe
to
use?
B
And
then
you
should
only
use
the
chain
id
submitted
with
the
request
in
order
to
sign
transactions.
So,
like
don't
ask
the
endpoint
at
runtime
at
what
the
chain
id
is
because
a
faulty
or
malicious
endpoint
could
lie
and
cause
the
user
to
sign
transactions
for
a
chain
other
than
the
one
they
intended,
which
is
very
bad
and
then,
of
course,
with
rpc
endpoints
like
even
if
the
endpoint
isn't
malicious.
B
You
know
it
minimally
sees
every
rpc
method,
call
that
the
user,
that
the
user's
wallet
submits
to
the
endpoint
and
also
sees
the
user's
ip
address.
So
that's
important
to
be
aware
of
them
for
the
user
to
be
aware
of,
and
then
there's
all
the
like,
ux
stuff
that
I
mentioned
and
trying
to
validate
parameters
to
the
best
extent
possible.
So
there
is
a
website
maintained
by
the
sort
of
co-maintained,
I
think
by
liggy.
B
I
forget
what
name
is
and
pedro
gomez
that
keeps
a
list
of
common
chains
and
their
metadata.
So
that's
something
that
metamask
uses
to
try
to
do
some
minimal
validation
and
warn
the
user.
If
anything
seems
wrong,
I
think
I
skipped
one
yeah
and
so
finally,
just
next
steps,
I've
been
talking
a
lot
and
I
want
to
get
move
on
to
the
discussion.
So
eip3085
is
currently
in
draft
in
order
to
get
it
to
review
and
then
last
call.
B
Since
vip
3085
has
already
received
significant
attention
from
editors
and
community
members,
and
I
want
to
thank
mike
zoltu
and
ronan
sanford
in
in
that
regard,
especially
and
then,
as
previously
noted,
I
will
also
create
eips
for
all.
It
has
ethereum
chain
and
wallet
switch
ethereum
chain,
and
that
is
the
presentation
and
I'm
you
know,
look
forward
to
answering
any
questions
you
may
have
at
this
point.
Thank
you.
So.
D
First
off
great
presentation,
thank
you.
I
really
like
the
demo.
Do
you
mind
explaining
more
about
like
how
it's
done
currently,
because
you
know,
for
example,
like
ledger,
you
can
do
you,
can
access
chains
and
stuff
but
like
how
is
it
different?
How
is
this
different
from
the
way
that
it's
done
in
that
case.
B
B
D
B
You
know
the
individual
apis
of
any
number
of
different
wallets
out
there,
and
so
we
try
to.
Whenever
we
create
ad
functionality
that
could
be
standardized,
we
try
to
standardize
it
and
create
an
eip
for
it,
so
that
you
know
other
wallets
can
simply
go
and
be
like.
Aha,
I
want
to
add
this
functionality.
Here's
an
eip.
B
B
D
B
D
B
No,
no,
I
don't.
I
don't
think
it's
damning
for
this.
I
think
I
think
you're
absolutely
right.
It
is
an
impossible
problem
to
solve
fully,
but
I
don't
think
that
it's
damning
for
this
eip
by
any
means,
I
mean,
I
think
the
users
have
demonstrated
that
you
know
they're.
Many
of
them
have
demonstrated
that
they're
willing
to
accept
the
risks
and
people
are
going
to
and
as
long
as
at
layer,
one
network
fees
or
gas
costs
remain
as
high
as
they
are.
B
People
are
going
to
try
to
look
for
a
cheaper
alternatives,
and
you
know,
and
as
and
as
a
community
like
we.
I
believe
that
we
that
we
need
it,
and
this,
and
this
particular
eip
is
sort
of
it,
makes
it
easier
to
add
those
networks,
but
users
seem
to
figure
out
how
to
add
them
even
without
it
and
so
those
security
concerns.
Are
I
see
them
as
orthogonal
to
this
eip,
just
like
in
its
tiny
little
universe,
of
creating
a
useful
interface
for
adding
networks
to
the
wallet.
D
C
If
I
could
hop
on
the
the
end
of
that,
though,
there
was
something
that
I've
been
thinking
about,
asking
which
is
the
nature
of
this
proposal,
probably
means
that
at
some
point,
there's
going
to
be
some
user
of
metamask
who
ends
up
getting
fed
bad
data
or
something
like
that.
How
do
you
view
the
process
of
of
trying
to
educate
users
like
sort
of
the
the
task
of
like
desperately
trying
to
get
their
attention?
To
like,
say
like
hey
here?
Are
the
concerns?
Here's
what
you
need
to
be
careful
with.
B
Right
sure,
and
so
one
of
our
designers
that
spend
you
know
the
most
of
the
time
on
our
team
thinking
about
those
questions
would
be
better
to
talk
to,
but
I
can
definitely
speak
to
some
of
it,
because
it
is
something
that
we
like
at
metamask.
We
have
to
think
about
that
constantly
and
how,
to
you
know,
get
your
users.
B
B
That
gets
the
user
to
be
like
wait.
Should
I
really
be
doing
this,
or
should
I
go
to
google
and
like
check
like
try
to
understand
what
is
this
thing
that
I'm
trying
to
add
to
metamask
and
how
does
it
actually
work?
Do
other
people
use
it
to
other
people,
trust
it,
and
so
it's
a
constant,
basically
thinking
about
like
how
to
educate
users
about
risks
and
try
to
invite
and
thinking
about
like
what
they
need
to
understand
and
then
informing
them
of.
C
C
B
B
The
reason
I've
been
talking
about
layer
twos
is
because
they're
very
much
at
the
top
of
my
mind
in
terms
of
like
you
know
why
this
method,
why
now
you
know
the
extremely
high
network
fees
and
the
main
netting
of
evm
layer
twos
like
optimism,
for
instance,
there
are
a
bunch
of
others
as
well.
You
know
that's
why
it
was
high
time
that
this
method
came
into
existence
and
was
and
is
added
to
wallets.
D
C
Understand
that,
just
as
a
last
question
from
my
side
also,
I
was
wondering
if
there's
application
for
rpc
methods
like
this,
not
just
for
wallet
ui
but
also
in
terms
of
nodes,
as
in
these
days,
at
least
with
the
nodes
that
I'm
familiar
with,
if
you'd
like
to
run,
say
a
main
net
node
and
rap
stunt
mode.
So
you'll
need
two
completely
different
instances.
You'll
need
to
work
the
ports
out,
you'll
kind
of
need
to
work.
Everything
out.
C
That's
fair.
That
is
fair
enough.
I
understand
there's
a
the
this
is
like
the
wallet
method,
but
at
the
same
time,
when
you
were
talking
about
the
ability
to
kind
of
allow
more
chain
management,
the
way
that
this
vip
does
it
made
me
wonder
if
maybe
there's
a
maybe
there's
an
application
there.
Also
okay,
yeah.
B
Yeah
I
mean
it,
you
know,
I
will
add
there
that
you
know
the
reason
that
this
that
this
is
a
thing
your
currently
selected
network
in
metamask
is
something
we
we
just
inherited
that
from
the
ethereum
clients
which,
as
you
said,
are
configured
in
exactly
that
way.
There's
no
reason
for
a
wallet
really
to
just
like,
because
metamask
literally
like
this
isn't
just.
Unfortunately,
this
isn't
just
like
a
view
in
the
ui.
This
chain,
literally,
like
metamask,
only
communicates.
B
D
A
So,
first
of
all
like
it
as
I
mentioned,
it
was
a
wonderful
presentation,
thanks
a
for
that,
and
I
must
say
that
by
this
time
you
have
already
answered
a
few
questions
that
were
in
my
mind
for
this
proposal,
but
I
have
a
few
more
first
one
is
related
to
the
url
field.
So
there
was
this
discussion
going
on
around
the
url
field.
So
could
you
briefly
talk
about
why
you
decided
to
have
url
field
as
a
string
arrays
like
in
the
name
of
blog
explorer,
explorer
and
rpc
field?
B
Sure,
yeah
yeah,
I
can
definitely
talk
about
that
and
I
will
pull
up
the
relevant
slide
as
well.
So
yes,
all
right
so
then
we're
talking
about
you
know.
Why
did
we
decide
to
go
with
string
arrays
as
opposed
to
just
strings?
Basically
you
know
just
to
for
for
icons.
There
was
there.
Was
this
thought
that
you
know
a
like
often
times
like
when
you
have
like
icons
for
for
a
website.
B
You
know
they
can
be
in
multiple
sizes,
multiple
file
formats,
whatever,
and
so
that's
simply
a
desire
to
support
that
functionality.
And
just
let
you
know
the
wall,
you
can
just
choose,
whichever
one
it
wants,
that
fits
its
ui,
the
best
it
you
know
personally.
If,
if
I
were
super
opinionated
and
just
did
what
I
wanted,
I
would
just
be
like
icon,
single
icon,
url
single
svg
file.
B
There
can
only
be
one
like
we
just
take
the
first
one
and
ignore
the
rest,
because
we
don't
really
have
a
way
to
support
multiple
at
the
moment
like
we
want
to
and
there's
or
I
think
we
want
to,
and
we,
but
we
have
some
ref
actoring
to
do
before
we.
We
could
hope
to
support
that.
But
again,
like
there's.
Just
no
reason
for
the
specification
to
be
like
there
can't
be
multiple
rpc
endpoints.
More
than
anything.
A
B
B
B
Metamask
at
the
moment,
we
do
not
have
websocket
support
just
yet,
but
we
definitely
want
to
go
there,
and
you
know
with
hindsight
like
we
would
have
I'd
love
to
have
had
websocket
support
for
a
long
time,
but
yeah
for
speaking
for
our
own
part.
That's
definitely
something
we
we
want
to
do
in
the
hopefully
near
future.
A
Great
that's
good
to
know
so.
My
next
question
is
related
to
the
chain
id
like,
as
the
proposal
suggests,
the
method
accepts
a
single
object,
parameter
with
a
chain
id
and
some
chain
metadata,
and
the
method
returns
null
if
the
chain
was
added
to
the
wallet
and
frozen
error.
Otherwise,
so,
like
I
was
wondering
first,
like
you
know
what
is
the
basic
difference
between
chain
id
and
network
id
and
why
is
it
recommended
to
use
chain
id
instead
of
network
id.
B
Sure
so
chain
ids
were
introduced
with
eip
155,
which
I
think
was
just
written
by
vitalik
for
the
purpose
of
replay
attack
protection
so
like
when
you
have.
If
you,
when
you
sign
a
transaction
for
ethereum,
you
perform,
you
take
the
transaction
like
data,
and
then
you
perform
a
bunch
of
operations
on
it
and
then
prior
to
the
introduction
of
chain
ids.
You
know
you
that
transaction
was
submissible
to
any
chain
like.
B
You
have
a
different
network
and
chain
id.
So,
there's
a
mismatch
between
the
two,
so
the
chain
id
has
effectively
superseded
the
network
id
and
that's
why
the
network
id
is
just
omitted
in
the
specification
because
as
of
eip155
and
then
695,
which
specifies
the
rpc
method
for
getting
the
chain
id
from
the
node
and
that
one
which
I
also
helped
author.
Since
those
methods
like
there's,
never
any
reason
to
use
the
network
id
over
the
chain.
Id.
A
Okay,
so
I
mean
like,
while
you
were
explaining
about
the
like
network
selection
processor,
I
would
suppose
that
it
means
that
method
can
be
used
for
ethereum
and
few
other
networks.
At
the
moment,
I'm
aware
that
it
supports
ethereum
ethereum
testnet,
as
you
have
shown
along
with
extar.
Is
there
any
specific
network
that
it
is
supporting
or
just
it
can
be,
supporting
every
network
just
by
entering
the
rpc
node
number
a
chain
id
there.
B
Yeah,
so
so
there's
a
lot
of
in
order
to
in
order
to
support
a
network.
There
is
a
a
lot
of
stuff
that
this
eip
doesn't
deal
with.
So,
like
obviously
like
any
wallet,
that's
ethereum
compatible
will
have
like
a
ton
of
functionality,
that's
about
handling
transactions,
signing
transactions,
reading
data
from
the
chain
and
so
forth.
So
as
long
as
the
network
is
evm
compatible,
it's
good
to
go
and
it
and
it
can
be
added.
B
But
if
it's
not,
then
this
this
method
is
called
ad
ethereum
chain,
because
we
can't
necessarily
anticipate
the
kind
of
or
we
not
necessarily.
We
can't
anticipate
the
kind
of
metadata
that,
like
any
arbitrary
blockchain
protocol
at
10
years
from
now,
will
need
in
order
to
be
useful
in
the
wallet.
And
so
that's
why
it's?
B
You
know
ethereum
one
chains
only
effectively
at
this
point
pedro
gomez,
my
co-author
is
involved
in
a
in
a
github
organization
called
chain
agnostic
that
have
these
chain
agnostic
improvement
proposals
c
ca,
ips
at
where
he
and
others
are
experimenting
with
creating
standards
for
like
cross
chain
chain
ids,
and
that
and
that
kind
of
thing.
So
there
are
other
ecosystem
efforts
for
non-ethereum
chains.
That
was,
I
went
a
little
bit
off-road
there,
but
did
that
answer
your
question.
A
So
that's
all
from
the
side.
I
have
a
like
couple
of
questions
on
the
proposal
side
like
in
your
last
slide.
You
have
mentioned
that.
Currently
it
is
in
draft
and
the
next
thing
would
be
maybe
review
or
the
last
call.
Obviously
it's
going
to
be
review,
because
that
is
a
new
status
that
is
introduced
in
between
draft
and
the
last
call.
A
A
B
Right
right,
good,
thank
you
for
asking
that,
and
I
should
have
put
it
in
the
slide,
I'm
going
to
remove
3091
as
a
dependency,
because
I
think
you
know
that
that
was
entirely
pedro's
initiative.
I
think
it
came
up
during
discussion
or
like
pedro
anticip,
someone
anticipated
it
probably
pedro.
It
was
just
like
you
know,
if
you
add
a
block
explorer
url
like
there's
a
lot.
If,
if
the
routes
are
standardized
for
like
looking
at
transactions,
looking
at
accounts
or
specific
addresses
and
so
forth,
then
there's
a
lot.
B
A
A
Authors
to
you
know,
move
the
discussion
to
section
to
the
fellowship
of
ethereum
magician
because
that's
like
the
best
place
to
go
to
about
discussing
any
of
the
proposal
and
that's
the
place
where
any
proposal
get
more
eyes.
You
know.
So
I
was
wondering
like
what
are
your
thoughts
on
creating
a
threaded
fellowship
of
ethereum
magician.
While
you
are
considering
it
to
move
it
to
the
review
status.
B
Yeah,
I'm
definitely
open
to
doing
that.
It's
funny
micah
zoltu
asked
me
about
I.
I
changed
the
discussions
to
link
of
an
existing
eip
to
a
to
a
github
issue,
because
for
some
reason
I
convinced
myself
that
that's
what
we
were
supposed
to
do
now,
but
yeah
no
clearly
they
should
be
on
the
fellowship
of
ethereum
magicians.
B
A
That's
great,
you
know,
I
mean
I
understand
this
is
a
fairly
new
process.
We
published
a
blog,
I
think,
member
or
december
of
2020
about
explaining
the
process,
this
introduction
of
review
status
and
how
this
standardization
process
should
go
ahead,
because
it
is
actually
being
separated
from
the
network
upgrade
process.
So
we
are
trying
to
educate
people
on
how
and
where
we
should
be
going
for
what
steps.
So
that's
fine.
Thank
you.
So
much.
A
A
On
this
note
for
our
youtube
viewer,
if
you
have
any
questions
that
could
not
be
answered
in
today's
episode,
you
may
leave
a
comment
or
ask
the
author.
His
twitter
handle
is
provided
in
the
description
section
below
we
are
planning
to
have
eric
again
in
two
weeks.
I
guess
to
talk
about
eip
1474
remote
procedure
called
specification,
and
next
week
we
are
going
to
talk
about
eip3074
that
is
native
sponsored
transaction
with
sam
wilson,
so
stay
tuned.
A
Your
feedback
is
important
to
us.
Let
us
know
how
you
like
this
episode
and
which
eip
would
you
like
to
see
in
future,
episodes
drop
by
our
ethereum
cat
herders
discard
invite
linking
is
provided
in
the
description
box
if
you're
a
first
time
viewer
for
our
show,
subscribe
to
ethereum
canada's
youtube
channel
hit
the
bell
icon
for
updates,
don't
forget
to
like
and
share
keep
watching
and
keep
sharing
your
love
with
ethereum
cat
headers.
This
is
all
of
us
signing
out.