►
From YouTube: EIP editors apprenticeship meeting
Description
Agenda: https://github.com/ethereum-cat-herders/EIPIP/issues/102
A
Welcome
to
the
eip
apprenticeship
call.
This
is
the
first
call
of
year,
2022
so
happy
new
year
to
everyone
for
this
wonderful
year
and
thank
you
for
joining
the
call
today,
as
some
of
you
may
know,
that,
generally
in
these
calls,
we
go
through
some
of
the
pull
requests
that
are
already
existing
in
eip's
github
repository.
A
B
Hello
all
happy
new
year,
let's
see
what
we've
got
going
on
today,.
B
That's
not
related
okay,
40
notifications,
I've
kind
of
been
going
through
this
a
bit
here
and
there.
So
I
don't
think
there's
a
whole
lot
of
things
to
do,
but
we'll
just
start
here.
A
I
just
noticed
michael
just
wondering
if
you
are
xor
on
the
discard.
A
All
right,
michael,
thank
you
so
much
for
joining
the
call
and
if
you
would
like
to
take
a
moment
to
introduce-
and
let
us
know
your
interest
just
for
everyone
to
know
here.
Michael
is
interested
in
erc,
editing
and
currently.
Liteclient
is
helping
us
with
that.
Michael.
C
Awesome
yeah
yeah,
hi
everyone,
I'm
michael
blau
yeah,
I'm
definitely
interested
to
help
out
with
the
erc
editing,
specifically
around
nfts
on.
I
know
you
mentioned
on
discord.
I
my
name
is
xor
x0r
and
that's
sort
of,
like
my
alias
an
nft
artist,
name
that
I
use
so
yeah
definitely
excited
to
be
here
and
learn
more
about
it.
D
A
Thank
you
yeah.
Please
go
ahead.
B
Great
okay:
this
person
wants
to
implement
the
transfer
function
on
erc721s.
B
F
B
F
Yeah,
I
know
the
concept
does,
but
the
problem
that
the
1155s
have
the
additional
amount
are,
whereas
721
20s
have
the
same
number
of
arguments
and
transfer.
F
F
B
B
Yeah
other
than
that,
it's
got
his
abstract
motivation.
I
don't
know,
should
this
require
years
c20.
F
The
truth
is,
I
mean
one
or
the
other
like
either
both
or
neither.
I
suspect
that
that
is
a
good
way.
Actually,
maybe
the
contract
is
supposed
to
be
an
erc20
contract,
though
I'm
not
sure.
F
Makes
sense
to
me
and
russell,
like
I,
I
know
ross
just
like
crypto
twitter
now
he's
a
solid
dev.
He
knows
what
he's
doing
like
you
know.
I
read
through
this
also.
I
thought
it
was
pretty
well
put
together,
like
I'd
seen.
His
rationale
also
like
the
idea
is
basically
just
being
able
to
have
contracts
that
are
able
to
use
the
same
functions
to
either
call
721
or
20
with
without
needing
like
two
sets
of
functions.
Yeah
makes
sense.
B
Righty,
I
don't
think
these
things
are
going
to
merge,
been
having
problems
merging
things,
so
I'm
going
to
leave
that
tab
open
come
back
to
it
all
right.
What
does
micah
want
to
talk
about
here?
E
G
F
B
A
By
the
definition,
informational
eip,
there
is
nothing
that
we
need
to
follow
as
a
mandate.
That
is,
the
definition
of
meta
eip
for
informational
eip.
As
for
the
like
description
provided
in
eip1,
people
are
free
to
ignore
if
they
would
like
to,
but
it's
good
to
have
a
standard.
I
do
agree
to
the
point
that
if
we
are
using
minute
in
this
particular
fashion
everywhere
that
will
help
us
make
a
standard,
but
I'd
put
the
present
definition.
I
don't
think
it's
a
mandate.
B
B
F
I
think
that's
kind
of
its
own,
like
standards
based
kind
of
war,
because
it
made
it
to
final
with
that
in
there,
but
like
first
of
all,
it's
not
enforced
anywhere.
If
you
take
a
look,
it
opens
up
once
165
implementation.
For
instance,
they
don't
enforce
that.
It
only
uses
30
000
gas
yeah
and
it
probably
shouldn't
be
in
the
eip
that
it's
already
final.
So
it's
like
yeah,
it's
on
thing.
B
D
F
F
F
F
F
F
G
G
F
So
I
mean
basically
what
this
is
doing
it
looks
like.
Is
it's
adding
a
second
I
mean
if
you
take
a
look
at
an
erc.
721
token
is
kind
of
a
ledger
of
ownership
of
token
80s,
so
it
looks
like
it's
adding
another
kind
of
series
of
indexes
that
could
be
owned,
which
are
like
the
I.
I
think
that
might
be
the
sft
type
like
more
than
a
bit
confused
myself,
though,.
A
F
I
I
mean,
I
think,
linguistically
you've
got
a
point
there,
but
I
don't
think
that's
what
the
author
of
this
standard
is
doing
sounds
like
the
author
of
this
standard
has
like
a
fungible
token
that
can
automatically
be
transformed
into
an
nft
like,
as
in
a
token
id
in
a
721
contract.
Though
I
mean
there.
I
think
it
might
depend
on
your.
F
A
H
Something
like
having
having
a
voucher,
that's
currently
fungible
and
it
can
be
traded
against
or
exchanged
against
another
similar,
similar
watcher
that
has
similar
kind
of
properties
and
once
you
redeem
that
it
converts
into
an
nft
and
loses
all
its
face
value,
that's
that
might
be
generally.
H
I'm
trying
to
guess
that,
because
I
kind
of
read
that
or
the
proposal,
so
it
seems
like
that
would
be
a
good,
not
a
good
use.
If
that
would
be
a
use
case
or
something
like
an
let's
say,
you're
attending
a
concert
and
you
have
multiple
tickets
right,
everybody's,
a
lot
of
tickets
and
these
are
being
traded
before
the
concert
starts
and
as
soon
as
the
concert
starts
now,
it
has
to
be
redeemed.
In
order
for
you
to
enter
the
concert,
and
now
it
becomes
an
nft
and
you
own
that
nfl.
F
H
So
there
you
can
actually
trade
those
vouchers
or
coupons
and
earn
some
money
from
that
right
that
that.
H
F
F
I,
a
trade
pair
is
also
generally
a
smart
contract
owning
an
asset,
though,
like
I
I
I
I
guess
what
you're
saying
is
before
the
contract.
It
should
be
in
the
rc20
and
afterwards
in
the
rc
721.
F
F
It's
it's
an
argument,
a
number
of
places
in
the
specification
like
whenever
they're
dealing
with
these
like
semi-fungible
token,
so
one
of
the
arguments
will
be
token
type,
which
is
the
semi-functional
token
type,
and
they
I
don't
see
anywhere
here
where
they
actually
define
what
that
means.
B
F
So
operator
is
something
that
you
get
across
a
lot
of
erc
erc2721,
1155
things,
which
is
it's
the
it's
like
the
message.sender.
That
way,
you
know
who's,
creating
the
transaction
or
who's
causing
the
transaction
to
happen,
even
if
it's
not
their
assets
like,
even
if
it's
just
something
they
were
approved
on.
F
H
Is
the
semi-french
ability
or
whatever
that
term
is?
Is
it
more
focused
toward
the
gaming
industry,
maybe
not
sure
like
I?
I
might
have
a
couple
of
hammers
like
1000
hammers
crc
20
harmless
and
you
might
have
erc
20
10
000
shields.
I
might
want
to
trade
those
and
then,
when
I
use
it
in
the
game,
then
I'm
basically
redeeming
those
or
whatever.
I
have.
J
J
J
F
But
if
it
were
me,
and
I
wanted
to
record
the
unique
seat
number
and
owner
name,
I
would
just
use
a
struct
initialize
them
with
zero
in
an
empty
string
and
then
have
the
ability
to
set
those
properties
later
and
keep
it
as
an
erc721
straight
through,
because
anyway,
you're
gonna
need
to
do
that
like.
Why
have
it
be
a
fully
fungible
like
erc20
in
the
beginning.
E
A
On
a
slightly
separate
note,
I
see
a
comment
in
chat
by
alpha
key
about
the
eip
proposal,
validated
I'm
not
sure
if
that
can
be
a
good
enhancement
on
the
present
vip
part,
maybe
light
client
and
shishanka.
You
guys
can
take
a
look
at
it
now
later
on.
E
F
So
it
could
be
the
front
ends
would
recognize
a
delegator
of
a
token
and
see
like
check
if
there's
a
delegator
and
then
let
them
do
it.
Let
them
like
you
know,
treat
them
as
a
owner
of
the
asset
or
someone
who
can
utilize
the
asset,
but
and
at
the
same
time,
if
that
is
the
case,
that
means
that
I
think
we've
seen
two
different
implementations
of
the
same
thing.
Another
in
other
eit's.
I
don't.
F
F
B
B
It
has
different
interface
arguments
yeah.
I
don't
know
if
you
want
to
comment
those
things
on
there.
I
can
do.
F
A
A
I
see
this
one
interesting
proposal
which
is
already
merged.
So
probably
it
is
not
in
the
pull
request,
anymore,
the
eip3668
by
nick
johnson.
That
proposal
is
in
last
call
and
it
is
an
erc
which
will
enable
access
to
retrieve
off-chain
data.
H
A
A
E
B
B
B
I
F
Oh
there's
one,
that's
not
showing
up
in
your
queue
I
actually
submitted.
One
for
bumping
2612
to
review
was
that
the
one.
B
F
B
B
B
G
B
Sweet,
I
don't
know
we
got
10
minutes
get
anything.
We
want
to
talk
about.
D
A
So
yeah
I
was
wondering
like
if
there
is
any
anything
in
specific
that
you
think
that
newcomers
can
consider
like
we
went
through
the
process.
You
especially
highlighted
with
sections
to
look
into,
but
do
you
find
anything
you
know
different
from
the
review
perspective
for
the
core
eips
or
the
erc
zips.
B
I
think
we
try
to
hold
corey
a
piece
to
a
higher
standard
than
erc's
there's
a
lot
of
reasons.
I
would
say
you
know
partially
there's
not
as
many
people
reviewing
the
ercs
and
I
don't
understand
the
application
side
of
things
as
well
as
understand
core.
So
it's
harder
for
me
to
give
like
really
solid
feedback.
There's
just
there's
a
lot
less
core
eips
that
come
through
it's
easier
to.
B
A
A
All
right,
anyone
else
has
any
question
for
today
I
mean
I
understand.
Sometimes
it
can
look
monitored
and
just
just
looking
on
to
the
screen
review
work
that
matt
is
doing,
but
the
questions,
if
you
have
it's
important
to
get
answered
so
you're,
you
are
around
to
keep
looking
into
the
different
proposals.
A
All
right,
in
that
case,
I
think
we
can
give
this
five
to
seven
minutes
back
to
everyone
to
prepare
for
next
call
if
they
have
any.
Thank
you
everyone
for
joining
us
today.
I
hope
to
post
the
recording
today,
sometimes
today
and
see
you
all
in
two
weeks.
We
are
planning
to
keep
this.
These
calls
in
the
interval
of
two
weeks.
So
we
get
enough
time
to
review
the
proposals
in
the
meanwhile
and
yeah.