►
Description
Host: David Utrobin
Special Guests:
We will be joined by a number of community members to talk about the Core Unit MIP Set that's currently in RFC.
Maker Relay Ep 31
https://forum.makerdao.com/t/maker-relay-ep-31
If you're curious to learn more about MakerDAO explore some of the resources below:
Awesome-MakerDAO Resource Repository: https://awesome.makerdao.com/
Technical Documentation: https://docs.makerdao.com/
Community Portal: https://community-development.makerdao.com/
Governance Forum: https://forum.makerdao.com/
Website: https://makerdao.com
Twitter: https://twitter.com/makerdao
Reddit: https://www.reddit.com/r/MakerDAO/
Chat: https://chat.makerdao.com/home
A
A
maker
dial
community
call,
my
name
is
david
utrobin.
I
am
a
community
development
lead
here
at
the
foundation
and
also
a
long
time,
community
member
and
I'm
really
happy
to
get
the
chance
to
lead
these
calls,
and
so
today
is
going
to
be
an
interesting
one.
Historically,
we
have
used
these
calls
to
do
a
few
things,
so
we've
used
it
for
sharing
updates.
A
So
last
week
we
actually
did
a
panel
discussion
on
the
surplus
buffer
and
this
week
we're
going
to
be
doing
a
panel
discussion
on
core
units,
and
so
just
like
last
week,
I've
invited
a
handful
of
people
on
the
call
today
and
I'll
be
inviting
them
on
the
screen
and
as
they
come
on,
I
am
going
to
give
them
a
chance
to
introduce
themselves,
and
then
we
will
jump
into
the
the
fun.
B
Everybody,
so
let
me
see
if
I
can
actually
share.
I
managed
to
share
my
screen
before,
but
first
here
just
a
second.
A
So
if
anybody
is
in
the
the
call
who
wants
to
come
on
screen
and
and
share
some
thoughts
and
and
talk
with
us,
definitely
just
ask
in
the
chat
I'll,
happily
invite
you
so
yeah
cool
before
you
share
your
screen,
imeo.
How?
Let's?
Let's
do
like
a
quick
round
of
introductions
and
and
get
everybody
to
you
know,
say
their
name
or
handle
talk,
talk
a
little
bit
about
what
your
involvement
is
at
maker
and
like
what
your
interest
is
with
the
core
units.
B
I
start
perhaps
I
see
myself
as
a
first
in
the
line,
so
maybe.
B
Random
community
user,
so
I've
been,
I
guess
I
joined
the
community
in
2009
when
I
discovered
this
project,
I
bought
a
few
tokens
kr,
and
so
I
started
following
the
project
and
yeah
very
recently
with
one
and
el
pro.
I
took
part
of
this
dedicated
group
to
basically
kick
off
this
idea
of
the
core
units.
B
The
attempt
is
to
try
to
decentralize
the
as
much
as
possible
make
her
dao
to
to
reach
really
the
the
level
of
the
centralization,
the
centralization
that
we
hope
to
achieve
in
a
couple
of
years,
or
hopefully,
even
earlier,
and
that's
it.
So
I'm
here
today
just
to
speak
about
the
discord
unit
idea
and
give
my
opinions
on
it,
and
so
that's
it.
A
Nice,
nice
and
just
to
repeat,
you
co-authored
the
the
mipset
with
juan
right
or
you.
You
just
were
a
major
contributor
or
how
what's
your
role
in
that.
B
So
I
would
say
well
a
minor
role
in
a
sense,
so
we
discussed
a
lot
together,
but
it
was
definitely
well,
at
least
in
my
opinion,
one
who
did
most
of
the
work
so
yeah.
I
just.
I
basically
accepted
the
invitation
to
speak
here
just
to
express
my
opinions
not
to
claim
any
ownership
or
anything.
It's
really
el
pro
and
one
definitely
took
the
the
biggest
cut
of
the
work.
I
think
very
cool.
A
D
Yeah
first,
I
I
disagree
with
what
mia
is
saying
but
yeah.
I
used
a
lot
of
help
from
a
lot
of
people,
so
I
don't
want
to
take
credit
for
it.
That
said,
my
name
is
juan.
My
handle
was
or
is
juan
juan
because
juan
was
already
taken.
I
think,
and
yeah
I've
been
in
maker
for
a
while.
Now
I
actually
worked
with
david
some
time
ago
and
we're
still
collaborating
in
different
projects
together.
D
What
else
I
don't
know
I
started
reading
about
maker
a
long
time
ago,
found
it
fascinating
and
and
got
sucked
into
the
the
rabbit
hole.
That's
that's
my
story.
A
Nice,
nice,
how
about
peyton
next.
C
All
right
hi,
my
name
is
peyton.
I'm
pros
11
on
the
forums
and
yeah
definitely
rabbit
hole
is
a
good
way
to
describe
it.
Juan
I'm,
I'm
still.
A
pretty
new,
relatively
community
member
got
involved
in
november
was
when
I
first
heard
about
maker
and
was
just
really
excited
about.
The
idea
came
on
the
forum
started,
contributing
and
now
I
help
out
with
governance
and
and
some
communications
as
well
and
just
happy
to
be
here.
So
yeah
fell
down
the
rabbit
hole,
we're.
A
Happy
to
have
you
man
and
then
finally,
l
pro
himself,
mr
frank,
cruz,.
E
Hey
y'all,
yes,
frank,
cruz,
aka,
l,
pro
aka,
l
progreso,
which
is
a
name
from
the
town
I
was
born
in,
which
is
el
progresso,
honduras,
central
america,
for
all
you,
geographical
fans.
Yes,
I
got
into.
I
got
I'm
just
a
maker
community
member
which
goes
to
show
you
that
anybody
out
there
who's
watching
this
or
is
going
to
watch.
E
This
can
become
a
community
member
and
I
fell
in
love
with
the
project
back
in
late
2018,
when
roon
christensen
came
on
the
laura
chin
podcast,
I
was
learning
about
oats
right
and
things
besides
bitcoin
and
ethereum
and
heard
this
guy
talk,
it
was
a
two-part
recording,
they
did
actually
back
then,
and
it
just
blew
my
mind
just
the
whole
mechanics
behind
it.
I
had
to
listen
to
it
probably
like
three
times
just
to
understand
governance
and
what
the
role
of
the
mkr
token
is
yeah,
even
laura.
C
E
Pack
during
the
2017-2018
winter
meltdown
or
whatever
it
was
called,
was,
was
amazing
right,
the
way
it
kept
this
pack.
So
that's
the
reason
why
I
got
involved
and
throughout
this
whole
journey
I've
met
a
bunch
of
awesome
people
right.
So
it's
it's
been
a
it's
been
a
great
journey
that
I
hope
to
continue.
A
Yeah
makers
certainly
proved
itself
through
the
fire.
After
that
2017
crash
and
so
frank,
you
were
also
a
contributor
to
towards
the
core
unit
mipset.
Did
I
hear
that
right.
E
Yeah,
so
I
was
part
of
the
working
group
like
iomeo
said
this
all
goes
to
to
juan
he's,
got
some
amazing
brain
in
there
in
that
head
of
his.
So
you
know
I
I
gave
the
input
as
best
as
I
could.
My
approach
was
things
I've
learned
in
life.
How
we
should
you
know.
A
An
awesome
experiment
and
yeah
totally
and
yeah
doing
it.
The
the
most
wise
way,
I
think,
is
like
everybody's
goal
and
so
that
it's
really
great
that
so
many
people
in
the
community
came
together
to
help
make
this
thing
happen
and
so
cool
everybody
did
their
intro.
I
believe
imeo.
B
Yes,
let
me
see,
if
I
can,
you
see
the
screen
at
the
moment:
yeah,
okay,
so
yeah,
so
my
plan
here
is
to
give
about
10
minutes
of
presentation
about
about
the
ideas
of
the
core
units
by
means
of
this
whiteboard
here
that
you
see,
and
so
the
idea
of
these
core
units
was
posted
in
the
forum
as
a
set
of
mips
around
three
weeks
ago,
and
we
are
very
happy
that
there
was
a
lot
of
discussion
that
the
community
reacted
very
positively.
B
So
I
think
most
of
the
people
already
know
what
what
it
is.
Basically
so,
my
this
presentation
is
basically
divided
in
two
parts.
The
first
part
we
go
over
through
the
very
basics
of
these
ideas,
these
primitives-
and
it's
mostly
intended
to
somebody
who
was
not
so
much
involved.
Okay,
so
probably
none
of
you.
B
So
if
somebody
sees
this
on
youtube
later
on,
maybe
you
can
get
something
out
of
this
first
five
minutes
and
then
in
the
second
part
I
would
like
perhaps
to
discuss
some
points
that
have
not
been
discussed
so
much
so
far,
and-
and
this
is
normal
because
our
idea
with
this
proposal
was
just
to
kick
off
the
you
know
the
the
the
process
that
the
community
must
do
not
not
any
of
its
initiators
right.
B
So
we
just
proposed
some
very,
very
basic
elements
and
we
hope-
and
it
is
happening
that
the
community
reacts
by
proposing
modification
and
this
type
of
things.
So
let
me
start
here
I
have
shown
basically
in
this
whiteboard
a
cloud.
This
represents
the
governments,
the
governance.
So
this
is
basically
the
forum
activity,
the
chat,
the
voting
process
on
chain
and
off
chain.
The
communica
community
calls
like
this
one,
so
everything
that
is
basically
around
this
governance
process
and
above
the
cloud
we
have
these
dots
and
they
represent
the
contributors.
B
So
these
are
people
that
do
actual
work
for
maker
dao.
They
can
be.
I
don't
know
smart
contract
developers,
oracles
sys,
admins
governance,
people-
I
mean
administrating
the
or
simplifying
the
governance
process
and
like
this,
so
they
all
do
some
kind
of
work
and
in
a
in
a
ideal
universe,
governance
would
be
able
to
handle
and
community
directly
communicate
with
all
of
them
right.
B
So
let
me
draw
a
few
lines
here
so
now
in
a
perfect
universe,
government
would
have
sufficient
time
sufficient,
intelligent
and
knowledge
to
basically
interact
with
each
of
these
contributors.
But
of
course
it's
not
it's
not
possible
right.
There
are
time
limitation
knowledge
limitations.
So
not
all
people
voting
or
interacting
in
the
governance
know
everything.
So,
for
example,
they
might
know
nothing
about
smart
contracts.
How
can
they
deal
with
developers
right?
So
this
is
completely
unrealistic.
So
let
me
cancel
this
line
immediately
and.
B
Pollution
absolutely
so
there
are
all
kind
of
problems,
so
this
would
be
was
basically
a
completely
naive
scenario,
so
a
standard
company-
I
guess
so
I'm
not
you
know
from
you
know
how
to
say
personal
management
or
whatever
in
any
company,
but
my
guess
would
be
that
a
very
standard
approach
will
be
to
structure
all
the
contributors
in
a
hierarchical
way.
Okay,
so
basically
strict
three
structures,
so
we
would
have
a
a
boston
or
some
kind
of
boss.
B
He
will
have
some
people
under
him
and
some
more
people,
and
so
this
type
of
hierarchical
structure,
right
that
makes
perfect
sense
in
the
context
of
a
centralized
entity,
but
in
other
decentralized
the
community.
This
does
not
work
very
well
right.
So
what?
If
this
contributor
disappear
overnight?
B
And
nobody
knows
how
to
contact
him
because
he's
never
shared
his
real
world
contacts
online?
And
you
know
half
of
the
three
disappears
right.
So
that's
not
not
a
very
realistic
approach
in
a
decentralized
situation.
So
what
can
we
do
really
now
completely
decentralized
situation,
which
is
what
maker
dao
is
well.
Our
idea
was
to
simplify
these
three
three
structure
as
much
as
possible.
B
All
the
contributors
are
inside
these
core
units
and
there
is
only
one
person
that
interacts
with
the
governance
and
that
simplifies
our
interaction
with
the
governance,
and
that
is
called
a
facilitator.
So,
in
our
original
proposal
we
suggested
to
have
one
facilitator
for
each
core
unit.
The
discussion
proceeds
on
the
forum
and
I
believe
now
the
consensus
is
to
have
multiple
facilitators
on
potentially
a
core
unit,
and
the
same
facilitator
can
also
be
a
facilitator
on
several
core
units.
B
So
this
is
something
in
progress,
something
that
is
being
discussed
and
that's
and
that's
great.
B
So
the
idea
is
that
this
core
unit
represents
a
bunch
of
people
coordinated
by
the
facilitator
or
the
facilitators
of
that
core
unit
devoted
to
us
same
type
of
tasks.
So,
for
example,
this
could
be
the.
Let
me
think,
smart
contract
contractor
unit
okay
inside
here.
Basically,
we
do
work
related
to
smart
contract
development.
Another
core
unit
will
be
the
oracle
core
unit
etc,
and
there
will
be
the
govern
the
governance
core
unit,
the
whatever
okay,
all
types
of
core
unit.
B
In
fact,
I
started
a
forum
post,
I
think,
a
couple
of
weeks
ago,
or
even
less
than
that
called
core
units
I
wish
existed
and
many
people
answer
with
very
very
natural
and
interesting
proposals.
B
So
yeah,
please
have
a
look
at
that
thread
if
you
are
interested
in
what
kind
of
car
units
makerdaw
would
benefit
having
anyway,
this
is
the
basic
idea.
We
have
a
bunch
of
people
working
under
the
control
of
this
facilitator
within
the
context
of
a
core
unit,
and
how
does
it
work
the
payment
right,
because
people
want
to
be
paid
actually
to
do
some
work
and
the
idea
that
we
have
is
that
which
a
core
unit
we
assigned?
B
Let
me
use
another
symbol
like
I
don't
know
a
symbol
like
that,
and
this
is
a
budget
and
governance
attached
a
budget
to
each
core
unit,
and
so
let
me
try
to
depict
it
in
this
way.
Okay,
so
it's
not
a
great
symbolism,
but
I
think
it
will
work
so
the
facilitators
go
to
governance
and
ask
them
for
some
money.
Basically,
a
budget.
B
This
budget
will
be
approved
to
the
governance
and
will
be
attached
to
the
core
unit,
but
it
will
be
the
responsibility
of
the
facilitator
to
pay
the
contributors
inside
that
core
unit
okay,
so
this
allows
basically
to
discharge
all
the
complexity
or
the
great
majority
of
the
complexity
of
coordination,
payments,
human
interaction
and
control
of
quality,
basically
from
governance
to
just
the
facilitator.
B
Okay,
the
facilitator
is
basically
in
charge
of
managing
a
lot
of
people.
You
can
think
of
our
core
unit
in
some
sense,
as
a
as
a
company
right,
so
the
facilitators
company,
but
that's
a
very
gross
approximation.
But
that's
the
idea.
The
facilitator
is
in
charge
of
coordinating
these
people
and
we
are
going
to
talk
in
a
second
about
how
this
combination
might
happen,
but
yeah.
So
that's
that's
the
basic
idea,
and
one
important
thing
is
that
well,
this
goes
into
the
discussion
I
wanted
to
make
later
on,
but
yeah.
B
Another
point
here
is
that
the
same?
So,
let's
see
this
guy,
let
me
change
color,
so
you
can
follow
me
this
same
contributor
here.
This.
The
picture
might
might
suggest
that
it
cannot
work
for
another
core
unit.
This
is
not
the
case.
In
fact,
the
same
contributor
might
work
for
trucker
unit.
At
the
same
time,
okay,
just
as
a
normal
person,
can
work
part-time
into
companies.
There
is
no
no
problem
with
that,
given
that
this
is
possible.
B
Okay,
there
might
be
two
core
units
that
have
some-
I
don't
know
secrets
that
they
don't
want
to
share
with
other
core
units.
This
might
be
conceivable,
so
in
that
case,
that's
not
possible,
but
in
general
we
expect
that,
for
example,
if
there
is
a
figure
like
this
dot
here,
this
contributor
is
in
charge
of
doing
marketing
work
within
the
context
of
the
smart
market,
the
smart
contract
core
unit.
Well,
it
can
do
the
same
type
of
marketing
work
inside
the
oracles,
so
it's
not
prohibited
by
any
means
that
we
have
this
scenario.
Okay.
B
Another
thing
that
I
wanted
to
say
is
that
the
core
unit
itself
might
inside
of
it
might
be
composed
not
just
of
individuals
but
of
complex
entities
like
this
circle
here
or
figure
might
represent
a
company
okay,
so
we
might
have
a
real
world
company
working
within
the
context
of
a
core
unit.
It
will
interact
with
the
facilitator,
not
with
the
governance,
but
still
with
work
within
that
smart
contract
core
unit.
So,
as
you
can
see,
this
is
a
kind
of
trivial
in
a
sense
right.
We
have
a
free
primitives
that
we
are
talking
about.
B
B
It's
easy
to
understand
and
very
easy
to
modify
and
flexible.
That
means
easy
to
adapt
to
several
circumstances.
Okay,
so
there
is
not
much
complexity,
but
this
was
one
of
their
requisites
of
what
we
wanted
to
do.
Okay,
so
that's
basically
the
end
of
my
first
part.
I
just
want
to
mention
that
already
in
the
photo,
we
have
several
cory
units
proposal
or
several
are
coming
the
chart.
B
Many
people
are
not
not
yet
posted
their
proposal,
but
are
very
close
to
do
that
and
that's
great
so
I
guess
in
the
next
couple
of
months
we
will
really
be
able
to
see
the
first
few
core
units
activated
and
with
their
budget
with
their
facilitators,
and
so
people
really
working
for
maker
dial
in
a
decentralized
way.
Okay,
so
not
receiving
their
salaries
through
anything
like
the
maker
foundation,
for
example.
B
Okay,
now
I
want
to
start
the
second
part
with
some
topics,
topics
for
considerations
here,
so
these
are
just
mine.
I
mean
very
personal
and
opinions
on
on
where
this
can
go
wrong
basically
or
can
go
very
well.
B
The
first
concept
is
the
idea.
Okay,
so
let
me
make
a
box
here
and
I
will
call
this
box.
Oh
sorry,
risks
basically,
okay.
I
want
to
talk
about
potential
risks
of
this
of
this
framework.
B
The
first
risk
I
want
to
call
it
failure
of
a
core
unit
so
suppose
that
we
have
one
smart
contract
core
unit
or
let
me
talk
about
oracles
in
fact,
because
that's
even
more
critical,
because
you
know
oracles
need
to
be
up
all
the
time
and
they
cannot
go
down
even
one
minute
or
one
hour,
let's
say,
and
so
the
it's
failures
are
very
critical.
So
suppose
we
just
have
one
oracle
core
unit
and
for
whatever
reason,
the
team
disappear.
Okay,
so
there
might
be
stuck
in
an
airplane.
B
There
might
be
another
conference
where
internet
disappear.
They
might
even
do
something
bad,
okay,
maybe
a
competitor
paid
them
10
millions
to
just
leave
maker
dao
in
a
very
bad
situation.
So
this
is
not
going
to
happen.
Just
it's
just
a
an
extreme
scenario:
okay,
but
what
the
would
the
maker
down
do?
In
that
context?
B
B
So
what
I
want
to
the
conclusion
I
want
to
reach
here
is
that
it
is
incredibly
important
that
these
core
units
are
not
understood,
as
we
have
one
core
unit
for
each
topic
or
what
for
each
task,
but
we
need
to
replicate
this
core
unit,
so
it
would
be
amazing
if,
in
a
couple
of
years,
maker
dao
had
three
oracle
core
units.
Okay,
so
let
me
try
to
depict
the
picnic
here,
so
maybe
I
need
to
move
the
screen
a
little
bit.
B
We
need
another
oracle
or
calls
core
unit,
and
the
two
units
here
might
be
in
competition
with
each
other.
Okay,
a
healthy
competition.
So
I
think
that
would
be
very
important,
so
that
would
bring
costs
down
for
all
of
us
for
maker
dow,
I
mean
and
also
make
sure
that
the
best
solution
emerge
okay.
So
this
competition,
of
course,
should
be
positive,
not
negative,
so
the
core
units
should
be
required
by
governance,
to
interact
in
a
healthy
way
between
each
other
exchange
ideas,
apis
whatever
is
needed,
but.
A
B
A
that's
an
important
concept,
so
this
fail
really
duplicates,
as
somebody
already
wrote
in
the
chat
is,
is
the
consequence,
so
failure
means
that
we
need
to
duplicate.
Okay.
B
The
second
important
concept
is
that
the
concept
of
transparency
transparency
is
very
important,
because
we
need
to
check
that
what
these
core
units
are
doing
to
some
extent.
Okay,
for
example,
if
the
oracle,
just
again,
it's
a
very
important
example,
so
I'm
just
taking
this
oracle
core
unit
as
an
example,
we
want
to
check
if
they
are
actually
updating.
I
don't
know
their
servers
so
to
or
doing
their
work
right,
because
it
would
be
a
catastrophic
event
if
they
cannot.
B
I
mean
we
if
we're
surprised
by
some
bad
bad
news,
so
transparency
is
very
important
and
but
this
fight
versus
somehow
privacy.
Let
me
call
it
this
way.
For
example,
transparency
does
not
mean
that
the
salaries
of
every
contributor
should
be
disclosed
to
everybody
on
the
internet.
Okay,
that
would
be
crazy
because
not
all
contributors
would
like
to
do
to
have
their
salary
to
be
disclosed
and
also,
as
I
think
nick
pointed
out
or
either
in
the
chat
or
in
the
forum.
B
I
don't
remember,
there
are
simply
very
different
countries
in
the
world,
so
a
developer
from
norway
might
require
10
000
euros,
salary
per
month
or
even
more,
I
don't
know
the
same
developer
from
a
less
developed
country
like
italy
and
italian
would
be
happy
with
half
of
that,
for
example,
would
be
very
happy,
so
there
is
no
reason
really
economical
reason
to
pay
them
the
same.
There
could
be
a
reason,
but
it's
not
a
necessity.
B
Okay,
so
that's
a
there
is
a
tension
between
transparency
and
and
privacy,
of
course,
but
the
goal
ultimately
for
mkr.
We
want
these
query
units
to
work
well,
okay,
so
all
that
the
oracle
unit
must
provide
is
good
work,
efficient,
oracles
and
maybe
even
a
product
that
we
can
sell
to
others.
That
would
be
the
task,
but
of
course
they
need
to
provide.
They
will
be
incentivized
eventually
to
provide
transparency,
because
maker
dao
survives
only
if
it
can
prevent
disasters.
Okay.
B
So
there
is
this
attention
that
we
need
to
find
good
measure
to
to
balance
between
these
requirements,
and
so
that's
not
something
that
can
be
imposed
at
the
level
of
you
know
any
mip,
but
it's
something
that
I
think
should
emerge
as
a
culture.
It
make
a
dao
in
the
next
year
or
so
so
we
will
see
what
happens
so.
We
will
learn
from
hopefully
small
mistakes
and
and
see
and
see
what
happens.
B
Regarding
to
transparency.
I
think
there
is
another
important
concept
we
might
need,
and
I
think
it
will
be
necessary
to
have
some
core
units
per
unit
here
or
several
core
units,
as
already
mentioned
that
I
can
call
internal
affairs
okay,
so
internal
affairs
are
these
things
from
american
movies,
where
you
know
they
check
bad
cops
and
good
cops,
and
these
type
of
things,
but
I
think
it
would
be
very
important
to
have
a
core
unit
was
task-
is
to
check
that
other
core
units
are
doing
very
good
work.
B
They
are
not
selling
our
secrets
or
intellectual
property,
or
they
are
not
disclosing
critical
information
to
competitors
or
you
know
they
are
not
revealing
stuff
like
that.
So
it's
important
that
we
have
something
like
that,
especially
in
the
centralized
context
where
you
know
it's
not
clear
if
the
ordinary
low
government
law
can
protect
us
right
because
we
are
distributed,
we
don't
even
know
who
is
sitting
on
the
other
side
of
the
computer.
So
perhaps
coming
back
to
the
question
of
transparency
was
his
privacy.
B
We
can
respect
privacy
because
that
might
be
necessary
to
run
a
business,
but
we
might
force
facilitators
to
be
more
transparent
and
with
people
coming
from
this
internal
affair
unit.
So
that's
just
a
a
consideration.
I
don't
know
about
that.
The
third
is,
there
must
be
a
system
of.
B
The
third
thing
is
that
we
must
have
a
system
of
rewards
here
that
prevents
a
bad
behavior,
so
suppose
that
we
have
two
oracle
units
in
place
right,
one
one
in
competition
with
the
other,
but
it's
natural
among
humans
to
you
know,
try
to
make
cartels
or
you
know
to
just
talk
with
each
other
and
say:
okay,
I
will
make
this
price.
You
do
the
same.
B
Let's,
let's
get
happy
at
the
same
time
right,
so
we
must
find
a
way
to
give
positive
rewards
in
a
game
theoretical
sense
to
people
to
act
in
a
positive
way.
So
that's
a
very
difficult
question,
so
let
me
call
it
rewards.
B
And
these
rewards
might
be
in
the
form
of
mkr
tokens,
of
course,
on
whatever,
whatever
in
whatever
technical
way,
we
might
find
right,
so
people
will
be
incentivized
to
do
good
work
because
that
will
push
the
value
of
mkr
up
and
and
ultimately
that
will
bring
them
more
money
than
the
salary.
That's
just
a
possibility.
Of
course
there
will
be
1000
proposals,
I'm
sure,
but
it's
important
that
we
keep
this
system
of
rewards
in
place,
because
you
know
that's
key
to
the
success
of
the
centralized.
I
mean
bitcoin
material.
B
They
all
works
because
they
are.
There
is
a
nice
equilibrium
of
rewards,
and
you
know
punishments.
If
you
do
the
bad
bad
actors
are
not
rewarding.
Basically,
so
everybody
acts
in
a
nice
way.
B
The
fourth
is
about
a
code
of
conduct,
so
this
is
a
not
enforced
in
the
mips
that
we
have
seen
so
far
because
we
don't
want
to
force
anything
at
this
level
of
it
would
have
would
have
been
surely
a
mistake
to
force
things,
but
just
for
example,
one
example
suppose
the
mkr
alders
go
crazy.
Okay,
they
just
want
to
become
a
billionaires
tomorrow
and
they
ask
to
meet
5
billion
guys
tomorrow.
So
technically
this
is
doable
right
and
maybe
the
the
market
in
a
crazy
burran
might
be
happy
about
that.
B
I
don't
know,
but
there
must
be
some
sort
of
consideration
for
the
for
the
users.
Okay,
the
people
who
are
actually
using
die
because,
eventually,
if
the
system
collapse,
they
are
going
to
pay,
so
there
must
be
a
code
of
conduct
that
is
not
enforced
really
by
rules
but
is
more
enforced
by
culture
again.
So
I
guess
that
will
also
merge
at
some
point
I
have.
B
I
have
no
idea
how
to
enforce
this
in
a
in
a
a
formal
way,
but
because
we
are
in
the
centralized
right,
we
are
out
of
the
low
system
in
a
sense,
so
yeah
it's
difficult,
but
yeah.
I
think
it's
important
that
we
understand
that
facilitators.
Yes,
they
need
to
do
what
governance
tells
them
right,
but
they
also
have
to
have
some
intellectual
code
of
conduct
and
moral
conduct
that
they
have
to
be
brave
enough
to
take
decisions.
B
Sometimes
I
don't
know,
that's
just
a
point
that
I
wanted
to
make
and
let's
see
if
I
have
one
last
point
yeah,
so
somebody
already
raised
this
point
in
the
forum
and
it
is
about
intellectual
property
and
secrets
in
general.
B
So
how
do
we
handle
these
type
of
things?
Because
here
these
core
units
will
do
work
and
they
do
work
that
sometimes
it's
valuable,
just
as
an
intellectual
contribution
sure
everything
here
is
going
to
be,
or
the
vast
majority
of
things
here
are
going
to
be
open
source
right,
but
suppose
this
oracle
unit,
again
as
an
example,
develop
some
oracle
technology.
B
Who
is
the
owner
of
this
intellectual
property?
It's
it's
maker,
dal
is
the
facilitator.
Who
is
it
intuitively?
We
would
like
to
be
makerdale
right
because
they
are
working
for
mcgraw
so
and
how
does
that
work
exactly
because
intellectual
property
is
governed
by
real
water
laws
right?
So
it's
not
just
an
ethereum
smart
contract.
So
how
does
this
work?
I'm
not
really
sure
so
in
the
forum,
somebody
one,
I
think,
mentioned,
that
there
is
a
concept
at
the
moment
that
is
called
the
dye
foundation.
B
So
this
by
foundation
is,
I
think,
it's
different
than
the
maker
from
the
I
I
don't
know
so
I
don't
know
the
details
about
this,
but
the
general
idea,
I
believe,
would
be
something
like
the
linux
foundation
yeah
exactly.
This
was
announced
in
the
in
the
maker,
dow
blog,
I
think
about
two
years
ago.
Yes,
so
the
idea
of
this,
but
I
couldn't
find
more
information,
so
I
I
don't
know
that's
my
telephone.
B
What
I'll
answer
later
anyway,
this
is
basically
the
something
like
the
linux
foundation
should
be
a
non-profit
organization.
A
I
mean
okay,
can
you
can
you
can?
Can
you
like
mute
the
ringer.
B
A
You
covered
quite
a
wide
range
of
really
really
interesting
stuff,
so
I
want
to
give
a
chance
of
to
juan,
to
payton,
to
frank,
to
to
comment
or
or
ask
any
questions
around
these
and
while
they
get
their
questions,
I
know
luis
slozada
asked
a
question
in
the
chat
so
and
I'll
just
read
it
out
loud
for
the
recording,
so
lewis
asked
so
it's
good
that
the
facilitator
only
asks
for
a
budget,
and
he
says
he
will
manage
it
with
all
his
team.
A
Or
is
there
a
way
to
protect
the
team
members
who
don't
want
to
show
their
gains?
I'm
not
100
sure
on
the
wording
of
that
question,
but
I
think
I
understand
the
the
gist
of
it.
Basically,
is
it
okay
that
the
facilitator
has
that
control
and
that
link
with
governance
and
and
what
kind
of
mechanisms
are
there
in
place
to
prevent
a
facilitator
from
abusing
that
position
of
privilege?.
D
I
I'm
not
sure
if
he
means
I
because
he
was
saying
it
well,
while
mia
was
talking
about
the
privacy
part,
so
I'm
not
sure
in
which
I
don't
know,
maybe
luis
you
can.
You
can
comment
on
it,
but
but
yeah
as
you
mentioned,
and
I
don't
know
frank
if
you
want
to
go
for
it,
but
the
way
we
saw
it
originally
is
that
we
give
the
facilitator
the
the
freedom
to
and
the
responsibility
at
the
same
time
to
to
deal
with
the
with
the
budget
in
the
way
that
they
feel
comfortable.
D
If
they
want
to
to
form
a
company
and
convert
the
dye
into
fiat
and
pay
in
fiat,
they
can
do
that
if
they
want
to
set
a
another
dao
for
that
core
unit
or
lao
or
or
or
something
with
more
people,
they
can
do
that
as
well,
so
there
are
different
possibilities
that
they
can
potentially
choose
to
to
go
for
and
and
actually
yeah
this
this
system,
this
model
or
framework
allows
this
flexibility.
A
Yeah
totally-
and
I
like
the
idea
of
like
an
internal
affairs,
the
department
that
imeo
brought
up
because
in
some
sense
there
has
to
be
accountability
for
all
these
different,
like
independent
core
units,
and
you
know
whether
it
is
you
know
them
being
very,
very
public
about
all
their.
You
know,
budget
and
operations
and
everything
you
know:
that's
one
option
and
there's
just
kind
of
like
a
natural
accountability
that
happens
in
that
model
and
then
there's
the
more
private
version.
A
But
when
there's
more
privacy,
you
know
there
has
to
be
some
sort
of
allowance
to
a
special
party
so
that
there
can
be
accountability
to
governance.
So
I
like
that
internal
affairs
idea.
But
of
course
that's
like
you
know
it's
still
super
early
for
that,
since
the
very
very
concept
of
core
units
is
still
being
built
into
maker
down
right
now,.
D
And
also
luis
thanks
for
rephrasing
the
the
question:
is
it
better
to
be
transparent
or
not?
So
we
believe
that
it
is,
but
we
also
believe
that
transparency
doesn't
mean
that
it
doesn't
need
to
be
private
right.
So,
a
way
of
of
doing
this
is
potentially
the
the
core
unit
facilitator,
saying
hey.
I
need
to
hire
three
people
and
I'm
going
to
need
a
budget
of
150k
per
year
for
those
three
people
and
you
don't
know
how
much
each
people
is
actually
being
paid.
D
Point
number
one
point
number
two:
we're
encouraging
facilitators
to
actually
have
a
little
bit
of
a
buffer
in
case
something
comes
up,
but
also
if
they
need
to
negotiate
or
hire
someone
else
or
or
anything
that
might
happen,
so
you
could
potentially
try
to
get
a
budget
approved
and
not
use
the
whole
of
it.
So
it's
more
about
but
yeah.
Eventually,
you
will
need
to
do
a
report
saying
we
paid
this
much
in
salaries.
D
This
is
everything
that
we
achieved
in
this
last
month,
but
it's
more
of
a
of
showing
value
and,
at
the
same
time
showing
the
money
that
you've
used.
A
E
For
me,
it
was
a
thing
where
I
think
it's
important
to
retain
talent
right,
like
one
just
mentioned
that
if
you
want
to
attract
talent,
you
got
to
be
able
to
pay
up
sometimes,
but
I
also
thought
about
this.
Even
after
the
mips
were
released,
and
you
know
one
way
I
looked
at,
it
was,
if
you
work
for
a
publicly
traded
company
from
the
stock
market
a
lot
of
times.
E
People
want
to
go
after
the
ceo,
because
the
ceo
is
making
millions
and
millions
in
stock
options
whatever
these
are
publicly
traded
companies
right.
So
this
comes
down
to
the
public,
but
then
I
realized
that
I
you
know,
I
have
a
few
friends
and
you
guys
might
have
some
friends.
I
work
for
some
of
these
entities
and
I
don't
know
what
they
make:
it's,
not
public
and
technic
honestly.
For
me,
I
don't
really
care
what
they
make.
I
don't
even
care
what
their.
E
But
so
yeah
at
first
I
was
like:
should
it
be
transparent,
should
it
not
be
transparent
and
then
it
kind
of
came
around
that
you
know
it's
it's
pretty
much
up
to
the
core
unit
you
know
and
and
for
me
the
most
important
thing
is
again
to
retain.
A
It's
going
to
be
super
interesting,
seeing
different
core
units
come
about
with
different
models
because
we're
gonna,
you
know,
there's
gonna
be
some
that
decide
to
make
it
all
public
and
others
that
you
know
do
more
privacy
around
things
like
specifically
salaries,
but
I
think
all
of
the
core
units
are
gonna.
Have
a
level
of
transparency
like.
I
don't
expect
that
any
of
them
would
be
100,
just
opaque.
A
You
know,
like
the
budget
is
still
out
there
right.
The
the
goal
for
the
quarter
is
there
in
the
proposal
for
the
budget.
You
know,
and
then,
when
it
comes
around
to
the
next
quarter,
when
maker
has
to
you
know
reapprove,
you
know
this
next
chunk
of
money.
A
You
know
that
there's
all
of
the
information
in
place
there
should
be
all
of
the
information
in
place
for
the
maker
voter
to
say.
Oh
yeah,
this,
this
core
unit
is
clearly
like
failing
like
very
badly
failing,
mildly
or
like
achieving
and
like
succeeding
and
growing
right
like
they're
yeah.
I
I
expect
there
should
be
enough
transparency
to
at
least
make
that
those
kinds
of
judgments,
but
for
salaries,
of
course,
like
it's
going
to
be
interesting
to
see
how
core
units
handle
it.
A
I
think
an
interesting
thing
that
was
brought
up
was
the
code
of
conduct
risk
where
it's
really
hard
to
enforce
something
by
like
a
law.
You
know
I
know
some
companies
have
have
like
found.
You
know
they
have
like
bylaws
and
like
there's.
They
have
like
their
whole
internal
structure
of
law
and
they
have
a
means
of
actually
enforcing
it,
because
it's
a
centralized
company
and
they
could
you
know
they
have
full
control
over
their
entire
organization.
A
But
with
this
it's
yeah
that
idea
of
culture
ruling
the
enforcement
versus
like
an
actual
enforcement
agent
like
an
internal
affairs
department,
or
something
like
that,
will
be
interesting.
I'm
curious
if
anybody
on
the
panel
has
has
a
thoughts
on
that.
D
I
thought
that
you
were
going
to
take
it
frank
or
mia,
since
you
were
there,
the
one
listing
it,
but
I
can
I
can
attempt
I
can
try
to
yeah
regarding
the
the
the
code
of
conduct,
it's
it's
more
they're
different
they're,
different
ways
of
tackling
potential
risks
and
issues
and
well
david,
has
written
a
lot
regarding
the
emergency
shutdown
and
different
things.
So
so
he
can
probably
tell
us
more
about
that.
D
But
ideally
what
we
want
to
to
promote,
especially
in
the
very
beginning,
is
that
we
do
have
people
and
we
do
have
talent
that
we
trust.
So
the
the
original
approach
is
to
to
trust
and
then
verify
compared
to
asking
for
an
authorization
for
for
everything.
So
if
someone
asks
for
a
budget-
and
it
looks
reasonable,
the
idea
is
not
to
go
after
them
and
try
to
check
every
single
line.
D
It's
more
of
okay,
we'll
trust
you
with
this
and
then
once
we
see
the
reports
and
we
see
how
things
are-
are
moving
forward
check
more
yeah
these
things
and
how
how
every
different
budget
is
is
being
used
for
the
different
objectives,
but
that's
a
little
bit.
The
thought
behind
it.
D
I'm
not
entirely
sure,
but
I
I
would
argue
that
that
actually
we're
seeing
the
opposite.
There's
a
different
there's,
an
interesting
discussion
going
on
in
the
forum
with
the
governance
team,
going
all
transparent,
all
public
with
with
different
salaries
and
and
different
people,
one
of
them
myself,
arguing
that
those
rates
are
probably
below
market.
D
In
the
case
of
governance,
it's
relatively
hard
to
measure
and
and
maybe
a
little
bit
controversial,
because
we
don't
have
a
lot
of
information
about
governance,
facilitators
in
different
companies
right.
It's
a
it's,
a
role
that
that
not
many
projects
or
companies
will
have.
D
A
D
I
mean
eventually
it's
it's
almost
like
a
like
a
ceo
right.
It's
it's
there,
making
sure
that
if
you
see
the
token
holders
as
a
board
of
directors,
it's
it's
the
one
kind
of
like
making
the
liaison
between
the
board
of
directors
and
every
single
other
team,
but
at
the
same
time
you
need
to
run
communications.
D
If
you
find
any
company
that
has
a
ceo
that
communicates
as
much
as
long
for
wisdom.
Please
let
me
know
I
want
to
apply
that
right,
so
so
yeah,
it's
we
might
see.
We
we
might
have
a
slightly
like
average
or
above
average,
operations
cost
right
now.
That
does
not
seem
to
be
the
situation
and
we'll
see
it
as
more
core
units
decide
to
to
contribute.
So
we're
looking
forward
to
that.
A
Yeah-
and
there
is
a
really
good
question
in
the
chat
from
louis-
the
core
units
have
to
decide
their
own.
B
A
D
My
instinct
and
instinct
is
the
keyword,
so
I
don't
have
the
the
the
data
to
to
back
it
up.
Unfortunately,
but
it's
I
think
it's
one
year
that
said
if
your
core
unit
is
new
and
you're,
proposing
something
a
little
bit
more
extraordinary.
Maybe
it's
better
to
ask
for
something
less.
D
I
think
that
quarter
might
be
a
little
bit
too
much
since
you
don't
want
governance.
To
I
mean,
probably,
governance
doesn't
want
to
vote
every
three
months
on
on
on
the
core
units,
especially
if
they're
working
well.
So,
if
you
trust
them-
and
you
see
the
reports
and
everything's
going
smoothly,
you
don't
want
to
to
start
voting
on
these
things
so
yeah
as
you're
saying
david.
My
incident
is
by
annual,
so
every.
A
Yeah,
I
I
definitely
agree
I
100
agree.
I
think
that
quarterly
is
just
very
hard
to
keep
up
with
the
reporting
and
like
the
proposing
aspect,
it's
just
like
you.
You
have
to
devote
basically
the
first
two
weeks
in
the
last
two
weeks
of
each
quarter
to
just
making
sure
that
all
of
the
documentation
and
stuff
is
really
properly
done,
and
also
with
the
fact
that
there's
a
governance
cycle
that
requires
you
know
at
least
like
one
to
two
months
for
things
to
pass.
D
E
And
I
think
traditional
companies
do
it
annually
correct
they
usually
put
in
a
budget
for
the
whole
year,
so
usually
around
the
the
end
of
december
early
january
they're
scrambling
to
get
their
budgets
together
so
yeah.
Originally,
I
was
thinking,
maybe
six
months,
but
then
they
came
around
and
it's
like
just
one
year
makes
sense.
You
know
it's
just
something
that,
in
my
opinion,
is,
has
worked
more
traditionally.
So.
A
I
really
like
the
the
point
that
juan
makes
about
experience
and,
like
you
know,
core
units
that
have
been
around
for
a
while
and
have
proven
their
competency
versus,
like
somebody
a
little
newer
with
a
core
unit
that
might
not
be
as
like
fundamental
doing
something
shorter
term
like
a
six
month
or
quarterly
thing.
A
But
the
fact
that
this
framework
actually
accommodates
for
that
kind
of
flexibility
is
really
impressive.
B
Yes,
because
I
mean
flexibility
is
important
because
suppose
you
are
the
facilitator
of
core
unit
devoted
to
smart
contracts.
Okay,
you
have
a
contract
of
let's
say
six
months
or
one
year,
but
that
is
kind
of
frustrating
right
because
you're,
how
can
you
expand
your
business?
For
example,
you
would
like
to
hire
10
new
people
to
new
coders,
but
it
takes
some
time
to
you
know:
have
them,
learn
the
tools
and
the
the
the
maker
dial
code
and
everything,
so
they
will
become
productive
after
nine
months
right.
B
So
that
might
not
be
such
a
great
idea
if,
after
one
year,
the
governance
can
just
decide
to
shut
down
the
operation,
so
the
facilitator
is
in
a
difficult
situation
in
this
sense.
Do
I
risk
you
know,
investing
all
this
money
to
to
get
new
people,
and
then
this
band
they
will
group
or
not.
So
I
think
for
some
code
unit,
it
would
be
great
to
have
you
know
this
evaluation
every
three
months
for
some
career
unit.
B
We
need
to
be
more
of
a
long-term
investment
approach,
because
there
are
some
just
things
that
require
infrastructure,
long-term
planning,
long-term
investments,
and
we
cannot
just
every
six
months,
put
them
in
a
situation
where
they
could
go
home.
B
Basically,
so
we
have
to
to
plan
these
things
accordingly,
and
also
one
thing
I
think
is:
if
we
have
two
several
core
units
for
the
same
task
like
oracles,
I
think
it's
inevitable
that
this
thing
will
cost
more
than
a
traditional
business
in
the
same
way
that
bitcoin
costs
more
or
retiring
costs,
more
than
visa
right
doing
transaction
on
them.
So
there
are
benefits
that
will
come
from
this
decentralization,
so
we
will
reduce
dramatically
certain
types
of
costs,
but
not
all
of
them.
Some
of
some
of
them
will
rise
right.
B
So,
ultimately,
I
think
decentralization
brings
a
profit,
it's
an
optimal
solution,
but
not
in
all
aspects
right.
So
we
we
should
expect
in
fact,
to
spend
more
than
an
average
company
on
certain
things.
A
Especially
to
eliminate
risk
like
with
with
an
oracle's
team,
that's
failing
right,
you
know
having
that
redundancy
is
super
important.
C
I
did
have
a
question
along
those
lines.
I
was
wondering,
if
maybe
we
could
get
some
of
the
reflection
about
how
how
the
core
unit
model
really
allows
for
that
redundancy
because,
like
I
think
it's
pretty
easy
for
us
to
imagine
like
a
competition
scenario
right
where
one
group's
doing
articles
and
another
group
says
you
know
what
I
can
do
better
and
you
know
they
can
beat.
But
what
is
like
a
healthy
redundancy
look
like
in
the
dow
and
how
does
the
core
operating
unit
model
kind
of
facilitate.
A
In
my
opinion,
I
think
that
the
most
important
thing
is
having
like
a
level
of
transparency
around
documentation,
especially
for
any
core
units
that
deal
with
a
more
technical
side
of
the
protocol
being
able
to
really
stay
true
to
the
open
source
nature
of
the
protocol
and
and
the
open
source
nature
of
of
maker
dow.
A
It's
important
to
be
able
to
have
documentation
available
for
anybody
to
pick
up
and
go
where
somebody
left
might
have
left
off.
That's
one
aspect
of
it
in
my
opinion,
and
then
the
other
part,
which
is
just
an
observation
for
me,
is
that
it's
gonna
be
a
lot
like
you
know,
bidding
on
on
a
work
contract
like
you're
gonna
have
different
contractors
that
are
trying
to
get
the
same.
A
You
know
that
same
one
job,
and
so
I
think
the
historic
team
is
is
always
gonna
have
preference
unless
they're
really
failing
and
then
at
some
point
I
imagine
like
there
will
just
be
a
way
to
propose
like
a
minimum,
viable
core
unit
that
just
maybe
takes
one
thing
away
from
the
oracle's
team,
because
the
oracle's
team
deals
with
like
a
whole
array
of
different
different
responsibilities,
and
so,
let's
say
oracle
assessments
right
like
the
oracle
team
is
just
you
know
not
doing
as
many
as
it
should,
and
you
know
it's
just
really
lagging
behind.
A
Let's
say
a
new
oracle
team
comes
by
and
takes
that
responsibility
from
them.
It's
almost
like
yeah,
like
you
know,
our
team
lost
the
bid
for
that
part
of
our
budget.
You
know,
and
and
so
it
I.
I
really
like
the
that
dynamic
of
even
that,
creating
like
a
fire
under
people's
ass,
for
accountability
right
and
for
outstanding
competence
and
whatever
it
is.
Your
core
unit
is
doing.
E
Actually,
I
did
want
to
say
you
know
retaining
somebody
like
chris
mooney's,
switching
it
up
to
smart
contracts
and
that's
just
something
that
you
need
to
go
all
out
in
my
opinion,
right
because
he's
the
type
of
not
just
him
brian
kurt,
which
I
haven't
seen
in
a
while,
actually
kurt
berry
lolly,
I
mean
so
many
of
them
smart
contract
guys.
These
are
guys
that
other
protocols
can
easily
easily
swoop
up
because
they're,
just
so
talented
right.
E
E
You
know
me
personally,
I'm
always
going
to
put
my
best
foot
forward
as
an
mkr
token
holder
and
voter
and
governance
participant
and
look
out
after
those
people,
because
those
people
really
have
the
passion
for
the
project
the
same
way
that
all
of
us
here
have.
So
those
are
the
people
that
I
want
to
retain,
and
I
do
hope
that
we
do
get
more
of
those.
So
I
would
love
to
have
10
chris
moody's
and
20
kurt
barry's,
and
you
know
brian's
and
even
amy's
and
david's
and
juan.
So
it's
exciting.
A
Stuff
also,
it
might
be
that
a
core
unit
that
might
be
on
the
decline.
You
know
you
never
know
why
it
might
be
and
being
able
to
propose
like
a
duplicate
core
unit
from
out
of
the
team
or
basically
just
like
replacing
the
facilitator
with
somebody
else.
Having
that
kind
of
flexibility
is
also
important.
Also,
culturally,
like
being
able
to
be
okay
with
with
those
kinds
of
shifts,
is
important
so
because.
A
B
No,
I
I
agree
totally
and
I
think
I
made
a
comment
on
this
direction
on
the
application
of
the
smart
contract
core
unit,
so
they
didn't
ask
a
very
high
budget,
so
I
commented
that
please
ask
a
higher
budget
to
pay
people
to
duplicate
yourself.
So
I
think
this
perhaps
goes
into
the
rewards
sort
of
point
that
I
made
earlier.
B
So
we
should
promote
this
type
of
behavior,
so
one
of
the
achievement
of
the
core
unit,
besides
doing
good
job,
is
to
duplicate
the
competencies,
the
knowledge,
the
tools
and
duplicate
itself,
so
that
should
be
rewarded
heavily
and,
of
course,
we
might
check
what
it
means
to
have
a
nice
objectively,
independent
duplication,
but
that
should
be
a
core
objective,
because
duplication
redundancy
is
really
the
only
way
to
make
the
centralized
things
work
right.
So
all
the
core
units
should
be
incentivized
to
do
that,
I
think.
D
Regarding
the
budget,
something
that
I
wanted
to
add
that
maybe
wasn't
very
clear,
but
maybe
a
creative
way
of
using
budgets,
a
core
unit
could
actually
you
you
can
attach
more
than
one
budget
to
a
core
unit.
So,
potentially
you
could
say
hey.
We
want
to
hire
these
five
people
to
do
these
things,
and
you
could
also
say
we
also
want
this
other
budget
to
create
a.
I
don't
know
radio
show
with.
D
I
don't
know
with
famous
people
and
for
this
we
need
another
half
million,
so
potentially
governance
could
say
we
do
approve
the
budget
for
you
hiring
people,
but
this
other
one.
We
don't
so
it's
a
little
bit
of
asking
for
direction
for
your
core
unit
by
kind
of
splitting
up
the
different
budgets.
So
that's
another
yeah.
Another
way
of
using
this
framework
to
ask
for
feedback
kind
of.
A
We
have
about
five
minutes
left
on
the
call.
Is
there
any
like
absolutely
important
things
that
any
of
you
feel
we
should
definitely
talk
about
before
ending.
D
Maybe
resources
but
yeah.
If
you
go
to
forum.maker.com
you'll,
find
a
bunch
of
resources
there
post
explaining
what
this
mipset
is
all
about,
then
you
will
also
find
the
each
map
with
the
with
comments
below
and
questions
and
different
answers,
something
something
else.
There's
the
core
units
I
wish
existed,
that's
being
kind
of
like
a
brainstorming
section
of
the
forum
where,
where
people
say
what
they
would
like
to
see.
D
D
So
if
you
go
to
chat.maker.com,
which
is
called
core
units,
I
forgot
the
name,
but
if
you,
if
you
google,
for
core
unit
well,
not
google,
if
you,
if
you
look
within
the
the
chat
for
the
the
co-unit
channel,
you
have
the
you
have
help
so
there's
a
lot
of
people
helping
each
other
asking
questions
and
asking
for
reviews
like.
Can
you
please
review
this
document
we're
about
to
submit
this
a
proposal?
D
A
Yeah,
I'm
throwing
all
the
links
in
the
chat
for
for
anybody
who
wants
to
just
go
directly
in
there.
D
D
No,
I
was,
I
was
wondering
if
there's
anything
that
I'm
forgetting,
but
there
has
been
a
couple
of
calls
that
we
did
more
specifically
with
presentations,
so
you
could
check
those
potentially
where
more
people
asked
questions
about
this
and
then
yeah.
If
you
have
any
questions,
you
know
where
to
find
us
where
we're
in
the
forums.
A
Also,
this
month
is
almost
completely
dedicated
to
proposals
that
are
in
the
request
for
comment
phase.
There
are
like,
I
think,
over
20
of
them
and
of
those
20,
this
mipset
of
the
core
units,
which
consists
of
mip.
What
is
it
38,
39,
40
and
41.?
A
I
think
yeah,
so
so.
Those
four
mips
are
part
of
the
rfc
and
I
highly
recommend,
if
you're
interested
in
in
helping
shape
the
way
that
the
core
unit
frameworks
is
formally
proposed.
Definitely
look
through
those
mips
comment
on
any
anything
that
can
be
improved
from
the
style
of
the
things
that
are
written
to
the
way
that
this
entire
mipset
is
structured.
A
D
A
And
so
maybe
one
more
question
a
lot
for
the
last
minute
for
for
for
the
authors,
what's
the
timeline
that
you're
expecting
for
formal
submission.
D
So
we
I
think
we
would
like
to
have
it
submitted
in
the
next
cycle,
which
is
march.
Yes,
I
think
it's,
the
third
of
march,
can't
remember
the
exact
state
yeah
there's
a
lot
of
sub
proposals
that
already
want
to
go
in
with
the
the
mipset.
So
we
want
to
to
be
there
to
support
them.
A
Right
on
all
right,
thank
you,
everybody
who
was
on
the
call,
and
thank
you
everybody
who
watched.
I
hope
this
was
super
valuable
to
to
all
of
you
and
yeah.
A
This
whole
last
month
was
all
about
acclimating
to
this
idea
and
to
how
it's
going
to
work
practically
and-
and
it's
been
just
a
total
joy
from
my
perspective,
to
see
the
community
yeah
just
organize
around
this,
and
the
fact
that
we
already
have
three
core
units
proposing
alongside
this
framework
is
just
a
testament
to
the
fact
that
that
this
whole
idea
is,
is
a
really
great,
a
really
great
one.
So
cheers
to
you
guys
and-
and
thank
you
for
coming
on
the
call.