►
From YouTube: Know Your MIP: Utilizing Hats Protocol (MIP93)
Description
Hear all about MIP93: Utilizing Hats Protocol (https://mips.makerdao.com/mips/details/MIP93)!
Know Your MIP is a Maker series where we bring authors of Maker Improvement Proposals (MIPs) to talk about their proposals and parameter design. Visit the Maker Forum to see all the current MIPs and propose something yourself :)
A
All
right,
hello,
everyone
and
welcome
this
is
know
your
MIP
call
with
Hats
protocol.
My
name
is
Hayden
I
go
by
Pros
11
online
and
I'm
one
of
the
governance
facilitators
here
at
maker
now,
I'm
joined
by
some
awesome
people
from
hats,
as
well
as
the
general
maker
community
and
we're
here
to
talk
about
kind
of
the
MIP
93.
How
hats
can
be
incorporated
in
maker
and
and
get
some
feedback
from
from
the
community
as
well.
A
B
B
I
prefer
to
keep
the
this
like
super
conversational,
so
I'll
share
kind
of
the
high
level
go
over
a
couple
slides
come
about
like
kind
of
how
we
think
about
it
and
what
hats
is
useful
for
and
then
please
interrupt
with
any
questions
that
you
have,
and
you
know
we
can
kind
of
go.
Do
deep,
dives
into
aspects
of
the
protocol,
the
code,
you
know
how
we're
going
to
actually
implement
it
via
a
maker
spell,
as
you
guys
see
fit
so
I'll
share
my
screen
here
to
start.
B
Okay,
cool
so
yeah,
so
we've
been
working
on
this
with
Peyton
for
the
last
few
months
originally
started
here
with
the
kind
of
utilizing
hats,
as
an
idea
talked
about,
basically
the
the
concept
of
bringing
the
single
source
of
truth
of
roles
for
maker
on
chain
and
actually
owned
by
the
Dow.
So,
instead
of
having
it
in
kind
of
the
mirror
board
that
was
linked
from
the
work
that
SES
did
or
having
it.
B
B
So
three
key
features
of
hats.
The
first
one
is
that
they
are
governed
by
the
Dow,
so
their
their
role
bound
as
opposed
to
sole
bound
tokens,
which
means
that
they
can
be
transferred
by
the
Dow
or
they.
You
know
the
ability
to
create
them
and
mint
them
and
revoke
them
is
something
that's
actually
delegatable
within
the
protocol,
but
the
person
who
has
the
Hat
we
call
them.
The
hat.
Wearer
is
not
able
to
transfer
the
hat,
so
you
can't
just
like
you.
If
you
work
for
a
company,
you
can
sell
your
job
title.
B
You
can't
go
on
openc
and
sell
your
your
hat
token.
They
have
a
specific
scope
of
authority,
so
they're
plugged
into
token
Gates,
like
Guild,
XYZ
or
collab
land,
and
in
order
to
give
you
access
to
specific
platforms
that
are
associated
with
the
token
ID
of
your
particular
hat.
So
if
you
have
you
know
the
growth
core
unit,
you
know
facilitator
hat,
then
that's
gonna.
B
So
one
of
the
coolest
Parts
about
hats
is
that
you
can
bring
your
own
logic
to
determine
when
someone
has
a
hat
or
doesn't
have
a
hat.
Basically,
we
call
this
eligibility,
but
you
could
say:
okay.
If
this
person
has
a
certain
amount
of
mkr
in
their
wallet
or
mkr
dedicated
delegated
to
them
or
they
have
participated
in
the
last
n
of
M
votes
makes
you
know
automatically
grant
their
hat
or
if
they
haven't
signed
a
multi-sig
in
the
last
60
days,
then
automatically
revoke
their
hat.
B
That's
the
type
of
logic
that
we
think
is
going
to
make
Dao's
increasingly
automated
and
we're
already
starting
to
see
interesting
ways
that
we
could
kind
of
do
that
within
the
the
maker
ecosystem.
Using
staked
mkr
but
there's
this
is
totally
bring
your
own
logic,
so
anything
that
that
you
want
to
use
from
on-chain
data
as
criteria
for
granting
or
revoking
hats
totally
possible
within
the
protocol
and
I
already
mentioned
some
of
these.
But
you
know
just
as
a
mental
model,
we
kind
of
think
of
a
hat
as
a
job.
B
In
a
box
where,
once
the
Dow
gives
a
contributor
a
hat,
they
have
everything
they
need
to
get
work
done.
So
access
to
Discord
roles
like
via
Guild
access
to
the
multi-6
signing
via
zodiac
we've
done
stuff
like
voting
weight
and
snapshot.
We
have
kind
of
a
hacked
solution
to
post
into
Twitter
via
having
a
hat
accountability
because
your
hat
can
be
revoked
or,
in
another
case
we're
working
on
right
now
slashing
like
staked
eth.
B
B
You
can't
like
sell
it
for
ether
Trent,
you
know,
send
it
to
another
world
if
you're
just
send
it
to
someone
else,
but
you
can
say
you
can
send
it
to
the
burn
address
and
then
the
dowck
and
the
Dow
can
move
them
around.
They
yeah
they're
modified
ERC
1150.
At
55s
we
modified
the
balance
of
we
modified
the
transfer
function.
B
B
And
then
also,
the
other
thing
we
I
want
to
share
is
that
we
have
this
early
draft
of
a
guide
on
how
to
use
hats
written
by
one
of
our
contributors
Maurice,
and
this
goes
through.
Basically,
the
couple
functions
that
I'm
going
to
show
you
about
how
to
use
hats
protocol.
So
whenever
you
get
started
with
Hats,
you
have
to
Mint
a
top
hat.
B
That
is
basically
the
root
node
of
a
Hat's
tree,
and
then
every
hat
can
create
immense
child
hats
below
it.
So
the
top
hat
you
just
send
it
to
the
address.
You
might
use
the
pause
proxy
here
or
if
you
have
a
core
unit
multi-sig,
you
might
use
the
core
unit
multisig
here
with
the
intention
to
later
kind
of
graft
that
the
tree
that
you
create
onto
the
larger
maker
tree.
B
This
would
be
like
creating
a
child
hat
for
off
of
the
top
hat.
You
use
the
top
hat
ID
as
admin
again
details
here.
You
can
include
ipfs
link,
you
have
a
Mac
Supply,
so
sometimes
a
lot
of
times
it's
since
the
CRC
155.
You
have
one
of
ones,
but
sometimes
you
might
have
like
five
multi-six
signers
on
something
five
core
unit.
You
know
team
members
eligibility
is
what
I
was
mentioning
earlier.
B
Is
the
ability
is
the
address
that
you
use
to
revoke
the
hat
Under
certain
conditions,
so
this
can
be
smart
contract
address
or
it
can
be
just
a
you
know
an
eoa,
a
multi-segger,
a
dow
that
is
manually
able
to
revoke
the
hat
and
then
toggle
is
similar
to
eligibility,
except
instead
of
removing
it
from
a
particular
address.
It
turns
the
entire
hat
on
or
off
so
you
can.
B
You
could
say
that
we
have
this
hat
for
just
you
know,
for
this
quarter
at
the
end
of
the
quarter
automatically
turn
the
half
all
you
know
all
these
hats
off
and
that's
just
like
an
interesting
way
to
do.
Expiration
mutability,
is
you
know
if
you're
creating
a
hat
that
you
think
is
going
to
change
over
time?
B
Your
hat
can
be.
Your
hat
can
be
mutable,
but
we
see
we
think
that
generally
hats
are
going
to
move
toward
becoming
immutable
in
the
long
term,
so
this
is
kind
of
like
draft
almost
like
draft
mode
and
then
once
you
get
solid
on
what
your
hat,
you
need
your
hat
structure
to
be,
then
you
just
you
change
mutable
to
false,
and
then
it
kind
of
creates
a
more
solid
form
and
then
again
you
get
the
image.
B
So
you
create
the
hat
and
then
once
you
create
it,
you'll
get
a
you
get
the
token
ID
of
the
hat
out
of
this
hats
contract
and
then
you
use
the
mint
hat
function
with
the
hat
ID
and
then
the
person
who
you
want
to
be
wearing
the
Hat
I
can
get
into
how
hats
are
revoked
and
things
like
that.
But
I
think
I'll
just
pause
there
to
see
what
questions
have
come
up
so
far.
B
B
Something
that
you
have
accomplished
or
something
that
that
you,
you
know
an
event
that
you
went
to
some
work,
that
you
did
some
you
know,
membership
that
you've
held
for
some
period
of
time,
I
really
like
that
those
are
soul
bound
and
that
they're
not
that
they
aren't
revocable
they're,
not
transferable
by
the
doubt,
because
they're
really
a
data
primitive.
Is
it
you
own
your
own
data
about
the
things
that
you've
done?
B
B
That
is,
which
is
why
we
have
a
tree
of
hats
in
the
first
place.
So
I
would
say
that
hats,
hats
are
not
badges
because
they
can
be
moved
they're,
not
a
data
primitive,
but
they
use
data
Primitives
like
badges,
especially
in
the
automatic
automatic
granting
and
revocation.
So
you
can
imagine
you
know
having
a
baseline,
a
requirement
of
anyone
who's
going
to
wear
a
maker
hat
to
have
a
certain
number
of
badges
that
include
contributions
to
the
Dow
participation
in
votes
showing
up
to
town
halls,
and
maybe
you
accumulate.
B
A
Right
now,
I
think
that's
a
cool
way
to
think
about
it
and
definitely
kind
of
got
me
further
down
the
issue.
Just
in
terms
of
how
I
approach
it
from
a
governance,
standpoint
and
I
think
it's
probably
clear
to
most
people,
at
least
in
in
the
room
who
who
are
familiar
with
this,
but
the
fact
that
it's,
you
know
a
deployed
contract
I
think
you
can
scan
you.
A
Have
the
guide
really
adds
to
that
decentralized
governance
aspect
to
it
as
well,
like
I,
think
what
got
me
most
excited
about.
This
was
just
the
idea
that
it's
it's
just
another
Lego,
it's
a
it's
another
tool,
that's
out
there
for
building
on
top
of
governance,
which
means
that
there
are
a
lot
of
potential
angles.
A
You
can
take
this
and
I
think
that's
kind
of
what
we're
going
to
get
into
the
back
side
of
the
call,
but
before
we
did
I
kind
of
just
wanted
to
see
if
you
had
any
thoughts
there
in
terms
of
on
the
governance
and
why
why
you're
spending
your
time,
working
on
this
and
and
and
kind
of
why?
You
think
this
is
an
important
problem
to
be
dedicating
so
much
time
to.
B
You
know
new
nft
based
mechanisms
that,
and
it
seems
like
there's
a
lot
of
interesting
ways
of
divvying
up
the
natural
power
of
the
Dows,
like
the
the
natural
power
being
like
the
control
of
the
top
level
governance,
surface
and
maker,
that's
the
false
proxy
and
and
other
contracts
that
you
know,
there's
other
top
level.
You
know
like
a
compound
Governor
Bravo
or
a
molok
dow.
They
both
have
that
kind
of
top
level
governance
surface.
Where
voting
happens,
but
there's
so
much.
B
Inefficiency
are
specifically
around
and
I'll,
maybe
can
nerd
snipe
Spencer
a
little
bit
with
this
is
he's
dispenser,
just
coined
the
term
the
accountability
comments,
so
Dows
are
really
good
at
solving
tragedy
of
the
commons
problems.
That's
like
one
of
the
most
interesting
things
that
those
can
that
are.
Those
are
useful
for
and
why
I
think
that
it
can
be
so
impactful
in
the
world,
but
there's
in
terms
of
getting
things
done
like
turning
resources
and
people's
time
and
skills
into
deliverables
and
achievement
of
goals.
B
Even
if
we
know
which
direction
we
want
ahead.
There's
a
challenge
around
understanding
who
is
actually
going
to
get
get
which
thing
accomplished
and
how
to
what
you
know
what
penalties
and
rewards
we
can
create
for
people
as
incentives
for
them
to
accomplish
those
things
so
that
I
think
that
Dows
are
going
to
be
the
most
efficient
organizations
that
human
Humanity
has
ever
created,
and
this
seems
like
a
key
building
block
to
overcome
some
of
the
challenges
that
we've
seen
in
Dows
over
the
last
few
years.
B
C
Yeah
Nick
is
always
good
at
nerds.
Sending
me
he
knows
knows
what
what
I
don't
know
knows.
The
sniper
corridors
that
I'll
be
I'll,
be
down
or
something
but
I
I
feel
like
because
I
agree
with
everything
that
Nick
said
and
I'll.
Add
that
as
somebody
who
is
like
I
expect
all
everybody
here
who
is
really
inspired
by
and
almost
like
a
maximalist
for
real
dows
I
have
observed
a
tendency
among
the
broader
Dao
space
to
make
a
trade-off
between
getting
stuff
done
and
being
a
real
Dao
that
I.
A
D
Peyton
yeah,
hey
everybody,
just
one.
One
quick
thing:
I
wanted
to
add
before
we
get
into
the
details
possible
implementations
to
keep
in
mind
is
that
the
hats
are
really
designed
to
evolve
with
your
Dao
as
it
grows.
You
know
we
know
these
structures.
Are
these?
Organizing
structures
are
emergent.
We
can't
plan
it
all
out
in
advance.
One
of
the
key
things
of
hacks
is
that
hat
trees
can
be
linked
together.
D
They
can
be
grafted
on
to
another,
and
so
what
that
enables
is
you
know
you
have
your
primary
maker
Dow
tree
where
it's
unchain
verifiable,
you
know
more
solid,
but
then
individual
core
units
or
or
small
groups
or
even
individuals
could
be
experimenting
with
hats
on
their
own
defining
roles.
You
know
creating
structures
for
their
for
their
group
and
then
only
at
the
point
where
you
know
it
feels
right
or
there's
some
some
stability
there
year.
Then
they
could
submit
a
proposal
to
link
that
their
Branch
to
to
the
maker
tree.
D
A
A
Okay,
so
just
kind
of
wanted
to
talk
about
like
timeline,
because,
as
we
were
first
getting
to
know
each
other
with
Hats
right,
we
were
at
the
just
I
believe
the
start
of
the
in-game
vote
well
nicknament,
together
in
in
Bogota,
and
it
was
kind
of
this
question
of
like
okay.
Well,
we
know
that
this
is
a
super
useful,
primitive.
A
We
know
like
there
are
a
ton
of
ways
we
can
apply
this
to
maker,
but
like
how
are
we
gonna
deal
with
end
game
and
and
the
shift
and
what
that
means?
For
us
and
in
many
ways
that's
still
a
question.
I
think
we're
answering
but
I
think
we're
getting
better
at
answering
so
kind
of
just
wanted
to
give
the
audience
and
an
overview
here
say
like
all
right.
A
A
But
the
point
is
that
in
in
that
time,
before,
the
full
Constitution
drops
will
kind
of
be
able
to
figure
out
exactly
where
the
the
core
value
is
for
for
maker
in
this
this
primitive
and
then
hopefully
get
it
into
that
toolkit
for
decentralized
governance,
because
I
think
it's
going
to
become
quite
clear
through
what
we're
going
to
share
and
start
talking
about.
Next
and
and
all
the
concrete
ways
that
you
can
apply.
A
A
A
Okay,
let's
take
the
work
that
retro
did
in
terms
of
mapping
our
core
unit,
wallets
and
and
facilitator
addresses,
and
let's
actually
like
put
that
on
chain
with
a
recognizable
token
and
I
still
think
this
is
useful
for
facilitators
that
will
not
opt
into
it.
I
still
think
it's
great,
but
also
there
are
a
ton
of
other
ways
that
we
can
be
using
this
and
and
our
talk
for
the
map
was
kind
of
like
okay.
How
do
we
get
the
the
Baseline?
A
A
Additionally,
since
it
is
a
an
1155,
the
ability
to
use
snap
snapshot
polling
is
is
really
great.
A
lot
of
people
are
always
asking
like.
Oh,
why
does
it
make
your
use
snapshot
and
there's
like
a
complicated
technical
history
there
for
for
how
we
ended
up
where
we
are,
but
one
kind
of
core
problem
is
just
like:
okay,
well
with
how
the
IOU
tokens
are
structured,
it's
really
hard
to
just
spin
up
a
a
maker
snapshot.
A
A
Yet
we're
relying
on
a
lot
of
social
structures
that
kind
of
use
web2
tools
to
verify
legitimacy.
When
we
could
be
using
the
blockchain,
so
yeah,
the
obvious
other
one
to
mention
there
is,
is
multi-sig
use,
hats
is
really
cool
and
that
you
could
spin
it
up
and
and
actually
have
signers
be
people
who
who
hold
the
the
ads
roll
token.
So
this
is
something
we've
struggled
management
wise
with
in
the
Dow
I.
Think,
it's
fair
to
say
it's
like
anytime.
A
A
That
gives
the
way
to
actually
manage
it
to
from
from
a
decentralized
org
perspective
right,
because
it's
easy
on
a
social
level
to
say
like
oh,
okay,
these
people
are
deciding
things,
but
this
will
allow
us
to
put
it
on
chain
and
actually
have
people
put
put
it
on
their
address.
Sign
publicly
for
everyone.
When
they're
taking
a
stance
on
a
on
a
dispute
so
yeah,
we,
we
see
simple
voting
and
meta
delegation,
probably
being
a
use
there.
Treasury
management
for
the
multiplexig
bit
I
mentioned
earlier.
A
Roll
tracking,
pretty
obvious,
as
well
as
just
general
Community
Management,
with
Discord
role
functions.
One
neat
onboarding
thing
I
did
with
when
I
was
learning.
The
hats
protocol
was
setting
up
with
them,
getting
my
hat
minted
on
on
the
test,
Network
and
then
getting
added
to
their
Discord
based
on
having
that
role.
So
that
was
a
really
neat.
Onboarding
experience,
experience
and
one
I
think
that
we
could
kind
of
bring
to
to
sub-dos
and
might
be
particularly
helpful
in
an
in-game
rollout
cool.
A
E
Yeah,
hey
guys
thanks.
It's
Frank
from
flip
flop,
flop,
delegate,
loc
at
spotty
internet
connection.
So
sorry,
if
you
already
answered
this,
but
I
have
a
lot
of
experience
with
joining
Discord
communities
and
one
thing
that
I
hate
I'm,
not
that
I
hate
but
I,
just
I
always
get
nervous
when
I
do
it
is
connecting
you
know
your
wallet
to
to
collab
land
and
all
that
good
stuff.
I
know
they're
trying
to
do
a
lot
of
good
with
Lapland
and
others
alike.
C
C
For
the
first
time,
any
kind
of
earning
your
way
by
demonstrating
your
alignment,
credibility,
skill
set
Etc
earning
your
way
towards
a
position
where
you
can
actually
get
more
more
responsibility
and
Authority.
So
we
don't
want
I
I,
don't
want
to
see
people
using
hats
to
like
keep
people
out
of
their
community.
A
A
Well
we're
the
governance
facilitators
we're
in
charge,
it's
our
job
to
tell
you
that
we
don't
think
this
is
allowed,
which
is
always
going
to
be
a
centralizing
factor.
So
one
of
the
neat
things
with
this
technology
is:
it
can
allow
us
to
kind
of
encode
the
rules
and
encode
some
of
the
protections
that
we
we
naturally
would
rely
on
on
the
social
airtime
Force
into
the
permissions.
A
B
Sure
also
good
news
asked:
does
it
work
for
with
safe
addresses
as
holders
of
hats,
and
the
answer
to
that
is
absolutely
hats,
are
modified,
ERC,
1155
tokens
and
it
can
be
held
by
any
address,
eoas,
multi-cigs
or
Dows,
and
they
can
even
be
held
by
you
know,
worn
by
other
smart
contracts.
We
see
a
world
where
you
know
Dows
become
increasingly
automated
by
delegating
authorities
to
to
you
know
small
groups,
individuals,
even
sub-dos
or
meta
Dows,
as
well
as
contracts
that
are
kind
of
representing
different
workflows
or
logic.
B
That
automatically
gets
things
done
on
behalf
of
the
Dow
and
we,
as
David
mentioned
earlier,
instruments
were
mentioned
in
the
chat.
We
have
this
kind
of
like
emergent
structure
that
is
possible
to
you,
know,
I.
Think
any
network
David
David
has
written
a
lot
about
this.
Any
network
is
going
to
have
a
more
emergent
structure
than
kind
of
a
planned
top-down
structure.
B
Dows
are
definitely
a
category
of
networks
and
we
have
the
opportunity
to
kind
of
evolve.
The
role
structure
of
hats,
via
you
know,
moving
the
hat
from
an
individual
to
a
multi-sig
to
a
dow
or
even
kind
of
like
creating
additional
child
hats
within
a
hatch
tree
to
increasingly
decentralize
the
The
Authority
in
a
very
down-native
ethos
using
hats.
You
know
we're
really
strong
Believers
in
that,
and
we
think
that's
how
you
know
that
that
flexibility
is
going
to
be
super
important
to
to
douse
that
juice
to
use.
Heads.
A
A
So
the
kind
of
neat
thing
about
this
is
like
you,
don't
actually
have
to
add
in
much
to
to
kick
off
the
sandbox
right,
like
all
you
need.
Is
that
top
hat
and
a
way
to
add
hats
underneath
the
kind
of
annoying
I
don't
knowing's
wrong
word,
but
with
maker
governance
right
like
it
could
be
quite
slow,
it
can
be
hard
to
build
a
consensus.
These
aren't
problems
limited
to
us,
but
they
are
ones
that
we
feel
acutely.
A
So
one
problem
with
just
setting
up
the
top
hat
and
and
leaving
it
up
to
mkr
voters
to
add
subsequent
rules
is
then
you'd
have
to
kind
of
go
through
a
governance
measure
for
anything
you
wanted
to
set
up
so
kind
of
based
on
that.
The
the
idea
behind
this
MIP
and
and
what
we're
trying
to
accomplish
with
it
is
this
kind
of
motive
of
like
you
can
build
your
own
hat.
That
you
see
is
useful.
A
You
can
test
it
play
around
with
it
on
girly,
and
then
you
can
apply
through
this
MIP
to
make
it
a
part
of
the
official
maker
tree,
and
sometimes
that's
easy.
You
can
just
add
it
in
through
so
some
downlines,
sometimes
we'll
need
governance,
votes
and
yeah
that
will
kind
of
be
hammering
that
bit
out,
as
as
we
see
how
people
use
it,
but
in
terms
of
like
how
we
can
instantly
start
grabbing
value
with
this
I
know,
we
for
gavalpha
are
going
to
be
playing
around
with
our
arbitration.
A
A
In
that
way.
That,
like
different
parts
of
that
tree,
can
can
develop
organically
and
and
be
grafted
on,
but
yeah.
Basically,
that's
kind
of
how
I
see
it
starting
and
how
I
see
this
project
evolving
and
adding
value
is
just
starting
small
and
then
experimenting
with
how
we'd
like
to
better
manage
our
community.
A
B
One
is
just
a
level
of
opinionation
of
our
approaches.
We
try
to
design
the
basically
the
best
possible
composable,
primitive
for
like
governance,
Legos
or
structural
Legos
for
Dows,
and
that
means
that
we
made
a
lot
of
like
a
lot
of
the
pieces
open-ended,
including
the
like.
The
the
person
who
wears
a
hat
could
be
a
multi-save,
could
be
a
doubt.
You
could,
you
could
create
a
whole.
B
Just
so
that
Dows
can
build
the
right
governance
structure
that
they
need
and-
and
you
know,
use
Case
by
use
case
example,
and
also
so
that
it
can
change
over
time.
Like
the
flexibility
we
talked
about
earlier
for
increased
decentralization
I
think
hats
handles
that
a
little
bit
better
than
pods
pods
are
a
great
starting
place
and
they
their
tools
are
composable
with
one
another.
B
So
you
can
have
pods
that
wear
hats
or
you
can
have
pod
members
that
wear
hats
within
a
pod,
very
doable
and
we're
talking
with
about
we're
talking
with
them
about
an
implementation
for
another
project
that
y'all
might
know
about,
and
I
would
say.
Hats
are
really
has
a
really
particularly
useful,
because
you
can,
you
can
get
them
down
to
the
individual
level
as
well.
B
B
A
Yeah
I
always
found
that
really
cool,
because
it's
like
you
know
the
ability
to
use
roles
means
you
can
delegate
not
only
to
to
the
Pod
but
to
the
individual
as
well.
Yeah
I
I,
just
like
it's.
It's
really
neat
and
kind
of
fits
that
that
dowy
dose
of
like
one
of
many
in
and
kind
of
all
the
parts
contributing
to
the
idea
of
the
whole.
A
A
B
B
Protocol
again
and
you
can
see
the
the
readme
the
early
version
of
the
docs-
we
are
at
hats
protocol
on
Twitter.
You
can
send
us
a
DM
or
hit
me
up
I'm
in
the
I'm
in
the
maker,
Discord
ninty
Nick
or
just
ninty
Nick
on
telegram,
I'm
happy
to
answer
questions
and
connect
you
with
our
team
as
needed,
and
thank
you
all
for
your
time.
A
Thank
you
guys,
as
always
take
a
look
at
the
Forum
I.
Keep
an
eye
out
for
the
latest
votes
and
updates
on
this,
like
I,
said
well,
be
be
pushing
this
through.
Hopefully,
some
different
implementations
as
well
so
keep
an
eye
on
that
for
maker
governance
and
we
hope
to
be
developing
some
exciting
features
for
for
the
hold
down
to
be
using
this
year.
So
thank
you.
Everyone
and
yeah
hope
you
have
a
great
rest
of
the
day.