►
From YouTube: Governance and Risk | Ep. 173
Description
Agenda:
Introduction -
@GovAlpha-Core-Unit : Hosting, Introduction, Agenda.
@gov-comms-core-unit : Slides
Governance Round-Up -
@LongForWisdom Poll + Executive Status
@blimpa - MIPs Update
@Artem_Gordon Forum at a Glance
Selected Presentations -
2021 Governance Review
Where did we start?
What has been accomplished?
Where are we going?
What are the focuses for 2022?
Deco DSSGate -
How’s Deco doing?
What is DSSGate?
What governance parameters will governance need to manage in the future?
Disclaimer:
The views and opinions expressed in these public calls are those of the hosts and guests involved and do not reflect the official policy or position of MakerDAO or any of its contributors, Core Units, or affiliates.
A
Hello,
everyone
and
welcome
to
the
mecca,
dao
scientific
governance,
meeting
number
173
taking
place
on
january,
the
6th
2022
now
our
first
meeting
of
the
new
year.
I
hope
everyone
enjoyed
their
time
off
if
they
well.
Hopefully,
everyone
managed
to
take
some
and
yeah,
hopefully,
everyone's
excited
and
back
and
ready
to
get
back
into
maker
I'll.
Do
the
usual
preamble,
yeah
we'd
like
to
hear
from
people
in
this
meeting
so
feel
free
to
comment
or
ask
questions.
A
A
I
believe
we're
going
to
look
back
at
2021
and
then
take
a
brief
look
ahead
to
2022
and
we
also
have
a
presentation
from
deco
and
talking
about
a
little
bit
on
what
they've
been
doing
is
the
core
unit
and,
I
believe,
talking
about
dss
gates,
which
I
think
is
one
of
the
important
small
contracts
with
relation
to
the
fixed
rate
stuff
that
they're
working
on
so
yeah.
Let's
move
on.
A
A
I
know
what
some
of
those
are,
but
I'm
sure
you
can
find
out
what
they
are
on
the
forum.
If
you
are
interested,
we
have
a
couple
of
mips
certification
polls
as
well,
and
pablo
will
go
over
those
in
just
a
moment
and
then
I
think
two
signal
request
polls
for
prioritizing
the
compound
d3m
and
raising
the
emergency
shutdown
threshold.
A
Let's
look
out
for
all
those
on
monday,
so
also
no
executive
for
a
result.
This
week,
I
think
we
only
had
one
one
item
in
which
was
delegate
comp.
So
given
that
everyone's
kind
of
blowing
off
the
cobwebs
a
little
bit,
I
think
we're
going
to
push
that
and
in
combination,
because
there's
not
much
to
really
do
this
week,
so
we'll
have
the
first
one
of
those
next
week
on
it's
friday,
all
right.
That
brings
us
to
your
mips
updates.
B
B
Sorry
and
we've
had
12
formulas
mentioned.
So
let's
do
a
quick
review
of
them.
We've
had
three
mips
supposed
to
support
those
whose
enemy
family
submitted.
We've
had
that
maybe
62
collateral
affording
process
by
gfx
labs.
One
of
our
recognized
delegates,
mip
63
maker
keeper
network
by
hexanot
from
vertical
engineering
and
the
mip
64
of
the
doc
mounted
program
for
microdollar
critical
infrastructure
by
traveling
for
its
unique
possibilities,
oriented
facilitator.
B
B
And
we
have
our
two
new
car
limits
being
proposed.
One
of
them
is
strategic
finance
whose
mission
is
to
provide
financial
reporting
and
analysis
further
down
with
mike
phillips,
also
known
as
ice.
I'm
never
sure
if
I'm
pronouncing
that,
currently
as
it's
fascinating
better,
we
also
have
a
tech
ops
whose
mission
is
to
provide
technical
support
service
to
down
with
a
dimitro
separation
in
simon
of
us
facilitators.
B
We
also
have
the
images
proposals
for
the
removal
of
content,
production,
facilitators,
seth
goldberg,
and
this
coordinates
budget,
and
we
have
a
range
proposal
to
onboard
rebelo
as
real
world
finance.
Facilitator
and
roon
had
also
posted
a
proposal
to
afford
the
current
the
current
facilitator
for
the
guaranteed
self-esteem.
B
However,
seth
has
publicly
declared
that
he
will
be
stepping
down
from
the
road
voluntarily
on
january
25th,
so
this
proposal
has
been
marked
as
ruth
bond,
so
these
proposals
we
spoof
just
for
you.
I
don't
think
anything.
I
will
have
the
ratification
polls
going
live
on
monday
10,
if
you're
thinking
of
having
a
yet
composting
proposal
entering
for
the
experimental
cycle,
you
still
have
six
days
until
january
january,
12th
and
yeah.
B
A
C
Yep,
hey
everyone
happy
new
year,
happy
2022.,
welcome
to
the
forum
at
a
glance
this
time
actually
covering
for
the
last
couple
of
weeks
because
of
the
holidays
so
covering
december
16
to
january
6th,
on
the
forums
and
we'll
begin
with
the
announcements.
So,
first
up
matthew,
rabinowitz
published
a
comprehensive
four-part
four-part
update
on
the
future
and
roadmap
of
success
and
the
community.
They
utilize
walk
the
crawl,
walk
and
run
approach
and
announce
that
it's
time
to
transition
to
walking
in
order
to
help
develop
appropriate
objectives
for
2022.
C
The
post
begins
looking
forward
into
the
far
future
of
what
tao
and
defy
construct
may
look
like
where
we
are
headed
as
the
community,
from
both
six
s's
and
maker
da
dao's
perspective,
and
as
then,
we
reel
back
into
the
present
for
2022
matthew.
Rabinowitz
further
defines
the
agenda
for
successes
roadmap
which
covers
their
intentions,
their
strategy
objectives
for
growth
and
scaling
their
mission,
clarity
and
quantifiable
portfolio
targets.
C
Next
up,
govalfa
publishes
december's
delegate
compensation
for
our
nine
recognized
delegates.
The
total
payout
for
december
is
forty.
Eight
thousand
two
hundred
and
ninety
die
compared
to
november's
payout
of
thirty
five
thousand
eight
hundred
thirty
four
die.
This
leads
to
an
annualized
production
projection
of
about
half
a
million
die
which
does
require
more
months
of
data
to
confirm
and
moving
on
to
our
discussions.
There's
only
two
discussions
that
I
put
up
for
this
post.
C
First
up
andrew
hall,
a
political
economy,
professor
at
stanford,
who
studies
governance
and
solutions
shares
his
team's
research
driven
insights
for
maker
governance.
The
discussion
presents
three
central:
dow
governance
challenges,
aligning
incentives
with
stakeholders,
increasing
mkr
participation,
improving
the
delivery
of
information
and
expertise,
and
he
finishes
off
with
potential
next
steps,
and
what
we
can
do,
andrew
hall
is
seeking
community
feedback
feedback
to
help
improve
and
initiate
this
project.
C
Next
up,
el
progresso
continues
to
help
rock
the
d5
chasm
by
publishing
three
more
parts
to
the
topic.
He
talks
about
complacency,
risks
and
conquering
l2s
through
mergers
and
acquisitions
rocking
the
d5
chasm
number
three
asks
whether
defy
kpi
goals
are
possible,
and
what
can
we
do
if
dao
airdropped
make
a
breaker
for
further
decentralization
decentralization?
C
Moving
on
to
our
active
signal
requests,
we
have
the
maple
protocol
in
consultation
with
growth
core
unit
and
real
world
finance
signaling
to
onboard
a
d3m
for
the
creation
of
a
maple
dye
pool
lucas
asks
the
community
whether
makers
should
onboard
a
maple
finance
d3m.
His
post
provides
an
overview
of
the
proposal's
pros
cons
and
risk
mitigation.
C
Next,
up
as
loss
funds
continue
to
become
a
recurring
issue
for
dye
users
lost.
Some
dye
presents
a
case
where
a
user
accidentally
called
the
burn
function
on
daiso
on
optimism,
burning
10
million
die.
He
asks
the
community
whether
an
executive
vote
should
manually
pull
the
10
million
die
from
the
optimism
escrow
via
executive
vote.
C
And
the
next
up
maker
dao
has
had
several
conversations
about
how
to
develop
an
effective
framework
for
soliciting,
disseminating
and
acting
on
legal
advice.
Sef
from
content
production
proposes
to
sponsor
a
bounty
of
forty
thousand
die
to
be
paid
to
whoever
submits
a
mip
that
successfully
passes
through
governance
and
meets
the
requirement
about
what
we
need
for
a
legal
framework.
C
A
D
D
I
think
between
like
artem
said
or
arden
mentioned
asus
post.
You
know
we
increased
our
revenues
by
20-fold
since
2020,
but
really
we
progressed
so
much
more
than
that,
and-
and
this
is
an
attempt
to
capture
most
of
it,
I
think
something
that
I
actually
missed
in
the
recap
is
kind
of
all
the
core
units
that
we've
onboarded
so
before
I
start
on
the
on
the
first
official
slide.
D
After
this
this
one
yeah
we've
onboarded
18
different
core
units
this
year,
which
is
absolutely
herculean,
so
yeah,
let's
get
started
so
q1
2021
was
pivotal.
We
had
news
of
the
maker
foundation
dissolving
likewise,
as
a
ex-foundation
member
myself,
you
know
internally
many
many
many
of
the
people
from
the
foundation
kind
of
broke
off
and
some
left
some
started
their
own
cus.
D
We
also
had,
with
the
dissolution
of
the
foundation
the
sunset
of
the
development
grants
program
and
in
its
place
this
year,
we've
seen
a
number
of
different
tools
for
doing
grants
through
maker,
not
through
the
foundation.
So
we've
seen
the
special
purpose
fund
mip
come
about
we've
seen
ses
the
core
unit
that
does
incubations
and
various
grants
come
about.
We've
also
seen
various
core
units
doing
their
own
micro
grants
and
granting
programs,
so
thankfully
maker
is
still
really
healthy.
D
D
D
D
We
also
had
the
very
first
real
world
assets
on
boarding
through
the
tin
lake,
a
centrifuge
and
also
the
success
vault
facilities
and,
of
course,
it's
a
walk
or
sorry.
Crawl
walk
run
for
everybody,
so
it's
been
nice
to
see
that
we're
making
progress
and
yeah
we've
also
seen
governance
launch
vote
delegation
in
response
to
kind
of
concerns
about
passing
executive
votes
and
not
having
a
dedicated
voting
and
discussion
team
around
various
issues
and
topics,
and
so
this
has
greatly
improved
our
throughput
in
governance.
D
D
You
know
factoring
in
the
open
open
market
the
the
group
that
sets
rates
or
proposes
rates,
rather
did
so
through
monetary
policy
trying
to
make
generating
diet
from
non-stables
a
bit
more
attractive,
etc
and,
as
a
result,
yeah
maker,
open
market
committee.
Thank
you
long
and,
as
a
result,
usd
collateralization
fell
below
26
from
its
high
of
I
think
55.
D
So
that
was
a
really
great
success
story
for
for
diversifying
that
backing
collateral.
But
of
course
it
is
back
up
to
45.
Thanks
to
this,
this
looming
market
crash.
Also
in
q4,
we
had
a
two-year
anniversary
of
the
launch
of
multi-collateral
die.
I
remember
that,
like
it
was
yesterday,
I
can't
believe
it's
been
two
years.
I
feel
like
waiting
for
multi-collateral
die.
D
D
Another
pivotal
thing
we
saw
in
q4
is
an
infusion
of
vision
by
one
of
the
co-founders
of
maker
dao.
Originally
roon
christensen.
He
published
the
case
for
clean
money
advocating
for
a
whole
different
class
of
collateral
that
should
be
prioritized
mainly
esg,
collateral
collateral.
That
is
positive
for
environmental
impact
around
the
world.
D
It's
it's
also
a
subset
of
real
world
assets
and
likewise,
a
part
of
his
vision
included
a
redesign
of
mkr's
economics
and
really
he
proposed
many
interesting
ideas
that
I
believe
many
of
us
are
still
chewing
on,
and
thinking
on
and
and
and
eventually,
hopefully,
we'll
implement
in
in
a
in
an
ideal
sort
of
way,
and
I
believe
roon
is
actually
gearing
up
to
post
a
refined
version
of
this
version.
Sometime
this
year.
D
Also
in
q4,
so
this
is,
this
is
actually
really
interesting.
So
monkey
irish,
who
is
the
facilitator
of
the
collateral
engineering
services
corps
unit,
who
is
an
ex-foundation
employee,
presented
beyond
the
maker
foundation,
the
past
present
and
future
at
eth
portland,
and
the
reason
I
put
this
on
here
is
because
I
feel
like
his
talk,
really
resonates
with
a
lot
of
the
people
who
went
from
being
at
the
foundation.
D
You
know
centralized
sort
of
company
bootstrapping
maker
to
being
a
independently
funded
core
unit
amongst
many
at
a
dow,
and
so
this
transition
from
like
centralized
company
to
decentralized
organization
is
a
really
really
really
interesting
story,
and
I
it
resonates
with
me-
and
I
think
it
resonates
with
many
other
core
unit
facilitators,
and
so
we
are
really
on
the
bleeding
edge
here.
So
a
huge
pat
on
the
back
for
people
that
are
engaging
and
really
making
a
career
out
of
their
involvement
here
at
naper.
D
D
I
think
this
number
is
might
be
underrepresented.
I
think
it's
because
a
few
of
them
were
onboarded
in
late
2020,
but
I
might
my
timeline.
Brain
is,
is
not
perfect
right
now,
so
at
least
15
quarter
units
onboarded
within
the
year
of
2021,
with
with
actually
a
total
of,
I
believe,
18
or
19
right
now,
I'll
get
the
exact
numbers
for
the
next
call.
D
We
also
had
a
unified
auctions,
ui
release
a
brand
new
auction
ui
for
just
regular
non-technical
folks,
which
is
really
great
and
yeah
amongst
other
things.
So
if
I
did
miss
anything
like
major,
please
dm
me
we
we
did
try
to
cover
most
of
everything
all
right.
So,
let's
move
on
to
the
next
part
of
the
segment.
D
So
here's
some
interesting
governance,
metrics
that
we
pulled
and
if
you're
interested
in
where
we
pulled
them
from
you,
could
actually
go
into
the
presentation
which
is
linked
in
the
forum
agenda
for
this
call
and
you
could
just
go
to
the
slide
and
click
on
those
links
below
there's
they're
really
great.
The
voting
portal
itself
is
really
great
and
also
the
the
the
beta.mcd.gov.info
site
by
tokenflow
guys
are
is
really
great.
D
We
had
307
governance
polls,
I'm
not
going
to
go
through
all
of
the
different
types
of
governance
polls,
but,
as
you
can
see,
some
of
the
major
ones
we
had
122
different
ones
related
to
collateral.
We
had
74
different
ones
related
to
mips,
24
related
to
governance,
18
related
to
risk
parameters,
I.e
variables
and
many
others.
D
Another
interesting
thing
is
the
first
poll
of
2021
passed
was
around
67
000-ish
maker,
with
25,
unique
voters
and
the
very
final
one
passed
with
around
80
000
mkr,
but
about
half
as
many
or
a
little
bit
more
than
half
as
many
unique
voters.
17.-
and
this
is,
I
believe,
a
result
of
not
only
increased
gas
costs
which
deter
a
lot
of
the
smaller
voters
from
voting
in
every
single
vote.
But
also
this
was
affected
by
the
introduction
of
the
delegate,
the
delegates
right.
D
D
As
for
delegation
metrics,
we
have.
We
have
had
nine
recognized
delegates
introduced
in
2021,
with
almost
80
000
mkr
delegated,
all
of
whom
meet
the
performance
requirements
naturally,
because
if
they
didn't,
they
just
wouldn't
be
able
to
be
recognized
delegates
officially,
then
we
have
nine
shadow
delegates
with
about
21
000
mkr
delegated.
D
If
one
of
them
wanted
to
be
a
recognized
delegate,
they
probably
could
because
they
meet
the
performance
requirements,
but
three
somewhat
meet
them
and
five
don't
need
them
at
all.
So
there
is
a
there's,
obviously
yeah,
just
the
differences
in
people's
voting
behavior.
Some
people
are
extremely
consistent.
Others
might
vote
on
just
the
things
that
they're
most
interested
in.
D
The
first
big
ticket
item
is
layer.
Twos
maker
dow
has
three
different
layer,
twos
that
it
is
focused
on
arbitrarium
optimism
and
starknet,
but
really
it
can
get.
It
can
get
a
lot
more.
It
can
get
a
lot.
We
can
get
a
lot
wider
coverage
with
later
twos
with
wormhole,
so
I'm
very
excited
about
wormhole.
D
As
for
collateral
management,
we
have
parallel
tracks
for
collateral
management,
on-chain
and
off-chain,
and
so
off-chain
referring
to
real-world
assets.
Of
course,
they
have
a
whole
different
set
of
requirements
and
complexities
that
on-chain
collateral
management
doesn't,
and
so
that's
why
they're
separated,
but
the
various
things
that
are
a
focus
are
improved
stakeholder
alignment
and
coordination
around
these
initiatives,
optimizations
around
collateral
management
and
cross-team
work
for
real-world
assets,
a
revamping
of
the
collateral
prioritization
framework,
improved
partnership
practices
as
well
as
progressing
the
real-world
asset
deals
frameworks
and
processes.
D
For
technical
upgrades
there's
a
number
of
different
focuses:
we've
identified
this
year.
There
is
a
looming
governance
contract
redesign.
Many
of
you
know
it
as
the
sagittarius
engine
and,
of
course,
the
details
of
which
are
still
being
discussed
and
figured
out
it's
accompanied
by
an
mkr
tokenomics
redesign.
D
We
also
have
deco
fixed
rate,
vaults
you're,
going
to
hear
a
presentation
from
vamp
c
right
after
me
on
that
we
have
various
module
enhancements
and
integrations
from
the
pe
team.
I
highly
recommend
going
and
reading
their
core
unit
update
in
the
forum.
They
list
out
all
the
specifics
there.
It
was
too
much
to
add
to
the
slide
deck.
So
I
didn't.
D
We
have
various
technical
upgrades
for
auction
keepers,
infrastructure
and
ui,
including
liquidations
2.0
for
flap
auctions
yeah.
We
also
have
a
number
of
safety
and
tooling
upgrades
in
in
the
pipeline
as
well
as
something
that
the
pe
team
has
been
teasing
us
all
about.
Internally
is
nfc,
is
collateral.
There's
gonna
be
some
interesting
proposal
or
proposals
coming
up
around
that.
D
Various
organizational
improvements
are
also
on
the
horizon.
We
are
a
a
you
know,
a
protocol,
very
technical,
but,
of
course,
we're
also
an
organization
there's
people
here
and
there's
teams
here,
and
we
all
work
together
to
try
to
achieve
our
milestones
and
goals,
and
so
some
of
the
different
focuses
on
this
front
are
optimizing
and
streamlining
protocol
operations,
both
from
a
governance
perspective
and
from
you
know,
across
team
working
relationship
perspective.
D
D
We
have
improved
financial
reporting
thanks
to
ace
in
the
works.
We
have
initiative
map,
we
have
initiative
mapping
in
the
works.
We
have
stakeholder
alignment
calls
in
the
works
and
we
have
a
general
focus
on
just
improved
stakeholder
communications
overall
in
the
works,
that's
right
and
so
for
growth.
Another
major
initiative
at
maker
we
have
a
number
of
different
focuses,
improved
partner
relations,
institutional
vaults
and
how
to
streamline
those
types
of
deals.
D
Additional
psms
and
d3ms
more
grants,
improved
message,
propagation,
ie,
marketing
and
just
talking
about
how
what
we're
doing,
because
there's
a
lot
continued
partnership,
development
of
course,
and
more
core
unit
incubations,
thanks
to
scs,
continuing
to
focus
on
how
we
could
scale
maker
to
be
what
it
needs
to
be
for
security,
yet
another
really
important
initiative
at
maker
thanks
to
unified
security
and
also
the
tech,
ops
and
the
security
mindedness
of
the
various
sec
technical
teams.
Here
at
maker,
we
have
operational
security
and
bug
bounty
mips
in
the
works.
D
D
D
We
also
have
various
number
of
user
interfaces
at
maker,
with
a
number
of
different
teams
focusing
on
improving
them
and
developing
them.
First,
we
have
content
productions,
team
working
on
community
portal,
2.0
also
known
as
makernow.world
yeah.
We
have
auction
uis
being
developed
by
the
new
sas
team
side
stream
auction
services.
D
D
Basically,
we
have
a
singaporean
jurisdiction
study
for
being
able
to
source
real-world
asset
deals
from
singapore,
and
we
also
have
real
dao,
which
focuses
on
the
centralized
spd
infrastructure
in
the
works,
and
I
think
one
thing
I
might
have
forgotten
about
for
growth
is
yeah
more
more
videos
from
content
production
on
tutorials
how
to
interact
with
us
how
to
vote.
How
to?
Basically,
you
know
how
do
we
educate
our
would-be
stakeholders
to
come
into
maker
down
and
really
participate
and
yeah?
I
hope
I
didn't
spend
too
much
time.
D
It
was
only
like
40
slides,
but
yeah.
We
ran
through
it
pretty
quick,
so
so
yeah
thanks
for
listening.
I
and
again,
I
don't
think
we
even
covered
everything
in
completion.
There
were
numbers
of
things
like
off
the
top
of
my
mind.
There
were
a
number
of
different
upgrades
as
a
result
of
bug
fixes,
thanks
to
thanks
to
the
pe
team,
for
example,
like
the
governance
contract
upgrade
that
happened
last
year,
yeah
there's
there's
some
other
stuff,
but
yeah
million
other
things.
D
So
thanks
for
listening
and
I-
and
I
hope
that
this
is
a
testament
to
just
the
incredible
amount
of
work
being
done
by
the
numerous
teams
here
at
maker,
many
of
which,
if
we
didn't
have,
we
would
be
that
much
less
fortunate.
So
thank
you.
All
you've
been
you've
had
a
great
year
and
I'm
looking
forward
to
a
fantastic
2022.
A
A
E
E
All
the
extensive
feedback
that
we
received.
We
did
like
some
redesign
we're
almost
like
done
with
the
redesign
off
like
the
integration
like
taking
into
account
all
that
feedback
and
we've
actually
finished
like
designing
and
implementing
dss
gate
which,
which
also
like
came
out
of
discussions
with
the
ses
team
and
as
well
as
the
pe
team
like
during,
like
november
or
december
last
year,
on
on
on.
E
In
that
sense-
and
I
would
say
it's
like
a
governance
tool
to
limit
like
white
dots,
suck
integration
risk,
you
might
be
asking
like.
Why
are
you
adding
like
more
stuff
to
like
governance?
Why?
Why
are
you
forcing
like
governors
to
deal
with
like
dots
again?
I
promise
like
it
will
be
interesting.
So
this
is
like
a
small
module
that
we
have
developed.
E
That,
like
I
said
we
will
use
like
for
the
echo-
affects
trade
world
integration,
so
here
like
I'll,
spend
about
like
15
minutes
quickly
going
over
like
what
this.
What
this
does
it'll
touch
upon.
Things
like
I've
been
thinking
about
like
while,
while
doing
this
like,
while
preparing
this
presentation
right,
I've
thought
about
like
the
protocol
control
value.
Meme,
that's
been
that's
like
pretty
popular
these
days
in
d5,
and
this
is
like
kind
of
my
take
on
like
what
like
what
I
think
makeup.
E
Protocol
control
valuability
integrations
and
then
a
couple
like
links
to
the
code
base,
so
at
a
high
level,
like
I
mean
I
I
think
like
maker,
is
essentially
a
liquidity
engine.
Right
like
like
you
need
liquidity,
like
almost
everybody.
We've
seen
this
trend
in
like
20
20
21
everybody
who's
faced
like
problems
with
liquidity,
have
essentially
like
approached
maker
you've
seen
like
other
d5
projects
to
it
you've
seen
you
know
real
world
asset.
E
E
So
surplus
buffer
can
suck
as
a
channel
to
access
like
make
a
liquidity.
We've
there
have
been
a
few
I
mean
I
was
trying
to
make
a
list
of
like
okay.
What
what
modules
have
so
far
like?
Have
access
like
access
to
sucker
have
access
suck
like
one
flap
auctions,
although
not
directly
but
roughly
like
access
stuck
and
then
try
to
buy
mkr
from
the
market
and
then
like
burn
it
off.
E
We
have
like
diet,
saving
state
contract
that
accesses
the
pod
contract
that
access
suck
and
promises
a
yield
to
depositors,
dye
depositors
into
part.
We've
seen
like
dss
west
being
used
like
using
the
surplus
buffer
like
to
pay
pay
teams.
Employees
like
using
a
stream
and
deco
fixed
rate
walls
like
we'll
share
the
design
like
a
couple
weeks
like
down
the
road,
but
would
also
like
use
like
to
make
the
integration
happen.
E
So,
in
a
sense
I
think
there
is
like
there
is
like
I
mean
there
is
a
little
bit
of
experimentation.
Most
of
it
has
been
like
internal.
So
far,
nothing
has
been
like
an
integration
focused
experience
around
suck
deco.
I
think,
like
would
be
probably
one
of
the
first
like
to
access
our
click
from
an
integration
perspective.
That's
not
like
internal
internal
to
the
maker
protocol
slightly
like
out,
so
the
big
pain
point
to
these
integrations
have
always
been
like
for
us
like
suckers,
like
scary.
Access
to
suck
is
like
it's
a
really
scary.
E
It's
a
really
scary
thing
right,
one
small
one,
small
mistake,
and
then
you
not
only
lose
the
surplus
buffer,
but
you
can
literally
suck
like
a
10
billion
hundred
billion.
One
trillion
die
so
suck
is
this
to
get
access
to
stuff?
You
need
authorization
on
what
and
that's
like
getting
direct
access
to.
That
is
like
really
scary.
So
last
year
like
when,
when
we
put
out
a
proposal
and
then
we
were
like
we
were
talking
to
ses
pe.
E
So
there
there
asked
us
was
see
you
we
there
there's
no
way
like
you
can
get
like
direct
access
to
suck
from
mcd
right
because
it
comes
with
a
whole
ton
of
risks.
Why
don't
you
think
of
like
a
sandbox
in
between
that
limits?
The
amount
of
risk
that
maker
is
taking
on?
So
essentially,
if
the
sandbox
says
like
say
it's
a
total
supplement
of
one
million
diet.
E
So
so
we
took
that
concept,
and
then
we
tried
to
basically
implement
it
and
also
like
look
for
look
for
a
couple
other,
like
we
made
a
few
other
design
choices,
to
make
it
a
bit
more
generalized,
not
just
like
to
suit
the
needs
of
like
deco
protocol,
but
also
potential,
like
future
maker
pcv
integrations
so
again,
like
just
to
recap
again
any
integration
that
needs
access
to
suck.
It's
like,
like
a
lot
of
upfront.
E
Work
has
to
go
into
into
alternating
the
integration
like
completely
to
ensure
that
it
doesn't
like
impose
risks,
the
primary
reason
being
that
has
almost
like
a
a
binary
approval
process.
So
when
wired
gives
access
to
a
smart
contract,
it
gives
it
authorizes
that
smart
contract
to
call
all
the
restricted
functions
and
an
unlimited
amount
of
like
and
stock
and
unlimited
amount
of
like
die
out
of
out
of
that.
E
So
in
a
sense,
dss
gate
acts
as
an
intermediary
between,
like
that
particular
sub
call.
So
so
here,
like
you,
can
see
dss
a
gate
like
a
gate
contract
like
sets
between
an
integration
and
what
would
only
authorize
gate
to
execute
suck
and
then
gate.
Is
this
like
minimal?
It's
a
small
module
that
only
deals
with
like
putting
a
gate
on
like
the
amount
of
diet
that
can
be
sucked
out
of
that.
So
we
can.
E
We
can
call
it
like
something
like
a
draw
limit,
so
gate
would
in
turn,
approve
the
integration
to
execute
so
from
an
integration
perspective
like
it's.
Making
the
same
sub
call
it's
just
like
not
making
it
directly
into
art,
it's
like
making
it
it's
doing
that
into
dss
gate
which
implements
the
gate,
so
the
so
a
gate
contract
like
does
two
things
one.
It
implements
this
draw
limit.
You
can
think
about
a
draw
limit
as
like
a
static,
number
kind
of
like
a
token
approval
right,
you
get
an
approval
up
to
five
million.
E
You
can
spend
like
up
to
five
million.
For
example,
you
get
an
approval
up
to
like
one
million
you
can
play
like
an
integration
can
suck
up
to
a
total
off,
like
one
million.
So
in
that
sense
the
draw
limit
acts
as
like
this
limiting
factor
in
terms
of
the
amount
that
can
be
sucked
out
so
cater
implements.
That
gate
actually
implements
a
second
thing
called
a
backup
balance.
E
So
the
idea
behind
backup
balance
was
like
is
like
twofold,
actually
one:
what
if
the
integration
is
like
completely
not
tested?
It's
like
super
early
stage
where
make
a
protocol
does
not
want
to
even
authorize
the
gate
contract
like
up
to
any
amount.
It
just
does
not
want
to
set
like
any
sort
of
authorization
or
wants
to
set
the
draw
number
to
zero,
so
gate
can
actually
work
with
local
diet
balance.
E
We're
calling
it
like
backup,
balance
and
governance
can
like
do
a
one-time
transfer
or
like
set
up
a
dessert
stream
and
then
load
up
a
gate
contract
with,
like
a
certain
die
amount.
Gate
is
like
not
even
connected
to
that,
and
the
integration
can
get
like
can
get
going.
It
doesn't
have
to
like
wait
for
any
permissions
into
the
core
like
make
a
protocol,
so
backup
balance
can
be
like.
E
I
don't
know
if,
if
you
wanted
to
take
a
phased
risk,
roll
out
approach
to
launching
integrations,
we
could,
like
governance,
could
actually
like
set
up
the
gate
contract
with
a
backup
balance
and
get
the
integration
going
and
over
time.
All
it
takes
is
a
single
approval
on
that
to
to
just
like
set
up
set
up
that
draw
limit,
backup
balance
actually
like
the
idea
behind
backup
balance
is
actually
twofold,
like
I
said
one
to
get
integrations
quickly
going,
but
also
to
give
integrations
a
little
bit
of
a
trustless
guarantee.
E
So
governance
can
remove
like
authorization
to
gate
or
the
integration
at
any
time.
Right,
like
all
it
takes,
is
an
executive
vote
and
then
remove
the
authorization
for
gate
and
the
integration
essentially
wouldn't
be
able
to
suck,
but
integrations
usually
have
like
a
little
bit
of
like
long-term
obligations
to
the
users.
So
if
the,
if
there's
a
collect,
fail
abruptly
because
governance
like
decided
to
remove
authorization,
it
would
be
like
a
disaster
for
them
or
other
ways
in
which
this
could
happen.
E
Balance
can
act
as
that
that
resource
that
integrations
can
like
drop
on
and
not
to
wind
down
their
operations
or
like
just
when,
like
the
when
these
like
calls
fail,
either
like
temporarily
or
like
permanently.
So
in
a
sense,
it's
a
nice
backup
that
increases
the
trust
trustworthiness
off
like
the
sub
call
like
for
an
integration,
so
in
combination
like
one
one
example,
would
be
like.
Okay
once
all
this
is
set
up
like
the
backup
balance
is
just
just
sitting
there.
It's
not
like
actively
used.
E
One
simple
thing
that
we
are
going
with
right
now
is:
like
the
subtrue
token
approval
style,
where
so
the
okay,
so
this
is
this
is
the
role
of
governance
right,
so
now,
governance
basically
has
a
couple
things:
analyze
the
integration
and
it
and
its
requirement
like
to
access
suck,
deploy
a
gate
contract.
This
gate
contract
is
completely
controlled
by
like
maker
governance.
Again,
it's
not
controlled
by
like
the
integration
and
one
and
make
a
governance
like
gets,
has
to
take
like
two
decisions.
E
We
we
have
the
implementation
ready
and
we
have
like
some
docs.
So
if
you
go
to
like
deco
protocol,
slash
dss
gate,
you
can
look
at
the
look
at
the
code
base.
What
we've
done
is
we've
implemented,
like
one
design
called
like
just
calling
it
like
gate.
One
simple
gate
implements
a
couple
features
like
token
approval
style,
draw
limit
and
then
implements
a
backup
balance,
and
then
there
are
two
balances
you
need
to
decide
priority
right
like
does
the
integration
like?
Does
the
gate
contract
like
access,
backup,
balance
first
or
like
the
sub
call?
E
E
So
in
that
sense,
like
yeah,
we
will
be
discussing
that
probably
later
a
couple
couple
weeks
down
the
road
but
but
yeah
overall.
Like
I
mean
I
think,
suckers
like
an
interesting
integration
pathway
to.
I
think
I
think
folks
should,
like
think,
a
little
bit
more
about
it.
Anybody
like
looking
to
integrate
it
but
make
a
protocol
should,
we
think,
should
think
a
little
bit
more
more
about
it
and
dds
gate
is
like
we
hope
like.
F
Yeah
yeah
I've.
I
just
want
to
highlight
that
if
anyone
is
interested
in
this
design
pattern
that
it's
based
on
this
sandbox
research
project
that
vamps
you
talked
about
from
from
ses
and
there's
some
information
here.
But
I
think
this
is
a
very
powerful
design
pattern
and
it's
really
awesome
to
see
it
actually
being
used
now,
because
it
can
also
really
help
in
terms
of
parallelization
of
work
because
yeah,
as
brian
wrote
in
the
chat
the
issue
with
adding
new
modules.
F
The
mega
protocol
today
is
that
there's
a
very
like
binary
authorization
system.
So
if
we
grant
something
authorization
on
the
vet,
you
know
it.
It
basically
has
full
authorization
on
all
the
functions
and
there's
no
limitations
to
what
it
can
do.
As
I
mean,
obviously,
it's
limited
by
the
code,
that's
written,
but
then
we
need
to
really
extensively
review
and
audit
that
code.
F
How
can
we
also
do
some
of
this
for
the
collateral
onboarding,
because
when
you're
onboarding
new
collateral
types,
you're
also
messing
with
a
lot
of
parts
of
the
mega
protocol
that
external
teams
can't
do
because
yeah
there's
when
you're
building
a
spell,
you
have
root
access
to
all
parameters.
There's
no
limits
to
what
harm
you
can
do.
When
you're
building
a
new
giant
adapter,
you
are
getting
authorization
on
the
vet
as
well.
F
So
there's
a
lot
of
things
where
we
can
really
make
a
really
neat
sort
of
integration
surface
that
can
also
improve
the
overall
security
of
the
mega
protocol
and
also
increase
the
or
decrease
the
time
to
market,
rather
because
we
don't
need
to
necessarily
verify
every
single
line
of
code.
At
least
we
can
minimize
the
exact
vector.
So
so
that's
the
whole
point
of
this
design
pattern
so
yeah.
If
anyone
is
interested
in
knowing
more
about
this
yeah,
please
reach
out.
E
Tend
to
answer
like
frank's
question,
one
investment
for
gate,
I
think,
or
one
integration
per
gate.
I
think
that's
the
right
way
to
do
things.
It's,
although
there's
not
nothing
like
stopping
from
10,
integrations
to
access
the
same
gate,
but
it's
like,
I
think
the
right
way
to
deal
with
this
is
like
deploy
one
for
an
integration
and
then
like
operate
operate
that,
like
top
up
the
approval
and
it's
like
a
backup
balance,
but
maybe
you
don't
even
need
a
backup
balance.
So
just
take
those
decisions
like
based
on
an
integration.
E
Repayment
yeah
it's
a
like
the
suck
itself
is
like
one
way
and
then
if
the
integration
has
to
repair
they
might
they
could
just
like
transfer
the
dye
back
to
like
pause
pause
proxy
for
the
backup
balance,
you
can
essentially
implement
a
withdrawal
condition
right
and,
like
governance,
could
say,
load
it
up
with
hundred
thousand
die
and
then
say
like
we
will
withdraw
it
only
after
like
the
end
of
this
quarter.
So
before
the
end
of
the
quarter,
the
backup
balance
cannot
move.
It
can
only
be
accessed
by
the
integration.
E
The
governance
can't
like
take
it
back,
but
after
the
end
of
the
quarter,
like
governance
can
now
like
withdraw,
withdraw
that
the
type
back.
So
that's
why
it's
like
backup
balance,
you
don't
really
use
it
as
a
primary
one.
First
up
yeah
one
way,
and
if
the
integration
has
to
give
it
back
like
I
don't
know,
maybe
they
just
push
it
handle
up
there
and
yeah.
E
The
other
thing
that
we
really
try
to
do
is
not
add,
like
not
add
any
requirements
on
the
integration
like
that,
they
would
have
to
implement
like
like
any
of
these
limit
checks
or
any
of
that.
So
for
them
we
basically
replicated
the
suck
interface,
the
same
function,
interface
and
get
so
gate
would
exactly
look
like
what
to
them.
They
wouldn't
really
have
to
do
like
anything
else
like
inside
the
integration
itself
to
handle
like
to
handle
this
so
yeah.
D
D
So,
basically,
it
would
create
like
a
middle
step
and
instead
of
sucking
directly
from
the
surplus
buffer,
it
would
suck
from
the
gate,
contract,
yeah
and
the
gate
contract
would
just
hold
that
balance
in
the
interim
and
consistently
kind
of
re-uh
re-up.
That
balance
over
time
as
it
gets
depleted.
Is
that
the
right
way
of
thinking
about
it.
E
Maybe
not
because
the
goal
is
not
to
like
get
like
every
single
like
sub
call.
The
goal
is
about,
like
usually
stuff,
like
join
adapters,
dss
best.
These
are
contracts
that
can
be
like
audited
like
once,
and
you
can
be
like
completely
sure
that
the
calls
like
coming
from
these
contracts,
like
will
not
do
like
anything
anything
shady
or
anything
like
that's
like
high
risk.
E
So
if
you
can,
if
you
can,
if
you
can
create
the
create
a
contract,
that's
already
risk
limited
and
then
once
you
create
a
west
right,
it's
all
about
like
just
redeploying
the
same
thing
again
and
again
and
again
to
handle
like
different
payments.
So
there's
really
like
no
need
for
a
gate
contract
to
step.
In
again,
I
don't
think
like
a
gate
would
would
really
benefit
being
between
like
white
and
like
something
like
dss,
west
or
probably
even
a
join
adapter
like
yeah
join
adapters.
E
Don't
really
use
sub,
but
but
in
that
sense,
like
small
like
well
tested,
contracts
can
obviously
continue
to
be
used
like
dot
sub
directly.
This
is
more
about,
like
let's
say,
an
integration
like
deco
right.
It's
like
this
large
body
of
like
this
is
like
probably
a
large
protocol.
That's
like
completely
new!
That's
from
the
maker
protocol
perspective.
It's
like
not
sufficiently
well
tested,
but
like
there's,
there's
an
opportunity
like
to
get
it
going
like
quickly.
E
Parallel
development
like
deploying
it
fast
like
testing
it
all
that
so
far
like
the
the
thing
is
this
west,
the
contract
can
be
like
like
audited
right,
but
it's
just
that.
How
do
we?
How
do
we
get
like
these
large
surface
area
like
new,
smart
contracts
from
accessing
like
part.,
without
really
like?
I
guess
like
in
a
much
more
like
faster
fashion.
So
like
again,
it
would
be
helpful
because
gate
would
be
like
this.
One
thing
that's
like
well
tested
well
audited.
E
The
actual
protocol
like
that
would
be
audited
like,
like
maybe
like
down
the
road,
but
this
like
it's
almost
like
a
chicken
and
egg
right
like
you,
you
won't
be
confident
about
deco
without,
like
you,
you're
testing
it
and
without
totally
giving
access
to
that
suck.
But
then
you
can't
do
that
because,
like
giving
the
untested
protocol
like
access
to,
it
is
scary,
yeah.
So.
D
So
state
like
restated,
basically
for
simple
contracts
that
do
suck
calls
like
that
are
pretty
low
risk,
like
you,
don't
need
to
do
a
dss
gate,
because
it's
additional
gas,
like
it's
just
unnecessary
but
dss
gate
enables
you
to
integrate
with
way
more
complex
external
modules,
without
worrying
about
whether
those
modules
are
like
a
thousand
percent
foolproof
right.
So
you
can
basically
limit
your
risk,
while
obviously
also
doing
the
due
diligence
of
auditing,
like
that,
whatever.
D
G
Yeah,
I
mean
think
of
it
like,
like
maker,
goes
to
a
hackathon
and
gives
everybody
like
a
25
000
balance
to
like
implement
their
project
with,
and
we
can
literally
just
give
out.
You
know
like
10
different
projects,
access
to
this
25
000
balance
and
and
we
we
know
that
they
can.
They
basically
there's
a
guarantee
that
they
can't
like
mess
with
the
system's
accounting
or
break
anything.
G
We
don't
have
to
do
a
full
audit
and
then
the
idea
is
like
some
of
those
are
going
to
prove
themselves
out
as
being
like
pretty
cool,
and
then
we
increase
their
balances
and
eventually,
like
we,
you
know
if
they
actually
like
find
product
market
fit
or
whatever
we
we
can
find
a
maybe
a
more
gas
efficient
implementation,
but
this
allows
this
allows
for
a
lot
more
experimentation,
yeah,
the
the
other.
The
other
thing
is
the
paradigm
I
was
thinking
of
this,
as
is
like.
G
G
E
A
D
E
So
the
question
is
like:
is
the
plan
to
like
eventually
remove
gate
and
give
like?
Let's
say
the
integration
is
like
super
well
tested,
has
been
around
for
a
couple
years
and
is
the
plan
to
eventually
remove
gate
and
give
it
direct
access
to
like
y
dot
suck
I've
thought
about
it,
but
I
think,
like
having
gate
would
still
help
because
of
the
backup
balance
feature.
So
direct
access
to
suck
means,
like
you,
that
direct
taxes
just
disappears
right
can
disappear
like
maker
call
maker
has
to
make.
E
A
governance
has
to
do
is
like
why
dot
deny
the
integration
address
and
then
click
boom
it's
gone
so
so
integration
that
can
be
like
really
abrupt
for
integrations,
it's
kind
of
like
I
mean
we
thought
about
that
in
a
way
for
decor
right,
like
water
flick
that
happens,
and
then
you
have
a
like
decker
protocol
has
a
bunch
of
obligations
right.
I
don't
know
for
the
next
like
three
months,
like
maybe
not
new
issuances,
but
then
like.
That
would
be
that
that
that
wouldn't
that
would
be
like
a
like
a
mess.
E
So,
in
that
sense,
gate
can
still
be
like
a
long-term,
long-term
piece
of
that
puzzle.
So
this
ability
for
maker
governance
to
do
like
hit
well
dot
deny
at
any
time
it
can
be
mitigated
by
governance,
locking
up
a
backup
balance,
click
and
putting
a
stamp
on
it.
Saying
like
yeah,
we're
locking
up
like
1
million,
and
we
can't
take
it
out
like
until,
like
the
end
of
this
quarter.
E
So
like
no
matter
like
what
we
do,
you
have
access
to
a
million,
so
in
that
sense,
like
gate,
can
still
be
like
a
long-term
long-term
piece
for
integrations
that
demand
that
additional
trustlessness
from
from
from
from
the
makeup
protocol
side.
So
now
it's
like
yeah,
it's
limiting
with
rest,
not
just
flick
from
equal,
but
it's
actually
like
limiting
risk
on
the
for
the
integration
tool
like
risks
coming
from
maker
like
to
the
integration.
E
D
There
were
ideas
about
kind
of
taking
out
funds
from
the
surplus
buffer
and
holding
them
in
separate
pools
to
ensure
like
continuity
of
operations-
and
I
know
some
core
units
also
have
like,
like
my
core
unit-
has
a
operational
continuity
sort
of
wallet
for
like
three
or
six
months
of
operations.
I'm
curious
like
if
dss
gate
can
be
used
as
like
a
a
limiter
like.
D
Basically,
you
still
retain
like
the
liquidity,
for
whatever
the
20
million
or
30
million
in
overhead,
and
you
just
keep
that
and
it
doesn't
get
removed
from
the
surplus
buffer
but
but
yeah.
So
I'm
just
thinking
about
also
like
how
we
can
improve
our
our
safeguarding
like
operational
continuity
in
the
event
of
massive
losses,
while
also
like
not
relying
on
totally
like
diluting
mkr
to
fund
operations
after
the
fact
yeah.
That's
just
something!
That's
on
my
mind.
It
kind
of
fits
into
this
discussion.
F
A
F
E
E
E
F
Yeah-
and
another
thing
I
want
to
point
out
is
the
concept
of
quantifiable
risk,
which
is
you
know.
We
saw
that
the
compound
had
that
weird
governance
bug
and
they
were
actually
kind
of
saved
by
the
fact
that
the
contract
that
was
emptied
had
you
know
it.
They
could
only
siphon
comp
from
like
a
specific
smart
contract
and
it
wasn't
like
a
mint
function
and
that's
kind
of
an
example
of
a
sandboxed
setup,
because
there
was
a
limit
to
how
bad
it
could
go.
G
Yeah
I
mean
it's,
it's
a
it's
possible
that
we
could
get
through
and
audit
it,
but
it's
like
severely
underestimates
the
amount
of
time
it
takes
to
like
safely
audit,
something
like
we
saw.
This
was
sort
of
centrifuge
right.
They
had
a
whole
liquidation
module
designed
and
when
we
finally
started
cracking
it
open
we're
like.
G
So
it's
the
same
thing.
It's
just
you
know
we're
going
to
get
a
lot
more
integrations
be
able
to
set
like
lower
debt
ceilings.
If,
if
we
have
these
like
more
restricted
modules,
I
I'll
add
just
so
people
know
this
isn't
as
easy
to
do
with
collaterals
that
have
liquidations
turned
on,
because
the
liquidations
can
kind
of
violate
the
debt
ceiling
constraint
right
so
like
there's
a
debt
ceiling,
and
then
you
think,
oh,
they
can't
exceed
the
debt
ceiling.
G
But
if
you
have
liquidations,
you
actually
get
a
chance
to
like
remove
that
debt
ceiling,
and
so
so
the
sort
of
first
order
collateral
types
of
liquidations
actually
are
aren't
as
like
easy
to
constrain
in
this
way.
But
but
there's
a
whole
range
of
integrations
that
don't
require
like
liquidations
and
or
can
manage
their
own
or
or
whatever.
And
and
if
they
go
through
this
one
interface,
then
we
can
guarantee
that
the
the
constraints
hold
and
we
can
do
all
kinds
of
integrations
safely.
F
B
A
All
right
so
we're
approaching
half
past.
We
still
got
a
few
five
five
eight
minutes
left.
So
are
there
any
sort
of
final
questions
or
comments
anybody
wants
to
ask
or
make
about
jesus
gates
or
about
some
david's
presentation
before
we
wrap
up
for
the
day,
I
guess
we're
starting
the
day
from
my
us
works,
but.
D
Yeah
I'll
shout
out
the
the
calendars
that
we
have,
so
we
have
a
votes,
boats
and
important
dates,
calendar
that
you
can
subscribe
to
it's
a
public
calendar,
it's
maintained,
and
it
includes
all
of
the
important
mip
cycle
dates,
as
well
as
the
various
votes
that
happen
both
like
governance
polls
and
executive
votes.
I
believe,
are
on
there
and
then
we
have
a
second
calendar
for
calls.
D
So
these
include
public
calls
like
this
one,
as
well
as
semi-public
calls
like
stakeholder
alignment
meetings,
so
we've
begun
listing
them
in
public
and
they
are.
They
are
not
public
per
se.
You
can't
just
come
in,
but
you
can
request.
So
if
you
are
a
stakeholder
and
you
see
an
initiative
that
is
relevant
to
you,
you
are
welcome
to
request
access
and
so
yeah
subscribe
to
those
two
calendars.
They
are
very
helpful,
and
so
yes,
that's
my
shout
out
I'll
post
the
links
in
the
chat.
A
Perfect,
thank
you
david,
so
I
know
we've
had
a
little
bit
of
a
presentation
heavy
meeting
this
week,
I'm
so
trying
to
a
little
more
discussion
in
in
next
week.
We
also
wanted
to
try
getting
some
light
sort
of
topics
for
these
calls
from
the
recognized
delegates
instead
of
just
from
the
core
units.
So
if
you're
a
recognized
delegate-
and
you
have
a
topic
you
want
to
bring
up
in
the
next
meeting-
please
reach
out
to
me
or
to
david.