►
From YouTube: Core Developer Learning Ecosystem Call #1
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
My
name
is
Hudson
Jameson
I
work
for
the
etherium
foundation.
I
am
a
I.
Kinda
have
a
lot
of
different
roles,
but
one
of
my
main
roles
is
core
developer
liaison
and
community
coordinator.
So
ever
since
late
2016
I've
been
organizing
and
running
the
core
developer
meetings,
also
known
as
the
all
core
dev
calls.
A
Those
are
where
the
core
developers
of
aetherium
come
together:
core
developer,
meaning
someone
working
on
the
low-level
protocols
such
as
like
a
client
or
a
networking
layer,
or
something
that
deals
with
core
changes
that
affect
consensus
and
network
upgrades.
They
all
come
around
and
discuss
changes
and
optimizations
to
their
client
es,
which
are
some
of
our
kind
of
specifications
that
we
have
in
our
system
in
order
to
update
the
system-
and
you
know
effectively
and
some
other
things
that
are
important
deals
with.
A
So,
let's
see
what
else
is
what
else
do
I
do:
I've
two
cats
and
one
wife?
No,
they
have
three
cats.
What
am
I
thinking
the
third
one,
just
stays
in
the
other
bedroom
and
I
also
enjoy
playing
overwatch
and
I.
Think
that's
about
it.
For
me,
I
have
some
other
like
internal
jobs
at
the
foundation
like
DevOps
and
security,
but
that's
not
public
facing
really.
A
You
can
mostly
see
my
public
facing
work
on
Reddit
and
Twitter
and
the
core
dev
meetings
and
stuff
with
the
etherium
cat
herders,
which
are
a
group
of
people
in
the
ecosystem
that
do
decentralized
organizational
work
like
taking
meetings
or
notes
at
meetings
and
like
working
on
community
efforts
that
need
some
kind
of
push
for
organization.
Basically,
so
that's
it
with
me:
let's
move
it
to
and
rhotic.
If
I'm
pronouncing
that
correctly
yeah.
B
C
I'm
I'm
from
gnosis
and
I'm,
the
first
full-time
hire.
My
nose
is
to
work
on
open
ethereal,
so
I'm
the
first
one,
but
this
is
the
team
that
will
expand
I
think
to
at
least
six
people
eventually,
but
I'm
happy
to
be
here:
I'm
from
Moscow,
so
I
will
crew
mili
but
I
attended
the
workshop
and
liked
everybody.
C
E
G
H
I
J
A
Awesome
so
how
I
think
I'm
gonna
do
this?
Is
I'm
gonna
go
through
and
just
give
some
essentials
that
every
core
developer
kind
of
needs
to
know
it's
gonna
be
heavy
on
the
IPS
for
the
most
part
and
then
just
give
some
kind
of
odds
and
ends
that
Isis
think
of
suddenly
and
also
take
questions.
So,
if
you
think
of
a
question
along
the
way,
just
unmute
and
just
say
hey,
can
you
stop
for
a
second
I?
Have
a
question
and
I'm
happy
to
answer
it
so
without
much
to
do?
Let's
get
started.
A
A
A
Something
proposals
and
that's,
then,
what
Bitcoin
improvement
proposals
is
based
on
which
then
a
theory
of
improvement
proposals
was
based
on
and
then
there's
also.
A
theory
implies
Vic
and
provement
proposals.
There's
CIP
s4z
cash
for
G
cash
improvement
proposals.
So
it's
just
a
way
to
develop
specifications
and
standards
for
etherium.
A
So
if
you
go
to
e
IP
one,
that's
the
purpose
and
guidelines,
that's
a
continuously
active
IEP.
It
gives
the
rationale
it
gives
the
types
of
VIPs,
the
workflow
and
stuff
like
that.
So
we'll
just
run
through
this
real,
quick
there's,
four
types
of
the
IPS
there's
standard.
Now,
there's
three
types:
I
should
say:
sorry:
standard,
Trekkie,
IP,
a
meta,
a
IP
and
an
informational
e
IP
standard
track
is
gonna,
be
what
mostly
has
worked
on,
especially
if
you're
a
core
dev.
A
A
Let's
see
including
it
says,
also
as
well
as
changes
that
are
not
necessarily
consensus.
Critical
that
may
be
core
deb
discussions
like
a
IP
90.
The
minor
node
strategy
changes
there's
a
networking
layer,
that's
mostly
for
dev
p2p,
eventually
I
believe
will
be
limp
p2p
when
we
get
to
eath,
2.0
and
stuff,
like
the
light
aetherium
sub
protocol.
I
think
that
would
include
light.
Sync.
Someone
can
correct
me
if
I'm
wrong
in
her
face
would
be
stuff
with
a
PIR
PC
specs
that
doesn't
come
up
much.
A
We
probably
are
gonna
change
that
and
then
er
C
is
application
level
conventions.
So
if
you've
heard
of
ER
C
20,
that's
a
token
standard,
that's
widely
used
across
the
ecosystem,
and
that
is
also
something
that
has
one
of
the
most
used.
Ew
I
guess
types
is
one
of
the
most
usee
IP
standard
track
types.
A
It's
cool
to
look
through
and
just
kind
of
see,
some
of
the
VIPs
and
ER
sees
and
see
how
they're
set
up.
There's
a
template.
I'll
just
go
back
real,
quick,
there's
a
template
VIP,
where
you
need
to
kind
of
copy
this
to
make
your
own
a
IP
and
make
sure
you
have
all
of
the
required
specs
and
things
like
that.
We
have
an
e
IP
bot
that
will
go
through
and
automatically
merge
VIPs
as
draft
status
which
we'll
be
getting
to
next.
A
There's
a
meta,
a
I
P.
That's
a
change
in
and
of
itself
in
the
process.
This
VIP
one
is
a
meta,
EIP
informational,
a
IPS,
describe
an
aetherium
design
issue
or
provide
general
guidelines
or
information
at
the
etherium
community,
but
do
not
propose
a
new
feature,
so
it
doesn't
represent
consensus
necessarily
or
even
a
recommendation,
so
users
are
free
to
ignore
these,
but
they
are
just
informational
pieces.
A
This
is
hardly
used,
however,
there's
been
something
called
the
prog
pad
debate,
which
has
been
a
recent
debate
within
the
etherium
ecosystem,
on
the
possibility
of
changing
the
proof-of-work
algorithm
of
aetherium
from
ET
hash
to
prague,
pow,
programmatic
proof
of
work,
and
there
are
some
informational.
There
was
an
informational
AIP
being
drafted
and
going
to
be
merged.
A
Where
people
signed
a
letter
saying
we
don't
want
Prague
pal,
so
there's
been
some
discussion
on
if
that's
the
right
venue
for
an
informational,
AIP,
that's
still
up
for
debate
at
this
point
would
be
good
to
mention
that
there
is
something
called
the
e
IP
IP
meetings.
They
happen
every
two
weeks
on
Wednesday
if
you
want
to
invite
just
reach
out,
but
what
they
are
are
a
theory
of
improvement
proposal,
improvement
meetings
or
improvement
process
meetings,
so
e
IP
IP.
A
So
what
we're
doing
is
we're
taking
the
IP
one
and
we're
making
some
changes
to
it.
To
streamline
the
process,
make
things
easier
to
understand
all
that
jazz
and
we're
making
some
progress
right
now
it's
a
difficult
task
because
of
some
of
the
EIP
ones,
just
kind
of
dense
and
has
a
lot
of
different
intricacies
that
have
to
be
discussed
amongst
people
and
it's
hard
to
gauge
consensus.
When
people
don't
look
at
the
e
IP
repo
a
lot
so
Corey
IPS
have
a
a
special
requirement.
A
If
a
quarry
IP
mentions,
proposes,
or
changes
to
the
theory
and
virtual
machine,
it
should
refer
to
the
instructions
by
their
mnemonics
and
to
find
the
opcodes
of
those
mnemonics
at
least
once
so.
For
instance,
if
you're
talking
about
revert,
you
would
be
talking
about
0xf
e
I,
believe
the
I
guess
the
hex
reference
to
that
position
and
the
e
vm
there's
something
called
shepherding
any
IP.
A
What
that
is
is
basically,
if
you're,
creating
the
IP,
you
need
to
either
become
a
champion
or
find
a
champion
of
that
e
IP,
a
champion
as
someone
who
doesn't
necessarily
write
the
e
IP,
but
there's
someone
who
pushes
it
along
and
can
be
the
point
of
contact
during
discussions
about
that
e
IP,
so
it
doesn't
become
stagnant.
It's
a
new
thing,
we're
trying.
So
a
lot
of
the
e
IPS
you
see
won't
have
a
champion
even
some
of
the
newer
ones.
A
Don't
have
it
on
the
on
the
template,
because
we
are
not
looking
closely
at
drafted,
II
IPS
as
they
come
in,
because
we're
a
bit
understaffed
and
overworked
from
our
other
jobs.
There's
only
I
think
six
to
80
IP
editors
and
some
of
them
are
more
active
than
others.
I'm,
not
very
active,
because
I
got
a
lot
going
on
and
I've
just
been
neglecting
this
and
so
of
other
people.
A
It
also
says
that
you
need
to
ask
the
kathira
community
if
the
idea
is
original
or
if
it's
wasting
time
or
something
like
that
by
going
to
the
ethereal
magicians
form
or
the
gaiter
chat
rooms,
aetherium
subreddit
or
the
issue
section
of
the
repository.
The
fellowship
of
ethereal
magicians
is
a
website
and
forum
of
people
who
go
over
technical
specifications
and
technical
issues
within
the
community
and
come
up
with
processes,
procedures
and
discussions
around
certainty
ip's.
So,
for
instance,
there
is
a
subsection
of
this
form
for
Cori
IPS
and
Greg
Colvin
who's.
A
There's
discussion
in
this
forum,
where
people
give
back
and
forth
questions
about
it.
It's
free
to
sign
up
on
here,
I
highly
recommend
you
do
for
giving
comment
back
to
e
IPS,
there's
not
enough
people
who
do
that
and
it'll
be
very
helpful
if
that
happens,
or
if
you
were
able
to
contribute
back
in
that
way
within
the
product.
The
EIP
process.
A
We
kind
of
try
to
make
a
point
that
the
EIP
process,
and
especially
the
Alcorn
apps,
call,
were
not
designed
to
address
contentious
non
technical
issues.
However,
we
often
become
entangled
in
them
because
there's
not
a
way
to
present
them
or
to
present
them
to
the
community
in
a
way
that
gets
proper
feedback
and
signaling
methods.
So
what
I
mean
by
that
is,
if
there's
a
controversial
change
it
and
it's
like
at
the
core
level,
so
something
like
prog
pal
that
I
was
just
talking
about.
A
That's
something
that
we
like
to
avoid
doing
for
a
few
reasons
as
core
developers,
because
that
complicates
things
that
affects
a
lot
of
the
protocols
on
the
network
if
anyone's
heard
of
the
maker
or
anything
in
defy.
If
you
you
know,
fork
etherium,
then
what
happens
to
all
of
the
contracts
in
their
state
and
the
for
the
defy.
You
know,
platforms
that
go
to
the
new
chain,
there's
a
lot
of
unanswered
questions
that
are
not
that
are
not
really
well
thought
out
by
some
of
these
platforms.
So
there
isn't
a
plan
for
that.
A
A
All
core
dev
cert
meetings
serve
three
things
discuss
the
technical
merits
of
an
EIP,
discuss
whether
clients
will
be
implementing
and
coordinate
the
EIP
implementation
for
network
upgrades
James
Hancock
who's
on
the
call
is
the
hard
fork
coordinator.
So
he
has
the
responsibility
of
going
through
and
looking
over.
A
Maybe
it's
like
a
forum
post
on
a
theory
in
magicians
to
working
to
draft
drafts
are
automatically
merged
using
the
using
the
EIP
bot
that
we
need
to
improve
a
lot
and
that
bot
goes
in
and
if
it's
properly
coded
and
then
it
gets
merged
as
a
draft
and
then
an
EIP
editor
can
look
over
it
and
from
there
after
a
lot
of
discussion
has
happened
and
it's
listed.
It's
gonna
be
listed
on
the
IPS
down
to
theorem
dot
org
as
a
draft.
There
is
something
called
last
call.
A
Last
call
is
a
period
of
two
weeks
where
there
would
be
can
be
material
changes
in
the
EIP
or
substantial
and
address
technical
complaints
which
may
cause
the
EIP
to
convert
to
giraffe.
There's
an
RSS
feed
for
last
call
that
you
can
pull
up
I.
Believe,
there's
also
a
last
call
section,
and
here
let
me
look.
Oh
there's
not.
We
need
to
fix
that.
So
yeah,
an
RSS
feed
exists
for
that
Horry
eye.
Peas
have
an
accepted
phase.
A
Oh
sorry,
there's
the
final
pay
phase
and
non-core
II
IPS,
where
it's
currently
state
of
the
art.
It
should
only
be
updated
to
correct
Arata
so
like
misspellings
and
stuff,
like
that,
there's
a
phase
before
accepted
when
you're
talking
about
a
Corey,
I.
Sorry,
there's
a
phase
before
final.
When
you
were
talking
about
a
Corey,
IP
called
accepted.
What
that
means
is
the
status
signals
indicate
that
it's
unlikely
that
the
client
developers
are
going
to
throw
this
one
out
and
it
is
considered
for
inclusion.
A
They
basically
said
yes,
this
is
going
into
some
future
network
upgrade
slash
hard
for,
and
basically
this
is
the
step
before
final,
because
it's
not
actually
in
the
network
upgrade
yet,
but
it's
been
accepted
by
the
core
developers
as
something
is
going
in.
There's
also
other
statuses
like
active,
which
is
for
information.
A
Lee
ip's,
like
this
one
abandon
4e
IPs
no
longer
pursued
rejected
for
ones
that
are
broken
or
rejected
by
a
the
quarry,
IPS
or
superseded,
which
is
ones
that
were
previously
final,
but
no
longer
considered
state-of-the-art,
here's
all
of
the
parts
of
an
EIP
preamble,
abstract,
etc.
You
can
look
through
these
later
we're
also
looking
at
what
type
of
copyright
waivers
to
use
in
the
future
right
now,
most
people
use
I
think
it's
CC
by
oh.
Let
me
look.
A
A
Perfect,
okay,
well,
belongs
in
any
IP.
My
the
IPS
are
in
markdown
format,
easy,
that's
just
more
than
what
needs
to
be,
and
there
there's
a
section
on
transferring
the
IP
ownership
and
then
a
section
that
has
the
e
IP
editors.
This
is
out
of
date.
The
current
IP
editors
are
other
people
Nick
still
in
the
IP
editor,
as
is
Casey
myself,
Nick
savers,
Greg,
Colvin
and
Alex.
A
So
we
don't
yeah,
we
don't
pass
judgment
on
the
IPS.
We
just
do
the
administrative
and
editorial
part.
However,
that
gets
a
little
messy
when
it
comes
to
gauging
community
consensus.
So
it's
like,
when
is
an
e
rc
standard
up
to
par
for
people
using
it
enough
in
the
community
to
be
final,
so
that
kind
of
gets
weird.
So
really
the
EIP
authors
have
to
make
a
case
for
that,
so
that
we
don't
have
to
work
as
hard.
There's
a
history
section
and
that's
the
end
of
the
IP
one.
C
A
There's
a
few
different
ways:
the
IP
one
mentions
a
few,
but
there's
like
other
ways
as
well.
If
it's
a
quarry
IP
you
bring
the
EIP
to
the
court
developers
and
that
then
they
basically
talk
about
it,
ask
technical
questions.
They
pull
up
your
thread
and
etherium
Magicians.
At
that
point,
the
EIP
is
probably
strat
draft,
so
the
fellowship
of
ethereal
magicians
forum
serves
as
a
really
popular
place
for
discussion
over
quarry
ip's.
A
There
is
for
non
quarry
IPS.
A
good
example
of
this
would
be
ERC.
20
standard
was
starting
to
be
used
by
multiple.
You
basically
champion
the
e
IP
and
the
standard
to
be
used
by
multiple
companies
or
organizations
or
entities
so
that
it
becomes
more
of
a
community
standard
before
it's
even
officially
approved.
That's
what
happened
to
e
rc
20.
The
same
thing
happened
to
the
crypto
kiddies
DAP
standard
I'm
blanking
on
it
is
that
ERC
10:57
now
777,
which
ones
the
crypto
kitty
standard.
A
That's
perfect
yeah.
That
is
exactly
it.
The
IP
721
is
the
non
fungible
token
standard
and
it
was
starting
to
be
used
across
the
ecosystem
after
it
was
publicized
on
Reddit
and
Twitter,
and
at
meetups
and
on
theory,
magicians
and
in
different
projects
that
you
know
showed
off
using
it
and
the
PR
for
our
issue,
for
that
a
I
P
started
to
show
more
and
more
activity,
so
that
was
kind
of
how
it
was
decided.
In
my
opinion,
to
be
go
from.
A
You
know,
draft
to
final,
and
the
reason
you
want
to
do
final
is
because,
if
you
keep
iterating
on
it,
then
there
it's
not
a
standard
anymore.
It's
just
a
continuously
updated
standard
where
it's
gonna
break
compatibility.
So
the
author
has
the
responsibility
to
not
have
it
get
too
much
like
that.
Did
that
answer
your
question?
I.
A
A
A
For
instance,
can
we
you
know,
get
a
IP
10:57
on
the
agenda?
Can
we
put
the
following
Fiat
500,
CIL's
on
the
agenda,
etc?
Usually,
when
you
ask
for
something
to
be
on
the
agenda,
we
want
yourself
or
someone
else
who
declares
they
want
to
represent
that
agenda
topic
to
be
on
the
call,
and
so
we
usually
try
to
push
for
that.
Anyone
can
ask
for
things
to
be
on
the
agenda.
There's
also
stuff
like.
A
A
If
we
go
to
the
awkward
devs
folder,
we
have
all
the
meeting
notes,
let's
just
get
them
random
meeting
like
meeting
number
66,
there
was
a
link
to
the
github
agenda,
there's
also
an
audio
video
of
the
meeting
to
eat
from
YouTube
and
then
we've
within
the
last
half
year
or
so.
Maybe
a
little
more
have
been
doing.
The
decisions
made
an
action
item
section
or
no
just
decisions
made
I
think
actions
might
be
at
the
bottom.
No
just
decisions
made
yeah.
We.
K
Yeah
I'm
sorry,
my
system,
rebooted
and
I
have
to
drop
the
call
so
I'm
puja
ranzan,
a
member
of
a
tedium
cat
hurdle
and
I
may
be
basically
interacting
with
the
Conchords.
They
are
part
of
the
meeting,
takes
note
and
try
to
coordinate
with
the
non
development
staff
for
the
evening.
I'm
also
part
of
the
EIP
IP
meetings,
so
helping
out
with
that,
if
you
guys
would
be
interacting
with
EF,
is
more.
We
would
like
you
guys
to
invite
in
the
meeting,
as
Hudson
already
did,
yep.
A
Thank
You
Pooja
she's
been
in
a
role
and
a
lot
of
the
etherium
cat
heard
her
stuff
and
the
etherium
counters
have
a
twitter.
We
have
a
website,
that's
not
really
updated,
and
we
tried
to
push
out
blog
post,
with
updates
for
the
community
to
read
we're
responsible
for
stuff
like
the
prog
pal
audit.
That
happened
earlier
at
the
request
of
the
core
developers
stuff,
like
that
note.
A
Takers
are
paid
and
died
through
the
etherium
cat,
herders
fund
I
think
it's
a
hundred
diaper
note-taking
for
a
core
dev
meeting,
because
generally
you
want
to
be
pretty
thorough
in
your
notes
and
then
you
also
list
the
attendees.
Sometimes
you
list
links
that
are
shared
in
the
calls
things
like
that
it
takes
a
while
to
do,
which
is
why
we
paid
100
buckaroos,
for
it.
A
Let's
see
what
else
do
we
have?
We
got
the
PM
repo
out
of
the
way
so
yeah.
If
you
want
to
see,
what's
happening
on
a
call
or
request
something
on
the
agenda.
Go
to
the
issue
section.
If
there's
not
agenda,
you
can
bug
me
about
making
one
because
I
need
to
get
reminded
sometimes
and
there's
also
a
getter
channel
that
I
will
pull
up
over
here
called
the
all
core
devs
chat.
So
if
you're
not
in
here,
you
definitely
should
get
in
here.
It's
a
very
good
resource
for
keeping
up
with
the
meetings.
A
Where'd
it
go
anyways
basically,
I
have
a
post
and
it
says
the
zoom
link
about
5
to
15
minutes
before
the
call
starts,
and
it
also
has
a
link
to
the
YouTube
chat
box,
because
that's
kind
of
fun
to
look
at
sometimes
if
it's
a
popular
call
and
also
the
agenda.
So
add
it
to
your
calendars.
We
don't
have
a
like
universal
calendar
entry.
For
that,
that's
something
we
might
do
in
the
future.
It
happens
every
two
weeks
at
1400
UTC
on
Fridays.
A
You
can
see
in
the
agenda
again
like
when
it
is
so
that's
the
all
coordinates
chat
if
you're
not
joined
on
there
jump
on
and
introduce
yourself.
So
people
know
that
you're
working
on
open,
aetherium
or
aetherium
j/s
or
whatever
you're
working
on,
and
they
know
they
can
reach
out
to
you
for
questions
about
that.
A
If
we
go
to
I'm,
not
gonna
go
to
discord,
but
there
are
discord
channels
for
open
etherium.
There
are
also
channels
that
are
able
to
be
joined,
for
guess
the
go
etherium
client
that
are
per
that's
pretty
popular.
So
if
you
all
need
links
for
that,
just
reach
out
to
me
I
can
send
those
to
you
and
you
can
kind
of
be
active
and
different
client
channels,
I'm,
not
sure.
If
aetherium
jeaious
has
a
public-facing
community,
they
might
have
a
get
her.
A
Anyone
knows
from
the
j/s
the
etherium
j/s
team.
If
they
have,
if
you
all
have
like
a
place
for
the
public
to
go
to
yeah,
we
have
a
public
dinner,
yeah
awesome,
yeah,
there's
actually
a
ton
of
Gators.
Let
me
just
pull
up
all
the
channels
I'm
involved
in,
but
I
don't
actually
participate
in.
We
got
ya.
The
II
was
remix
privacy,
Rob,
stone
research
which
is
kind
of
dead.
A
Now,
because
we're
using
a
different
telegram,
I
guess
that's
a
good
time
to
talk
about
the
relationship
between
a
theory
and
1.0,
a
theory
m1x
and
a
theory,
'm
2.0.
So
back
with
all
this
started
back
in,
you
know
the
2014
to
2015
era,
when
a
lot
of
this
was
being
coded
that
what
there
was
only
a
few
clients
there's
like
a
C++
client,
a
go
client,
a
Java,
client
and
a
actually
that
might
have
been
it
was
the
Java
client
even
around
I,
don't
think
so.
A
There
was
only
a
handful
of
clients
as
the
point
and
it
was
really
easy
for
them
to
coordinate
on
the
court
developer
meetings
and
jump
into
a
room
and
literally
in-person
a
lot
of
the
time
in
Berlin
or
wherever
they
were
located
at
the
time
and
decide
what's
going
into
the
network.
Now,
with
all
these
other
stuff,
we
have
to
have
more
coordination,
like
the
all
core
dev
calls.
A
theorem
1.0
represents
anything
that's
happening
for
the
current
aetherium
infrastructure.
So
whatever
happens
on
these
all
core
dev
calls
there's
also
a
theory
'm.
A
A
F
A
F
F
I
would
say
something
like
1559
is
isn't
stateless
aetherium,
but
it
is
equal
in
X
as
it
affects
it's
like
it's
an
upgrade
that
we're
looking
to
do
in
the
short
term,
that's
better
for
the
main
chain,
and
then
stateless
etherium
is
a
specific
initiative
about
moving
to
stateless
to
having
a
allowing
a
spectrum
of
statelessness
for
clients
which
includes
a
eventual
moving
into
then
includes
the
road
map
into
eath,
to
where
clients
are
stateless.
A
Great
yeah,
that's
perfect
and
I
just
pulled
up
a
IP
1559
that
James
just
referenced.
It's
a
it's
a
way
to
change
the
fee
market
for
eath
1.0.
There
are
some
VIPs
that
are
so
massive
and
scope
to
change
the
network
that
they
are
thrown
into
the
1x
bucket.
There
are
other
things
like
some
updates
to
the
EVM.
Some
pre
compiles
like
cryptographic,
pre-compile
that
enable
things
like
ZK
or
zero-knowledge
cryptography
that
are
more
in
the
1.0
realm,
because
they're
being
worked
on
actively
and
are
almost
done,
there's
also
some
stuff.
A
That's
weird
in
between
there's
a
BLS,
a
cryptographic
BLS
curve
precompile
that
is
needed
for
eath
2.0,
that
is
kind
of
falling
in
the
1.0
and
1x
category
and
is
being
actively
worked
on.
It'll,
probably
be
in
the
next
network,
upgrade
that
we
do,
among
other
things,
that
we're
looking
at
putting
in
that's
all
discussed
on
the
coordinate
meeting
and
then
the
notes
kind
of
talk
about
it.
A
Oh
cool
someone,
someone
marked
in
yellow
I,
think
that
that
might
be
all
for
EIP
x'
Oh,
a
theory
I'm
2.0,
aetherium
2.0
has
calls
I,
don't
know
where
that
repo
is,
but
it's
very
similar
to
the
all
core
dev
calls
it's
actually
going
on
right
now
and
you
can
tune
in
after
you
leave
here.
I
guess,
I
think
it
goes
on
for
an
hour
to
an
hour
and
a
half
and
it's
a
similar
format
as
the
all
chord
to
have
calls
and
that
it
just
talks
about
aetherium
to
stuff.
A
A
You
can
draw
using
zoom,
anyways
I,
think
that
might
be
it
actually
for
for
for
this.
If
there's
no
more
questions
other
core
devs
on
the
call,
is
there
anything
that
you
can
think
of
as
far
as
what
needs
to
be
known
for
someone
jumping
into
the
ecosystem.
A
A
So
that's
how
old
it
is
from
there
I
used
to
take
all
the
notes
and
run
the
meeting.
So
I
would
just
you
know,
do
the
notes
after
the
meeting
was
over
I'd
also
do
a
reddit
post,
sometimes
here's
an
example
of
one
I
did
a
couple
years
ago,
where
I
just
post
the
meeting
number
and
people
talk
about
it
on
reddit
I
stopped
doing
that.
I
haven't
been
as
active
on.
Reddit
I
probably
need
to
get
active
again.
A
As
far
as
the
background
on
aetherium,
the
talaq
Lutheran
O's
was
the
primary
founder
of
aetherium.
He
came
up
with
a
theory
'm
out
of
a
need
to
create
this
eco
or
to
create
this
blockchain
platform.
That
was
the
bitcoin
could
not
support.
There
was
limited
scripting
and
quote
smart
contract
and
quote
ability
and
bitcoin.
So
you
could
only
do
things
like
multi
signatures
or
different
op
codes
to
trigger
you
know
dispersal,
a
bitcoin
at
certain
time
and
that
wasn't
sufficient
for
what
metallic
had
in
mind.
A
As
far
as
the
bigger
ideas
of
a
general
use
case,
blockchain
platform
goes
so
he
wrote
the
white
paper
at
the
December
2013.
He
distributed
it
out
around.
You
know
the
end
of
that
year
and
into
2014.
He
announced
aetherium
at
the
Miami
Bitcoin
conference
in
2014.
From
there
he
developed
a
there
were
people
who
were
interested
there
or
had
already
somewhat
joined
the
team
out
of
interest
from
reading
the
white
paper
and
that
team
over
the
next
two
years,
developed
or
really
over
the
next
year.
A
A
Sorry
about
that
just
went
on
a
whole
rant,
alright,
so
yeah
for
Prague
pal.
Let's
go
to
Prague
pal.
That's
a
really
good
question.
I
think
it's
10:57,
yep
Prague
pal
was
started
in
2018,
May,
28
and
basically
there's
this
group
called
F
Neff
else.
They're
semi-anonymous.
There
is
one
public
member
named
Christie
mine,
Han
or
christieelee
mine
Han,
and
they
wanted
to
study
the
growth
of
Asics
on
the
network.
A
So
what
I
mean
by
all
that
is
that
aetherium,
according
to
the
white
paper
in
the
yellow
paper,
which
are
two
documents,
that
kind
of
outline
how
aetherium
goes
is
said
that
there
should
be
a
sip
resistance
because
of
mining
centralization
concerns
so
for
the
next
nearly
I
guess,
four
to
five
years,
aetherium
was
a
sick
resistant.
There
were
no
Asics
being
publicly
built
on
aetherium
that
changed
in
2018
when
an
ASIC
was
announced.
A
That
was
sorry
that
were
specifically
programmable
for
et
hash
and
was
economically
feasible.
So
it
wouldn't
be
a
waste
of
money
or
time
if
you
were
to
create
them.
The
motivation
for
prog
POW
is
to
basically
kick
a
six
off
the
network
or
make
it
a
sakra,
xizt
in',
so
it'd
be
more
expensive
than
it's
worth
to
design
them.
A
A
What's
it
called
code
for
prog,
pal
and
late
in
2015,
Marten
swin
day
and
others
made
a
test
net
called
the
Gangnam
test
it
to
test
the
transition
from
ET
hash
to
prog
pal,
which
was
successful
on
a
test
net
throughout
the
history
of
prog
pal,
there
has
been
I,
actually
wrote
a
giant
blogpost
on
this,
the
other
night,
so
it'll
be
really
fun.
When
I
released
this
I'm,
literally
going
from
my
blog
post
here,
they
released
a
or
as
these
prog
pal
became
more
and
more
apparent
that
it
might
be
entering
the
network.
A
The
the
community
that
warrant
wasn't
miners
kept
getting
bits
and
pieces
about
it
and
they
wore
felt
like
they
weren't
being
heard.
There
were
people
who
were
anti
prog
pal
and
they
felt
like
in
the
cordon
of
meetings
they
weren't,
properly
represented
or
properly
heard
or
dismissed
so
because
of
that,
there's
been
kind
of
some
trouble
brewing
over
prog
pal,
because
of
that
sentiment
mainly
there's
also
concern
over
the
safety
of
prog
pal,
which,
in
January
2019
prompted
the
core
developers
to
ask
the
etherium
cat
herders
to
fund
and
do
an
audit
of
prog
pal.
A
So
a
software
and
hardware
audit
was
done.
The
software
audit
was
my
least
Authority,
and
the
hardware
on
it
was
by
Bob
Rao.
And
if
you
go
to
Prague
pal
audit
theory
at
herders,
you
can
see
that
there
was
two
blog
posts
by
the
etherium
cat
herders.
That
outlines
that
you
can
look
those
up
just
do
aetherium
cat
herders,
Prague
Pal
on
YouTube,
sorry
on
Google
I
get
the
giant
monolith
websites
next
up
something
else
we
were
also
tasked
with
doing
was
gauging
sentiment.
A
We
did
a
coin
vote,
which
is
where
people
stake
their
coins
for
whatever
position.
They
want
it's
kind
of
flawed,
because
big,
like
companies
with
a
ton
of
ether,
can
just
like
stake
their
coins
toward
one
thing
or
another,
there's
also
a
minor
vote
that
was
had,
which
is
more
interesting,
because
what
what
we
did
is
miners
use
the
extra
data
every
time
they
mined
a
block
to
basically
say
if
they
want
Prague
POW
to
be
included
or
not.
There
was
a
77%
turnout
amongst
mining
pools
and
all
of
them
were
yes.
A
There
were
obviously
23%
that
didn't
vote
at
all,
but
there
were
no.
There
were
zero,
no
votes
toward
Prague
pal.
There
was
also
a
survey
done
with
interviews
with
different
people.
You
can
view
that
in
here
as
well,
although
it's
anonymous
so
there
could
be
biases.
Obviously,
and
then
there
the
technical
audit
was
funded,
it
was
completed
and
you
can
view
that
and
the
etherium
cat
herders
github.
If
you
go
to
a
theory,
'm
cat,
herders,
prog,
pal
audits,
release
blog
there's,
also
a
link
to
it.
A
So
after
this
was
released
and
late
September
Prague
POW
came
up
again
in
the
community
with
again
a
lot
of
fanfare.
There
were
times
throughout
the
year
where
people
felt
like
I
and
others
within
the
core.
Deaf
community
didn't
properly
communicate
the
fact
that
prague
pal
was
going
in
it
was
accepted
in
January
2019,
but
people
throughout
the
kept
finding
out
that
it
was
accepted
as
an
EIP.
Without
a
lot
of
talking
about
it,
I
guess,
with
the
community
at
least
that's
their
perspective,
you
can.
A
It
goes
back
and
forth
what
people
think
about
it
or
if
they
were
correctly
I
guess
involved
in
the
process.
I
think
there's
they
weren't
and
that
we
could
have
done
a
lot
better
job.
So
that
brings
us
down
to
the
Istanbul
Network
upgrade.
We
were
gonna
put
Prague
Palin
there,
but
there
were
more
important.
A
The
IPS
to
put
in
so
we
pushed
it
away
and
Istanbul
went
in
in
December
and
also
Muir
glacier
went
in
and
January
Muir
glacier
was
a
network
upgrade
that
corrected
the
ice
age,
which
is
something
built
into
the
etherium
protocol.
That
artificially
creates
a
difficulty
bomb
within
the
mining
algorithm
to
make
block
times
higher
in
order
to
get
core
devs
to
get
off
their
bets
and
do
a
hard
fork,
slash
network
upgrade
if
they
haven't
done
it
in
a
long
time.
A
We
forgot
to
push
the
ice
age
down
the
road
because
we
weren't
calculating
it
correctly,
so
it
kind
of
sprung
up
on
us.
So
we
had
to
do
two
network
upgrades
back-to-back
so
anyways
January
comes
around.
We
have
a
January
and
February
cordon
of
meetings
in
which
Prague
POW
is
brought
up
again.
This
time
when
it's
brought
to
the
community,
there
is
a
lot
of
yelling
about
it,
yelling
in
a
way
where
people
are
expressing
their
opinions
loudly,
some
of
them
politely,
some
of
them
not
politely
and
overwhelmingly.
A
A
A
That's
one
position,
I,
don't
know
if
I
believe
that
at
this
point,
because
there
are
good
reasons
not
to
put
it
in
and
in
their
opinion,
there's
some
conspiracy
theories
around
if
death
else,
because
there's
semi-anonymous
and
Kristy
Lee
mine
hand
because
of
people
coming
up
with
conspiracy
theories
about
her
involvement,
so
that
kind
of
raises
the
alarm
bells
for
people
there's
just
a
variety
of
reasons:
I'm
releasing
a
blog
post
today
or
tomorrow.
That
outlines
all
the
arguments
there's
about
sometimes
for
28
to
30
arguments.
A
I
outline
that
you
can
read
through
including
an
entire
history
of
what
I
just
said
about
Prague
POW
and
my
personal
opinion
and
conclusions.
So
where
we
are
now
is
Prague
POW
is
technically
an
accepted
state.
If
we
go
to
Prague
POW,
it's
still
in
draft
because
we're
lazy-
and
we
didn't
put
in
an
accept
it
yet,
but
it
is
technically
an
accepted
state
meeting
that
it
is
being
slated
for
a
future
hard
fork.
A
The
last
core
dev
meeting
we
were
thinking
of
putting
the
BLS
signature
curve
pre-compile
in
Berlin,
which
is
the
next
hard
fork
name
and
then
three
weeks
later,
having
Prague
POW
goin.
The
reason
for
this
is
if
Prague
now
is
put
in
with
other
AIPS
people,
can
accuse
us
of
smashing
a
controversial
AIP
with
a
non
controversial,
I
P,
to
force
people
to
upgrade.
Now
that
all
this
controversies
happened,
I
believe
Prague
POW
is
not
gonna
be
going
forward.
That's
a
personal
opinion.
A
We
still
need
to
talk
to
the
core
devs
and
see
what
their
opinion
is,
but
I'm.
Guessing
at
this
point,
there's
been
enough
community
sentiment
that
has
come
up
again
that
we
wouldn't
want
to
do
something
like
that.
That's
a
personal
opinion
again
we're
gonna
have
to
see
where
we
stand
on
that
and
as
core
developers.
If
you're
on
this
calling
you're
a
core
developer-
and
you
have
an
opinion,
I
highly
encourage
you
to
participate
either
in
Twitter
reddit
and
if
you're
not
comfortable
doing
that
because
of
the
vitriol
participate
in
the
all
core.
A
Dev
call
and
give
your
opinion
there,
because
there's
not
enough
people
speaking
up
about
their
opinion,
the
matter
and
there's
just
a
lot
of
misinformation
and
noise
being
thrown
around.
So
it's
important
to
educate
yourself
and
voice
your
opinion
as
a
core
developer
in
my
head
and
my
mind.
So
that
is
prog
pal.
C
A
Totally
and
like
there
are
so
at
the
time
that
prog
POW
was
proposed,
there
were
Manero
was
doing
like
Manero
decide
to
be
a
sikh
resistant,
so
what
they
would
do
is
every
four
to
six
months.
I
think
they
would
change
their
algorithm
to
a
different
mining
algorithm
that
was
ASIC
resistant
for
the
time,
but
Asics
would
catch
up.
A
On
top
of
all
of
this,
something
I
forgot
to
mention:
ET
hash
has
what
can
be
considered
a
exploit,
vulnerability,
optimization,
etc,
called
the
light
evaluation
attack
where,
basically,
when
you
have
the
here's,
how
I
understand
it
Christy
was
talking
to
me
about
it
and
will
correct
me
in
the
blogs.
So
don't
take
this
as
gospel,
but
you
have
to
load
the
dag
into
memory
when
you're
mining
and
so
the
DAGs
reaching
for
gigabytes
or
greater,
and
so
that's
going
to
brick
a
lot
of
the
current
Asics
and
some
of
the
GPU
cards
out
there.
A
As
part
of
that
concern,
according
to
their
side
of
the
argument,
is
centralization
concerns
around
having
one
or
two
ASIC
entities
that
are
unknown
mining
mining
on
a
theorems
network
and
having
more
than
51%
of
the
network,
so
they
can
perform
a
tax
or
do
what
they
will
so
that's
kind
of
another
tidbit
in
there.
But
yeah
I
agree
with
you.
It's
it's
interesting
how
its
controversial
and
how
we're
not
looking
at
other
things,
but
I
think
we're
gonna
start
looking
at
other
algorithms,
especially
since
Prague
passed
a
controversial
at
this
point.
C
As
it
happens
before
my
involvement
with
Syria
before
I
started
working
on
open,
a
theorem
I
was
a
part
of
the
Monaro
ecosystem
community,
so
I
saw
the
developments,
the
rise
and
the
adoption
of
random
packs
with
my
own
eyes,
and
basically
this
was
my
neighbor's
last-ditch
solution.
So
basically
it
was
either
random
acts
and
either.
If,
if
random
acts
didn't
succeed,
then
an
ASIC
frankly
algorithm
would
be
adopted
and
mineiro
would
become
a
sick
friend
Lee.
But
basically
what
happened
is
that
random
acts
got
for
security
orders
all
funded
by
the
Monaro
community.
C
A
Really
interesting,
I
think
your
perspective
at
the
cordetta
meeting
would
be
highly
appreciated
because
you
kind
of
have
the
history
from
the
Monaro
perspective
of
how
they
were
secretly
hai6
were
secretly
mining
the
network
supposedly
and
that
there
was
over
51%
of
them
and
how
that
was
discovered
and
things
like
that.
That's
an
interesting
perspective
for
sure
that
I've
only
looked
into
on
the
surface,
so
I
just
understand
it
at
a
basic
level.
A
K
A
Think
that
would
ever
go
through
with
the
fact
that
it's
all
GPU
miners
we
have
right
now
so
yeah
that
would
be
really
difficult
to
push
through,
because
we're
our
community
is
different
than
how
the
Monaro
community
does
governance
from
my
understanding.
So
it
would
just
be
difficult
any
other
questions
or
comments.
A
All
right
well
as
much
as
I
love,
hearing
myself
talk
all
day:
I
need
to
drink
some
water
and
we're
gonna
end
this.
For
now.
Let
me
stop
sharing
my
screen.
So
yeah
thanks
everyone
for
coming,
if
you
have
any
other
questions,
feel
free
to
reach
out
to
me.
The
most
efficient
way
to
reach
out
to
me
is
on
telegram:
I'm
at
soup,
tacular,
sou,
P,
TAC,
ul
AR,
or
on
Twitter
at
Hudson
Jameson.
A
You
can
DM
me
I'm,
also
on
getter,
but
I
forget
to
check
those
messages
and
I'm
also
on
discord
and
I.
Do
check
discord
and
I'm
in
various
channels
on
discord,
but
again
telegram.
Twitter
I
also
have
an
email
Hudson
at
etherium
org.
If
you
want
to
reach
out
to
their
I
check
that
every
once
in
a
while
as
well.
So
anything
y'all
need
as
new
people
to
the
newer
people
to
the
ecosystem.
A
A
You
can
Hudson
yeah
and
we
will
see
you
on
the
chord
F
calls
hopefully-
and
we
might
do
this
again
in
the
future-
if
we
get
even
more
people
on
board
it.
If
you
all
can
keep
me
up
to
date
with
how
gnosis
is
doing
with
the
onboarding
and
just
show
them
this
video
and
if
they
have
more
questions
or
there's
a
need.
Just
let
me
know-
and
we
can
have
more
of
these
all
right
and.