►
From YouTube: Governance and Risk Meeting #134
Description
## Introduction
* @LongForWisdom: Hosting, Introduction, Agenda.
* Daylight Savings
## Weekly Updates
* Governance - @Gov-Facilitators + Contributors
* Smart Contracts - @Smart-Contracts
* Oracles - @Oracles
* Risk - @Risk
* Real World Finance - @SebVentures
* Operational Support - @operational-support
* Community Development - @Anna
* MIPs - @MIP-Editors
## Procedural
* Monthly Governance Cycle Review - @Gov-Facilitators
## Discussions and General Q&A
Budget Simulation Tool
## Links
Website: https://makerdao.com
Twitter: https://twitter.com/makerdao
Forum: https://forum.makerdao.com/
Chat: https://chat.makerdao.com/home
Email: info@makerdao.com
Governance and Community Events Calendar:
https://calendar.google.com/calendar?cid=bWFrZXJkYW8uY29tXzNlZmhtMmdoaXBrc2VnbDAwOWt0bmlvbWRrQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20
A
Hello,
everybody
and
welcome
to
the
make
it
out
scientific
governance
and
risk
meeting
number
134
taking
place
on
thursday
march
25th
1700
at
utc.
My
name
is
long
for
wisdom.
I'm
the
government's
facilitator
at
maker
dao
right
now,
I'm
joined
by
host
of
mega
people
as
usual.
Seeing
participation
pick
up
a
little
bit
recently,
which
is
just
cool
to
see,
but
yeah
we've
got
a
we've
got
a
kind
of
agenda
to
get
through.
As
usual,
we've
got
our
regular
weekly
updates.
A
We've
got
some
kind
of
procedural
mips
stuff
to
get
through
it's
the
end
of
march,
so
we'll
have
like
a
kind
of
review
of
the
march
governance
cycle
and
then
we'll
kind
of
open
up
into
a
kind
of
more
more
general
qa
and
discussion
as
as
per
usual,
so
kind
of
usual
preamble
on
comments
like.
If
you
want
to
comment
or
interrupt,
please
please
feel
free.
We
like
it
when
people
get
involved.
If
we
end
up
spending
too
much
time
on
one
segment,
that's
fine.
A
A
Cool
so
I'll
do
a
quick
reminder
for
daylight
savings.
I
know
this
has
hit
most
people
already,
at
least
for
at
least
in
the
uk.
It
hasn't
hit
yet
so,
possibly
for
others.
So
be
aware
that
daylight
savings
time
is
approaching
and
may
affect
when
this
meeting
shows
up
in
your
time
zone
and
the
meeting
is
set
in
utc.
So
the
meeting
doesn't
move.
It's
though,
obviously
it
will,
if
your
time
zone
changes.
A
Let's
see,
that's
my
list
cool,
so
yeah,
so
we've
seen,
we've
had
two
executives.
In
the
last
week
we
had
the
regular
friday
weekly
executive
on
friday
and
we
had
the
monthly
maps
executive
on
monday.
So
both
of
those
have
passed
at
this
point,
which
is
which
is
good
to
see
so
australia's
executive
contained
some
increases
to
the
maximum
debt
ceiling
for
ether
and
wbtca.
A
A
We
passed,
some
technical
mips,
the
keg
term,
lending
module
liquidations,
2.0
lots
of
kind
of
big,
big
and
exciting
things,
and
we
passed
some
sort
of
sort
of
process,
guiding
guidance
mips
as
well
in
the
form
of
the
multi-sig
wallet
management
map
and
the
parameter
proposals.
Group,
sorry
parameter
proposal,
group
smith,
so
bring
us
to
polls.
A
So
this
week's
poll
is
also
finished
and
we
saw
that
let's
double
check
these,
so
we
had
a
poll
for
the
let's
see
for
e3
dust
which
got
left
left
accidentally
left
out
from
last
week,
so
that
poll
kind
of
ended
with
us
with
make
holders
agreeing
to
change
the
dust
feed
from
2000
to
15,
000.
and
so
higher
than
the
other
volt
types
and
they're
obviously
not
implemented.
Yet
not
the
executive.
A
So
if
all
goes
well
this
friday
and
the
executive
passes,
we
should
see
debt
ceilings
of
those
rise
soon,
so
that
kind
of
covers
the
governance
actions
that
happened.
I'm
just
going
to
give
a
brief
update
of
what
my
kind
of
core
units.
My
coin
has
been
doing.
We've
continued
working
on
project
compass,
you
guys,
are
continuing
to
take
the
lead
and
manage
that
process.
We've
seen
we've
seen
an
update
to
the
mips
portal.
A
A
A
B
B
Also,
regardless
of
the
rise
and
demand
die,
manages
to
keep
its
peg,
the
volume
weighted
average
price
is
at
1.002
dollars
for
this
week
onto
announcements.
All
97
initiatives
in
the
maker
dial
ecosystem,
including
community,
calls
grants
products
and
teams
are
now
collected
in
one
place.
Thanks
to
amy.
B
B
We
have
a
new
single
request
by
immio,
who
is
looking
to
gather
consensus
around
the
petition
for
a16z
to
get
involved
in
governance,
and,
last
but
not
least,
ultrashoopy
is
looking
for
consensus
on
raising
the
surplus
buffer
and
potentially
burning
some
mkr
from
fees
and
that
that's
it
from
me.
Thank
you
very
much.
C
A
D
Thanks
a
lot
so
yeah,
I
I'll
do
my
usual
preamble
and
on
a
sterling
connection,
and
so
I
might
freeze
for
like
five
to
ten
seconds
so
burping
if
you
could
keep
like
moving
just
so
I
I
know
if
I've
frozen
or
not
that'd
be
great
yeah.
So
I
just
a
reminder:
we
are
not
doing
collateral
onboarding
right
now,
so
the
normal
sort
of
collateral,
priority
sheet
work
or
collateral
assessments,
all
of
that
stuff
is,
is
on
hold.
D
While
we
work
on
liquidations,
2o
or
mip-45,
and
so
I'm
going
to
just
try
and
go
through
everything
else
that
we've
had
on
our
plate
this
week
before
I
get
to
the
mc45
stuff,
but
so
we've
been
working
with
centrifuge
on
mip
22
and
we've
finished
reviewing
the
manager.
I
think
I
mentioned
last
week
that
centrifuge
was
trying
to
to
take
their
sort
of
mip-22.
D
D
D
So
while
we
did
look
at
the
manager
and
we
have
every
confidence
in
their
team
and
the
code
looked
okay
to
us,
I
just
want
to
make
it
clear
that
the
smart
contracts
domain
team
can't
really
give
a
a
warranty
on
whether
or
not
that
code
is
working.
But
we've
discussed
this
with
them
and
they're
taking
responsibility
for
whatever,
whatever
loan
governance
decides
to
give
them
whatever
debt
ceiling
is
there?
D
So
the
next
steps
are
going
to
be
that
we're
going
to
rework
the
deploy
script
a
little
bit
for
mip
21,
so
that
it
can
deploy
more
generically
their
code
as
well
and
then
they've
got
to
construct
the
spell
that
is
basically
a
template
off
of
mip
21's
spell
and
they'll
do
a
bunch
of
like
rpc
or
simulation
tests.
As
as
a
result
of
that
and
then
probably
next
week,
we're
going
to
be
deploying
to
covant.
D
So
we're
going
to
review
all
of
that
code
next
week
and
then
fix
anything
that
we
find
and
then
deploy
to
covan,
hopefully
on
wednesday
and
yeah,
and
then
they'll
test
their
code
in
covan
and
in
theory
they
they
could
go.
I
guess
to
mainnet
at
any
point
after
that,
except
that
we
discussed
and
I'll
actually
maybe
come
back
to
that
on
the
liquidation
schedule.
D
So
moving
on
to
like
sort
of
miscellaneous
stuff,
there's
a
lot
of
like
improvements
on
spell
readability
and
also
we've
been
trying
to
make
the
like
ether
scan,
verify
a
little
bit
more
usable
and
that's
partly
for
governance,
but
actually
mostly
for
us.
It's
it's
becoming
even
difficult
for
us
to
like
validate
the
the
spell
on
chain,
and
so
we
want
to
you
know
we're
trying
to
use
the
api
to
like
break
that
up
and
make
it
easier
to
review.
D
But
then
we
could
cycle
back
and
finally
do
pax
g
once
we're
finished
that
work,
some
echidna
tests
for
layered
the
layer,
two
optimizes
or
sorry
optimism,
dye
bridge
we're
run
and
we've
got
a
auditors
engaged
for
the
sushi
join
adapter.
Abdk
is
going
to
be
taking
a
look
at
that
and
that's
like
the
crop
join.
D
There's
no
like
super
severe
bugs
there.
It's
mostly
just
us
trying
to
get
it
ready
to
probably
replace
the
oracles
that
are
there
and
then
also
you
know,
make
it
so
that
we
can
use
them
in
in
the
future.
Although
yeah
uniswap
v3
is
now
coming
out,
so
we'll
see
how
useful
those
are
going
to
be
for
for
a
while
right,
I
mean
yeah
anyway.
That's
that's
not
it
that's!
D
I
guess
maybe
not
totally
in
our
domain,
but
I'm
I'm
sure
people
have
been
talking
about
it
and
then
yeah
and
then
we
just
did
a
bunch
of
updates
in
kovan
for
pricing
and
whatnot.
So
that's
all
the
miscellaneous
work
and
for
mip
45,
which
is
liquidations2o
actually
can
I
can
you
give
me
screen
share
capability.
A
D
We're
seeing
that
there's
a
lot
of
like
just
minutiae
in
there,
like
lots
of
eyes
to
dot
t's
to
cross,
and
so
just
to
give
like
an
example
of
some
of
those
we've
got.
We
we've
got
like
a
pr
for
dust,
consistency
and
also
the
also
a
circuit
breaker
change.
That's
going
to
go
into
the
sort
of
main
code.
So
there's
like.
D
Let's
see
oh
yeah,
there's
a
two
prs
that
are
gonna
happen
there,
and
then
we
have
the
clipper
mom
that
we
talked
about
last
week.
So
we're
gonna
upgrade
the
clipper
mom
so
that
it
can
act
as
an
instant
access
module
to
circuit
break
the
auctions.
So
we've
had
that
work
and
then
just
a
bunch
of
like
little
tendrils
of
our
system.
We've
had
to
make
changes
to
the
oak
registry,
the
dss
exec
lib,
the
emergency
shutdown
module.
D
We've
got
dss
interfaces
in
there.
We
also
need
to
update
the
mip
45
dock,
so
we're
going
to
have
a
pr
that'll
go
out.
Mostly
that's
there's
not
like
a
big
substance
of
like
change
there.
It's
just
gonna,
be
like
you
know,
a
number
of
small
sort
of
things
from
the
auditors
and
some
clarifications
so
that
pr
will
happen.
Maybe
we
can
talk
to
governance
about
that,
I'm
not
entirely
sure.
That's
gonna
invalidate
mip
45,
because
my
45
is
just
approved.
D
This
is
more
like,
like
so
just
like
we're,
adding
like
the
audit
documents
and
stuff
like
that
to
it.
So
it
shouldn't.
I
don't
think
it
should
should
invalidate
mip
45,
but
I'm
maybe
biased
and
and
then
there's
a
lot
of
like
cross-team
coordination
tasks
as
well.
So
there's
there's
lots
of
like
us
reaching
out
to
other
teams,
and
so
let
me
actually
turn
my
video
off
and
I'm
gonna
share.
D
D
We
were
hoping
to
have
it
done
yesterday,
but,
as
I
mentioned
earlier,
there's
a
bunch
of
stuff
and
then
I've
slid
the
entire
set
of
the
timeline
over
by
like
a
week,
and-
and
so
you
can
kind
of
see
like
link-
is
now
scheduled
for
friday,
the
9th
which
would
be
the
first
deploy
there
right.
So
we've
got
yeah
we'll
do
the
bug
bounty
documentation,
update
link
will
go
out
on
the
9th
followed
by
wi-fi.
D
So
what
I
was
talking
about
with
centrifuge
is
that
we
won't
do
it
here,
but
mip
22
could
possibly
go
out
on
the
17th
or
on
like
the
what
30th
over
here
or
or
on
the
sixth
right.
So
again
we're
just
we're
going
to
we're
going
to
block
out
link
in
wbtc,
f
and,
let's
see
so
then
there's
some
stuff
from
like
blog
posts
and
whatnot
that
were
moved.
Another
sort
of
just
like
making
sure
keepers
are
ready.
D
We
slid
that,
although
maybe
they'll
be
ready
earlier,
because
they've
already
had
access
for
a
while
same
thing
with
uis,
we
did
get
the
final
set
of
risk
parameters
from
risk.
So
thank
you
guys
for
for
doing
that.
I
don't
know
if
anyone
saw
that
post,
but
you
should
check
in
the
forums
for
the
link
parameters
and
add
any
discussion
there
and
that
is
about
it.
Does
anyone
have
any
questions,
let's
just
say
about
anything
that
I've
brought
up
or
the
schedule.
While
I've
got
the
schedule
up.
D
Are
they
two
different
colors?
I
don't
know?
No,
I
don't.
I
was
gonna
feign
that
I
was
colorblind
yeah.
No,
I
I
I
I
think
we
I
I
think
we
started
like
some
of
these
were
supposed
to
be
like
critical
deadlines
or
something
but
we've
since
sort
of
lost.
I
think
any
meaning
there,
because
these
maybe
could
be
also
read
if
we're
talking
about
these,
but.
A
So
yeah,
I
guess
I
had
a
question
related
to
the
mip,
21
and
22
stuff,
so
I
can't
actually
stupidly
before,
but
it
would
be
great
to
have
like
kind
of
more
documentation
of
the
parameters
around
those
around
like
the
the
structure
and
the
setup
for
that
and
like
the
important
parameters
for
governance.
In
terms
of
I
forget
what
they're
called
now
but
like
there's
a
there's,
a
couple
of
newer
ones.
There's
a.
A
D
We
actually
have
to
set
the
price
of
the
token
that
we
create
for
them
based
on
the
debt
ceiling
that
we're
gonna,
give
them
right.
So
that
was
like
one
of
the
surprising
ones
that
maybe
needs
an
update.
I
will
make
a
note
of
that
because,
at
the
very
least
we
can
the
same
way
we're
updating,
mip
45.
We
should
update
map21
to
include
those.
A
We'll
ask
you
for
the
first
half
of
that,
but
maybe
it's
kind
of
not
critical,
maybe
just
want
to
make
sure
that
you're
yeah
that
we
have
kind
of
those
ready
for
when
we're
ready
to
push
the
map
22
stuff.
I
wouldn't
want
to
kind
of
delay
it
just
because
we
don't
have
to
write
down
anywhere
where
all
the
parameters
are
yeah
yeah.
D
Those
parameters
meet
my
intuition
of
of
what
I
think
should
be
set
and
so
yeah
I
don't
know
you
know
people
should
sort
of
review
that
it
was
like
a
lot
of
work
that
went
into
selecting
those
parameters
with
gauntlet,
modeling,
also
risk
zone
modeling
and
smart
contract
like
technical
risk
on
top
of
it.
So
it's
the
culmination
of
like
serious
like
months
worth
of
of
like
modeling
and
effort,
so.
A
Yeah
I
I
would
encourage
anyone
from
governance,
who
kind
of
has
kind
of
a
large
stake
in
the
system
to
to
give
it
a
readover
as
well.
Obviously,
we
kind
of
know
what
happened
to
last
time.
We
we
pushed
auction
parameters
and
they
turned
out
to
be
not
ideal,
so
we
kind
of
want
to
make
sure
that
we
don't
end
up
in
a
situation
like
that
again
so
yeah.
A
E
So
there's
there's
the
the
technical
piece
of
how
you
do
this
right,
which
is
you
need
to
have
a
instead
of
putting
your
liquidity
into
uniswap
v3
directly
right.
You
need
some
kind
of
middleman
kind
of
contracts,
right
that
will
deploy
a
a
kind
of
common
strategy
and
we'll
issue
people
a
a
token
and
and
that
middleman
contract
will
then
deploy
that
liquidity
into
uniswap
and
and
the
contract
can
even
you
know,
be
be
adjusted
right.
E
The
the
only
thing
that
matters
is
that
you
know
the
the
the
tokens
themselves
represent
kind
of
a
common
like
chunk
of
liquidity.
That's
that's
uniform!
So
that's
the
technical
piece
and-
and
that's
actually
not
that
bad,
it's
more
just
the
on
the
execution
side.
In
terms
of
like
who
does
this
right?
E
I
would
prefer
it
be
someone
like
swap
then
there's
kind
of
you
know
a
a
blessed
solution
right
that
we
know
is
secure
with
all
of
their
crazy
moon,
math
and-
and
it's
really
easy
for
for
people
to
like
build
and
integrate
around
when
there's
like
an
official
one.
What
I
actually
think
is
going
to
happen
is
that
there's
too
much
competition
right
now
to
be
the
the
lender
against
lp
tokens
right.
You
know
between
maker
ave
and
you
know
alpha
hamora
and
I'm
sure
a
couple.
E
Others
are
looking
at
this
as
well,
probably
even
compound
that
everyone
rushes
to
to
make
their
own
and
that
can
work,
but
it
kind
of
sucks,
because
now
you,
you
start
fragmenting
this,
you
start
fragmenting
this,
this
liquidity
right.
So,
for
example,
if
you
know
alpha
hamora
has
you
know
their
eth
range,
you
know
between
a
thousand
and
two
thousand
right
then
and
ave
has
that
one,
and
we
have
that
one
right,
all
those
tokens
should
technically
be.
You
know
the
same
token.
E
E
I
guess
like
how
a
developer
wants
to
view
the
world
which
is
you
know.
We
have
common
standards
that
we
conform
to,
and
it
just
makes
things
much
easier
from
a
from
a
liquidity
point
of
view
when
you're
trying
to
liquidate
this
stuff,
but
also
from
like
an
integration
point
of
view.
Right,
you
don't
have
to
integrate
every
single
standard.
E
You
can
just
integrate
one,
so
I'm
I'm
wondering
if,
like
we
can
just
reach
out
to
the
the
you
know
the
aves
and
the
you
know
the
uniswaps
and
the
whatevers
of
the
world
and
kind
of
come
to
an
agreement
of
like
this
is
what
we're
gonna
do.
Yeah
should
be
exactly
like
that.
Xkcd
comic
right.
We
have
you
know
x,
number
of
standards,
that's
ridiculous.
We
should
make
one
that
unifies
all
of
them.
You
know,
and
now
the
new
lay
of
the
land
is.
E
You
have
a
a
bunch
of
competing
standards
right
so
yeah,
so
I'm
trying
to
talk
with
ave-
and
you
know,
swap
and
and
those
guys
to
see
if
we
can,
you
know
reach
like
a
gentleman's
agreement
on
you
know
it
doesn't
really
matter
who
builds
it.
But
can
we
just
agree
on
like
an
implementation,
but
game
theory
says
it
says?
No,
so
we'll
we'll
see
what
we'll
see
what
happens
there.
E
The
other
thing
that
I've
been
working
on
really
is
the
the
oracle's
core
unit
yeah.
I
I
don't
want
to
give
out
too
many
details
yet,
but
it's
a
it's
a
lot
of
work.
I
in
terms
of
like
the
date
that
I'm
targeting
I'm
targeting
to
submit
that
may
1st,
so
that
would
give
governance
like
a
month
to
review
it
and
discuss
and
give
feedback
before
it
would
go
in
the
june
mip
cycle
right
and
then
would
be
voted
on
end
of
june.
A
A
A
F
We
should
hopefully
have
this
soon
marcus
working
on
that
yeah.
So
that's
that's
the
answer
on
the
other
stuff.
So,
as
mentioned,
we
released
a
proposal
for
link
a
liquidations.
2.0
parameters
yesterday
suggest
to
read
it
provide
feedback
before
it
goes
to
ancient
paul.
I
think
I
think
that's
happening
week
after
next.
If
we
are
having
official
launch
on
ninth
at
as
christian
but
yeah
it's
up
to
smart
contracts,
really
gauntlet
also
published
the
report.
I
made
a
few
comments
on
their
proposal
as
well.
F
Just
according
to
the
timeline
question,
as
mentioned
already,
the
parameters
won't
hugely
differ
among
wall
types,
apart
from
one
parameter,
which
is
called
ilk
hole,
so
this
parameter
limits
the
amount
of
pending
liquidations
per
wall
type,
so
it's
similar
as
box
parameter
under
current
implementation,
but
this
one
is
limits
this
one
limits.
Specifically,
you
know
wall
type
pending
lipidations,
and
this
helps
us
with
auction
to
limit
auction
throughput
per
collateral,
and
we
also
made
a
few
new
tools
to
measure
some
of
the
risk
metrics.
F
One
of
them
being
is
on-chain
slippage
for
collateral
assets
that
are
held
at
maker,
and
this
actually
helped
us
with
addressing
one
of
the
main
parameters
for
liquidations
2.0,
which
is
this
auction's
throughput.
So
this
parameter
called
alcohol,
but
it
also
helps
us
when
we
have
discussions
about
debt
ceilings,
risk
premiums
and
such
so
this.
This
is
still
in
beta
work
in
progress.
I'll
share
the
link
here
in
the
chat
so
yeah.
I
suggest
to
take
a
look
and
and
provide
feedback.
F
We
expect
more
to
to
list
more
metrics
in
next
few
weeks
and
then
the
ultimate
plan
is
to
have
a
live,
valued
risk
metric
calculated
for
the
whole
maker
portfolio,
and
this
way
the
community
or
any
other
potential
risk.
Analysts
are
able
to
observe
maker,
dao
portfolio
risk
in
real
time
and
then
observe
trends,
and
this
again
also
helps
us
with
dev
ceilings,
risk
premiums
or
even
surplus
buffer
debates,
so
other
than
than
working
on
these
tools,
making
additional
proposals
for
liquidations
2.0
parameters.
A
So
the
plan
from
governance
against
point
of
view
to
be
would
be
to
vote
on
the
parameters
the
monday
kind
of
before
those
that
kind
of
target,
so
we'll
be
targeting
the
fifth.
This
kind
of
gives
us
time
to
do,
to
governance
time
to
do
kind
of
documentation.
The
parameters
which
we've
been
working
on
and
obviously
it
kind
of
leads
time
for
kind
of
comments
and
stuff
in
the
forum
as
well.
A
H
H
So
on
other
news,
we
had
a
coordinate
presentation
last
friday,
that
is
on
youtube,
discussing
what
is
world
finance
and
all
the
stuff.
We
made
some
progress
on
the
analytic
front.
So,
as
I
said
last
week,
the
financial
statement
of
makeup
dao
that
I
made
on
gene
analytics,
is
no
longer
working
because
it
no
longer
supports
a
pivot
table
presentation.
H
I
talk
to
them
and
they
will
remake
it
possible
in
the
near
future
or
the
future.
They
don't
know
when
I
didn't
try
to
bribe
them,
and
I
have
some
meetings
with
a
lot
of
people
from
the
foundations
that
are
working
on
vulcan
eyes
and
other
other
data
stuff,
maybe
to
take
some
some
expertise.
They
have
and
maybe
work
on
a
more
robust
solution
and
not
depending
on
the
third
party
and
lastly,
last
item.
H
I've
made
a
budget
dashboard
that
I
published
on
the
forum
just
just
before
the
meeting
that
presents.
This
is
a
simulator
where
you
can
add
more
car
units
to
see
what
happens.
If
you
increase,
some
targets
increases
die
in
circulation,
increase
leverage
ratio
that
you
want
to
target
or
other
stuff.
How
much
mkr
token
you
want
to
give
to
all
the
teams
and
what
is
the
split
between
the
teams?
Because,
obviously
that's
a
complex
question
as
well.
H
A
I
I
We
had
done
three
since
our
last
call
of
these
launch
pod
sessions
with
core
units,
so
smart
contracts,
real
world
finance
and
content
production,
which
is
what
we
did
yesterday.
I
believe
so
all
three
are
now
up
the
recording's
up
and
you
can
watch
them
on
youtube,
as
well
as
accountable,
came
back
for
the
community,
call
that
that
david
has
run
so
you
can
watch
that
as
well,
where
they
kind
of
talk
about
their
different
services.
I
One
of
them
is
this
autonom,
autonomous
and
otoco.io,
which
is
around
if
a
different
kind
of
way,
if
you're
trying
to
pay
your
contributors,
that's
another
core
unit
tool,
if
you're
looking
to
some
some
options
for
your
core
unit
and
then
right
after
is
the
very,
very
hotly
debated
framing
a
framework
for
mkrs
compensations
call.
So
this
is
where
we'll
have
the
discussions
around
mkr
and
all
kind
of
piled
into
one,
so
bring
really
great
discourse.
Great
questions.
I
Try
not
to
bring
pitchforks
instead
try
to
bring
some
intellectual,
stimulating
questions
and
energy
instead,
and
but
it
is
kind
of
a
debate
around
kind
of
different
perspectives,
because
we
do
really
want
to
see
that
in
terms
of
the
core
units
and
development,
we
do
have
quite
a
few
now.
We
today
kathleen
just
posted
the
strategic
marcom's
core
unit,
so
you
might
want
to
take
a
look
at
that
as
well.
I
There
are
some
really
interesting
conversations.
As
we
said,
there
is
the
first
one
where
I
kind
of
just
summarize
all
the
topics
that
are
happening
in
within
the
smart
contracts
thread
and
around
incentives,
budgets,
estimates
and
so
on,
and
then
juan
just
kind
of
re-like
proposed
and
framed
a
great
way
to
kind
of
talk
about
mkr,
specifically
and
so
definitely
check
that
out.
I
A
lot
of
the
conversations
in
that
thread
are
what
we
kind
of
want
to
talk
about
in
the
call
that's
happening
wednesday,
so
please
come
as
well
and
he
also
posted
kind
of
a
vital
functions
not
covered
by
current
core
units.
I
think
that's
a
really
important
one
as
we're
developing
kind
of
from
the
bottom
up.
I
There
might
be
things
that
there
might
be
critical
like
responsibilities
or
are
kind
of
sort
of
functions
that
we
might
not
be
able
to
see
right
now,
but
in
the
transition
after
the
solution,
maybe
are
missing
so
then
we,
I
did
kind
of
post,
also
a
core
unit's
feedback.
If
you
have
just
general
feedback
around
the
framework
of
how
core
units
are
being
developed
or
or
anything
like
that,
feel
free
to
leave
your
thoughts
and
comments
there.
I
know
those
are.
I
So
one
of
this
thing,
one
of
the
reasons
this
was
done
is
people
who
are
not
ready
to
like
jump
straight
into
a
mip,
might
want
to
kind
of
go
run
some
proposals.
If
you
have
an
idea,
you
want
something
to
happen,
but
maybe
you're
not
the
person
that
want
to
run
it.
So
you
might
just
propose
like
hey.
Can
we
get
some
call
for
proposals
around
this,
and
so
one
of
the
first
things
we
did?
I
Is
community
development
just
proposed
one
for
grants,
so
anybody
who's
interested
in
potentially
running
a
grand
core
unit,
just
exploring
some
ideas
around
what
grants
large
or
small
could
happen
inside
the
dow.
You
can
go
ahead
and
propose
there's
it's
a
very
kind
of
commit
less
way,
you're
just
kind
of
proposing
idea.
If
you
want
to
further
pursue
it
into
a
core
unit.
You
totally
can
this
also
gives
us
some
great
feedback
points
for
just
kind
of
seeing
different
proposals.
I
Then
we
have
kind
of
the
summary
of
these
97
initiatives
from
the
maker
dao
community.
I
saw
some
great
feedback
and
kind
of
iterated
on
it.
It
is
a
v1
resource.
So
that's
why
it's
on
notion.
It's
just
to
get
the
information
out
there.
If
you
want
to
drive
it
or
you
see
that
there's
like
a
different
way,
we
can
do
this.
Please
dummy
and
reach
out.
I
That's
it
for
the
operational
support
side,
but
I
did
want
to
share.
One
thing
was
I:
I
just
got
off
the
call
with
this
like
senior
in
high
school,
and
she
just
said
all
her
and
her
friends
talk
about
as
maker
dao
and
like
the
power
it
has
as
like
of
economics
in
her
ap
class,
which
is
like
so
crazy
and
she's
really
also
was
like
wow
there's
a
lot
of
impactful
things
that
I
can
do
so.
Keep
that
in
mind.
I
A
C
C
And
it
goes
into
details
about
that
announcement
and
then,
as
amy
mentioned,
we
have
this
resource
for
the
all.
The
initiatives
that
are
going
on
in
community
development
and
a
lot
of
what
we've
been
working
on
is
working
with
individuals
and
small
groups
joining
some
of
the
the
projects
in
community
in
the
core
community
development
team,
working
on
evaluating
different
projects
that
are
in
the
pipeline
and
the
different
deliverables
that
are
still
being
worked
on
in
community
development
by
individuals
and
small
teams.
A
J
J
Some
highlights
from
this
month's
accepted
proposals,
as
long
mentioned
in
the
governance
and
risk
channel.
Yesterday
we
have
liquidations
2.0,
a
bunch
of
new
core
unit,
onboarding
and
their
budgets
for
risk,
real
finance
and
governance
and
payment
streaming
via
the
keg,
as
well
as
long
term
lending
so
fixed
term
loans,
which
is
really
awesome.
J
So
next
week's
activity
it's
a
gap
week.
So
that's
from
march
29th
to
the
second
of
april,
so
there's
no
polls
or
votes
can
be
happening
related
to
a
governance
cycle
and
just
for
awareness,
april's
governance
cycle
will
begin
on
april
5th
and
that
formal
submission
period
for
proposals
will
be
beginning
on
april
5th
and
end
at
the
end
of
day
on
on
the
7th.
J
So
then,
next
week's
governance
risk
call
there's
not
going
to
be
any
direct
mip
updates
related
to
a
cycle.
But
we
can
use
this
to
talk
about
the
upcoming
cycle.
Any
formal
submission
questions
around
preparation,
and
maybe
if
we
have
time
we
can
get
some
of
the
authors
to
speak
about
the
proposals.
J
So
don't
forget
to
vote
on
those
and
then,
in
terms
of
the
newly
submitted
proposals
to
rfc.
As
previously
mentioned
on
this
call,
there
is
a
new
core
unit
proposed
by
kathleen
for
strategic
mark
homs,
so
definitely
check
that
out.
If
you
have
the
time
and
from
the
past
week
or
so,
we
had
the
other
three
core
units
proposed
for
marketing
the
maker
dial
shop,
as
well
as
the
growth
core
unit.
J
So
there
are
approximately
30
proposals
in
rfc
right
now.
Around
half
of
them
are
eligible
for
inclusion
in
maximum's
governance
cycle.
I
didn't
include
them
in
the
presentation
today
because
it's
it's
quite
a
long
list,
but
I
will
be
putting
it
up
on
the
forums
right
after
this,
so
you
can
take
a
look
at
what's
eligible
and
and
what
else
is
coming
in
the
next
couple
months
but
yeah?
That's
it
for
my
update
today.
A
Perfect
thanks
charles
I
kind
of
do
the
the
kind
of
monthly
government
cycle
review
from
from
kind
of
governance
perspective.
So
obviously
it
was
pretty
successful.
In
general,
like
we
passed
everything
we
wanted
to
pass,
we
saw
that
the
kind
of
combined
mixed
bundle
poll
didn't
see
a
lot
of
participation
like
11
11,
12,
000
maker
and
but
some
of
the
inclusion
polls
saw
kind
of
a
lot
of
kind
of
a
lot
of
a
lot
of
participation,
which
was
good
some
more
than
others.
A
I
guess
they
need
to
or
guess
they
don't
feel
strongly
about
so
kind
of
hard
to
draw
conclusions
from
that
right
like
it's.
I
don't
think
the
numbers
were
massively
worse
than
they've
been
previously
but
yeah.
It's
kind
of
interesting
how
it
varies
over
the
various
inclusion
polls
in
the
various
stages.
A
A
G
Yeah,
so
I
wanted
to
bring
something
up,
so
I
noticed
like
in
this
month's
monthly
executive
spell.
There
was
kind
of
like
it's
kind
of
getting
close
to
the
expiry
date
for
those
who
don't
know
in
the
monthly
spell
there's
four
days
before
the
spell
will
deactivate
itself
and
can't
be
passed
anymore.
So
we
have
sort
of
a
tight
time
frame
with
that
and
just
sort
of
thinking
about
like
in
the
future.
It
passed
this
month
but
like
what?
G
What
if,
in
these
four
days,
sort
of
we
have
a
whale
who's
away
or
something
like
that,
just
some
like
sort
of
circumstances
of
voter
apathy
or
whatever,
and
suddenly
we
don't
have
a
monthly
executive
pass
and
I'm
kind
of
concerned
about
like
the
stage
we're
at
in
comparison
with
sort
of
the
triple
voting
to
get
things
through.
I
just
I
think
it
might
be
a
little
bit
conservative
for
how
fast
we
need
to
move
so
like.
G
G
J
I
definitely
agree
that
it
could
result
in
some
problems
with
that
four
day
limit,
and
earlier
this
week
on
the
governance
domain
call
we
had
spoken
about
potentially
coming
up
with
a
new
way
to
model
the
mep3
aka
the
governance
cycle
and
make
it
more
flexible
for
that.
Like
future
approach,
so
I
mean
I
would
suggest,
maybe
we
could
have
an
open
call
like
on
the
governance
ones
weekly
to
chat
about
potential
improvements
to
the
governance
cycle,
but
I
definitely
want
to
hear
people's
opinions
on
suspending
it
in
the
interim.
A
No,
I
was
just
gonna
say
to
sort
of
echo
sam's
points
really
like,
especially
with
relation
to
the
the
final
executive
and
kind
of
how
that
can
sometimes
suffer
from
like
voter
empathy.
So
obviously
we
have
kind
of
weekly
executives
every
friday
and
the
kind
of
general
consensus
is
that
once
a
week,
it's
kind
of
the
it's
not
the
best.
It's
not
the
best
we
can
do,
but
it's
kind
of
pushing
more
than
one
a
week.
It
becomes
risky
just
in
terms
of
participation
and
the
amount
of
mkr
on
the
hat
dropping.
A
So
we've
kind
of
always
been
aware
that
it's
kind
of
not
ideal
to
have,
like
you
know,
kind
of
three
and,
like
a
you,
know,
sort
of
ten
day
period
whatever
it
is.
That
happens
at
the
end
of
each
month,
and
we've
definitely
seen
in
the
past
that
it's
kind
of
come
down
to
the
wire
a
couple
of
times
before,
with
the
four
day
expiry
like
this,
this
cycle
actually
ended
up
being
all
right,
but
like
in
previous
cycles,
it's
kind
of
been
a
lot
more
close,
so
yeah.
A
It's
definitely
something
we
maybe
should
consider
adjusting.
So,
to
briefly
speak
to
the
kind
of
three
poles
thing,
the
main
reason
we
have
like
the
threes.
The
set
of
three
is
because
it's
mainly
because
we
have
the
executive
at
the
end
like
if
we
so,
for
example,
the
second
bundle
poll
is
basically
only
there
because
we
have
the
executive.
A
A
The
kind
of
downside
to
losing
the
executive
is
that
currently,
the
mips
are
kind
of
hashed
and
stored
on
the
blockchain
in
that
spell,
which
is
kind
of
meant,
to
be
kind
of
the
immutable
record
of
what
make
holders
have
voted
for
in
case
there's
like
kind
of
confusion
or
contention
later
over
what
was
agreed,
and
so
that's
kind
of
the
trade-off
that
we
lose
that.
But,
to
be
honest,
we
hash
like
a
lot
of
things.
We
hash
like
the
polls
and
we
hash
like
the
executives.
A
A
J
In
in
addition
to
that,
so
with
the
inclusion
polls,
it
kind
of
individually
filters
out
the
individual
proposals
and
then
the
governance
poll.
Is
that
bundled
thing
where
everyone
kind
of
agrees
on
these?
So
if
you
were
to
take
out
the
executive
that
allows
the
domain
teams
to
kind
of
take
those
proposals,
that
would
need
an
implementation
later
and
kind
of
take
them
on
a
one
by
one
basis
or
you
could
have
like
bundle
them
in
the
future
if
they
are
a
technical
proposal
that
requires
like
an
on-chain
action
but
yeah.
A
Yes,
so
kind
of
as
child
seriously.
We
can
discuss
this
a
little
bit
last
week
because
sam
kind
of
reached
out
to
me
what's
worse,
privately
as
well,
so
there's
a
couple
of
ideas
we
have
for
how
we
could
adjust
things,
I'm
less
keen
on
kind
of
suspending
it
and
more
leaning
towards
just
kind
of
changing
it,
because
I
think
suspensions
get
a
little
bit
weird
right
and
you
suspend
things.
A
A
G
A
Yeah
so
a
couple
of
people
mentioning
like
kind
of
replicity
and
things
as
well,
I
kind
of
want
to
avoid
making
the
multi-cycle
like
faster,
because
that
kind
of
we
kind
of
already
have
governance
processes
that
are
faster.
If
we
do
need
to
do
things
more
quickly,
so
I
think
kind
of
making
them
the
cycle.
Shorter,
isn't
necessarily
a
good
idea,
because
we
kind
of
already
have
tools
that
don't
manage
the
shorter
turnaround
but
yeah.
I
completely
agree
with
the
points
you
know.
C
C
A
Yeah
I
mean
it's
also
like
well
a
few
hours
of
work
for
smart
contracts,
maybe
more
than
a
few
hours
like
a
few
hours
from
for
me.
A
few
minutes
so
we'll
be
able
to
review
right
in
the
kids,
yeah
so
yeah.
I
said
we'll
consider
the
next
week
and
maybe
kind
of
going
up
to
give
an
update
in
next
week's
going
to
school.
A
A
All
right,
no
one's
picking
up,
so,
let's
maybe
move
on.
I
guess
this
is
the
end
of
the
official
agenda,
so
there's
nothing
to
really
move
on
to
so
yeah.
I
guess
that
kind
of
opens
the
kind
of
qa
discussion
portion
of
the
call
who
knows,
questions
or
or
kind
of
comments
on
any
of
the
things
we've
discussed
any
other
things
that
they're
interested
in
talking
about
to
relate
to
maker.
C
H
So
do
you
see
my
screen
yep
yeah?
So
sadly
I
just
put
back
the
m
car
right,
but
we
will
discuss
that
if
you
want,
because
I
remove
them
to
not
start
any
discussion.
So
this
is
just
a
model.
It's
all
the
numbers
are
fake,
so
what
you
should
do,
if
you
want
to
play
with
it,
is
to
go
to
file
and
make
make
a
copy.
H
H
It
just
has.
Does
that
give
me
the
good
numbers
to
make
some
tests
and
see
that
all
the
colors
are
okay,
mk
outstanding
target
robert
rishowitz
for
to
understanding
what
is
the
target
we
want
for
the
surplus
buffer,
because
here
we
have
the
die
end
of
the
period,
so
the
forecast
of
dies
that
will
be
outstanding
at
the
end
of
the
year
or
a
bit
later.
H
If
you
want
so,
for
instance,
in
the
budget,
we
can
forecast
that
we
want
to
have
five
billion
at
the
end
of
the
year,
but
in
the
act
in
the
actual
scenario,
is
what,
if
what
we
you
have
in
the
budget
is
not
the
good
elements.
So
what
happens
if
die
at
the
end
of
the
period
is
not
5
billion
but
10
billion?
What?
If
the
price
of
income
token
is
not
2
thousand,
but
four
hundred
four
thousand
and
stuff
like
that,
you
can
change
the
price
of
gas,
but
that's
not
super
event.
H
H
I
made
it
up,
it's
only
a
formula.
I
say
that
oracle
will
spend
5
million
this
year,
but
you
can
disagree
and
put
something
else.
It's
not
the
most
super
important
parameters.
Well,
maybe
for
our
qualities,
because
it's
a
big
big
budget
for
gas,
then
you
have
the
anchor
that
you
want
to
allocate
to
people
and
you
can
change
it
here
to
whatever
number
you
want.
The
actual
number
is
not
important
you
can.
H
H
So
you
start
as
a
at
17
million,
and
you
try
to
achieve
the
target
position
which
is
more
or
less
die
at
the
end
of
period
times.
The
target
reversal
issue
and
you
can
see
if
you
reach
it
at
the
end
of
payload.
If
you
don't,
you
might
want
to
say
that
you
don't
need
one
percent
of
dye
as
a
surprise
buffer,
but
only
0.5,
and
then
it
gives
you
a
different,
a
different
perspective.
H
H
A
J
A
A
Lucas
from
centrifuge
in
a
little
while,
I
guess,
with
the
progress
we're
making
on
myth,
22
and
there's
not
fusion
assets
like
I
guess,
but
yeah,
I'm
hoping
that
they're
feeling
better
about
how
things
are
going
now
previously
yeah,
I
see
I
saw
I
saw
there.
I
thought
I
saw
it
earlier
as
well.
I
think
they
have
moved
on
now.
This
one.