►
Description
Agenda: https://forum.makerdao.com/t/core-unit-launch-pod-sessions-session-17-development-and-ux-core-unit/10297
Development and UX Core Unit Proposals: https://forum.makerdao.com/search?expanded=true&q=dux-001%20%23mips%3Afs%20tags%3Adux-001%20order%3Alatest
A
Okay,
hello:
everyone
welcome
to
another
core
unit,
launchpad
session
today,
we're
at
number
17.
My
name
is
juan
I'm
the
facilitator
from
the
sustainable
ecosystem
scaling
core
unit,
and
today
we
have
a
group-
that's
very
special
to
us,
because
if,
if
well,
if
they
are
going
to
be
voted
in,
that
would
mean
that
they
are
the
first
successful
inquiry
coming
out
of
the
ses
incubator.
So
it's
something
I'm
personally
very,
very
happy
about.
A
B
Okay,
I
assume
you
guys
can
see
my
screen
yeah.
Yes,
so
my
name
is
phil
bain,
I'm
the
facilitator
for
the
ducks
core
unit,
and
thank
you
guys
for
joining
me
today,
joining
our
team
and
letting
us
speak
about
what
our
team
is
up
to
so
we'll
jump
right
into
it.
So,
first
a
little
introduction
to
our
team.
We
are
the
development
and
ux
core
unit,
otherwise
known
as
ducks.
We
have
six
members
of
our
team.
B
So
what
does
this
mean?
Well,
we're
going
to
break
that
down
over
the
next
next
several
slides
and
talk
to
you
about
what
that
means
to
us
and
how
we
need
to
go
about
to
accomplish
that
so,
first,
in
order
to
do
that,
we'll
we'll
talk
about
our
vision
and
which
impacts
the
mission
a
little
bit.
So
the
vision
is
to
provide
the
best
governance
user
experience
following
key
governing
principles.
B
So,
in
order
to
do
this,
there
are
three
points
that
we're
going
to
follow
three
main
features
of
the
vision
and
that
is
facilitating
the
decision-making
process,
ensuring
protocol
and
user
security
and
bringing
the
state
of
governance
in
the
industry
forward.
So
out
of
all
of
the
initiatives
that
we
have
and
everything
that
we
move
forward
with,
these
are
the
ideas
in
mind
as
we
as
we
go
so
the
first
one
of
those
facilitating
the
decision-making
process
we'll
break
that
down
a
little
bit.
B
So
what
this
means
for
us
is
providing
easy
access
to
information
for
users,
so
that
can
include
showing
mkr
weight,
visualizations
on
polls
and
delegates
pages
and
showing
mkr
in
support
of
an
executive
and
so
on.
So
some
of
these
are
features
that
we've
we've
implemented
already
or
we're
planning
on
implementing.
B
C
B
Which
can
be
accomplished
by
encouraging
the
maximum
amount
of
mkr
on
chief
at
all
times,
ensuring
availability
of
the
governance,
ui
and
blockchain
data,
so
perhaps
decentralizing
the
ui
deploying
it
to
ipfs
real-time
monitoring
of
system
health.
We
recently
added
sentry
to
our
application,
stack
to
get
errors
for
system
health
and
database
database
problems
and
encouraging
participation
and
safe
user
behavior.
So
this
can
be
done
through
just
general
good
user
experience
and
includes
tool,
tips
faqs
things
like
that.
A
B
A
B
B
So
they
are
the
ethereum
push
notification
service,
the
third
party
not
related
to
mtr
but
to
maker,
but
they
they
reach
out
to
us
with
a
collaboration
and
basically
you
can
subscribe
to
events.
So
a
lot
of
our
contracts
have
events
that
are
emitted
so,
for
example,
chief
when
you
vote
things
like
that,
so
we'll
be
when
new
executives
are
are
ending
or
beginning.
We
can
sort
of
announce
these
events
to
people
through
the
blockchain.
You
know
rather
than
email,
signups
or
traditional
subscription
methods.
B
So
it's
a
more
decentralized
approach
to
notifying
people
about
your
about
things
that
are
happening
with
our
system.
So
yeah
we've
got
a
pilot
program
with
them
and
we'll
be
if,
if
we're
approval,
if
we're
approving
it,
if
we
like
what
they've
provided
us,
we
will
share
with
the
community
and
go
from
there
so
but
yeah
that's
on
our
roadmap,
we'll
talk
about
it
towards
the
end
of
the
slide,
as
well
as
end
of
the
presentation.
B
B
So
we
have
a
strategy
to
to
accomplish
all
of
these
tasks.
The
strategy
is
five
stages
which
we'll
jump
into
discover,
define,
design
and
develop,
deliver
and
then
analyze
and
reflect
so
we'll
talk
about
each
of
these
individually
and
we'll
break
it
down
a
little.
I
know
that's,
not
super
easy
to
read
the
graphic
right
now,
but
essentially
this
is
a
continuous
iterative
looping
process
with
five
stages
that
have
broken
down
into
two
separate
sequences.
B
So
for
the
first
sequence,
is
discover
and
define,
and
that's
a
we
have
discover,
which
is
a
divergent
phase
where
we
uncover
problems,
discover
new
opportunities
and
we're
open-minded,
brainstorming.
That
sort
of
thing,
and
then
define
is
the
convergence
phase
where
we
come
upon
ideas
for
implementing
a
possible
solution.
So
you
can
see
that
this
kind
of
cycle
allows
us
to
take
our
ideas
and
run
with
it.
B
So
quantitatively,
this
can
include
running
surveys,
analyzing
user
metrics
data,
for
example.
We
use
mixpanel
right
now.
We've
been
talking
about
open
sourcing
metrics,
similar
to
the
way
it's
done
in
dye
stats,
which
is
a
really
interesting
concept.
So
that's
something
that
we
can
look
into
in
the
future
and
then
qualitatively.
We
do
internal
meetings
with
a
focus
on
feature,
discovery
and
competitor
analysis.
So
to
that
respect,
you
know
I
have
a
few
examples
of
some
some
competitors
that
we've
looked
at
and
and
introduced.
Some
ideas
is.
A
B
Joining
that
meeting,
yes,
okay,
sorry,
I
thought
someone
had
a
question
yeah,
just
a
few
examples
here
of
competitors
that
we've
looked
at.
You
know
you
can
see.
This
is
the
polka
dot
substrate
page,
and
they
have
similar
things
that
we
do
we're
at
the
outcome
prediction
the
voting
details.
How
much
was
weight
was
put
on
those
voted,
so
they
have
an
interesting
interface.
They
also
have
a
comments
tab
which
they
have
an
embedded,
diskus
or
yeah
discus
link.
B
So
you
know
that's
inspiration
for
us.
Maybe
we
need
to
find
a
way
to
embed
the
the
forum
post
a
little
bit
more
into
into
the
the
governance.
Ui
indexed
has
a
really
cool
voting
power
graph
voting
power
over
time.
This
is
something
that
we're
also
looking
into
ours
looks.
I
think
ours
is
going
to
look
even
nicer,
but
you
know
they
have
some
very
interesting
properties
of
this
page
and
then
this
one,
which
is
very
interesting
to
us,
is
the
communications
tab.
B
The
discussions
tab
on
dydx
this
looks
very
tightly
integrated
with
their
their
polling
and
their
proposals.
So
this
is
some
inspiration
for
us
to
draw
on,
because
communication
is
a
big
topic.
That's
come
up
with
people
that
we've
interviewed
and
talked
to,
and
that's
something
that
we
want
to
to
really
focus
on
as
well.
So
on
that
note
one
another
thing
we
did
for
research,
we've
done
a
series
of
one-on-one
interviews
with
mkr
holders
and
delegates.
So
current.
B
In
the
last
three
weeks,
we've
had
four
casual
conversations
with
people
but
learned
a
lot,
exploring
sentiment
and
opinions
on
the
maker
governance
system,
how
people
use
it
what
they
can,
what
can
be
improved
and
so
on?
We've
collected
ideas
for
new
features
and
and
also
importantly,
raised
awareness
of
our
team
and
our
feedback
channels,
because
now
that
you
know,
as
the
foundation
is
winded
wound
down
and
our
team
is,
is
moving
forward,
we
want
not.
Everybody
is
aware
of
that.
So
we
want
to
get
out
there
as
well.
B
B
We
want
to
stay
on
top
of
our
public
communication
channels,
get
feedback
from
the
maker
forum,
all
that
kind
of
stuff,
some
some
other
kind
of
third
party
solutions
that
are
out
there
now
snapshot
boardroom
tally
commonwealth.
These
are
gaining
a
lot
of
popularity,
so
we
want
to
look
into
collaborations
or
just
extract
information
from
them.
B
One
thing
important
to
note
is
we
believe
the
security
of
the
protocol
shouldn't
defend
depend
on
third
party
tools,
so
none
of
these
ideas,
suggestions
are
are
to
replace
any
of
our
existing
tooling,
but
just
to
kind
of
complement
them
a
little
bit
and
then
the
ideation
phase
of
our
discover
discovery
phase
is
one
of
the
things
that
we've
done
here
is
workshops
with
fig
jam.
So
this
is
a
screenshot
from
a
really
awesome
fig
jam
that
we
did
we
held
in
collaboration
with
ses.
B
Our
designer
thiago
built
put
this
together,
and
it
was
a
way
for
our
teams
to
kind
of
figure
out
what
what
things
should
be
prioritized.
What
things
are
interest
us?
We
have
like?
You,
know,
long,
shot,
ideas
and
easy
wins,
and
that
was
a
really
awesome
session
and
I
think
we're
going
to
do
a
lot
more
stuff
like
this,
to
kind
of
to
really
brainstorm
and
and
get
creative
and
gain
some
insights
and
an
outcome
of
this.
B
This
fig
jam
session
was
the
starting
point
for
our
road
map
and
also
some
of
the
new
features
we
released
in
our
most
recent
release
came
out
of
this
ideation
session
and
another
step
in
that
is
using
frill
so
to
capture
ideas.
We
use
frills
as
a
public
idea
board,
we'll
share
that
link
with
you
guys
in
the
chat,
and
but
this
is
a
really
awesome
new
kind
of
way
for
us
to
get
insight
from
the
community
as
to
what
features
are
important
to
you.
B
There's
the
upvoting
mechanism
and
dennis
has
done
a
lot
of
work
on
getting
that
board
cleaned
up
and
getting
it
to
work
work
for
us
in
a
way
that's
useful,
so
worker
items
in
thrill
are
prioritized
in
accordance
with
the
framework.
That's
centered
around
our
principles
and
more
impact
on
the
prioritization.
A
little
bit
or
sorry
more
on
prioritization
and
roadmap
a
little
bit
later,
but
here's
just
a
quick
screen
share
for
those
of
you
that
don't
have
the
link.
B
B
We
understand
everything
that
needs
to
be
done
at
this
phase,
and
now
we
just
need
to
know
how
to
make
it
happen
and
what
to
take,
what
action
to
take
so
transforming
our
ideas
into
a
work
log,
sharing
our
progress
through
coms
channels
and
validating
our
assumptions
to
create
a
product
market
fit,
and
so
this
is
something
that
we
you
know.
We
can
utilize
the
research
that
we've
done
at
this
stage,
one
example
of
a
bad
product
market
fit
if
anyone
remembers
the
juicero
controversy
from
a
few
years
ago.
B
B
Excuse
me
so
at
this
stage
we
can
now
execute
our
plan,
so
we've
done
the
discover
and
the
define.
So
we
validated
our
assumptions
through
our
designs
and
prototyping
and
we
can
work
together
to
complete
this
task.
So
you
have
a
design
and
develop
phase,
which
is
the
first
step
and
the
deliver
phase,
which
is
the
second
step
in
this
and
then
finally
analyze
and
reflect,
which
is
a
kind
of
a
epilogue.
You
know
retro
to
the
the
first
four
phases,
so
our
dev
processes
are
pretty
standard.
B
B
A
lot
of
people
have
good
experience
with
that
and
then
peer
review
code-
that's
you
know,
maybe
should
be
a
given,
but
not
necessarily
always
the
case
and
just
to
point
out
here
we're
we're
still
working
on
setting
up
all
of
these
processes
in
a
like
totally
seamless,
frictionless
fashion.
That's
why
we
have
a
new
pm
dennis
who's,
really
enthusiastic
about
this
kind
of
thing
and
he's
helping
us
set
up
all
these
processes.
B
B
We
decouple
the
design
and
dev
cycle
so
the
way
that
we
work
our
design
system
that
we've
created
at
the
foundation
that
we
brought
into
our
core
unit
unblocks
work
by
empowering
both
sides
to
work
independently,
while
still
receiving
continuous
feedback.
So
the
designer
and
the
devs,
our
tooling
allows
us
to
kind
of
not
be
blocked
by
one
another
and
instead
work
seamlessly
together.
B
B
B
B
B
So
no
no
like
schedule
on
that
kind
of
thing,
but
only
when
the
features
are
ready
when
we
think
it's
something
that's
important
that
the
community
would
be
really
inspired
about,
and
one
important
aspect
of
this
is
demonstrating
the
motivation
for
the
release.
So
here's
a
screenshot
from
our
release
that
came
out
last
week-
or
you
know
it
was
last
week
and
so
the
theme
kind
of
of
this
one
was
making
informed
decisions.
So
you
know
we
try
to
tie
it
all
in
like.
Why
were
the
features
that
we
worked
on
important?
B
We
want
to
give
context
on
that
to
the
community,
so
they
know
why
these
things
were
necessary
and
we
gave
a
little
bit
of
context
there
as
to,
in
this
case,
making
informed
decisions.
We
released
a
lot
of
visualizations
for
the
portal
and
other
things
to
assist
people
in
that,
and
the
last
part
of
our
qa
of
our
delivery
phase
is
the
qa
processes.
So
we
of
course
have
our
testing
features.
We're
really
focused
on
testing
qa,
something
super
important
to
us.
B
Our
our
stack
is
comprised
of
a
lot
of
moving
parts,
so
we
have
application
layer,
which
is
our
ui.
We
have
middleware,
which
is
the
dyjs
library,
and
then
we
have
back-end,
which
is
the
gov
polling
database
and
also
the
blockchain
itself.
So
a
lot
of
challenges
there
so
incorporating
integration,
test,
unit,
testing
and
then
manual
testing,
just
using
the
app
as
a
user
would
in
order
to
to
maintain
the
best
quality
there.
So
again,
automated
delivery
with
ci
systems.
B
B
B
Of
course,
we're
also
creating
documentation,
guides
and
technical
diagrams
to
go
along
with
our
releases,
and
importantly,
we
have
a
narrow
domain
focus.
So
what
I
mean
by
that
is
we,
our
team
is
strictly
focused
on
governance,
we're
not
you
know
doing
anything
with
auctions
or
any
other,
any
other
sub
module
of
the
maker
protocol.
B
So
that's
gonna
allow
the
entire
team
to
focus
just
on
this
one
product
which
is
gonna
to
get
a
lot
more
eyes
and
a
lot
more
focus
on
that,
so
that
should
really
help
with
the
quality
in
the
future
as
well.
So
we
do
one
thing
and
do
it
well
and
for
us
that
will
be
governance
and
then
this
is
an
example
of
a
technical
diagram
that
that
thiago
put
together
for
us
when
we
released
the
vote
delegation
feature.
B
So
just
this
is
the
quality
of
of
sort
of
documentation
that
we
want
to
deliver
with
with
releases.
So
you
know
when
we
put
out
new
features
that
have
complicated
user
flows.
You
know
these
are
the
sort
of
things
that
can
come
along
and
make
it
easier
for
people
to
comprehend
all
right
and
then
the
last
and
final
stage
is
the
analyze
and
reflect
stage
for
our
strategy
after
delivering
a
product.
B
So
that
was
a
big
portion
of
what
we
wanted
to
talk
about
today,
but
I
think
it's
important
to
get
our
processes
out
there
and
have
people
understand
what
motivates
us
and
why
and
how
we're
going
to
do
the
work
that
we
say
that
we're
going
to
do
so.
Moving
on
to
everybody's
favorite
topic,
we'll
talk
about
the
budget
for
our
our
core
unit.
B
It's
you
know.
This
is
based
off
with
help
from
svs,
and
we've
done
a
lot
of
work
to
define
this
as
as
accurately
as
possible.
So
we
have
a
few
budget
allocation
items
here.
So
our
contributor
compensation,
we
have
four
full-time
senior
engineers,
one
full-time
product
manager
and
one
full-time
designer
ux
specialist.
B
So
the
total
cost
of
these
employee
compensations
or
employees
are
contractors,
so
contractors
often
have
to
take
care
of
health
benefits
insurance
other
expenses,
which
is
why
we
justify
this
cost,
because,
if
you're
an
employee,
sometimes
you
you're
you're
able
to
get
benefits,
you
know
benefits
covered
and
so
on.
So
for
contractors,
it's
a
little
bit
more
difficult,
travel
and
conferences.
Again.
This
is
right.
Here
is
based
on
six
people
going
to
three
conferences
per
year
at
about
three
thousand
dollars
per
person
per
conference.
B
So
this
is
conferences
are
a
great
way
to
keep
retention
and
keep
morale.
High
people
love
going
meeting
going
out
meeting
people
and
it's
a
good
way
to
get
the
team
together
to
work
on
things
as
well.
So
we
in
fact,
are
hoping
to
all
go
to
the
lisbon
liz
con
conference
next
month
and
we're
planning
a
team
off-site
workshop
there.
B
This
is
high
because
of
our
software
subscriptions
cloud
services
analytics
and
tooling.
We
have
aws,
we've
got
databases,
application
monitoring,
so
we
have
a
lot
of
expenses
related
to
maintaining
our
our
it
infrastructure
gas
costs.
So
we
we
try
to
do
as
much
testing
as
we
can
on
test
nets.
We
have
we're
working
on
and
getting
our
gurley
deployment
system
set
up,
but
at
the
same
time
you
have
to
test
on
mainnet
a
lot
and,
of
course,
that
cost
gas.
B
B
Gas
was
about
120
ways,
so
yeah
that's
an
expensive
cost
for
for
us
to
undertake
and
the
professional
and
legal
costs.
This
is
a
big
topic
that
we've
been
talking
a
lot
lately
with
ses,
and
it's
really
important
for
us
to
cover
our
legal
services
and
our
financial
services,
our
payment,
processor
fees.
We
are
working
with
a
legal
team
to
develop
terms
and
and
conditions
that
we
can
apply
to
the
the
front
end
because
we
want
to
protect
our
team
members
legally
there
as
well
and
contractor
services.
B
We
may
need
to
occasionally
hire
out
contractors.
Devops
we've
been
working
with
the
tech,
ops
team
as
well
security,
auditing
quality
assurance
stuff,
like
that,
we
may
need
to
reach
out
to
people
to
get
some
additional
help
with
those
things
the
one-time
costs.
This
is
a
hardware
welcome
package,
that's
intended
to
subsidize
new
technique,
new
tech
equipment
for
team
members
or
office
equipment,
or
you
know
remote
working
things
when
you're
working
remotely
like
we
all
do,
there's
a
lot
of
expenses
that
go
into
building
out
your
your
work
environment.
B
So
this
total
cost
here
per
quarter
is
420
000
and
then
we've
added
this
contingency
buffer,
which
brings
us
to
483
000,
and
so
our
model
of
funding
is
basically
a
three-month
continuous
runway.
So
we're
asking
for
this
three-month
runway
up
front
when
when
we
create
or
when
our
mip
goes
up
to
vote,
and
then
from
that
point,
each
month
we
re-evaluate
the
three-month
runway
and
we
top
up
whatever
is
needed
just
to
kind
of
get
back
to
this.
This
new,
whatever
we
reevaluate
with.
B
B
B
So
this
is
pretty
much
exactly
like
all
the
other
teams
are
working
three-year
vesting
period,
12-month
cliff
fest
and
then
every
six
months
after
the
cliff
fest
okay,
so
that
was
the
fun
stuff,
and
now
we
get
to
the
prioritization
and
road
map.
So
this
is
this
is
actually
the
real
exciting
stuff
to
kind
of
give
you
guys
a
sense
of
where
we're
going
and
how
we
want
to
get
there.
B
So
work
that
aligns
with
our
governing
principles,
which
are
accessibility,
neutrality,
transparency
and
verifiability
is
prioritized,
and
also
we
wanted
to
call
out
a
special
note
to
dao.
Why
prioritization
so
when
long
for
wisdom
posted
a
really
informative
forum
post
recently
about
prioritization
in
endow
and
the
challenges
involved
thereof,
so
we
we
need
to
align
our
prioritization
framework
with
the
dao's
priorities
to
the
best
of
our
ability,
and
once
again
our
pm
dennis
here
has
a
lot
of
enthusiasm
for
this
topic.
B
We
want
to
adhere
to
continuous
and
public
prioritization
and
planning
instead
of
working
in
a
static
roadmap.
So
for
us
this
is
going
to
be
using
our
frill
idea
board
as
sort
of
a
public
face
to
our
roadmap
and
the
prioritization,
and
that
allows
people
to
go
in
and
offer
their
opinion
and
really
collaborate
with
the
community
on
how
we
want
to
work
there.
So
that
will
always
be
something
that
is
transparent
from
us
and
publicly
available
to
everybody.
B
But
that
being
said,
you
know
we
don't
give
the
idea
that
we
don't
have
a
delivery
timeline
for
work,
so
we'll
always
have
a
delivery
timeline
for
the
immediate
work
that
we're
doing
like
any
other
web
2
team.
But
as
we
prioritize
things
down
the
road,
we
don't
look
as
far
ahead.
We
want
to
make
sure
that
we're
agile
enough
to
to
change
up
if
the
need
be
and
then
so
here
is
the
concrete
stuff.
It's
not.
B
This
is
our
prioritized
work
for
the
rest
of
q4,
so
there's
a
few
items
here,
they're
not
in
a
priority
order.
Yet
so
it's
not
like
this
is
the
priority
we'll
be
working
on
them,
but
these
are
the
things
that
our
team
has
kind
of
come
together
with
and
and
that
we've
got
from
the
frill
board.
This
is
a
snapshot
of
that
thrill
board.
B
As
we
worked
on
it
yesterday,
we
kind
of
synthesized
some
of
those
things
so
just
really
quickly
to
go
over
some
of
this
adding
more
methods
for
manual
verification
of
important
data
points.
So
this
comes
in
light
of
what
we
dealt
with
last
week
with
the
difficult
to
verify.
Make
your
way
so
we'll
find
ways
to
let
people
audit
that
and
verify
those
things
on
the
site.
B
We
want
to
add
the
on
chain
effects.
Tab
that's
been
highly
requested.
We
want
to
really
look
into
how
we
can
improve,
commenting
and
context
building
for
polls
and
executives.
So
there's
a
lot
of
ideas
there
and
that's
been
a
very
popular
request
from
people.
We've
talked
to
we're
going
to
continue
to
improve
our
user
account
page,
which
we
released
last
release
last
week,
the
landing
page.
B
We
want
to
redo
that
that
I
think
that
has
been
a
while
that,
since
it's
had
a
nice
refresh,
and
we
want
to
find
a
way
that
we
can
utilize
the
landing
page
to
kind
of
funnel
users
into
the
platform
epns
integration-
we
talked
about
a
little
bit.
But
again,
this
is
allowing
us
allowing
us
to
provide
people
to
subscribe
and
get
notifications
for
events
that
are
going
on
on
the
protocol.
B
And
then
we
want
to
explore
moving
maker
governance
to
l2
or
leveraging
l2s
in
some
way-
and
this
is
a
pretty
big
undertaking.
But
this
we're
going
to
explore
this
process
and
see
what
that
might
take
and
if
that
would
be
impactful
for
people
to
to
encourage
people
to
get
get
participating
in
governance
and
then,
like
I
said
we're.
B
We
have
a
meeting
later
today
after
this
to
discuss
our
testing
processes
and
improve
that
that's
a
big
deal
for
us,
especially
because
you
know,
in
light
of
the
the
issues
that
we
ran
into
last
week.
We
want
to
make
sure
that
we
are
really
tightening
down
that
qa
process
make
it
iron-clad
fixing
our
deployment
pipeline
and
then
auditing,
all
of
our
third-party
dependencies
that
we
rely
on
and
seeing
maybe
where
we
can
decentralize
some
of
that
or
remove
things
that
aren't
necessary
for
our
security.
B
C
B
B
Definitely
be
a
collaboration
that
we
would
be
looking
to
have
with
the
protocol
engineering
team
and
any
other
team
core
units
that
that
are
interested
in
talking
to
us.
The
first
phase
is
definitely
just
an
exploration
phase
and
figuring
out
how
it
can
be
done,
maybe
bringing
some
of
our
ideas
to
various
core
units
like
the
pe
team
or
tech,
ops,
team
and
just
learning
about
what
it
would
take.
We
recognize
that
a
lot
of
the
the
hard
work
wouldn't
be
done
by
our
team,
because
we
don't
have
that
that
experience.
A
B
You
know
financial
losses
or
even
the
protocol
itself
can
be
dangerously
affected
if,
if
something
goes
wrong,
so
we
need
to
have
legal
coverage
for
us
to
to
protect
us.
In
case
of
you
know
some
errors
or
something
like
that.
That
would
happen
if
somebody
lost
their
money
or
they
or
something
happened
to
the
protocol.
We
we
don't
want
to
be
sued.
Obviously,
for
that,
so
we
need
to
come
up
with
an
entity.
That's
a
limited
liability
entity
that
can
sort
of
protect
us
from
from.
A
A
What
are
your
plans
regarding
that?
Yeah?
That's
a
that's
a
great
question
and
I'm
personally
really
excited
about
it,
because
I
think
the
way
that
especially
d5
teams
need
to
work
on
something
like
this
is
is
very
different
from
let's
say
a
traditional
web
2
company,
where
you
have
like
a
top-down
strategy
right
and
then
you
have
static
road
maps,
all
that
kind
of
stuff.
A
I
think
in
maker,
since
we're
working
on
yeah
consensus,
based
decision
making
and
we're
working
on
a
space
that
just
moves
very
quickly
and
then
I'm
talking
about
the
the
maker
down
context,
but
also
defy
as
a
whole
right.
So
therefore,
I
think
we
need
to
look
for
yeah.
We
need
to
use
tools
that
that
match
this
context.
I
really
like
frill,
because
it
allows
us
to
do
everything
out
in
the
open
right.
A
The
idea
is
that
we
we're
going
to
use
it
as
a
publicly
available
tool
for
anyone
to
to
give
feedback
or
or
post
ideas.
It
can
also
be
used
by
pseudonymous
users,
and
then
we're
actually
going
to
use
this
to
yeah
basically
index
all
of
the
ideas
that
we
have
also
the
ideas
that
come
from
the
team
itself
and
we're
going
to
actually
make
sure
that
the
prioritization
exercise
happens
in
this
tool
as
well.
So
it
will
be
open
for
everyone
to
see
what
the
prioritized
list
is.
A
A
Phil
already
mentioned
the
one-on-one
interviews
that
we
that
we
did
we
plan
to
do
a
lot
more
of
those,
and
the
idea
is
to
basically
funnel
all
the
insights
and
ideas
onto
that
board
and
just
make
sure
it's
out
there
for
everyone
to
see,
and
it
also
allows
for
us
to
yeah
stay,
keep
people
informed
on
the
status
of
these
cards
right.
So
if
we,
if
we
plan
something
in
a
sprint,
we'll
just
make
sure
that
we
comment
it
in
that
particular
work
item.
A
And
if
we
know
when
we're
gonna
deliver
it,
then
we
can
also
add
it
there,
and
I
don't
know,
that's,
I
think,
that's
a
really
cool
way
of
working
out
in
the
open
and
yeah.
I
think
it
matches
our
context
very
nice.
Hopefully,
the
rest
of
the
coordinates
we'll
start
going
towards
a
more
open
model
that
we
I'll
be
great
for
everyone.
I
think.
D
A
B
Oh,
that's
a
really
good
question
from
your.
The
amount
of
tokens
that
you
hold
is
equivalent
to
your
weight
in
the
vote,
so
there
is
no
minimum
amount
to
hold,
but
there
your,
however
much
you
have
will
be
the
way,
the
weight
that
you
vote
with.
So,
if
you
have
say
a
fraction
of
one
mkr,
your
voting
weight
is
a
fraction
of
that.
If
someone
else
who
has
maybe
ten
thousand
floating
weight
mkr.
So
in
that
respect,
it
can
be
it's
difficult.
This
is
one
of
the
challenges
that
we
face.
B
It's
difficult
to
encourage
people
who
have
a
very
little
amount
of
mkr
to
participate,
because
you
know
the
gas
costs
alone
make
it
not
really
worth
it
and
your
impact.
If
you
don't
have
a
lot,
you
have,
you
don't
have
a
great
impact.
So
this
is
one
of
the
main
reasons
why
we
implemented
the
delegation
feature.
So
if
you
are
familiar
with
that
or
in
case
you're,
not
you
can
delegate
your
mcare
to
an
individual
who
can
then
vote
on
your
behalf.
B
So
it's
a
good
way
for
a
lot
of
smaller
amcara
holders,
to
sort
of
to
collaborate
to
group
together
and
and
become
like
a
larger
unit
that
they
can
vote.
So
personally,
I
think
that's
a
really
I'd
love
to
see
that
in
the
future
of
vote
delegation.
It
is
you
know,
getting
people
to
kind
of
co-organize
and
combine
all
their
mkr
into
a
much
larger
voting
weight
so
that
they
can
have
more
impacts.
C
C
B
Yeah
definitely
there's
definitely
issues
and
communications
between
core
units
is
going
to
just
become
an
even
more
difficult
problem
than
it
was
at
the
foundation.
Fortunately,
we
we
all
have
like
some
pretty
a
lot
of
good
relationships.
We
have
good
relationships
with
the
tech,
ops
team
and
with
the
the
protocol
engineering
team.
So
in
we
have
our
own
discord,
chat
the
ducks
team
and
we
have
sub
channels
for
communications
with
each
of
those
teams
that
we
we
talked
about
and
a
lot
of
teams
have
their
own
community
communication
channels
as
well.
B
B
B
I
know
that's,
maybe
that's
a
little
selfish,
but
it
gets
people
onto
our
platform
and
when
we
have
problems
that
we
need
to
discuss,
you
know
we're
active
actively
talking
to
tech
ops
every
day
they're
in
our
channels,
talking
with
us
about
various
things.
Pe
team
as
well
so
right
now
we're
working
on
the
best
possible
solution
for
that.
But
but
we
have
a
lot
of
like
interim
solutions
right
now,.
C
C
B
Yeah
definitely
so
to
your
first
question
about
improving
communication
that
that's
a
major
thing
on
our
roadmap
and
that's
something
that
we
as
a
team
have
talked
about
a
lot
and
it's
something:
we're
gonna
figure
out
the
best
approach
to
that
like
we
don't
specifically
have
any
plans
to
improve
the
discourse
page,
although
something
we
can
bring
to
the
table
and
talk
about
internally.
But
I
think
it
would
be
something
that
we'd
rather
do
is
find
ways
to
bring
communication
onto
the
governance
portal.
B
Like
you
said,
the
forum
can
be
difficult
for
people
to
to
jump
in
on
and
communicate.
It
works
well
for
some
people,
but
not
for
everybody
and
then
so
to
find
ways
to
bring
the
conversation
to
the
portal
and
closer,
more
importantly,
closer
to
the
polls
themselves
closer
to
the
executive
votes
themselves,
so
that
you
don't
have
to
go
to
all
these
different
places
to
to
get
the
information
that
you
need,
and
that
was
one
of
the
things
that
we
talked
about.
B
I
know
with
you
and
with
other
people
is
like
having
all
these
different
platforms
that
you
need
to
kind
of
remember,
to
interact
with.
In
order
to
get
all
of
your
information,
so
even
if
it's
maybe
embedding
the
discord
or
sorry
embedding
of
forum
posts
in
the
tab
in
a
polling
page
or
something
like
that,
you
know
we
can
definitely
talk
about
looking
into
you
know,
I
don't
know
what
kind
of
configurability
there
is
for
the
forum.
B
I
think
it's
a
third
party,
maybe
there's
some
options
that
we
can
do
to
improve,
look
at
to
improve
the
ux
there,
but
I
think
our
main
focus
would
be
like
finding
a
way
to
to
bring
that
conversation
to
the
portal,
and
so
then
your
second
question
about
keeping
up
with
the
jones
is
yeah.
We
we
definitely
have
our
eyes
on
tally,
boardroom
snapshot
and
yeah
we're
following
those
projects
we're
gonna,
learn
from
them.
B
B
C
B
D
The
the
goal
is
as
a
high
level
goal,
which
is
to
increase
and
to
improve
and
build
the
best
governance
user
experience
as
possible,
and
the
reason
why
we
structure
it.
That
way
is
because
we
want
teams
to
consider
these
kind
of
factors
that
you
talk
about,
which
you
know
if,
if
you
really
interpret
it
very
narrowly,
that
would
be
other
scope
for
the
voting
portal.
But
because
the
core
unit
has
has
a
broader
mission
of
improving
governance
user
experience.
D
It
would
be
in
scope
to
start
a
conversation
about
the
fact
that
the
forum
really
is
confusing
users,
and
does
you
know,
does
not
contribute
to
govern
governance,
user
experience
or
organize
a
roundtable
to
have.
You
know
to
have
a
brainstorm
session
about
how
governance
user
experience
can
be
improved
with
the
wider
ecosystem
and
so
on.
As
was
mentioned,
collaborate
integrate
with
other
projects
to
to
improve
the
governance
user
experience.
D
So
those
kind
of
considerations
are
exactly
the
reason
why
we
want
core
units
that
are
focused
on
a
single
domain
and
they
have
a
mission
that
is
not.
You
know,
narrowly
interpreted
as
being
responsible
for
you
know,
keeping
this
web
page
online
so
that
that
should
also
help
to
to
get
a
better
end
result.
A
D
I
I
have
a
question
regarding
the
the
the
road
map.
Is
there
at
this
point?
Is
there
any
anything
on
the
radar
regarding
creating
more
transparency
around
the
the
what
what
goes
into
an
executive
vote,
especially
the
spell
there
was
the
the
feature
of
the
on
chain
effects,
and
I
can
imagine
other
mechanisms
to
improve
the
the
transparency
for
executive
spells
anything
you
could
elaborate
on
there.
B
Yeah
definitely
so
yeah
for
those
are
like
the
first
two
bullet
points
for
this.
The
voting
portal
improvements
like
when,
when
I
say
manual,
verification
of
important
data
points.
That's
you
know,
that's
one.
We
want
to
add
ways
for
people
to
you
know
either
link
out
to
could
be
ether,
scan
could
be
etx
or
it
could
be
yet
another
ability
for
someone
to
kind
of
verify
the
data
that
that
they're,
seeing
on
the
portal
and
then,
like
you,
said,
the
unchained
effects
tab,
that's
one
of
our
highly.
B
D
More
parties
will
get
involved.
So
that
might
be
an
interesting
avenue
to
think
about
how
the
dao
internally
organizes
and
the
the
kind
of
the
process
that
is
currently
run
through
rocket
chat.
It's
it's
a
channel
where,
like
the
different
participants,
they
they
share.
What
will
be
included
in
the
executive
vote
and
then
there's
a
lot
of
manual
work
by
by
the
gov
alpha
team
to
to
collect
all
that
information.
D
Make
sure
that
everyone,
like
reviews,
their
part
that
I
thought
was,
was
something
interesting
which
could
be
a
future
addition
to
the
to
the
voting
portal
to
help
organize,
also
that
internal
process
of
how
an
executive
vote
gets
even
composed
right
and
help
the
different
dow
participants
to
to
coordinate
around
that.
So
if
I
yeah
I'll
I'll
take
some
time
and
and
maybe
submit
a
few
ideas
to
the
frill
board,
so
that's
one
possibility
that
I'm
excited
about.
B
Yeah
that
that
is
very
cool
and
it's
you
know
it
expands
the
definition
of
what
the
voting
portal
is
capable
of
like
right.
Now,
you
think
of
the
voting
portal
as
just
a
way
to
vote
on
things.
I
mean
we
call
it
the
voting
portal,
but
well,
actually
we
call
it
the
governance
portal,
but
sometimes
we
call
it
the
voting
portal,
but
to
include
all
you
know,
more
capabilities
for
that
and
since
spells,
are
such
an
important
part
of
governance.
I
think
that
would
fall
under
our
domain.
B
B
You
know
if
anyone
wants
to
just
put
like
.01
mkr
on
no
just
to
kind
of
like
make
us
feel
like
there's
a
chat
like
you
know.
We
need
to
improve,
then
go
ahead,
but
no,
but
very,
very
thankful
to
everyone.
Who's
who's
excited
about
our
team.
It
means
a
lot
to
us
and
it
motivates
us
to
do
good
work.
So
thank
you
all.
B
B
Maybe
if
somebody
has
that
link
on
the
team
and
they
want
to
jump
and
then
for
anything
else,
please
come
to
our
discord
or
if
you
need
us
to
come
to
your
discord,
we
will
do
that
or
if
you,
if
you're
old,
school
and
you're
only
on
rocket
chat,
we're
still
there
too.
So
you
can
reach
out
to
me,
I'm
at
phillip
rocketjet
on
rocketchat,
but
yeah
come
on
over
to
our
discord
dennis
posted
the
link
there
come
over
to
our
frill
page.
A
Call
I
was
really
excited
to
be
part
of
all
of
this
and
yeah
just
looking
forward
to
collaborating
with
the
other
core
units
as
well.
That's
something
we
are
personally
really
looking
forward
to
now.
That's
what
it's
gonna
look
like,
but
yeah
for
now.
I
think
this
this
this
yeah
covers
all
of
it,
so
good
job
phil.