►
Description
Topics covered
-----------------------------
1:32 - Guest Intro
2:55 - Assumptions
05:09 - Problem statement
6:50 - Proposed solution
9:25 - Reference implementation
13:09 - Details (Code snippets)
13:30 - Implementing ERC-4400
14:12 - How is EIP-4400 used now?
18:14 - What does it enable?
22:03 - Q&A
22:44 - What is the difference between proposal EIP-4400 and EIP-2615?
25:15 - If EIP-4987 can be complementary to EIP-4400?
27:50 - EIP working group
31:21 - With multiple utilities, does the proposal allow the owner or renter to split utilities.
34:10 - Are you aware of any implementations?
36:45 - Any security considerations to keep in mind?
38:25 - What are your thoughts on the current Standardization process?
40:24 - Do you see any need for change in the ERC process?
41:45 - Any specific challenge faced during the documentation of an EIP?
43:25 - Anything else you would like to share?
Resources:
-----------------
Slides: https://docs.google.com/presentation/d/19ABzIwph43v5iHj6aRwJJhuuFZq0WiayyROIs3Dl_SQ/edit?usp=sharing
PEEPanEIP playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
ERC Playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxqXee9EMQDIEz2CslTnsW0K
Check out upcoming EIPs in Peep an EIP series at https://github.com/ethereum-cat-herders/PM/projects/2
Follow at Twitter
-----------------------------------------------
Daniel Ivanov @danielkivanov | 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-herders
Website: https://www.ethereumcatherders.com/
A
A
A
Right
so
just
to
provide
some
more
info
about
this
proposal.
This
eip4400
is
a
standard
track.
Erc
proposal
drafted
in
september
2021
is
merged
as
final
in
may
2022
and
is
available
for
application
developers
to
implement
in
their
projects.
In
this
episode,
we
will
learn
more
about
the
proposal
with
danielle,
starting
with
a
brief
introduction.
So
without
further
ado,
let's
peep
in.
B
Thanks,
okay,
so
just
an
introduction
of
myself.
I've
been
building
in
the
web3
space
for
several
years
now
and
I'm
the
co-founder
of
enter
dao,
which
is
a
dao
focused
on
building
metaverse
related
protocols,
one
of
which
is
called
land
work
or
land
works,
which
is
actually
the
reason
why
this
eip
was
introduced
in
the
first
place.
B
B
We
already
have
examples
for
for
that,
with
metaverse
land
or
game
items,
those
nfts
have
inherent
utility
built
into
them,
so
land
can
be
used
to
build
scenes
or
experiences
on
top
of
it.
Game
items
are
used
to
enhance
or
a
given
character
with
additional
stats
or
even
provide
a
separate
look
to
that
character.
B
B
So
the
best
case
to
showcase
or
validate
those
assumptions
are
by
looking
at
the
existing
metaverse
projects.
Developers
are
defining
their
own
custom
roles
that
utilize
or
capture
the
utility
of
a
given
nft.
A
clear
example
of
this
is
metaverse
land,
and
actually,
although
it's
the
first
example
as
I
already
mentioned,
I
do
not
think
that
it
will
be
the
last
one
so
giving
concrete
examples.
B
The
centerland
has
developed
the
concept
of
an
operator
and
an
operator
is
simply
another
address
that
is
able
to
deploy
scenes
or
experiences
to
that
land
in
the
in
the
metaverse,
but
it
does
not
have
the
full
ownership
permissions
attached
to
it.
Another
example
is
cryptovoxels
now
voxels
they
have
the
concept
of
collaborators
and
guess
what
collaborators
are
the
same
as
operators,
although
they
have
a
different
name,
so
they
have
the
same
functionality.
B
B
The
concept
for
the
interface
has
a
lot
in
common
with
the
approval
concept
of
erc721s,
meaning
that
the
token
id
can
only
can
have
only
one
consumer
set
at
a
given
time.
The
same
way
as
the
same
way
as
having
only
one
approved
address
for
a
token
id.
We
can
see
the
other
two
functions
there.
The
consumer
of
and
change
consumer
consumer
office
is
a
super
simple
standard
view
function
that
just
returns
the
consumer
at
the
moment.
B
B
B
Okay,
so,
along
with
the
eip,
there's
an
example,
implementation
that
users
can
easily
extend
and
not
implement
the
standard
themselves
and,
as
it's
shown,
the
extension
extends
the
erc721
and
has
only
one
additional
state
mapping
mapping
that's
stored
in
state,
which
is
a
mapping
between
the
token
id
and
the
given
consumer
of
the
token
specified
at
a
certain
moment
of
time
and
there's
no
changes
to
the
constructor
the
same
way.
You
you
create
a
new
c721.
B
You
create
earlier
721
consumable.
What
what
we
should
point
out
here
is
that,
obviously
we
have
the
consumer
of
view
function
that
simply
returns
the
consumer
of
a
given
token
id.
We
have
the
function
of
a
change
consumer
and
something
that
is
worth
noting.
Is
that
not
only
the
owner
of
the
token
id
can
change
the
consumer,
but
but
actually,
if
the
sender
is
an
approved
address,
he
can
change
the
consumer
as
well
or
if
the
sender
is
approved.
B
We
have
the
supports
function
there
as
well,
which
is
a
standard
one
and
something
that's
more
more
subtle,
but
it's
important
to
specify
is
that
we
are
overriding.
The
before
token
transfer
hook
provided
by
open
settling
so
before
you
transfer
something
a
normal
normal
ear.
C721
clears
out
the
approve
the
approved
address
for
the
token
and
the
same
way
that
the
approved
address
of,
for
the
token
is
cleared
the
same
way.
B
B
Although
it
is
recommended-
and
it's
specified,
as
recommended
to
clear
out
the
address
to
the
zero
address
of
the
consumer
on
every
transfer,
you
may
decide
to
set
it
to
some
specific
address,
for
example,
on
every
transfer,
the
talk
default
consumer
of
every
token
is
assigned
to
some
administrative
address,
that's
something
that
was
received
as
a
feedback
during
the
review
process,
and
that's
why
we've
made
made
the
eip.
The
address
not
to
be
a
must
to
be
changed
to
the
other
zero,
but
the
recommended
one.
B
So
before
we
are
transferring
tokens
we're
clearing
out
the
consumer,
and
when
we
clear
out
the
consumer,
we
are
obviously
emitting
the
consumer
changed
event.
That's
that's
the
actual
reference
implementation.
Now
I
want
to
show
you
now
how
people
can
actually
extend
it
and
include
it
into
their
contracts.
Yeah
I
already
covered
here.
What
I'm
showing
the
slides
right
now
is
the
code
snippet
for
the
before
token
transfer
modification
that
clears
out
the
consumer
on
every
transfer.
B
We
already
covered
that
a
couple
of
minutes
ago.
So
how
does
it
look
like
to
actually
use
and
create
such
a
token?
Well,
it's
super
simple
here
you
can
see
a
code
snippet
that
imports
the
erc721
consumable
solidity
file
that
I
just
showed
previously
and
it
simply
calls
the
constructor
with
the
two
arguments,
the
name
and
the
symbol,
and
everything
else
is
handled
automatically.
You
don't
have
to
implement
some
functions,
extent,
etc.
By
default.
B
B
B
After
she
receives
the
nft
she
can.
She
can
actually
deposit
it.
Let's
say:
there's
a
yale
farming
campaign
for
that
for
the
same
marketplace:
rent
land,
renting
marketplace.
Let's
say
that
the
developers
of
the
of
the
marketplace
want
to
incentivize
people
to
use
the
marketplace
so
they're
using
the
normal
mechanics
by
providing
yield
farming
campaigns,
and
you
can
deposit
the
eip4400
nft
that
you
got
issued
into
that
yield
farming
campaign
when
you
deposit
it
technically
speaking,
the
ownership
is
the
ownership
of
the
nft
is
within
the
yield
farming
contract.
B
So
you
cannot
actually
collect
your
fees
or
manage
your
listing,
etc.
So
what
the
iep
provides
as
a
functionality
is
whenever
she
alice
deposits,
her
nft
the
contract
sets
her
as
a
consumer.
So
while
the
ownership
is
within
the
yale
farming
contract,
alice
is
set
as
a
consumer
of
that
nft
and
what
what
what
it
basically
means
is
that
she
can
go
to
the
land
renting
marketplace
and
manage
her
listing
she
can
collect
rent.
She
can
update
the
renting
conditions
while
at
the
same
time
the
contract
is
deposited
and
owned.
B
So
that's
one
example
that
we
can
see,
which
is
life
currently
and
is,
is
working,
but
what
else
we
can
see
what
else
we
can
do
with
it.
So
I've
already
mentioned
that
users
can
delegate
the
management
of
their
erc721
to
some
other
person
or
actually
to
themselves
but
provide
the
ownership
to
an
ftl
farming
contract,
for
example.
That's
that's.
The
first
example
nft
owed
farming
example.
B
B
The
first
iteration
of
nft
renting
was
was
implemented
by
actually
transferring
the
ownership
of
the
nft
to
the
renter
and,
if
you
think
about
it,
when
you
rent
a
car
or
you
rent
an
apartment,
you
do
not
get
the
ownership
of
that
apartment
or
a
car.
You
just
you're,
just
renting
it
for
a
while.
The
owner
is
still
the
owner.
B
You're,
not
you're,
not
you're,
not
getting
you're
not
being
owner
while
you're
renting
it,
and
that's
that's
actually
a
limitation
to
the
first
iteration
of
nft.
Renting
now,
when
there's
a
separate
role
called
consumer
that
doesn't
have
the
ability
to
transfer
doesn't
have
the
ownership
rights,
we
can
build
out,
non-collateralized
nft,
renting,
meaning
that
you
don't
have
to
pay
some
amount
just
to
get
your
energy
just
to
to
rent
an
nft
and
pay
the
rent.
On
top
of
that,
you
are
just
paying
for
the
rent
and
being
able
to
utilize.
B
The
nft-
and
I
what
I
mean
trustless,
is
since
it's
inherent
to
the
erc721
you're,
only
trusting
the
the
smart
contracts
and
the
code,
if
there's
bugs
yeah
that
that's
that's
a
problem,
but
if
it's
written
properly
as
we
can
see,
unisop
can
be
can
be
thought
of,
as
is
a
public
good.
Almost
it's
it's
not
controlled
by
by
anyone
at
this
point
at
least
the
v2
or
the
other
versions.
B
It
is
actually
fractionalize
it
and
through
the
consumer
extension
again
when
you
fractionalize
it
you're
you
you're,
going
to
enable
someone
else
to
manage
it
or
you
can
manage
it
yourself
or
the
person
that
has
the
majority
of
the
shares,
etc.
You
have
more
flexibility,
you
don't
have
to
vote
on
everything
or
the
functionalization
protocol
is
not
required
to
to
to
manage
the
nft.
There
might
be
someone
else
that
manages
the
nft
generating
the
nft
that
generates
yelp,
so
that's
basically
the
overview
and
what
it
enables.
A
Thank
you
so
much
daniel
for
sharing
this
presentation
and
explaining
reference
implementation
and
even
the
code
snippet
things.
I
hope
this
will
be
helpful
for
developers
trying
to
implement
it
in
their
project.
So
for
people,
if
you
have
any
question,
you
can
drop
it
down
on
the
chat
and
we
can
probably
read
it.
B
A
So
my
first
question
is
about
the
renting
usage
and
multiple
proposals,
so
it's
been
observed
that
the
eip
repository
is
getting
multiple
proposals
for
the
same
kind
of
use
case
here.
The
use
case
is
ranked
so
following
the
discussion
on
fem,
I
figured
there
are
a
couple
of
more
and
one
of
them
is
eip2615.
A
B
The
two
six
one
five
eip
is
stagnant
for
a
while.
I
would
say
that
the
differences
are
the
following.
So
if
you
see
the
interface,
it
introduces
a
lot
of
complexity
and
the
proposed
interface
is
quite
big.
It
has
a
lot
of
functions
there
and
it's
not
lean
design
similar
to
what
we
have
simple
two
functions
in
one
one
event,
so
it
it
takes
the
approach
of
introducing
a
new
type
of
owner.
Therefore,
it
added
it
adds
a
lot
more
functions,
such
as,
adding
bounces
to
adding
balance,
functions,
etc.
B
Where,
in
the
four
four
zero
zero
eip,
we
we
are
leaning
more
towards
the
approval
or
delegation
side,
and
it
makes
it
smaller
in
terms
of
interface
compared
to
to
the
statement,
one
that
you're
referring
to.
If
you,
just
if
you
open
the
interface,
you
would
see
that
there's
20
new
functions
and
as
a
developer,
when
you
see
that
you
have
to
implement
20
new
functions
to
an
already,
I
don't
know
20
functions
of
within
the
year,
c721
you're.
Just
you
just
start.
A
B
I
think
that
theoretically,
renting
could
be
implemented
through
the
4987,
and
I
would
generally
say
that
I
cannot
think
I
cannot
see
a
straightforward
way
on
how
to
complement
each
other
they're,
just
taking
different
approaches
and
trying
to
tackle
the
issue
from
different
perspective
and
what
it
is
worth
noting
is
that
4987
actually
defines
not
only
erc721
changes,
but
year,
c20
and
1155,
which
is
more
in
terms
of
scope.
So
if
it
turns
out
that
that
health.
A
B
A
A
B
B
What
I
saw
was
that
there
are
multiple
people
trying
to
solve
the
same
problem.
They
are
all
proposing
different
stuff.
You
try
to
collaborate,
but
there's
quite
a
friction
in
in
some
cases
and
at
the
end
of
the
day,
what
I'm
scared
of
is,
let's
say
that
this
eip
has
been
finalized
at
some
point,
some
other
eip
related
to
or
tackling
renting
is
finalized
as
well
one
two
or
three
years
down
the
line.
B
Some
of
the
best
standards
that
I
think
the
crypto
industry
has
come
up
with
was
the
erc20
and
here
c721s
and
there's
no
there's
no
other
alternative,
so
to
say,
they're,
all
those
the
three
1155
721
and
erc20
and
those
are
the
dominant
ones
and
those
are
perfectly
fit,
but
those
perfectly
fit.
But
for
renting
or
other
types
of
extensions,
I
think
that
we
might
see
blurring
and
I
really
hope
that
we
have
a
good,
coherent
standard
for
different
types
of
things.
B
That's
something
that
I,
I
think
might
be
a
problem
and
it's
a
hard
problem
to
tackle
because
you
as
a
maybe
an
eip
maintainer.
Let's
say
you
have
to
keep
in
mind
that
there's
already
something
else,
that's
similar
to
what
this
person
is
proposing.
So
you
better
go
and
collaborate
with
that
person.
Otherwise,
we'll
have
we'll
end
up
with
multiple,
not
perfect,
standards
for
for
the
same
functionality.
A
C
A
They
either
encourage
having
an
extension
of
something
like,
for
example,
we
started
working
on
this
as
an
extension
to
seven
to
one.
So
that's
generally
the
idea,
if
you're
providing
more
than
whatever
is
existing,
then
only
they
are
allowed
to
be
merged
as
final.
Otherwise,
there
should
be
some
major
drawback
of
the
earlier
proposal
that
the
new
proposal
is
solving
again.
We
will
try
to
have
a
single
proposal
for
people
to
follow
as
a
standard.
A
C
B
B
B
But
if
it's
something
different,
let's
say
I
don't
know
who
is
eligible
to
collect
rent
out
of
that
nft
might
be
suitable
to
go
to
the
consumer,
because
the
owner
might
not
be
the
one
that
actually
produced
the
the
the
yield
it
was
produced
because
of
the
consumer.
So
there's
different
use
cases
and
there's
room
for
you
to
to
to
to
interpret
them.
As
you
wish
understood,
thanks.
A
B
So
we
have
several
implementations
that
I
am
aware
of.
Obviously
our
project
was
the
first
one.
Landworx
cryptovoxels
are
working
on
a
new
version
of
their
token
and
they
have
incorporated
it
as
well,
which
is
something
very
cool
because
they
are
major
player
in
in
the
crypto
industry,
so
to
say,
or
at
least
the
metaverse
industry.
Oh
referring
to
help
open
zeppelin,
they
tend
to
add
extensions
or
include
those
implementations
after
they
are
finalized
and
there's
a
significant
traction
and
developers
actually
want
to
use
it.
B
A
B
Yeah,
so
that's
oh
one,
actually,
another
project
that
I
just
thought
of:
there's
a
marketplace
for
nfts,
which
is
a
sort
of
competitor
to
openc
called
universe,
and
by
default
they
are
providing
way
for
users
to
mean
their
own
collections.
By
default
they
are
minting
nfts
with
the
consumer
extension,
so
people
can
easily
rent
their
collections
to
other
people
because
they
are
implementing
the
standard.
A
C
B
B
Mind
yeah
well,
I've
we
we've
added
it
into
the
security
section
as
well,
and
I'm
going
to
repeat
it
again
here.
It
is
very
important
not
to
break
the
main
assumption
of
the
consumable
role,
consumer
extension,
which
is
basically
the
consumer,
should
not
have
permissions
to
transfer
it
or
specify
other
people
being
able
to
transfer
it.
So
it
should
stay
as
simply
a
consumer.
B
That's
that's
the
the
first
reason
why
it
actually
exists
as
an
extension,
and
the
second
thing
is,
if
you
want
to
edit
the
address
that
you
are
going
to
set
on
every
transfer
as
a
consumer.
So
when
the
nft
is
transferred,
the
consumer
is
cleared,
as
I
mentioned.
If
you
want
to
specify
another
address,
you
have
to
be
very
careful.
What
address
would
be
because
it's
recommended
for
it
to
be
the
default
zero
address.
B
A
A
It
made
it
to
final
status
in
fairly
decent
time,
because
I
have
came
across
proposals
which
are
here
for
over
two
three
years
and
they
are
still
into
some
different
status
other
than
final.
So
I
hope
your
experience
can
be
learned
by
other
authors,
I'm
eager
to
know
your
thoughts
on
the
current
eip
process.
B
Yeah,
well,
I
briefly
mentioned
it
previously.
My
my
yeah,
my
concern
is
just
paying
attention
to
what
gets
approved
and
I've
noticed
that
eip
reviewers
are
actually
pointing
out.
This
is
similar
to
that
collaborate
with
that
person,
etc,
etc.
So
I've
already
mentioned
that
other
than
that.
I
think
that
when
I
first
created
the
eip,
maybe
there
were
less
eip
reviewers
compared
to
now,
and
it
was
a
more
slow
process.
B
He
took
more
time
to
get
the
the
pr
changes,
reviewed,
etc,
but
recently
I've
noticed
that
there's
drastic
change
in
how
people
how
fast
people
review
prs
for
for
eip.
So
actually
that
was
a
quite
I
would
say
that
was
the
main
reason
why
it
got
to
this
state
that
fast
I
mean
the
process
was
just
improved,
which
I
mean
congrats
on
that.
A
I'm
happy
to
know
that,
yes,
that
is
true
for
some
time
we
have.
We
were
like
having
very
few
reviewers,
and
recently
we
have
started
engaging
more
community
members
to
come
and
review
the
proposals,
even
even
not
as
an
eip
editor.
They
can
be
doing
it
as
an
external
reviewer
just
give
feedback.
We
are
inviting
projects
to
let
know
author
if
there
are
any
changes
that
may
help
their
project
kind
of
stuff.
So
definitely
we
are
trying
to
engage
more
people
there
to
get
these
proposals
move
faster.
A
B
I
think
that
the
it's
impressive,
how
good
the
process
is
and
what
I
mean
by
that
is
it's
really
hard
problem
to
solve
properly.
In
my
opinion,
I
think
that
the
last
couple
of
months
were
very
good
in
terms
of
organizational
wise,
organization-wise,
etc,
and
I,
I
think,
there's
additional
initiatives
that
are
basically
bringing
more
eip
reviewers,
which
is
great,
so
I
think
I
I
generally
I
have
positive
experience
with
the
whole
eip
submission,
etc.
B
Actually,
I
would
say
that
if
you
are
trying
to
write
an
eip,
make
sure
to
read
the
first
eip
because
everything's
written
there
and
the
challenges
were
actually
going
through
everything
in
the
first
eip.
Once
I
went
through
everything
through
the
first
eip,
I
was
aware
of,
there
were
clear
steps
of
what
should
I
do.
I
didn't
have
to
dm
someone
explicitly
or
talk
with
someone
just
to
get
explanation.
It
was
everything.
B
Was
there
just
you
have
to
go
to
the
first
eip
and
you'll,
be
I
think
that
you'll
be
you'll,
be
okay,
as
I
mentioned
the
statuses,
when
you
create
a
pr,
they
are
very
explicit.
They
say
what
exactly
went
wrong.
What
you
should
do,
whether
you're
waiting
review
of
someone
else
or
you
just
messed
up
and
you
you
don't
have
your
pr
ready
yet.
So
I
think
that
the
whole
process
is
very
explicit.
That's
and
that's
a
good
thing.
A
It's
always
good
to
hear
good
words
about
the
current
process,
because
we
have
been
hearing
more
complaints
than
appreciation,
so
I
really
appreciate
you
sharing
so
good,
so
much
of
good
words
for
us.
Well,
thank
you
all
right.
So
that
ends
the
list
of
questions
that
I
have
anyone
on
the
call
today,
if
you
have
any
question.
B
A
I
can
hear
one
of
the
eip
authors
saying
the
same
thing,
so
the
idea
here
is,
as
daniel
mentioned,
that
if
you
are
proposing
a
proposal
make
sure
it
is
not
trying
to
solve
multiple
issues
at
one
time.
Try
to
solve
one
issue
make
smaller
proposals.
There
are
high
chances
of
getting
it
passed
and
that's
that's
good
in
a
way
that
if
we
are
stuck
with
one
out
of
the
three
problems
that
a
proposal
started
to
solve,
we
don't
have
to
wait
till
the
third
problem
is
solved.
A
B
A
I'm
listening
on
this
note,
thanks
to
all
our
youtube
viewers
for
watching.
I
hope
you
have
got
answers
to
many
of
your
questions
check
out
the
description
section
for
link
to
the
presentation
and
other
useful
resources.
You
can
also
find
link
to
guest
twitter
to
follow
and
another
special
announcement
in
the
spirit
of
the
merge
upgrade.
We
have
started
know
your
client
series
on
penny.
We
have
shared
the
first
recording
on
client
basu
and
there
are
more
mud.
Special
talks
coming
up
your
way,
so
stay
tuned.