►
From YouTube: Issue Discussion Call # 6 | Collateral Onboarding
Description
▼Chapters▼
0:00 Introduction
0:59 Agenda
2:47 Collateral Onboarding Process
42:08 Open Discussion
▼Overview▼
GovComms Engagement Lead @thomas.flitter and Collateral Engineering Services (CES) Core Unit Facilitator, Monkey.Irish, lead a discussion on the new proposed collateral onboarding process and how it will create better transparency around our pipeline and decision making.
▼Tentative Agenda▼
• Welcome and Introductions
• What is collateral onboarding?
• What are the issues collateral onboarding is facing?
• How can we improve the process?
• Open Discussion
▼Resources▼
Call Notes:
https://docs.google.com/document/d/1D5wkxDP_MixAnj5AquaPrr4QtaRFXhbG0Yv3hbXToxg/edit?pli=1
Relative Posts and Links:
https://forum.makerdao.com/t/mip6-recommended-guideline-metrics-for-onchain-collateral-onboarding/14503
https://forum.makerdao.com/t/launch-of-the-new-collateral-status-index-csi/14723
https://forum.makerdao.com/t/collateral-status-index-csi-update-2022-04-28/14844
A
A
My
name
is
thomas
flitter
and
I
am
the
engagement
lead
for
govcom's
core
unit
I'll
be
your
host.
For
today
we
do
have
a
special
guest,
robert
jordan,
there's
monkey
irish
facilitator
for
the
collateral
engineering
services
core
unit
and
he's
going
to
help
lead
us
through
discussion
of
the
issues
being
faced
with
the
collateral.
A
How
is
the
process
understood?
How
well
is
it
understood,
how's
the
documentation
from
end
to
end
and
also
is
going
to
be
taking
a
look
at
covering
some
of
the
new
proposed
processes,
some
of
the
things
we
have
in
the
pipeline
that
will
be
addressing
those
issues
on
collateral,
onboarding,
and
so
I'm
very
pleased
to
have
robert
here
today.
A
He's
got
some
fantastic
slides,
but
also
as
a
reminder,
everybody
that
is
on
board.
Some
of
you
may
know
this
process
a
little
a
little
bit
have
heard
this
before,
but
some
of
us
may
not,
and
so
we're
excited
to
hear
from
robert
to
teach
us
a
little
bit
about
it.
Talk
about
issues
and
some
of
those
solutions.
I
do
want
to
encourage
everybody,
also
that
this
session
is
also
an
interactive
session.
Please
send
us
a
comment
on
the
chat
feature
also
raise
your
hand
or
just
speak
up.
A
B
I
always
like
to
start
some
of
these
discussions
because
I
believe
history
matters,
so
how
we
get
here
is
is
actually
very
important
as
well,
and
some
of
you
might
have
heard
of
the
multi
collateral
die
launch
that
happened
in
november
of
2019,
and
that
was
right
before
I
started
with
the
maker
foundation
way
before
the
transition
to
the
dow.
I
don't
think
any
of
us
would
have
anticipated
the
growth
we've
had
with
the
maker
protocol
to
support
this
growth.
B
Our
our
collateral
and
onboarding
has
tried
to
keep
up
with
the
quick
pace
of
our
industry
and-
and
we
went
through
from
from
the
mcd
launch,
onboarding,
eth
and
bat,
and
then
we
looked
around
and
said.
Okay,
what
else
can
we
onboard?
So
we
tried
to
onboard
just
about
every
euro
c20
clutter.
We
could
find
we
exhausted
those
tokens
we
off-boarded,
some
we
created,
which
was
interesting-
the
the
rap
btc
market,
a
lot
of
controversy
around
that
one,
but
you
can
see
how
much
that's
grown
inside
of
our
protocol
and
how
important
that
is.
B
What
it
looked
like
to
onboard
an
rwa
was
completely
unknown
back
then
notable
members
of
the
community
wrote
the
initial
mips
and
processes
to
define
collateral
onboarding
and
I'm
pretty
sure
they
they
weren't
thinking
about
rwas,
let
alone
collateral.
That
is
really
a
hybrid
of
what
we're
terming
on
and
off
chain.
B
B
At
the
beginning
of
the
year,
we
published
the
collateral
management
lifecycle
or
the
cml
as
a
holistic
view
on
how
the
collateral
engineering
services
core
unit
functions.
The
roadmap
involves
building
two
key
components
for
collateral
management
for
not
for
both
on
and
off
chain
collateral.
So
it's
really
important
that
we
understand
that
there
are.
There
are
two
types
of
collateral:
a
lot
of
the
same
processes
are
shared
amongst
them,
but
there
are
also
some
differences,
so
the
first
component
of
this
is
collateral.
B
B
We've
also
made
progress
there,
but
there's
still
a
lot
to
do
and
that's
where
we're
spending
most
most
of
our
energies
today
with
collateral
onboarding,
but
this
is
going
to
change
very
quickly.
The
second
component
is
collateral
maintenance,
and
today,
if
we
take
a
look
at
our
collateral
maintenance,
it's
dispersed
amongst
multiple
core
units
and
contributors.
B
This
is
especially
important
with
rwas,
since
we
cannot
rely
on
on-chain
data
to
make
decisions.
Work
is
already
beginning
in
this.
Our
program
manager
that
will
lead
this
effort
starts
next
week
and
she'll
be
taking
on
both
the
collateral
onboarding
changes
that
are
upcoming,
not
only
the
ones
that
we
just
did,
but
also
for
phase
two
and
then
this
whole
area
of
collateral
maintenance
and
the
processes
within
collateral
engineering
services.
B
B
B
Today
we
have
a
collateral,
onboarding
process.
Yes,
it's
real
and
it
went
through
a
significant
update
last
week,
and
I
also
want
to
know
is
we
use
it
every
day
now?
The
way
I
refer
to,
there
are
two
big.
There
are
actually
three
groups
of
of
wees
that
we
have
out
there.
There
are
the
on-chain
collateral
stakeholders,
which
typically
deal
with
the
native
collaterals.
B
We
have
the
off-chain
collateral
stakeholders
which
deal
mainly
with
the
real
world
assets
and
the
onboarding.
Then
we
have
the
mandated
actors,
because
the
mandated
actors
have
been
a
group
of
people
that
have
been
around
for
some
time
that
include
the
facilitators
and
other
recognized
people
within
the
community
that
have
been
voted
into
that
slot.
B
B
A
B
So
the
first
phase
of
the
cloud
onboarding
process
is
the
collateral
application.
In
the
past
there
was
a
bit
of
confusion
with
this
part
of
the
process.
Most
recently,
our
collateral
applicants
got
a
little
creative
to
test
the
governance
process
by
publishing,
nip
sixes
signal
requests
and
what
will
term
regular
mips.
B
As
a
result,
it
was
clear
that
we
had
not
educated
the
community
on
the
overall
collateral
collateral
onboarding
process
and
the
old
status
spreadsheet
did
not
communicate
the
current
state
of
the
collateral
moving
through
onboarding
plus
we
had
a
lot
of
greenlit
collateral
without
any
progress
and
that
needed
to
be
cleaned
up.
Those
are
great
learnings
for
for
our
team
and
I
think
for
the
community
currently
to
start
the
process
of
getting
collateral
added
to
the
maker
protocol.
B
Now
I'm
making
some
recommendations
and
suggestions
here,
anyone
is
free
to
do
whatever
it
is.
They
feel
they
need
to
do
given
our
governance
process.
Well,
I
want
to
point
that
out,
I'm
simply
providing
the
learnings
that
I've
seen
based
upon
the
experiences
that
we've
had
with
onboarding
our
collateral
for
the
past
18
months
now,
once
a
mip
six
is
posted
to
the
forums
we
have.
A
two
two
week
comment
period,
followed
by
a
two
week,
green
lag
poll.
B
B
B
B
B
However,
through
our
signal
request
process,
you
know
anyone
can
file
that
risk
takes
a
look
at
that
they
verify
the
parameters
and
then,
as
we
deploy,
that
new
vault
type,
it
has
different
parameters.
The
collateral
technically
has
been
onboarded,
we're
just
changing
the
parameters
for
that
particular
vault
type.
So
please
keep
that
in
mind
and
again,
just
for
completeness.
I
wanted
to
point
that
out
any
questions.
I
know
there's
a
lot
of
information.
B
Okay
next
slide,
please,
the
second
phase
of
the
collateral
onboarding
process
is
prioritization.
What
we
learned
is
the
key
to
prioritization
is
transparency,
clearly
communicating
the
process
and
decisions
of
of
the
collateral
stakeholders
was
missing,
and
I
think
that
was
pretty
apparent
by
by
much
of
the
discussion
in
the
community
today.
Once
again,
a
collateral
is
greenlit.
It
means
that
it's
it's
two
weeks
in
the
green
light
poll
and
there
are
more
yeses
than
nodes.
At
that
point
it
becomes
green
lit.
B
B
So
this
is
also
going
to
be
improved
in
what
I'm
calling
phase
two
of
the
collateral
onboarding
process
and
again,
if
you
want
to
take
a
look
at
what
is
up
next,
I
highly
recommend
you
look
at
the
collateral
status
index
and
there's
a
status
called
up
next.
What
that
indicates
is
that
that
collateral-
that's
classified
as
up
next
has
the
ability
to
move
into
the
next
steps
of
the
collateral
onboarding
process
and
we'll
talk
about
that.
Next
again,
I'm
going
to
pause
there
to
see
if
there
are
any
questions.
A
Okay,
so
robert
from
what
I'm
understanding
is
that
the
collateral
onboarding
in
the
past
was
just
hey,
let's
get
what
we
can
on
board-
let's,
let's
just
try
to
put
all
this
stuff
together,
as
is
we
find
one?
We
we
get
it
in
there.
It
was
a
hodgepodge
if
you
will
and
now
we're
in
the
process
of
of
figuring
out
that
from
the
prioritization
is.
That
is
that's
what
I
understand.
B
B
What
happened
is
that
as
more
court
units
came
on
board,
the
process
got
deluded
and,
and
there
wasn't
a
a
a
really
you
know
until
ces
came
along
there,
wasn't
a
group
to
really
own
that
process,
okay
and
and
shepherd
it
and
drive
it
forward,
so
it
so.
It
sort
of
sat
in
that
area
of
hey
who's
doing
this,
and
so
people
would
pop
in
and
they
would
put
their
feedback.
B
And
you
know
sometimes
you
know
some
core
units
were
much
more
engaged
than
others,
but
there
really
wasn't
a
body
of
people
that
were
responsible
for
the
process,
so
it
took
a
life
of
its
own.
The
the
essence
of
the
process
was
followed,
but
but
it
wasn't,
but
it
really
wasn't,
it
really
wasn't
iterated
on
so
it
was
just
left
to
be
implemented.
However,
the
team,
the
teams
felt
it
it
needed
to
be.
B
B
Now
there
were
cases
where,
for
example,
an
assessment
would
come
back
as
let's
say
high
risk,
or
let's
say
that
risk
said
we
can't
recommend
a
debt
ceiling
and
then,
at
that
point
a
decision
was
made
by
the
domain
teams
to
stop
working
on
the
collateral.
You
know
one
of
the
key
learnings
there
is
that
if
that
is
the
case,
then
it's
our
responsibility
to
communicate
to
the
collateral
applicant
that
that's
actually
what
happened
and-
and
we
saw
in
the
past
that
that
did
not
happen.
So
again.
B
B
B
Why
well?
This
really
gives
teams
the
ability
to
better
plan
their
work,
given
their
development
backlogs.
What
we
don't
want
to
do
is
we
don't
want
to
force
work
into
a
process
where,
where
teams,
especially
like
ces
and
others
like
pe
work
on
a
typically
a
two
week,
cadence
and
we
have
a
sprint
process
and
it's
very
detailed
and
we
follow
it-
every
single
sprint
cycle
and
we
refine
our
work
beforehand.
We
know
we're
going
to
work
on
during
that
cycle.
B
So
if
something
gets
forced
into
that
process,
then
if,
if
that's
the
case
either
we
complete
the
sprint
cycle
or
we
stop
doing
work
and
task
switch,
and
then
we
move
on
to
new
work.
That's
a
very
disruptive
process
for
anyone.
That's
done
software
development,
so
any
of
these
mips
that
have
suggested
a
forced
implementation,
a
prioritization
or
blocking
really
impedes
that
process,
and
it's
important
to
understand
it
does
not
help
us
and
in
fact
it
adds
time
to
the
overall
collateral
onboarding
process
again.
Please
keep
that
in
mind.
B
The
last
part
of
the
implementation
is
the
right
to
spell
now.
The
spell
is
code
that
actually
onboards
the
collateral
into
the
maker
protocol,
and
then
we
publish
the
executive
vote
now.
The
executive
vote
not
only
includes
new
collateral
to
onboard,
but
a
variety
of
parameter
changes
to
reflect
the
governance
process,
ratification
of
changes
to
the
protocol
once
the
on-chain
executive
vote
is
approved
by
mko
holders,
the
spell
is
executed
and
then
the
new
collateral
is
officially
onboarded.
B
B
Yeah
I
mean
I
spend
a
fair
amount
of
my
time.
One
of
the
one
of
the
the
the
services
that
I
offer
as
the
facilitator
of
ces
is
that
I
I
encourage
applicants
to
reach
out
and
to
ask
me
questions
about
the
process.
I'm
I'm
here
to
help,
and
that's
that's
one
of
the
main
one.
One
of
the
roles
that
I
do
as
a
facilitator
is
to
help
provide
a
business
advisory
about
the
processes
that
someone
might
go
through.
I
mean
the
proposer.
B
The
collateral
is
the
expert
with
their
collateral,
we're
the
expert
of
the
dow
in
the
process.
So
when
they
have
questions,
it's
very
natural
to
to
assume
that
you
would
have
someone
to
ask
questions
too.
This
could
happen
in
the
forum.
It
could
happen
on
discord.
We
have
plenty
of
public
channels
to
have
that
happen,
or
you
can
reach
out
me
directly.
So
I
can.
I
can
share
my
thoughts
and
learnings
with
the
teams
that
are
all
morning
collateral,
so
it's
really
nice.
B
B
You
know
one
of
the
things
that
I'll
also
about
thomas
is
that
I
spend
a
fair
amount
of
time.
Just
one
of
the
observations
is
that
we
throw
around
a
lot
of
technology,
and
we
talk
about
mips
and
you
know,
myths
are
just
the
maker
improvement
proposals
are
just
that
they're
necessary,
because
that's
what
defines
how
the
maker
dow
governance
system
works.
B
B
It's
a
set
of
smart
contracts
that
allows
us
to
do
something
special,
depending
upon
the
use
case
of
the
collateral
that
we
want
to
onboard.
So
it's
important
that
we
understand
that
if
someone
wants
to
utilize
a
technology,
that's
great
that
may
or
may
not
be
applicable,
given
the
type
of
collateral
that
an
applicant
wants
to
onboard.
B
So
the
other
thing
that
I
would
suggest
is
that
we
also
provide
a
technical
advisory
service
in
the
core
unit
that
will
sit
down
with
the
the
collateral
applicant
and
describe
you
know
they
could
describe
what
they're
trying
to
do
and
we
can
recommend
what
we
think
would
be
the
best
fit
based
upon
the
type
of
collateral
they're
trying
to
onboard
and
again
that's
something
that
we
provide.
It
can
happen
at
any
time,
preferably
before
an
applicant
files,
a
a
collateral
application.
A
B
So
I
think
it's
important
to
understand
the
preparation
work
in
q1
that
led
to
the
collateral
process
updates
we
published
last
week
at
the
beginning
of
the
year
meetings
for
the
collateral
stakeholder
alignment
calls
began
for
on
and
off
chain
collateral.
We,
we
did
a
little
work
before
the
end
of
the
year,
but
but
we
really
formally
did
that
at
the
beginning
of
the
year,
and
I
really
appreciate
govcoms
and
scs
for
coordinating
facilitating
these
calls.
B
Since
many
core
units
are
involved
in
this
and
and
before
these
meetings,
it
was
really
challenging
to
get
this
cross-functional
group
together
due
to
competing
priorities
and
the
lack
of
understanding
on
overall
dow
objectives.
I
appreciated
the
initial
work
of
david
and
louder
and
now
thomas
contributed
to
the
organization
and
facilitation
of
these
meetings.
B
Tenacity
would
be
the
word
that
I
would
use
in
facilitating
these
early
meetings.
It
took
a
number
of
meetings
before
we
got
into
a
cadence
and
everyone
fully
understood
the
importance
of
the
initiatives
and
and
what
we
were
doing
and
what
was
odd
is
that
at
that
time
is
that
we
had
initiative
work.
We
had
ongoing
work.
We
had
implementation
work
that
was
all
mixed
in
to
to
these
meetings
and
it
took
a
little
time
to
figure
out
like
exactly
what's
what
and
what
needed
to
be.
Where
and
an
alpha
joke
around
about.
B
You
know
in
a
centralized
world,
you
know
everybody
would
have
gotten
the
marching
orders
in
one
meeting
and
by
you
know
you
know
and
very
quickly.
You
know
we
would
have
brought
this
process
together,
but
you
know
this
is
a
dow
and
it
works
a
little
bit
differently.
So,
by
the
end
of
a
quarter
at
the
end
of
this
quarter,
the
last
quarter,
it
was
really
apparent
that
we
needed
at
a
specific
meeting
for
the
ongoing
nature
of
our
collateral
onboarding.
B
B
We,
we
then
moved
into
onto
the
assessment
and
the
recommendations
of
the
current
collateral
onboarding
process,
and
you
know,
let's
just
say
that,
asking
for
feedback
and
getting
everyone's
feedback
in
a
timely
manner.
Well,
it's
not
that
easy
everyone's
busy
and
I
realize
I'm
not
the
highest
priority
on
most
people's
list.
Believe
I'm
not
taking
any
of
this.
Personally,
we
collected
what
we
could.
We
made
the
recommendations
and
we
started
with
the
implementation
when
I
say
implementation,
implementation
of
the
changes
and
there
were
some
failed
attempts.
B
For
example,
you
know
we
were
looking
at
a
pre-mep
process
and
but
that
didn't
go
anywhere.
You
know
what
we've
done
has
been
a
driving
force
for
the
collateral
process.
Changes
that
have
happened
this
quarter.
There
was
also
work.
We
did
on
gaining
consensus
on
modifying
portions
of
the
mips
6
and
mips
7
and,
as
I
mentioned,
the
mips
6
is
an
application
template,
but
it
was
in
need
of
an
overhaul
because
the
questions
didn't
accurately
represent
what
we
needed
to
see
inside
of
the
application.
B
C
B
A
B
So
the
last
slide
here
I
just
want
to
talk
about
our
collateral
onboarding
phase
two
so
q1
was
about
learning
and
and
building
the
foundation
for
the
working
q2
and
beyond.
Well,
we've
done
a
lot
of
in
internal
work
between
the
core
units.
A
lot
remains
to
ensure
that
all
the
key
stakeholders
are
aligned
and
it's
important
to
understand
the
difference
between
alignment
and
agreement.
B
For
me,
when
there's
an
identified
issue
and
when
there's
already
defined
process,
my
first
step
is
to
take
a
big
step
back,
collect
information
and
then
move
forward
again,
because
feedback
is
a
critical
component
to
surfacing
the
solution
or
a
solution
that
will
bring
alignment
as
it
relates
to
our
collateral.
Onboarding.
B
The
goals
for
collateral
onboarding
in
phase
two
are
what
I'm
calling
the
big
four
transparency,
communication,
prioritization
and
commitment.
Implementing
change
with
some
of
these
is
pretty
easy
and
straightforward.
For
example,
one
of
the
first
deliverables
in
q2
was
revising
the
collateral
status
index.
B
We
did
verify
the
statuses
of
the
collateral
that
was
greenlit
using
not
only
the
new
collateral
application
template
the
one
that
was
recently
ratified
on
monday,
as
well
as
the
mips
six
guidelines
that
nikolai
had
published
last
week
as
well,
so
that
work
is
complete.
There
are
a
couple
of
collaterals
we're
still
waiting
for
input
on,
but
essentially
that's
complete
and
it
really
cleaned
up
the
list.
A
lot
now
for
the
offchain
collateral,
the
team
will
be
updating
the
applicants
of
the
remaining
greenlit
rwas
due
to
the
ratification
of
mip-67.
B
This
is
and
and
will
remember
and
his
team
will
be
making
those
posts
shortly
to
those
applicants
to
get
a
read
on
how
they'd
like
to
move
forward.
I
mean
this
has
already
cleaned
up
the
collateral
status
index
tremendously
and
it's
providing
us
much
better
guidance
on
where
collateral
is
at
in
our
process
and
the
next
steps.
B
B
In
addition,
as
I
mentioned
to
our
current
business
and
technical
advisory
work,
we're
doing
outreach
in
the
community
to
better
explain
again
the
collateral,
onboarding
process,
gather
feedback
and
continuing
to
use
this
as
inputs
into
modifying
the
process.
I
mean,
let's
face
it.
This
has
to
work
to
support
the
needs
of
the
maker
protocol.
B
I
also
want
to
specifically
call
out
prioritization
and
commitment
the
the
collateral
status
index
that
is
published
in
the
form
has
a
prioritization
system.
Now
again,
that
was
one
component
to
assist
us
with
us
being
the
collateral
stakeholders
and
prioritizing
the
collateral
and
again,
I
also
want
to
reinforce
that
we'll
continue
to
make
improvements
in
that
area
as
we
work
through
the
face
to
feedback
and
and
process
changes,
which
will
also
include
mip
changes
this
time,
so
it
will
be
a
pretty
significant
overhaul
last
and
maybe
most
important.
A
Thank
you,
robert.
That
was
really
great
information
and
thank
you
for
sharing
that
with
us
about
where
we've
been
and
where
we're
going
with
collateral
onboarding.
I
do
want
to
encourage
any
comments
or
feedback
if
anyone
has
them,
but
would
leave
this
few
minutes
for
open
discussion
as
a
reminder
to
please
go
and
take
a
look
at
the
latest
information.
C
Hey
robert,
I
have
a
good
question,
so
I'm
curious
the
difference
in
experience
between
the
first
version
of
collateral,
onboarding
and
the
second
version
from
the
perspective
of
a
collateral
applicant.
So
you
know
for
the
last
few
quarters.
A
collateral
applicant
would
have
put
up
a
nipsticks
proposal
and
then
basically
it
would
have
gotten
streamlined
into
the
collateral
green
light
poll
process
and
then,
depending
on
its
merits,
it
would
either
get
put
on
the
backlog
forever
or
it
would
kind
of
get
picked
up.
C
It
would
get
some
assessments
and
it
would
it
would
progress
to
a
government's
poll
before
eventually,
all
the
implementation
stuff
resulted
in
an
executive
that
fully
implemented
the
collateral.
So
there
was
the
experience,
basically
that
you
put
up
the
application
and
then
basically
there
would
be
no
communication
unless
something
happened.
So
what
is
the
difference
in
the
process
now
for
a
millisecond.
B
B
B
A
lot
of
that
just
doesn't
apply,
but
what
does
apply
inside
of
our
collateral
application
and
how
do
we
move
certain
types
of
collateral
very
quickly
through
the
system,
because
we've
already
done
a
lot
of
the
work
and
we
also
want
to
match
the
mips
so
right
now
we
have
mips
6
through
12
and
then
6
through
12,
technically
define
the
process
of
collateral
onboarding.
A
lot
of
that
is
outdated
or
has
references
to
things
that
don't
really
make
sense.
B
So
we
want
to
make
sure
we
have
a
complete
update
of
that
and
we
have
one
process.
That's
defined.
That
then
allows
us
to
be
able
to
say:
oh,
hey,
here's,
this
type
of
collateral
and
here's
the
opportunity
yeah.
Let's
move
it
this
way
through
the
application
process,
so
we're
very
consistent
and
clear,
and
no
one
has
to
guess
on.
Do
I
do
a
mip?
Do
I
do
a
signal
request?
Do
I
do
a
mip
six
application?
B
C
Yeah
I
got
it,
I
got
it
yeah
and
I
guess
that's
a
part
of
the
challenge
where
it's
like.
You
know
there
are
new
collaterals.
We
want
to
onboard
as
a
protocol,
but
then
there's
also
a
new
product
that
might
be
a
remix
of
existing
collaterals.
Like
you
know,
eb
c
wrapped,
you
know,
stick
b
c
whatever
and
then
there's
things
like
d3ms,
which
in
their
own
right
are.
C
They
are
like
new
collaterals
but
they're
like
a
whole
separate
thing
and
they
involve
a
lot
of
different
demons,
a
whole
pool
of
collaterals
from
a
separate
protocol
right
and
then
there's
institutional
vaults
which
again
takes
an
existing
collateral.
It's
a
it's
more
of
a
client
relationship
where
it's
like
you
get
a
favorable
set
of
terms
for
a
promise
to
do
a
certain
size
of
die
generation.
C
So
all
of
those
things
yeah
like
being
able
to
very
clearly
communicate
to
the
public
like
what
is
the
process
for
becoming
an
institutional
fault
part?
What's
the
process
of
proposing
a
d3m
for
your
protocol
and
differentiating
that
from
how
do
I
get
my
collateral
at
the
base
level
into
the
protocol?
Like
those.
B
Are
three
separate
things
yeah,
but
you
mentioned
something
that
was
really
key
there.
You,
you
went
to
the.
How
do
I
onboard
my
collateral
using
the
d3m
I'd
like
to
take
the
discussion
to
a
different
place
initially
to
say
here's
the
collateral
I
would
like
to
onboard
and
to
make
sure
that,
from
from
a
business
perspective,
we're
first
doing
the
due
diligence
to
know
why
we're
onboarding
that
collateral?
B
We
have
plenty
of
technology,
we
can.
We
can
find
the
appropriate
technology
or
in
a
lot
of,
in
some
cases,
develop
new
technology
if
there
is
a
product
market
fit
which-
which
I
also
want
to
impress
upon,
is
that
one
of
the
key
aspects
of
this
core
unit
that
I
proposed
from
the
very
beginning
was
having
a
productized
model
for
collateral.
B
So
you'll
be
seeing
more
about
this.
Our
product
manager,
miguel,
it
will
be
the
person
leading
this
effort
has
already
started.
This
is
that
how
do
we
decide
what
markets
that
we
want
to
be
in
and
when
collateral
comes
into
the
protocol?
Is
it
in
market
or
out
of
market?
And
how
do
we
signal
to
the
community
that
we're
looking
for
these
types
of
collateral,
because
we
believe
they
have
the
highest
impact
to
the
supply
generation
of
dye?
Of
course
we
want
demand
too,
so
we
work
very
closely
with
other
core
units.
B
So
there's
there's
a
product
piece
of
this
that
we
haven't
yet
addressed,
which
is
also
part
of
the
discussions
that
will
start
to
roll
out
to
take
a
very
concerted
look
at
the
market.
What
we
believe
is
needed,
publishing
those
guidelines
and
hoping
to
attract
that
type
of
collateral
into
the
maker
system.
Very
much
like
with
a
real
world
sandbox
work
that
luca
did
to
be
able
to
say
hey.
I
believe
there
are
market
opportunities
out
there
that
we
would
like
to
signal
to
have
come
and
be
part
of
the
maker
protocol.
B
Again,
anyone
can
propose
anything
at
any
time.
It's
a
completely
open
governance
process,
but
if
we're
looking
to
operationalize
our
collateral,
onboarding
and
scale
it
because
that's
the
key
here,
we
need
to
scale
it.
Then
we
need
to
look
at
systematic
ways
for
onboarding
our
collateral
and
targeting
places
or
targeting
specific
types
for
us
to
signal
or
go
after
or
even
internally,
core
units.
Writing
the
map
applications
right,
the
collateral
applications.
A
All
right,
wonderful,
so
I
just
I
had
a
quick
question,
quick
thought.
One
of
the
key
points
there
was
onboard
collateral.
You
know
for
someone
who's
not
in
ces
or
may
see
you
know
or
have
you
know
someone
communicate
with
you
hey
I
want
to.
I
want
to
be
a
part
of
you
know,
maker.
Now
I
want
to
on
board
with
collateral.
A
What
would
you
say
is
the
key
communications
if
someone
like
myself
who's,
not
in
your
you
know
your
core
unit
or
others
to
systematically
go
through
the
process
of
saying
hey,
someone
has
communicated
with
me.
What's
what's
the
first
step
or
the
steps
that
you
would
recommend,
I
know
you've
probably
mentioned
them,
but
I
think
that's
an
important
thing
to
maybe
reiterate.
B
Yeah,
the
I'm
just
typing
into
the
the
chat,
so,
okay,
one
of
the
places,
the
resources
that
I
would
always
recommend
people
take
a
look
at
is
the
documentation.
So
if
you
have
any
questions
on
the
process,
you
can
start
there.
You
can
also.
There
is
a
public
channel
for
ces
on
the
maker
official
discord
server.
You
can
reach
out
to
us
there.
You
can
also
join
the
ces
on
discord,
servers
server
and
we
have
public
channels
there.
B
I
will
generate
an
invite
here,
so
if
anyone
would
like
to
join
that,
please
do
so.
You
can
reach
out
to
us
on
our
discord
channel
and
we
can
take
the
conversation
from
there.
You
can,
even
if
you'd
like
to
post
in
the
forums.
So
hey
I've
got
this
idea.
I'd
like
to
get
some
feedback
from
the
community
great
be
completely
self-driven.
B
A
Okay,
all
right!
Well,
I
thank
you
everyone
for
being
here
today
again,
my
name
is
thomas
flitter
engagement
lead
for
governors
communications
corps
unit.
I
can
be
reached
at
my
discord
and
forum
and
my
email.
If
you
want
to
reach
out
to
me,
we
will
have
this
session
uploaded
the
recording
here,
the
next
little
bit,
and
I
want
to
thank
everyone
for
being
here
today.