►
From YouTube: Governance and Risk Call #220 - Jan 5, 2023
Description
Weekly community call for MakerDAO! The agenda and discussion links for this recording can be found here:
https://forum.makerdao.com/t/governance-and-risk-call-220-thursday-january-5th-2023-17-00-utc/19317
A
All
right,
hello,
everyone
and
welcome
this
is
the
220th
governance
and
risk
call
here
at
maker.
Now
my
name
is
Peyton
I
go
by
Pros
11
online
and
I.
Am
one
of
our
governance.
Facilitators
really
grateful
to
be
here
with
all
you
today.
A
This
is
our
first
governance
and
risk
call
Back
in
the
New
Year
2023
today
is
January
5th
for
historian
purposes
and
yeah
joined
by
a
bunch
of
people
who
either
already
contribute,
are
already
familiar
with
the
maker
protocol
or
would
like
to
be
more
familiar.
So
we
really
do
appreciate
all
of
you
that
joined
us
live.
As
you
might
have
noticed,
this
call
is
being
recorded.
So
hello,
if
you're
watching
from
a
later
date
should
be
fairly
simple.
A
Call,
though
just
a
few
rules
we
like
to
go
by
to
help
make
it
a
better
time
for
both
us
here,
live
and
watching
the
recording
later
first
off,
let's
avoid
talking
over
one,
each
other
Just
A
good
rule
to
have
in
general,
but
also
it's
pretty
terrible
for
recording
quality.
A
If
you
can
turn
those
screens
on,
it's
always
nice
to
see
some
people
talking
back
at
us.
Obviously
we
respect
the
pseudonymity
and
all
that
fun
stuff.
So
we
understand
if
you
have
a
reason,
to
keep
your
camera
off,
but
if
you
don't
turn
it
on
and
join
us
always
nice
to
see
who's
joining
us
and
and
what's
going
on
in
their
life,
we
have
reactions
as
well
as
the
chat
that
are
really
useful
for
Zoom,
in
particular,
I
like
the
raised
tan
function.
A
That
helps
me
a
lot
out
as
a
host.
If
you
have
a
question
a
comment,
you
want
to
add.
Basically,
if
you
want
to
join
the
speakers
list,
all
you
need
to
do
is
go
over
to
reactions,
click
that
raised
hand
button
and
it
lets
me
know
you
have
something
to
say
likewise.
If
you
can't
find
that
feature
or
otherwise
aren't
familiar
with
it,
you
can
always
drop
your
question
or
comment
in
the
chat
and
we'll
work
it
in
at
an
appropriate
time.
A
Also
seeing
some
cool
virtual
avatars
always
welcome
as
well
and
a
final
introduction.
I
apologize
for
all
the
rules
as
we
get
started
here,
but
that's
to
introduce
yourself
if
you
can,
while
you
speak,
that'll
help
with
the
recording
and
everyone
getting
along
in
the
call.
A
All
right
so,
as
usual,
we
do
have
a
bit
of
an
agenda
to
get
through
today,
we'll
start
with
our
typical
governance
Roundup
going
over
what's
happening
on
votes
and
in
the
land
of
mips.
Today
we
have
a
really
cool
initiative.
Update
got
some
folks
from
hats
protocol
to
talk
about
what
they're
building
and
why
it
might
make
sense
for
maker
and
then
finally,
we
are
going
to
be
talking
about
our
scope,
Frameworks
for
in-game
and
our
discussion
segment
today.
A
So
if
you're
unfamiliar
with
endgame
it'll
be
quite
the
dive
in
a
a
deep
rabbit
hole
if
you
will,
but
for
those
Vaguely
Familiar,
it
hopefully
will
be
a
pretty
cool
way
to
engage
and
and
learn
about
some
of
the
building
blocks
that
make
in-game
a
thing
and
introduce
kind
of
a
three-part
series
we
have
on
on
talking
about
what
in-game
is
and
and
how
we're
going
to
be
contributing
to
it
all
right.
That's
enough,
regular
rambling
for
me,
I'll
get
into
the
good
old
votes,
rambling.
A
Luckily,
there's
not
too
much
for
me
to
talk
about.
Obviously,
with
the
holidays,
we
took
a
bit
of
a
break.
We
will
have
a
ton
of
polls
coming
out
on
Monday,
so
do
be
mindful
of
those
you're
going
to
hear
from
our
MIP
editors
about
all
the
polls
going
in
for
Mitch
ratification.
We
also
have
a
few
one-offs
to
announce
so
keep
an
eye
out
on
the
forum
for
those.
Likewise,
we
do
have
a
number
of
individual
items
and
the
executive
we're
expecting
for
next
Wednesday.
A
Those
include
delegate
compensation
core
unit
die
budgets
as
well
as
some
mkr
vesting,
so
keep
an
eye
out
for
those
on
the
Forum
in
in
Discord,
we'll
be
keeping
you
updated
on
their
progress
with
that
I
will
turn
the
mic
over
to
our
MIP
editor
I.
Believe
Gala
is
with
us
to
walk
us
through
the
slides
today.
Is
that
right.
B
Yes,
hello
from
guadalfa,
so
today
we
are
in
January
the
formal
submission
window.
For
this
governance
cycle
closed
yesterday
we
have
16
proposals
that
were
formally
submitted.
So
let's
take
a
look
at
them
for
our
top
level
mix.
There's
MIP
92
will
that
will
onboard
100
million
of
PSM
usdc
into
a
bespoke
non-custodial
iron
ball
vault.
B
next
for
our
core
unit
Frameworks
framework,
we
have
the
core
unit
of
boarding.
Proposals
for
golf
comes
for
our
funding
requests.
We
have
two
special
purpose:
funds:
one
is
to
cover
strategic
finances,
expanded
mandate
related
to
real
world
assets
and
another
one
for
developing
a
proof
of
performance
for
Viridian
cluster.
B
We
have
two
protocol
guide,
transfer
requests
as
well,
so
one
is
to
found
the
tech
Ops
for
the
month
of
February
2023
and
want
to
fund
immunified
security
from
December
of
last
year
to
March
2023.
B
B
So
next
we
have
our
proposals
in
RFC.
There
are
a
few
of
them
for
our
top
level:
mips,
there's
midnight,
90,
onboarding,
a
real
world
both
to
acquire
uscc
and
then
purchase
structured
credit
and
money
market
funds,
maybe
91
introducing
the
concept
of
a
Defender
contract
against
governance,
attacks
and
mid
93
purpose
proposing,
and
they
will
utilizing
the
hats
protocol.
B
The
hotspot
allows
for
Real
Time
on
chain
verifier,
verifiable
roles
to
be
maintained
throughout
the
maker
protocol.
As
a
patent
just
mentioned.
This
is
our
initiative
update
today,
so
stay
there
if
you're
interested
and
also
we
have
a
know,
your
MIP
call.
This
is
next
week.
B
B
Next,
we
have
for
the
Amendments
and
removals
there's
an
amendment
proposal
that
modifies
me
41
to
expect
it
some
of
its
processes
and
increase
its
flexibility
and
finally,
for
the
core
unit
framework
proposals.
We
have
core
unit
of
boarding
proposal
for
CSS
CES,
a
budget
request
by
Tech
Ops
and
a
facilitator
onboarding
proposal
for
Nick
0
to
lead
CES
note
that
these
are
not
all
the
purple
the
core
unit
framework
proposals
that
have
have
been
posted
in
the
Forum.
B
However,
those
that
are
not
in
this
list
are
for
now
our
only
placeholders.
B
So,
finally,
for
our
important
dates
as
I
mentioned,
and
this
Monday
all
of
the
proposals,
informal
submission
are
going
on
on
chain
a
certification
pause
for
two
weeks
and
also,
if
you're
planning,
to
submit
a
new
proposal,
you
should
do
it
by
January
the
11th.
That's
the
next
Wednesday,
if
you
wish
for
the
proposal
to
be
eligible
for
February's
cycle,
so
that's
it
for
mips.
Thank
you
very
much.
A
I
appreciate
it
Kelly.
Thank
you,
one
of
our
map,
editors
for
bringing
that
together.
Obviously
a
lot
coming
down
the
pipeline
so
do
pay
attention
to
the
Forum
saying
on
the
voting
portal
starting
Monday
all
right,
so
we
don't
have
a
forum
update
this
week.
Obviously
things
have
been
a
little
bit
more
sparse
with
the
holiday
break.
A
A
Awesome
looks
like
gala's
got
the
chat
covered,
thank
you
and
with
that
I
think
we
will
go
into
our
initiative
updates.
So,
as
we
mentioned
a
couple
of
times
already
we're
going
to
be
hearing
from
the
fine
folks
over
at
hats,
protocol
I'm
actually
going
to
stop
sharing
my
screen.
So
I
can
assist
in
a
demo
and
looks
like
I
see
Nick
on
the
screen
there
hi
Nick,
you
should
have
screen
sharing
Powers
should
you
need
to
use
them
works.
A
C
Okay,
perfect
I
was
asked
to
take
less
than
five
minutes,
so
I'll
go
with
that
guideline
unless,
unless
I
get
another
advice
here,
so
I'll
just
share
a
couple:
slides
I'm
going
to
show
you
the
contract,
so
my
name's
ninty
nick,
you
can
call
me
Nick.
C
C
The
biggest
challenge
we've
seen:
we've
been
working
in
Dallas
for
the
last
two
years
and
we've
lived
this
pain
of
kind
of
disorganization
chaos,
people
running
around
in
discords,
making
social
agreements
trying
to
get
work
done.
It's
it's
really
messy
and
we
think
that
the
key
things
we're
trying
to
solve
are
the
lack
of
clear
roles
and
responsibilities.
The
fact
that
those
roles
are
not
legible
on
chain
for
distribution
of
power
and
access
and
that
Dow
votes
are
not
always
the
most
effective
decision-making
structure.
C
Sometimes
you
want
to
delegate
decision
making
to
a
small
group
or
or
to
an
individual
and
has
helped
you
do
all
this
on
chain.
We
think
about
hats
as
roll
bound
tokens
that
represent
specific
sets
of
responsibilities
and
Authority
for
individual
contributors.
There
are
tokens
that
are
governed
by
the
Dow,
so
their
ERC
1155s
that
have
been
modified
to
not
be
transferable
by
the
people
who
have
them
in
their
wallet,
but
they
are
transferable
by
the
Dow
or
delegate
of
the
Dow.
They
have
specific
scope
of
authority.
C
So
you
get
a
token
ID
that
you
can
connect
to
various
token
Gates
like
Guild,
XYZ
or
collablin,
and
use
that
to
plug
into
your
various
platforms
and
then,
lastly,
they're
built
for
automation,
so
at
first
you'll
have
the
Dow
voting
to
get
Grant
or
revoke
or
transfer
hats,
but
eventually
you
can
bring
your
own
smart
contract
logic
to
Grant
and
remove
hats
under
certain
conditions
and
some
of
the
examples
and
benefits
you
get
here.
This
will
be
my
last
slide
before
we
go
to
the
contract.
C
Is
you
can
kind
of
think
about
a
hat
as
like
a
job
in
a
box?
C
So
once
you
go
through
the
dial
proposal
for
getting
a
hat
to
an
individual
contributor
or
creating
an
entire
hat
tree
of
all
of
the
existing
structure
that
you
guys
have
at
maker
Dow,
for
example,
every
person
will
have
everything
that
they
need
in
order
to
get
their
work
done
in
a
way
that
is,
has
the
single
source
of
Truth
on
chain,
and
this
might
include
things
like
Discord
roles,
multi-sig
signing
Authority
voting
weight
in
off
chain
votes,
access
to
post
to
a
shared
Twitter
account
for
a
core
unit
or
for
for
the
whole
Dow
as
well
as
things
like.
C
You
know,
compensation
in
on-chain
formats
that
could
be
gated
via
the
fact
that
you
have
this
hat
in
your
wallet
as
well
as
accountability,
including
the
removal
of
the
hat
or
in
other
cases,
we've
seen.
People
doing
things
like
staking
eat
on
responsibilities
that
they've
they've
taken.
C
So
I'll
pause
there
for
now
and
move
over
to
the
contract
quickly.
Basically
and
I'll,
send
I'll
send
links
to
this
in
the
chat
as
soon
as
I
finish
talking
through
this.
But
here's
the
the
girly
deployment
of
hats
protocol
beta
V
0.6,
which
is
the
current
deployment,
some
of
the
key
functions
that
are
going
to
be
needed
for
for
the
the
multi-send
transaction,
we're
going
to
do
with
maker
Dow
we'll
be
creating
hats.
C
So
when
you
think
about
creating
an
actual
hat
token,
you
plug
in
the
admin
who,
in
this
case
in
this
case,
will
be
the
Dow
by
default.
There's
the
person
who
can
grant
the
hats
details,
which
can
be
anything
that
you
want
a
hat
name
or
ipfs,
link
a
Max
supply
of
the
number
of
that
particular
hat
token
and
then
eligibility,
which
is
that
area
where
you
have.
You
can
bring
your
own
smart
contract
logic
or
point
to
the
Dow.
C
To
say
this
is
the
this:
is
the
person
or
the
logic
that
will
revoke
the
Hat,
a
toggle
which
actually
turns
the
entire
hat
token,
on
or
off
across
all
of
the
hats
that
are
outstanding.
We
have
a
Boolean
from
mutability,
so
you
can
change
hats
from
mutable
to
immutable
once
you
feel
like
they
are
kind
of
solidly
what
you
need
and,
of
course,
they're
kind
of
like
nft.
So
we
have
an
image
URI
to
include
and
then
minting
hat
happens
separately
from
creating
a
hat
won't
go
too
too
much
more
into
detail
there.
C
You
can
view
all
the
docs
in
our
GitHub
repo,
like
I,
said:
I'll,
send
the
link,
but
the
docs
are
located
here
and
then
we
are
under
myth.
93.,
so
I'll
send
all
these
links
any
questions,
please.
Let
me
know.
A
Right
on
and
appreciate
you
coming
out
here
to
the
doctor,
snake
and
because
I
got
David
from
from
and
Spencer
I
think
from
hats
as
well.
I
know
we're
gonna
get
more
into
like
the
nitty-gritty
of
like
how
this
can
be
used
for
maker
next
week,
but
I'm
curious.
So
maybe
you
could
spend
a
minute
or
two
just
talking
about
kind
of
Hat's
origin
story
and
why
exactly
decided
to
start
jumping
on
these?
These
governance
problems.
C
Absolutely
we
we
Spencer
and
I
we're
collaborating
in
the
context
of
raid
Guild,
which
is
for
those
who
don't
know
a
dow,
that's
sort
of
a
freelance,
a
group
of
freelance
designers
developers
account
managers,
product
managers
who
came
together,
I
think
in
2019
or
early
2020
to
basically
serve
develop,
become
a
development
Agency
for
other
web
3
projects,
even
before
it
was
called
web3
building
dapps
in
a
decentralized
way
and
really
testing
out
this
ethos
of
how
do
we
operate
without
managers
and
I
think
that
as
raid
Guild
evolved,
we
started
to
look
at
interesting
mechanisms
that
could
support
accountability
around
specific
roles
and
responsibilities.
C
So
in
raid
Guild
you
get
put
on
a
project
which
is
called
a
raid
you're,
you
might
be
pseudonymous
or
Anonymous,
and
how
do
you
actually
hold
that
person
accountable
to
their
work?
And
how
do
you
give
them
all
access
to
all
the
platforms
that
they
need,
like
the
channels
that
they're
going
to
talk
in
on
Discord
or
access
to?
You
know
client-specific
documents
and
ultimately
like?
C
How
do
you
start
to
hold
people
accountable
to
and
build
reputation
for
the
work
that
they
did,
especially
if
they
came
in
pseudonymously,
so
we
started
building
early
mechanism
there.
We
saw
that
this
was
a
very
common
need
and
Spencer
sent
over
the
the
kind
of
more
formal
architecture
in
April
and
said:
hey
I
think
we
should
work
on
this.
What
do
you
think
and
I
was
super
excited
about
it?
C
We
didn't
even
call
it
hats,
then,
and
David
had
been
organizing
a
network
called
groundwork
which
had
pulled
together
over
60
Dow
leaders,
Dow
stewards,
including
linkla,
from
maker,
who
I'm
sure
some
of
you
know-
and
we
kind
of
could
verify
across
this
entire
network-
that
this
is
such
a
deep
pain
point.
An
opportunity
to
make
Dao's
much
more
effective.
Dows
are
really
awesome
at
being
decentralized,
but
maker
is
one
of
the
few
dials
that
consistently
gets
stuff
done
and
I
think
in
order
to
evolve
this
whole
Space.
C
We
really
need
to
get
to
the
point
of
efficiency,
of
getting
things
done
collaboratively
collectively,
without
giving
up
the
benefits
of
decentralization,
that
that
was
really
get
us
ability
to
share
resources
and
govern
public
goods
as
Sovereign
individuals
coming
together
into
collectives.
A
It's
really
awesome
and
I
think
a
lot
of
us
can
really.
A
You
know
a
lot
of
people
on
this
call
have
seen
maker
through
from
Foundation
to
Dao,
to
this
next
chapter
of
in-game
and
kind
of
the
I
don't
know,
uniting
Factor
seems
to
be
that,
like
it,
you
know
it
all
comes
down
to
coordination,
all
comes
down
to
organization
and
I
think
just
by
default,
we
we
tend
to
use
a
lot
of
like
web
2
tooling,
because
it's
you
know
what
we're
used
to,
and
it
doesn't
always
work
so
well
with
suit
Anonymous
identities.
A
It
doesn't
always
works
so
well
with
the
decentralized
like
Workforce,
so
yeah
I,
don't
know.
I
I
was
very
excited
to
hear
some
of
the
Native
web
3
solutions
that
that
we're
talking
about
here
and
just
highlight
again
like.
Let's
see
you
talked
about
potentially
being
used
in
multi-sigs
like
Discord
gated,
chats
like
organizational
structures
like
it
seems
like
it
really
provides
a
lot
of
sandboxes
to
play
on.
Is
there
a
direction
or
any
area
in
particular
that
that
you're
most
excited
about
that?
A
I
guess
like
if
you
looked
into
the
crystal
ball,
where,
where
do
you
see
hats
having
the
most
impact
in
in
the
next
five
years,.
C
This
is
a
great
question.
I
think
that
you
know
what
we're
kind
of
doing
is
creating
has
tried
to
be
the
most
unopinionated
primitive
that
we
could
create.
That
would
enable
people
to
use
it
as
a
sort
of
structural
Lego
for
organizational
design,
and
that
means
that
we're
not
up.
We
didn't
take
a
particular
angle
on
you
know
how
to
organize
the
roles.
C
So
you
want
to
have
a
dowel
that
you
know
has
a
traditional,
hierarchical
structure
or
you
want
to
introduce
holocracy
or
you
want
to
try
if
you're
Truckee
or
any
kind
of
model
of
Authority
delegations
between
individuals
you're
free
to
do
that
with
Hats
protocol.
C
I
think
where
it
becomes
really
amazing
and
kind
of
where
David
is
a
secret
weapon
for
this
project
is
when
we
can
create
an
entire
ecosystem
of
people
who
are
building
organizational
structures
and
kind
of,
like
you
know,
small
compositions
of
Legos
that
are
easily
forkable
and
replicatable
eligibility
contracts
that
you
can
kind
of
pick
up
off
the
shelf
and
use.
C
That
brings
the
logic
for
when
someone
should
have
their
hat
revoked
and
that
all
of
those
people
are
are
coming
together
and
kind
of
advancing
the
state
of
the
art
of
human
coordination
through
organizational
forms
that
we
I
think
together
we
can
push
forward
The,
Cutting
Edge
of
what
an
organization
of
human
beings
actually
is,
so
we're
we're
creating.
You
know
the
Hat's
Dao
to
support
the
evolution
of
the
space
using
the
hats
protocol
as
a
primitive,
and
we
couldn't
even
imagine
the
amazing
stuff.
A
Right
on
well
I
feel,
like
I've,
been
monopolizing
some
of
the
question
space
so
definitely
want
to
encourage
others
to
ask
I
saw
Francis
and
our
chat.
One
of
our
recognized
delegates
was
asking
if
this
result
of
an
inbound
or
an
outbound,
lead
kind
of
our
collaboration
with
Hats,
wasn't
really
sure
how
to
answer
that
other
than
say,
like
I
got
connected
with
Nick
and
bogoton.
A
We
really
hit
it
off
after
chatting
about
what
hatz
was
trying
to
do,
and
you
know
I
I
definitely
noticed
a
lot
of
governance
challenges
that
have
been
plaguing
me
kind
of
present
on
on
Nick's
tinkering,
so
that
was
kind
of
how
this
came
to
be
and
we're
still
figuring
out
the
best
way
to
to
work
together
and
and
place
it
with
the
ecosystem.
But
yeah
I
mean
it's.
A
It's
pretty
clear
to
me
that
there
there
will
be
a
lot
of
opportunities
within
the
in-game
framework
to
to
work
with
Hats.
A
So
if
you
know
there's
a
way
that
works
organization-wide
great,
if
it's
more
of
an
individual
like
kind
of
Lego
great
mostly,
my
kind
of
aim
is
just
to
make
people
more
familiar
with
it
and
and
all
the
cool
things
that
we're
trying
to
do,
particularly
because
a
lot
of
things
delegates
have
asked
about
like
token
gated
chat
and
involved
owners
chat
and
more
multi-sig
security,
like
our
our
direct
applications
for
hats.
So
it's
clear
there's
a
lot
of
similar
surfaces,
we're
working
on
there
well.
E
A
A
hand
from
Raphael
another
one
of
our
recognized
delegates.
If
you
want
to
take
it
away.
F
Thanks
Peyton
yeah
Nick,
thanks
for
the
demo
for
a
short
demo
or
the
deck,
and
what
I'm
wondering
about
is
like
how
does
the
role
management
work
and
like
especially
with
decentralization
in
mind
like
it,
seems
that,
like
worst
case,
that
I
can
imagine
is
that
it's
kind
of
like
a
Microsoft
active
directory
for
the
Arts
and
then
there's
some
poor
person
who
has
to
sit
somewhere
and
manage
all
of
that
and
maybe
I
think
I'm
sure
you
came
up
with
something
that's
much
more
down
native.
F
C
100,
it's
funny
that
you
bring
up
active
directory
because
someone
someone
else
made
that
analogy,
and
it
really
helped
me
understand
kind
of
the
progression
of
you
know
what
what
has
existed
in
the
past
and
what
we're
doing
now
and
how
it's
related.
It
is
kind
of
like
that.
The
the
one
chain
one
difference
I
would
highlight
to
answer.
C
Your
question
is
really
around
the
ability
for
any
hat,
to
create
child
hats,
underneath
it
so
and
then
manage
those
using
the
eligibility
contracts
so
that
we
separated
granting
and
revoking
intentionally
granting
is
done
by
you
know
any.
If
you
hold
a
hat,
you
can
create
an
ad,
a
child
hat.
That
will
be
that
you
would
be
the
admin
of,
and
then
once
you
have
created
that
hat
you
can
also
mint
that
hat
to
whichever
addresses
you,
you
find
that
you
should
do
that
too.
C
The
eligibility
contract
or
the
address
that
goes
into
the
eligibility
field
is
really
the
the
revocation
logic,
so
you
might
want
to
create
and
mint
the
hat,
but
make
it
so
that
some
other
Council
of
evaluators
someone
else
in
the
core
unit
is
responsible
for
revoking
the
hat
or
or
more
likely.
What
we
keep
seeing
as
a
as
an
interesting
use
case
is
adding
some
specific,
smart
contract
logic
that
says:
okay.
C
If
this
person
hasn't
signed
the
multi-sign
in
the
last
60
days,
if
this
person
hasn't
been
compensated
by
this
address
within
you
know,
the
last
two
epochs
then
automatically
remove
their
hat
or,
if
they
drop
below,
say
a
certain
amount
of
delegated
mkr,
as
it
would
be
another
type
of
logic
that
we
could
bring,
and
that's
really
how
hats
maintains
the
decentralization
of
kind
of
the
responsibility
of
holding
people
accountable
to
their
individual
roles
and
obviously
the
other
thing
I'll
mention
is
that
hats
can
be
worn
by
individuals
EOS,
but
they
can
also
be
worn
by
multi-cigs
Dow.
C
We
can,
you
know,
send
one
the
top
hat
to
the
pause
proxy
or
a
contract
that
is
managed
by
the
pause
proxy,
so
they
can
obviously
be
sent
to
contracts
as
well.
So
we
we
benefit
from
utilizing
all
the
existing
decentralization
of
the
core
Dow
contracts
and
empower
the
core
Dow
contracts
to
use
hats
protocol
in
this
kind
of
tree-like
way.
Does
that
answer
your
question.
F
A
couple
of
months
ago,
four
of
us
became
artistic
sinus
to
manage
the
velodrome
airdrop
to
make
a
dial
and
I
really
enjoyed
the
process
because
it
was
so
permissionless
and
I
think
this
is
exactly
what
attracts
me
to
crypto
and
it
was
basically,
there
was
a
thread
on
the
Forum
and
there
was
a
agreed
that
this
should
happen
and
then
should
we
just
spun
up
the
multisig
and
we
got
going
right
like
there
was
no
no
permission
necessary,
so
I
think.
How
can
that
happen
on
heads
right
like?
F
How
can
we
keep
that
that
permissionlessness,
because
I
think
this
is
really
one
of
the
of
the
tenants
that
enabled
the
house
and
and
I
will
unlock
Dow
productivity
in
the
future?
I
think.
C
Yeah,
absolutely
we're
working
right
now
on
ways
of
people
being
able
to
create.
Just
like
you
could
just
create
a
multi
Sega
and
get
started
permissionlessly.
You
should
be
able
to
create
a
branch
of
hats
and
then
later
graphed
it
onto
a
tree.
So
that's
definitely
functionality
that
we
see
as
important.
C
C
C
That
hat
and
now
the
Dow
has
that
kind
of
ability
to
revoke,
to
make
sure
that
designers
are
are
the
right
people
and
make
sure
that
there's
no
Bad
actors
acting
on
that
multi-sig,
because
the
Dow
is
really
delegating
that
authority
to
to
the
four
of
you
say
as
an
example
as
multi-six
signers.
So
it
creates
a
little
bit
more,
a
slight
amount,
more
overhead
and
a
little
bit
a
lot
more
security
for
the
Dow
itself.
A
We
did
have
one
more
question
in
chat
and
I.
Think
I'll
toss
that
to
you
guys
and
then
probably
call
it
there.
You
know
as
a
reminder:
we
do
have
a
dedicated
session
next
week,
so
I'll
get
a
hand
from
Patrick.
If
you
want
to
say
something,
first
go
for
it.
D
Yeah
I
mean
I
was
happy
to
wake
up
the
question
about
I'll
go
now.
I
was
just
wanting
to
flag
a
use
case.
That
kind
of
convinced
me
that
this
could
be
helpful
for
for
making
I'm
sure
Peyton
won't
necessarily
mind
me
saying
when
he
first
pitched
this
to
me.
I
was
quite
confused
about
why
we
would
bother-
and
you
know
how
is
this
that
useful,
but
a
recent
example
of
where
we
would
we
really
could
have
used.
Something
like
this
would
have
been.
D
The
recent
interim
facilitator
appointment
process
that
we
went
through
on
the
Forum,
so
we
had
to
get
votes
from
all
of
the
current
active
facilitators
on
candidates
for
whether
they
accepted
them
to
become
the
interim
facilitative
CES,
and
the
first
round
was
just
a
straight:
yes,
no
vote,
so
we
could
use
the
Forum
architecture
for
that.
That
worked
fine,
but
then
the
when
that
we
needed
to
proceed
to
the
fallback
process
which
used
Irv
to
run
off
audience.
We
actually
couldn't
do
that
using
using
the
Forum
architecture.
D
So
if
we
had
a
hat
set
up
where
each
facilitator
had
a
hat
that
they'd
been
granted
by
by
the
Dow
effectively,
you
could
have
set
up
a
snapshot
instance
and
use
them
for
voting,
and
that
would
have
actually
solved
the
entire
problem.
D
The
the
at
the
end
result
of
how
we
had
to
do
it
was
to
basically
send
everyone
a
Discord,
DM
say:
please
rank
your
candidates
and
then
put
it
into
a
spreadsheet
and
make
that
generate
a
winner,
and
so
so
that
was
a
really
good
example
to
me
of
how
we
could
use
this,
for
something
that
would
have
saved
us
a
hell
of
a
lot
of
time
and
a
lot
of
effort
would
have
taken
five
minutes
instead
of
a
couple
of
hours
and
so
just
wanted
to
provide
some
color
there
for
potential
other
potential
use
cases
and
the
things
that
we've
come
across
since
looking
at
this
protocol
and
saying,
oh
actually,
hats
would
be
really
good
for
this.
D
So
just
wanted
to
provide
that
that
insight.
There.
C
A
Yeah
cool
so
I
do
like
that
kind
of
Client
Services
question,
but
maybe
we'll
table
that
to
the
call
next
week
and
give
people
a
little
lead
in
a
reason
to
attend
and
yeah
I
really
appreciate
you
guys
taking
the
time
to
to
come
here
and
seems
like
we've.
We've
got
plenty
to
discuss
so
look
forward
to
the
follow-up
next
week.
C
Absolutely
thanks
so
much
for
having
us
feel
free
to
reach
out
on
Twitter
or
Telegram
and
yeah.
We'll
see
you
next
week
thanks.
Everybody
awesome.
A
A
Should
be
back
up
and
running
there
all
right
huge
thanks
again
to
the
guys
at
hats
that
call
again
it's
next
week
on
Wednesday,
so
take
a
look
at
our
public
calendar
and
make
sure
you
don't
miss
it
that'll.
Take
us
into
our
discussion
segment
of
this
call.
We've
got
a
little
less
than
an
hour
of
our
typically
scheduled
time,
and
we
wanted
to
kind
of
kick
off
the
year
talking
about
in-game
Scopes.
A
A
A
The
interim
CS
facilitator
help
walk
us
through
this
stuff,
but
our
plan
is
kind
of
you
use
this
breakdown
of
Scopes
and
Frameworks
subdials
and
ecosystem
actors,
and
then
just
the
game
theory
of
in
game
to
kind
of
give
three
little
presentations
during
these
gnrs
open
up
some
discussions
and
help
people
kind
of
see
where
they
can
contribute
and
get
get
a
better
understanding
of
in-game.
A
G
No
no
appreciate
the
introduction
you're
a
natural
already
at
this,
but
yeah
like
Peyton
highlighted
today's
presentation
is
primarily
going
to
focus
on
Scopes
and
Frameworks,
we'll
be
diving
into
the
terminology,
a
little
bit
end
with
a
call
to
action
and
then
happy
to
answer
any
questions
there.
If
you
could
hop
to
the
next
slide,
what
we
back
one
there
we
go.
G
What
we're
looking
at
here
are
the
12
defined
Scopes,
and
each
scope
has
an
accompanying
framework
that
defines
basically
the
entire
ecosystem
and
operations
of
maker
Dao.
On
the
top
level,
we
see
the
four
primary
Scopes,
which
relates
to
the
products
of
maker
dough
and
beneath
that
we
have
secondary
and
tertiary.
G
The
best
way
to
think
about
this
is
that
the
top
level
the
the
primary
product
Scopes
are
intended
to
receive
the
most
attention,
the
most
funding,
the
the
most
expert
input
into
guide,
the
protocol
towards
the
feature
path
of
resiliency
and
then
beneath.
It
is
more
of
like
the
Operational
Support
Scopes
that
are
required
to
enable
the
primary
Scopes
and
we'll
show
an
example
in
a
a
couple
slides,
but
taking
a
a
deeper
dive
into
what
a
scope
is
on
the
next
slide.
G
This
is
the
meeting
point
between
dvcs
delegates
and
then
the
facilitator
councils
and
tribunals
to
take
the
strategy
that
makerdale
wants
to
implement
for
the
products,
as
well
as
the
learnings
from
the
operations
of
the
decentralized
workforce
and
create
this
again
meeting
point
or
discussion
to
continuously
improve
our
operations
by
using
what
we
learn
documenting
it
and
making
sure
that,
in
a
decentralized
environment,
where
you
have
a
lot
of
diverse
teams,
working
separately,
that
they're
able
to
have
shared
learnings.
G
If
you
could
hop
back
one
real,
quick
there
we
go
so
again.
This
is
Focus
areas.
So
all
the
Scopes
have
the
dvcs
and
the
council
centripunals
as
the
the
working
group.
If
you
will
so
it,
the
graphic
demonstrates
there
that
the
dotted
line
separates
the
workforce
and
and
some
of
the
day-to-day
discussions
about
operations,
maybe
some
conflicts
and
suppresses
that,
so
that
the
strategy
can
be
the
primary
focal
point
from
there
as
well.
G
It
really
is
the
central
reference
point
for
all
the
organizational
actions,
because
this
primary
document
again
is
going
to
be
used
by
several
different
players
to
assess
if
operations
are
running
smoothly,
if
there
needs
to
be
certain
structural
improvements
or
operational
improvements,
defining
a
A
sub-dow
or
a
ecosystem,
actor's
quality
of
work
and
really
just
become
a
rubric.
So
if
we
advance
ahead,
the
Scopes
again
is
the
team
that
works
on
defining
the
framework.
So
the
framework,
then,
is
the
primary
output
for
guiding
the
workforce.
G
Everything
that
needs
to
be
done
should
be
documented
and
detailed
within
this
framework,
because
it
enables
the
meritocracy
and
equality
of
the
workforce,
then,
where
the
best
experts
to
contribute
knowledge
and
expertise
to
how
the
Dao
is
working
is
in
the
position
to
do
so.
This
also
provides
Clarity
and
removes
ambiguity
from
work
through
regulating
certain
actions
defining
where
reports
should
go
defining
when
reports
would
come
out
in
certain
Cycles,
as
well
as
creating
this
platform
for
again
enacting
improvements.
G
A
lot
of
discussion
and
research
has
gone
into
this,
especially
through
the
sustainable
ecosystem,
scaling
projects
of
conducting
The
Forum
audit
it
and,
and
trying
to
really
extract
as
much
knowledge
as
possible
through
that
exercise,
but
I
think
everybody's
very
familiar
with
the
form.
It
really
is
this
expansive
environment,
where
just
about
anything
can
be
posted,
but
by
refining
this
and
forming
the
different
segments.
G
What
we're
expecting
to
see
is
that
as
business
operates
as
usual,
will
be
able
to
assess
the
quality
of
that,
and
then,
if
there
are
these
these
points
of
Confrontation,
we
can
make
it
productive
so,
instead
of
just
resulting
in
a
lot
of
noise
on
the
Forum,
which
historically,
we've
potentially
seen
in
the
past,
what
this
creates
then
is
a
specific
process
or
exercise
then
to
enact
those
improvements
for
sustainable
change
and
then,
finally,
as
well,
something
that
is
is
formally
being
introduced
through
the
end
game
plan.
G
Is
this
concept
of
penalties,
so
it
gives
governance
fangs
where
grab
Alpha
facilitators
for
an
example
have
to
try
to
assess
well
what
is
the
best
course
of
action
if
a
rule
is
broken
about,
the
only
tool
that
they
have
right
now
is
to
bring
a
vote
to
governance,
to
assess
you
know
what
options
should
follow
to
correct
that
this
is
going
to
clearly
Define,
then
monetary
penalties
or
potentially
other
restrictions
for
sub
thousand
ecosystem
actors.
G
A
Before
we
move
in
there,
I
think
Rafael
had
a
relevant
question
on.
A
Are,
if
you
don't
mind
hitting
that
before
we
go
on
to.
F
The
next
yeah
sure,
let
me
know
if
this
is
the
best
time
or
or
I
can
we
can
go
through.
H
A
F
Unclear
like
what
Frameworks
exactly
are,
you
know,
you
know
like
a
physical
sense
or,
let's
say
structural
sense,
that
is
that,
like
a
bunch
of
documents
that
gets
iterated
on
and
that
kind
of
govern
these
things
or
is
it
the
whole
process
as
well
like
the
the
meetings,
the
work
sessions
that
then
kind
of
iterate
on
the
on
these
outputs
that
you
outline.
G
Yeah,
so
that's
an
excellent
question.
At
the
top
level,
the
scope
is
where
the
process,
the
engagement,
the
discussions,
the
quarterly
meetings,
are
defined,
and
then
the
framework
itself
is
a
document
similar
to
a
MIP.
G
If
somebody
could
grab
the
link
from
The,
Forum
I'd
appreciate
the
help,
but
roon
has
posted
an
example
or
a
preliminary
draft
for
the
third
scope
being
the
real
world
asset
collateral
framework,
and
what
that
shows
is
that
there's
certain
rules
that
define
ideal
collaterals,
there's
engagement
processes
for
the
workforce
to
follow,
but
then,
at
the
top
level,
where
the
framework
is
worked
on
within
the
scope,
the
processes,
the
quarterly
meetings
and
things
like
that
are
then
defined
in
the
Constitution
and
the
Constitution
itself
will
be
a
MIP
in
its
own
right.
G
That
defines
how
the
Dao
and
these
different
actors
need
to
engage
around
improving
the
framework.
That
again,
is
just
something
similar
to
a
MIP
that
defines
how
the
work
should
be
done
for
the
workforce
then,
and
the
penalties
Associated
to
breaking
them.
A
Well,
thanks
Richard
and
I
posted
that
link
to
the
real
asset
collateral
framework
draft.
If
people
want
to
take
a
look
and
see
what
he's
talking
about
there,
but
I
think
that
should
be
good
to
move
on
for
now
and
yeah.
Please
do
drop
questions,
especially
if
they're
enrollment
for
the
slide
we
can
address
them
before
we
go
on.
G
So
something
important
to
hear
to
highlight
going
back
to
that
first
slide,
showing
all
12
and
how
there's
the
different
layers
at
the
top.
We
do
have
the
primary
scope,
but
there
are
influenced
by
the
second
and
third
tier
Frameworks,
so
using
decentralized
collateral
as
an
example,
the
primary
scope
would
again
Define
the
certain
ideal
collateral
types
or
targets
or
goals,
and
how
assessments
need
to
be
done
and
shared
within
the
community.
But
then
beneath
that
operating
the
decentralized
collateral
say
once
it's
been
onboarded.
G
The
stability
and
liquidity
secondary
scope
with
an
influence
how
the
decentralized
scope
does
managed.
Another
example
on
the
right
would
then
be
the
interface.
So
how
is
the
front
end
presenting
the
distance
rise
collateral
across
the
the
various
sub-dos?
That
would
also
influence
that
particular
scope
or
framework
and
Finance
again,
which
is
primarily
being
defined
as,
as
you
know,
what
sort
of
metrics
and
Reporting
is
required
would
influence
the
scope
level
above
it,
which
would
then
influence
the
the
primary
scope.
G
So
it
is
this
sort
of
waterfall
where
at
the
top
it
it,
the
primary
Scopes
would
receive
the
most
finding
to
enact
and
and
deliver
through
operations
the
the
strategy
that's
defined,
but
beneath
it
is
really
I
think
where
a
lot
of
the
values
created,
because
it
it
takes
the
concept
of
saying
you
know
this
is
a
product.
G
But
then
how
do
you
support
a
product
and
its
entire
life
cycle
and
and
the
entire
structure
of
Scopes
and
Frameworks
is
then
built
to
define
the
human
processes
and
the
discussion
and
collaboration
about
making
them
better,
but
then
also
the
operations
for
again
the
complete
life
cycle.
So
it
isn't
like
we're
onboarding
an
asset
and
not
able
to
support
it.
G
The
the
entirety
of
the
life
cycle
for
a
feature,
product
or
or
even
a
growth
campaign
is
defined
thoroughly
and
should
be
taken
into
consideration
by
the
workforce
as
they're
working
to
enact
the
the
various
projects
so
before
moving
on
to
next
slide
happy
to
pause
here.
If
there's
any
questions
as
well,.
A
I
got
one
I
could
maybe
a
fire
retro,
so
I
know
like
a
common
shortcut.
I
I
use
this
right,
I.
Think
of
Frameworks,
as
kind
of
like
the
new
mips
right,
like
the
kind
of
like
the
new
bylaws,
the
new
ways
which
we
Define
work,
but
that
analogy
definitely
Falls
a
little
bit
short
I.
Think
it's
helpful
for
just
kind
of
getting
your
your
mind
around
like
okay.
How
does
this
puzzle
piece
plug
in?
A
G
Yeah
another
great
Point
and
I
I
think
that's
going
to
be
highlighted
as
we
move
deeper
into
the
year,
where
the
other
supporting
structures
of
endgame
really
come
into
fruition.
A
primary
example
would
be
the
unified
coordination
toolkit
where
the
logic
of
these
Frameworks
are
built
in
to
the
the
the
actual
user
interface
of
how
these
styles
are
going
to
be
communicating
to
the
core,
so
one
example
could
be.
G
G
Potentially,
these
it
could
be
a
very
simple
you
know,
drop
the
link
for
the
report
here
drop
the
link
for
the
report
here
and
then
that
will
start
and
feed
into
the
the
Scopes,
the
dvcs,
the
actual
meetings
to
make
that
information
very
organized,
very
accessible
and
and
I
I
think
very
comparable.
Where
you
know,
we
see
consistent
formatting
of
reports
across
different
posts,
but
to
have
that
in
a
more
structured
environment
where
it's
easier
to
navigate.
G
It
just
reduces
the
cost
of
information
and
and
makes
the
logic
that
we're
applying
to
operations
a
lot
more
accessible
and
applicable.
So,
instead
of
going
through
the
mips
portal
and
having
to
read
the
text
and
come
up
with
an
interpretation
we'll
be
able
to
have
the
reports,
the
examples,
different
comparisons,
all
organized
and
and
potentially
even
view
that
through
live
data
based
on
performance
and
and
other
applicable
things
that
the
the
the
dvcs
need
to
to
guide
maturing.
The
Frameworks.
A
I
know
that's
great
yeah,
smart
Maps
I,
like
that.
That's
I
prefer
need
some
more
fun
name,
so
we'll
have
them
on
the
sideline
for
him,
but
yeah
I
think
you
can
carry
on
as
a
reminder
to
raise
your
hand,
drop
questions
in
the
chat
obviously
make
some
more
engaging
presentation
if
we
can
kind
of
meet
you
on
on
your
curiosity.
So
thanks
for
engaging
folks
and
yeah
continue
on
Richard.
G
Yeah
so
kind
of
expected
in
a
ton
of
questions.
This
isn't
too
Earth
shattering
of
information
if
you've
been
following
the
Dao,
but
on
the
next
slide
we're
prepared
to
make
a
call
to
action
to
everybody
on
this
call
and
watching
the
recordings
we
we
need
help.
G
We
need
you
to
contribute
to
writing
Scopes,
there's
a
number
of
core
units,
very
Diversified
in
their
backgrounds,
as
well
as
contributors
and
interested
community
members
that
bring
Rich
experience
to
our
community
here
and
it's
time
to
to
to
to
share
and
use
that.
G
So
what
we're
asking
everybody
here
today
is
to
contact
one
of
the
for
ecosystem
contributors
via
Discord.
Our
handles
are
listed
below
and
what
we'll
start
to
do
is
to
form
the
working
groups
that
will
eventually
lead
into
the
dvcs
that
will
start
drafting
these
one
of
the
first
Scopes
that
I've
seen
support
has
been
the
governance
security
scope.
G
We
had
a
meeting
I
think
one
of
the
first
times
with
every
smart
contract
developer
within
the
Dow
in
roon
a
couple
weeks
back
and
started
to
build
out
the
end
game
Discord
to
have
different
permission
channels.
So
we
can
control
the
conversations.
We
can
make
sure
that
the
experts
are
focused
on
exactly
what
they
need
to
be
and
then
eventually
we'll
look
to
open
that
up
to
make
it
more
transparent,
but
for
right
now.
G
This
is
a
slow
iterative
process
where
we
want
to
make
sure
that
the
the
the
the
the
the
the
strongest
input
is
able
to
be
made
and
and
really
lay
down
the
foundation.
I
know
there's
been
some
Concepts
about,
or
questions
about.
You
know
the
formatting,
and,
and
maybe
where
is
this
information
going
to
live
and
and
right
now?
G
Is
this
first
step
we're
really
just
trying
to
form
the
groups
in
order
to
start
progressing
that
forward,
as
as
we
mature
this
process,
this
will
lead
into
again
those
DVC
calls
and
and
creating
shared
documents
and
then
eventually
getting
it
onto
the
Forum
like
we're,
in
demonstrated
with
the
real
world
asset
collateral
scope
and
and
sharing
that
for
further
the
community
community
feedback.
G
So
yeah,
please,
please
drop
us
a
message
reach
out
to
any
of
the
four
of
us
here,
we'd
be
happy
to
hear
what
Scopes
you
have
interested
in,
if
you're,
not
sure
which
one
you
would
like
to
contribute.
Definitely
again
just
ping
us
knowing
that
you
have
some
interest.
Some
will
help.
Sync
you
up
with
the
the
working
group
where
you
can
make
the
biggest
impact.
A
Yeah
awesome
because
there's
been
a
lot
of
talk,
I,
don't
some
of
us
we're
at
the
delegate
office
hours
a
little
bit
before
this
right
just
about
like
the
transition
phase,
and
you
know
exactly
what
work's
gonna
look
like
between
now
and
and
the
launch
of
the
subdowns,
and
it's
like
well
right
now.
The
biggest
thing
is:
is
the
Scopes
in
the
Constitution
right.
We
have
to
write
the
rules
that
are
going
to
define
the
framework.
A
So
obviously,
if
you're
you're
in
this
call
you've
got
some
experience
with
decentralized
governments.
You
got
some
knowledgeability
about
maker
and
can
probably
contribute
in
more
ways
than
you
realize.
A
So
a
big
part
of
this
conversation
is
just
kind
of
getting
this
out
there,
making
sure
we're
on
the
same
page
for
Scopes
and
people
feel
like
they
can
find
a
a
place
to
contribute
and
yeah
make
the
Dow
better
so
happy
to
open
up
conversation
here.
I
know
we
had
some
potential
discussion
questions
if
we
wanted
it,
but
also
happy
to
just
see
where
where
people
are
at
with
Scopes
and
if
there's
Parts,
they
feel
like
they,
they
still
don't
understand
her
they'd.
Like
us
to
go
into
deeper.
G
They
had
the
you
reminded
me
at
one
point
that
I
wanted
to
highlight
as
well,
which
is
it
may
seem
like
the
work
we're
doing
today,
may
not
not
change
for
six
months
or
whenever
the
Constitution
gets
ratified.
But
following
up
runes
DVC
call
yesterday,
there's
going
to
be
an
increased
focus
on
making
sure
that
we
can
Implement
incremental
changes
that
drive
impact
to
the
current
structure
of
the
doubt
today.
G
So
I
I
would
not
be
surprised
if,
if,
if
we
see
work
from
a
scope,
immediately
start
moving
into
mips
in
an
incremental
Pace
to
start
introducing
these
changes
playing
with
some
of
the
new
Concepts
and
the
the
more
that
we
could
attack
this
earlier.
I
think
the
better
off
will
be
as
a
community
and
and
ultimately,
the
the
more
insights
that
we
can
unlock
to.
It'll
just
help
again
build
this
recursive
feedback
loop
of
of
continuous
Improvement,
which
I
I
I.
G
Think
if
we
borrow
that
a
little
bit
from
the
traditional
industries
that
that
do
it
well
will
will
be
pleasantly
surprised
at
the
outcomes
that
they
can
drive
and
I
do
want
to
highlight
to
comment
that
Juan
dropped
in
the
chat,
which
is
if,
if
anybody
here
knows
of
people
outside
of
maker
that
want
to
contribute,
we
are
looking
for
experts
to
join
as
well.
There's
plenty
of
different
rules
within
endgame
that
they
can
eventually
grow
into.
A
Yeah
I
know
an
analogy
I
like
to
use
when
talking
about
governance.
Is
this
like
idea
of
running
into
brick,
walls
and
I
feel
like
by
nature
of
being
larger
and
bigger,
and
earlier
maker
we've
run
into
a
lot
of
vaults
and
that's
good
if
you
can
learn
from
it
right,
but
I
think
that's
kind
of
the
real
challenge
of
the
Scopes
is
like
okay.
A
Yeah
I,
don't
know
I
hoping
to
get
discussion
going
a
little
bit
here.
One
thing
I've
been
reflecting
a
lot
on
was
hearing
one
talk
at
and
I'm
gonna
forget
what
conference?
Even,
but
you
reference
a
lot
about
this
idea
that
when
we
started
with
the
Dao
we
kind
of
took
a
very
like
optimistic
view
right,
we
had
very
little
rules.
We
said
all
right,
you
do
what
you
want
you
come
in
here.
A
You
follow
these
and
and
we'll
build
a
Dao
and
and
in
some
ways
it
works
in
some
ways.
It
didn't
so
now
as
we're
trying
to
reorg
it's
kind
of
like
okay.
Well,
how
do
we
build
this?
Smartly?
You
know
how
do
we
kind
of
take
our
our
lessons
from
the
past
and
and
actually
apply
them
in
a
way?
That's
less
optimistic!
That
says:
okay!
Well,
the
fact
is
that
people
are
gonna,
make
mistakes
that
things
aren't
going
to
run
as
smoothly
as
we
might
have
expected.
A
So
how
do
we
design
a
system
that
can
anticipate
those
shortfalls
rather
than
scrambling
to
to
react
every
time
they
happen?
A
So
I,
don't
know.
One
thing:
I'm
excited
about
at
least
scope
wise
is,
is
looking
back
through
some
of
our
postmortems
looking
back
at
some
of
the
the
really
informative
risk
posts
on
the
Forum
and
kind
of
like
noting
what
those
things
have
highlight,
because
I
think
in
in
some
regards
a
lot
of
the
scope.
Work
has
already
been
done
just
by
the
the
culture
of
maker,
which
is
the
you
know,
very
conservative
kind
of
backward
looking
and
reflective
Community.
A
So
we
have
a
lot
of
work,
a
lot
of
the
stuff's
out
there.
We
just
need
to
start
coming
together
and
and
collaborating
and
I
hope.
This
was
kind
of
a
launching
point
for
that.
E
Hey
thanks
retro
for
putting
this
together
two-part
question
here:
circling
back
to
the
Frameworks.
How
often
can
they
be
updated
thinking
as
we
move
forward
and
web
3
gets
more
and
more
developed,
they'll
be
definitely
new.
Hopefully,
product
Market
fit
things
that
will
bring
the
retail
clients
back
and
also
you
know,
I
like
to
think
that
the
Innovation
is
just
going
to
continue
to
grow
right.
E
So
I
guess
my
first
part
is:
how
often
can
you
change
the
Frameworks
of
each
scope
and
then
the
second
part
is
when
creating
these
Scopes.
Do
you
also
need
to
include
I
guess
incremental
goals
of
each
scope
or
or
like
leading
targets,
or
is
that
does
it
that
does
it
boil
down
to
the
sub-dial
level
when
it
comes
to
goals
and
and
targets.
G
Yeah
again,
a
couple
great
questions:
the
Frameworks
within
a
scope
are
intended
to
be
fairly
fluid.
G
The
early
days
of
of
drafting
these
is
that
iterations
be
very
quickly
but
using
the
governance,
security
scope
as
an
example
for
how
a
framework
will
mature
once
end
game
plan
is
up
and
running,
is
the
Omnibus
spell
so
as
intended?
The
Omnibus
concept
is
allowing
sub-dials
to
submit
their
own
spells
that
are
intended
to
be
perfect
without
errors
to
be
enacted
within
an
executive.
G
If
there
is
a
framework,
breach
or
or
penalty
that
needs
to
be
assessed,
because
the
spell
isn't
secure,
then
there's
kind
of
a
checkpoint
that
needs
to
occur
so
first,
if
there's
an
opportunity
to
improve
the
framework
by
learning
through
that
example,
and
it
hasn't
been
previously
encountered-
and
it
hasn't
been
previously
defined
that
that's
almost
a
good
thing.
G
G
If,
however,
it
is
a
well-defined
thing
within
the
framework
that
is
breached
and-
and
it
should
have
been
obvious
that
that
error
shouldn't
have
occurred
or
or
they
constructed
the
spell
incorrectly,
then
that's
a
simple
case
to
assess
a
penalty.
G
So
as
time
moves
on,
we
expect
that
some
aspects
of
the
Frameworks
will
see
less
and
less
iterations,
or
at
least
a
slower
Pace,
as
as
they
become
more
thorough
and
mature,
but
definitely
early
on
that
that
Cadence
will
be
a
little
bit
quicker
and,
as
the
end
game
plan
is
discussed,
it's
defined
basically
a
mandatory
quarterly
check
on
each
of
them.
That
may
be
quicker
in
the
beginning,
but
then
slows
as
as
time
moves
on
this.
E
No
I
was
just
with
regards
to
like
leading
targets
right
and
kind
of
getting
incremental
goals.
So
as
an
example
right
that
you
have
that
growth
scope
there
on
the
right
hand,
side
of
my
screen
and
I
would
imagine
like
a
a
market-facing
sub-dial.
You
know
they
might
be
expected
to
grow
revenues
by
whatever
10x
and
then
x,
24
months.
So
you
know
incremental
goals
like
that.
Is
that
included
initially
in
the
in
the
framework,
or
is
that
boils
down
to
the
self-doubt
level
so
to
speak?
G
No
I
I
think
it's
a
good
point
to
bring
up
and
if
you
allow
me,
I'll
use
the
real
world
asset
collateral
framework
as
the
example
that
was
posted
in
the
Forum.
The
I
believe
it
was
like
article
two
mentioned
some
very
specific
parameters,
or
or
limits
for
say,
like
the
PSM
and
different
collateral
types.
I
would
expect
to
see
that
more
so
than
like
go
out
and
accomplish
access
more
of
like
a
Target.
G
That's
that
that
that
forms
an
upper
limit
and
then
and
potentially
based
on
how
the
budgeting
of
operational
funds
evolves
over
time.
We
could
see
different
incentives
handed
down
to
the
sub-dials
for
performing
and
delivering
against
those
targets,
but
the
the
framework
itself,
then,
would
be
more
of
like
the
restrictions
that
are
associated
with
it.
And
then
the
dvcs
can
work
with
facilitators
to
form
different,
say:
incentives
to
promote
different
actions
to
achieve
those
targets
or
to
get
closer
or
whatnot.
A
And
to
kind
of
build
on
that
right,
the
idea
is
that
these
are.
These
are
the
rules.
These
are
the
barriers
and
the
sub
Downs
are
supposed
to
be
incentivized
to
you
know,
do
as
much
as
they
can
within
those
parameters
and
and
capture
as
much
as
their
upside
as
possible.
So
in
a
well-designed
system,
Frank
like
the
idea
is
that
you'd
make
more
money
for
making
more
deals
right.
So
as
long
as
we
Define
what
you
can't
do
and
Define
like
you
know
basically
some
protection
someplace.
A
The
idea
is
that
you
would
then
be
incentivized
to
run
with
those
as
much
as
you
can
and
I
think.
That's,
what's
pretty
exciting
as
like
a
core
unit
contributor
right
like
one
one
thing
that
I
was
definitely
missing
from
our
model.
Was
this
idea
of
like
incentivizing
going
the
extra
mile
right
we
just
kind
of
assumed
like
okay?
Well,
let's
use
a
lot
of
salary,
they'll
do
their
work
and
then
it'll
be
great,
and
you
know
it
didn't
take
too
long
to
realize
it's
like
well.
A
I
I
could
work
10
hours
a
day.
It's
like
or
I
could
work
six
and
it's
like
if
no
one's
really
checking
on
me,
if
there's
no
clear
upside
for
putting
in
long
hours
like
you
know
human
nature,
what
do
we
expect
is
going
to
happen
and
I
think
over
the
past
two
years
or
whatever
it's
been?
Our
experimentation
has
been
quite
clear
that,
like,
if
you
don't
plan
for
things
like
it's,
it's
not
going
to
go
optimally.
So
a
lot
of
in-game
was
just
defining
these
Scopes
and
saying
okay.
A
Well,
these
are
the
12
areas
we
need
to
care
about,
and
these
are
kind
of
their
order
of
importance
in
terms
of
resources.
With
that
in
mind,
like
go
and
yeah
I,
don't
know
it's,
it's
definitely
an
exciting
environment
for
for
Builders,
so
pretty
curious
to
see
what
what
all
will
end
up
attracting.
E
Yeah
for
sure
and
I
guess
attracting
outside
contributors.
You
probably
would
want
someone
who
understands
the
concept
of
web
3
correct
or
do
you
think
that's
not
necessary
I
mean
I,
guess
for
rwa.
For
that
scope
there.
It
would
you
there's
a
plethora
of
people
all
around
the
United
States
the
country
I'm
in
that
could
probably
have
an
input
on
that,
but
understanding
the
concept
of
web
3
and
also
dials
is
kind
of
difficult
right.
So
I
guess
what
I'm
asking
is
that
you're?
Looking
for
anyone
or
any
thing?
H
I
mean
yeah
yeah.
No,
what
I
was
going
to
say
Frank,
the
the
calls
will
be
open,
so
we'll
try
to
make
it
as
open
as
possible,
and
ideally
we
get
a
lot
of
people.
I've
been
speaking
with
some
people
already
that
are
like.
Oh,
that's,
great
I'm,
going
to
start
joining
the
calls
and
then
we'll
kind
of
like
get
a
bit
like
homework
kind
of
for
the
next
session.
Okay,
who
who'll
do
what
to
make
the
to
make
sure
that
the
framework
actually
progress
so
I
think
that
this
is.
H
This
might
be
a
great
kind
of
like
introduction
or
a
great
starting
point
for
someone
that
wants
to
get
into
web3
and
I.
Don't
know
as
an
example:
it's
like
okay.
We
need
to
and
I'm
bringing
this
up
because
I
heard
it
in
the
delegates
call
here
earlier
today,
but
if
someone
wants
to
say
Okay
I
want
to,
we
need
to
create
like
an
off-boarding
program
for
for
potential
people
that
stop
working
with
that.
What
does
it
look
like?
H
So
maybe
someone
that's
there
in
the
call
is
like
oh
I
have
experience
in
this
from
what
up
to
so.
Even
if
there's
no
experience
in
web
free
whatsoever,
they
might
be
to
contribute
a
lot
so
yeah
the
course
will
be
open.
Anyone
will
be
able
to
assist
whichever
scope.
We
want
we'll
act
a
bit
as
facilitators
to
make
sure
that
we
stay
on
track
and
and
the
good
ideas
are
kept
and
we
can
actually
develop
these
things
and
then
we'll
try
to
make
everything
as
public
as
possible
without
any
restrictions.
A
And
I
think
and
there's
kind
of
this
like
return
to
Value
right
one
words
like
the
idea
that
okay
well,
if
you're,
an
expert
in
your
area-
and
that
applies
to
what
you're
doing
like
great.
We
want
you
aboard
if
you
can
provide
that
value,
so
yeah
I
think
there's
a
lot
of
opportunity
for
people
who
aren't
necessarily
web3
familiar.
It's
probably
going
to
be
harder
at
the
start,
but
especially
once
things
are
more
established
like
we
need
a
lot
of
experts
on
a
lot
of
different
areas.
F
F
Path
to
contribution
and
make
it
very
visible
where
we
want
input
and
not
I
think
this
is
this
is
probably
at
the
moment
still
people
pay,
but
I
expected
to
just
get
a
lot
clearer
once
we
start
working
on
that,
but
I
think
this
will
will
probably
just
attract
a
lot
of
people
if
it's
clear
like
what's
needed
and
and
how
they
can
contribute
and
I.
Think
people
will
just
show
up
because
make
us
super
visible
and
super
interesting
too.
It's
a
lot
of
thoughts
out
there
I
think.
A
Think
we'll
have
a
lot
of
people
who
want
to
jump
in,
but
making
it
like
easy
for
that
information
to
be
accessible
for
there
to
be
a
path
to
contribute
without
making
too
much
noise
is,
is
definitely
going
to
be
tough,
but
we'll
see
we're
like
I
said
we're
going
to
be
utilizing.
This
call
more
for
and
giving
contributions
we'll
be
playing
around
with
the
dvcs
yeah.
A
Basically,
the
the
idea
is
just
to
try
to
get
more
work
going
in
in
the
in-game
direction,
because
I
don't
know
I
personally
I
kind
of
feel
like
there's.
This
perception
that,
like
okay
well
end
game
is
going
to
happen
in
a
certain
amount
of
time
and
then
once
once
it
happens,
then
we'll
we'll
start
figuring
it
out,
which
might
be
like
a
sensible
position
to
take
as
an
individual
right.
A
Certainly
a
lot
of
balls
in
the
air
at
the
moment,
but
as
an
organization
right
like
there's
a
ton
of
work
that
needs
to
be
done
in
order
for
us
to
launch,
and
we
don't
have
that
many
people
so
like.
If
you
really
want
to
be
a
part
of
this
I
I,
don't
think
it's
going
to
be
too
hard
to
be.
A
It's
just
going
to
be
a
matter
of,
as
we
start
to
get
people
in
the
snowball
making
sure
that
they're
able
to
contribute
clearly
and
without
getting
away
of
each
other.
So
yeah
I,
don't
know
if
that's
going
to
be
good
hug
or
some
Version,
Control
or
or
what.
But
we
are
going
to
have
to
spin
up
some
some
collaboration
centers
for
for
us
to
talk
about
and
yeah.
That's
at
least
on
my
list.
G
Yeah
I
think
the
moral
of
the
story
is
we.
We
have
the
tools
we
have
the
purpose
and,
and
now
it's
just
starting
to
put
all
the
pieces
together.
We
appreciate
feedback
so
definitely
direct
any
comments
our
way
as
well
and
we'll
continue
to
iterate
as
we
move
forward.
A
Yeah
I'm
willing
to
open
up
the
call
a
little
bit.
Obviously
we
do
have
some
time
from
when
we
typically
end
happy
to
give
that
back
to
people,
but
if
there
are
related
subjects
unrelated
subjects,
anything
you
want
to
ask
or
discuss
you
know
this
is
our
public
recorded
version
of
the
column,
it's
a
great
place
to
do
it
and
get
some
ideas
down
and
and
start
building
off
of
one
another.
A
All
right,
all
that
said,
things
are
obviously
kind
of
in
flux
in
terms
of
people
in
terms
of
assignments
in
terms
of
work,
so
feedback
is
super
appreciated
right.
A
lot
of
us
are
doing
things.
We
typically
don't
do
we're
trying
out
new
things
on
the
community
and
the
only
way
we
know
if
that's
where
here
or
not,
is
to
hear
back
from
you
guys.
A
So
if
you
have
ideas
on
how
we
can
make
these
calls
more
engaging
or
ways
to
make
it
easier
for
someone
like
you
to
contribute
to
end
game,
please
do
let
us
know,
and
if
you
want
to
start
working
on
Scopes,
get
in
touch
with
Juan,
retro,
Patrick
or
myself,
we'll
facilitate
that
and
yeah
hit
the
ground
running.
A
So
I
want
to
give
a
huge
thanks
to
hats
protocol
to
Retro
and
everyone
else
who
spoke
and
engaged
on.
This
call
that's
a
real
privilege
to
be
able
to
host
these
and
and
be
a
part
of
this
Community
movement.
So
you'll
see
us
same
time
same
place
next
week,
thanks
for
joining
and
we'll
talk
soon,.