►
Description
Follow at Twitter
---------------------------
Sam Wilson @_SamWilsn_ | Pooja Ranjan @poojaranjan19
Resources
------------------
Slides - https://tinyurl.com/peep-eip-5757
Proposal - https://eips.ethereum.org/EIPS/eip-5757
Discussion - https://ethereum-magicians.org/t/eip-5757-process-for-approving-external-resources/11215
EIPs External Link Policy #shorts - https://www.youtube.com/shorts/BXNu45yPuA4
EIP-5757 #shorts - https://youtube.com/shorts/BKkT4fUQGeQ?feature=share
PEEPanEIP - https://www.youtube.com/playlist?list=PL4cwHXAawZxqu0PKKyMzG_3BJV_xZTi1F
EIP Editing Playlist - https://www.youtube.com/playlist?list=PL4cwHXAawZxong9j6g5Hd0tM-oC22WLh1
Questions for Guests - https://docs.google.com/forms/d/e/1FAIpQLSdsmujnH_ncIlSEJ23s9jzXAKwfpTGNeJqjREWPloBbkJVQTA/viewform
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.io/ethereumcatherders
Twitter: https://twitter.com/EthCatHerders
Medium: https://medium.com/ethereum-cat-herders
Website: https://www.ethereumcatherders.com/
A
A
The
Proposal
documents,
the
requirement
for
Origins
and
the
process
for
approving
a
new
origin
that
may
be
linked
to
in
a
proposed
standard
to
discuss
this
EIP
documentation
process
to
be
able
to
add
an
external
Link.
In
the
document
we
are
joined
by
the
author
of
The
Proposal
and
one
of
the
most
active
EIP
editors,
Sam
Wilson.
Welcome
to
the
show
Sam.
A
B
So,
like
Puja
said,
my
name
is
Sam
Wilson
I'm,
currently
working
for
the
EF
doing
research
and
maintenance
of
a
couple
different
projects.
You
can
find
my
Twitter
and
Mastodon
here,
they're
also
linked
on
the
slides
I.
Mostly
do
a
lot
of
VIP
editing.
So
you'll
see
me
on
your
pull
requests.
If
you
ever
author,
an
EIP
I
also
maintain
the
ethereum
execution
layer,
specification
or
eels,
and
that's
a
python
project
for
describing
ethereum
as
a
whole,
or
at
least
the
execution
layer.
B
A
B
There
are
three
main
definitions
that
the
EIP
creates,
so
the
first
is
link
this
isn't
limited
to
just
HTML
anchors
or
markdown
links.
This
is
any
any
way
for
an
EIP
to
refer
to
another
document,
so
this
includes
things
like
RFC
8966,
just
as
text,
that's
a
link,
a
picture
of
a
cat,
that's
a
link!
So
basically
any
way
of
reaching
for
another
document
that
isn't
part
of
the
each
repository
is
an
external
link.
B
The
things
links
point
to
so
the
actual
picture
of
a
cat,
the
actual
RFC
document,
those
are
called
resources
and
we're
kind
of
borrowing
that
term
from
URLs
and
Uris.
And
finally,
we
have
the
origin.
So
the
origin
is
what
5757
is
really
concerned
about.
The
origin
is
the
group
that
either
publishes
the
documents
or
curates
them,
so
an
example
of
a
publisher
is
w3c
or
the.
What
working
group
that
publishes
H
tml
and
an
example
of
a
quanticler
is
the
DOI
or
digital
object
identifier
system.
B
So
what
does
this
EIP
actually
do?
It
lays
out
how
EIP
editors
decide
whether
or
not
we
want
to
allow
links
to
a
particular
origin.
So
in
this
case
like
say,
you
want
to
link
to
a
w3c
document.
You
have
to
get
w3c
approved
as
an
origin
and
to
be
approved
as
An
Origin.
You
have
these
three
requirements
that
you
have
to
meet
the
first
being.
Each
document
must
be
uniquely
identifiable
and
or
each
resource
must
be
uniquely
identifiable,
so
this
could
be
for
a
git
repository.
B
B
Next,
we
have
availability.
Each
origin
must
have
a
track
record
of
availability.
So
that
means
like,
if
you
know,
we
link
to
your
personal
blog
and
you
tried
making
that
a
permissible
origin.
We
probably
wouldn't
allow
it
at
least
not
at
first,
because
it
hasn't
been
around
long
enough
to
know
that
it
isn't
just
going
to
disappear.
B
So
those
are
the
kind
of
requirements
that
you
have
to
meet
whenever
you
want
to
propose
a
new
origin.
So
how
do
you
go
about
proposing
a
new
origin?
First
step
is
pretty
easy.
You
want
to
discuss
it
somewhere,
so
this
could
be
on
a
pull
request
for
your
proposal.
Where
you
try
to
link
to
it
and
the
Bots
complain
you
can
bring
it
up
on
our
Discord.
B
You
can
post
a
message
in
ethereum
magicians
and
the
idea
here
is
to
kind
of
get
a
feel
for
whether
people
want
this
origin
or
not,
whether
we
think
it
meets
the
requirements
and
just
to
have
kind
of
like
a
general
discussion
about
it.
If
feedback
seems
generally
positive,
then
you
want
to
implement
your
change.
This
is
step
two
and
it's
as
simple
as
modifying
EIP,
opening
a
pull
request
to
modify
eip1.
B
The
Eep
itself
has
a
description
of
the
changes
that
you
have
to
make,
and
there
are
other
examples
in
eip1
that
you
can
copy
it's
not
a
complicated
process,
assuming
you
know
get,
but
you
know,
and
finally
you
know
assuming
that
all
the
editors
agree,
which
is
probably
the
longest
and
most
difficult
step
you
can
use
it.
You
can
use
your
origin
in
your
eips.
B
So
why
do
we
have
eip5757
so
early
on
in
the
EIP
history?
People
just
linked
to
wherever
they
wanted?
A
lot
of
early
eips
contain
links
to
implementations
or
projects
using
the
standard
or
to
blog
posts
that
have
since
disappeared,
and
you
know
more
recently,
probably
about
two.
Maybe
three
years
ago
we
added
a
rule
where
we
weren't
allowed
to
use
any
external
links
and
this
caused.
Well,
it
saw
the
availability
problem
new
erps,
during
this
period,
you
know,
didn't,
have
any
links
so
that
you
couldn't
lose
them.
B
They
couldn't
disappear,
but
authors
complain
about
not
being
able
to
provide
additional
context
having
to
duplicate
a
whole
bunch
of
things
and
yeah,
so
that
was
very
unpleasant
for
authors,
so
eat
5757
is
kind
of
a
compromise
between
two
sides
on
the
left
side
of
the
screen.
Here
we
have
the
reasons
why
we
allow
external
links
and,
on
the
right
hand,
side.
We
have
the
reasons
why
we
don't
and
5757
is
trying
to
find
a
balance
between
these
two
opposing
sides.
B
B
Sometimes
you
can't
straight
up
just
copy
information
and
put
it
in
the
each
repository
so
allowing
external
links,
let's
just
sidestep
that
a
little
bit
and
finally
there's
a
long
academic
tradition
of
citing
your
sources,
and
you
know
providing
credit
where
credit
is
due,
and
you
know
that's
important
to
some
of
the
EIP
editors
and
yeah.
So
that's
kind
of
why
we
allow
the
links,
but
on
the
flip
side
we
have
to
balance
that
against
links
disappearing
rotting.
B
That's
a
big
problem
happens
all
the
time
things
disappear.
Things
change
eip's,
also
follow
a
very
strict
process
to
ensure
immutability.
So
once
the
EIP
moves
into
last
call
and
Final
it's
much
more
difficult
to
edit,
and
we
do
that
to
ensure
that
things
that
were
spec
compliant,
you
know
two
years
ago,
are
still
going
to
be
spec
compliant
today
and
if
you
have
part
of
your
EIP
in
an
external
link,
then
that
external
link
isn't
subject
to
the
same
controls
as
the
EIP
Repository.
B
So
that's
why
we're
very
hesitant
to
allow
external
links?
And
finally
you
know
we
don't
want
standards
bodies
to
well.
We
want
to
provide
free
access
to
all
this
information.
We
don't
want
it
limited.
So
that's
why
this
process
exists.
That's
why
that
requirement
is.
Is
there
that's
pretty
much
the
whole
EIP
yeah?
So
does
anybody
have
any
questions
about
it?.
A
Thank
you
so
much
for
this
presentation,
Sam.
It
was
short
and
a
sweet
talk
just
for
people
who
aren't
aware
Sam,
Wilson,
generously,
donate
his
time
for
EAP,
editing
officer
to
help
new
and
existing
authors
understand
the
current
process
document
this
proposal
and
guide
with
do's
and
don'ts.
We
learned
about
some
of
the
do's
related
to
the
link
policy,
but
there
are
many
other
questions
and
if
you
do
have
those
questions,
you
can
join
us
on
this
bi-weekly
meeting
of
EIT,
editing
officer,
more
information
available
on
each
characteristics
card.
A
Well,
I
do
have
a
couple
of
more
questions
related
to
this
proposal.
Just
to
add
some
clarity
about
the
proposal
for
people
who
are
relatively
new,
we
use
the
term
external
link
here.
What
does
external
link
refer
to?
Does
it
mean
anything
outside
the
ethereum
eaps
GitHub
repository
or
any
Link
in
general?
If
you
can
maybe
clarify
it
a
bit
more
sure.
B
So
it's
the
the
technical
definition
is
either
a
hyperlink,
so
like
a
URL
that
does
that
contains
a
double
forward.
Slash,
so
that's
a
very,
very
specific
definition.
So
there's
things
that
start
with
like
HTTP
or
like
FTP
or
any
of
those
or
any
other
way
of
referring
to
something.
So
if
you
say
you
know,
I
don't
know.
B
A
A
B
Yeah,
so
eip1
has
a
list
of
all
of
the
external
resources.
It
has
a
regular
Expressions
that
Define
exactly
what
link
formats
we
allow
and
it
has
examples
for
people
to
copy
and
then
paste
into
their
proposals.
What
are
the
more
complicated
ones
is
the
digital
object,
identifier
or
DOI
system,
and
that
requires
like
a
formal
blob
of
Json
to
reference,
but
other
than
that.
The
other
ones
are
pretty
simple.
A
B
Something
that's
been
coming
up
a
lot
recently
and
I
think
could
stand
to
be
improved.
Is
our
categorization
I
think
that,
while
in
the
past
the
core
interface,
networking
and
ERC
categories
were
were
useful,
now
I
think
the
lines
are
starting
to
blur
a
little
bit,
especially
with
the
addition
of
the
consensus,
consensus
layer,
so
I
think
we
need
to
work
on
our
categorization
a
bit
more.
A
Right
I
know
this
was
not
directly
related
to
The
Proposal,
but
I
just
wanted
to
check
with
you,
because
it's
something
important
and
you
are
an
EIP
editor.
So
definitely
you
are
not
are
helpful
for
us
all
right,
yeah
I
think
we
are
coming
towards
the
end
of
this,
but
before
we
go
there,
I
want
to
ask
a
question
related
to
this
meta
and
informational
Eep.
Like
many
people
have
this,
you
know
kind
of
question
mark
why
some
of
the
proposals
are
considered
as
meta
Eep
and
wine
informational.
A
B
Sure
so,
meta
and
informational
is
actually
one
of
the
easier
ones
to
divide.
So
ahmeda
Eep
describes
something
about
the
EIP
process
itself,
so
eip1
is
a
meta
Eep.
This
is
a
meta
Eep
because
it
describes
how
you
make
changes,
how
the
governance
Works
those
kind
of
categories
are
all
in
the
meta.
But
if
it's
in
from
like
informational
eips
are
about
General
recommendations
or
information
that
the
authors
think
should
be
available
to
the
ethereum
community
that
aren't
related
to
the
EIP
process
itself.
So
there's
a
discussion.
A
B
A
B
A
B
B
What
else
said
don't
be
afraid
to
open
a
discussion
issue
on
a
theory
of
magicians
before
making
your
PR,
it's
always
good
to
get
feedback
from
the
community
and
oftentimes
there's
duplicate
eips
that
are
going
around,
so
that
provides
us
an
opportunity
to
like
point
you
guys
to
work
together,
yeah
and
other
than
that.
You
know
participate
in
the
process
and
yeah
see
you
around.
A
Well
said,
participate
in
the
process
and
then
don't
be
afraid
to
start
a
new
discussion,
because
with
discussion
we
can
have
a
right
set
of
governance
here.
So
yeah.
Please
join
us
on
on
discussion
and
most
of
the
discussion,
especially
related
to
eibs
happens
on
Fellowship
of
ethereum.
Magician
I.
Think
about
eipw
will
not
allow
anyone
to
kind
of
start.
Discussing
more
on
the
issue.
Is
that
a
correct
understanding.
A
Okay,
that
works
like
we.
We
want
to
have
one
thing
centralized.
That
is
the
discussion,
so
everyone
get
the
full
context.
What
what's
going
on
with
the
proposal?
That's
that's
quite
valuable
information.
I
know
this
is
a
short
proposal,
but
this
was
very
important
for
many
people,
because
many
times
we
have
received
this
question.
What
links
are
allowed?
What
links
are
not
allowed,
and
what
can
we
do
about
it
and
I
think
this
conversation
that
we
recorded
today
would
be
a
great
resource
that
we
can
share
with
people
I.
A
We
know
ethereum
has
an
amazing
community
of
contributors,
creating
blockchain
standards,
multiple
products
out
there
are
inspired
by
idiom
standardization
process
or
even
using
existing
ethereum
standard
I
suppose
this
talk
is
helpful
to
have
known
the
process
to
document
a
proposal
with
the
potential
of
becoming
a
standard
one
day,
Sam
Wilson
on
behalf
of
ethereum
community
I.
Thank
you
for
taking
out
time
to
share
valuable
information
with
us.
On
this
note,
thank
you
to
all
our
YouTube
viewers
and
podcast
listener
for
following
this
special
talk
on
EIP
documentation.