►
From YouTube: DXgov Weekly Meeting [2021-03-24]
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Welcome
to
deep
stock
governance,
discussion
march
24th
2021,
starting
first
with
the
proposal
roundup
and
we're
doing
proposal
roundup
on
both
mainnet
and
xdi.
So
looking
at
mainnet
first
just
past
about
an
earlier
this
morning
or
late
last
night
was
a
proposal
to
deposit
250
eth
into
swapper
on
x
dot,
and
so
this
will
be
spread
across
four
pairs.
B
The
west
wx
die
the
west
wbtc,
the
usdc
wxdi
and
the
west
dpi
or
d5
pulse
index
and
it'll
be
25,
so
that'll
add,
on
top
of
the,
I
think,
around
two
hundred
thousand
dollars
worth
of
existing
liquidity
on
swapper
on
xdi.
So
I
just
didn't
know,
but
it
would
be
good
if
we
could
do
some
of
the
mainnet
transactions
for
these.
B
I
don't
think
we've
redeemed
the
proposal
yet
so
we
could
do
the
mainnet
transactions
for
these
and
then
bridge
them
over
and
then
there'll
be
an
x
die
in
the
x
dive
base
and
then
we'll
have
to
proposal
there
to
get
them
over.
But
that
proposal
has
just
passed,
so
we
could
have
we'll
be
moving
that
over
to
exercise
soon
and
then
next,
a
gen
member
balancer
reimbursement.
This
is
because
we
need
jen
to
do
holographic
consensus
and
we
were
doing
a
proposal
on
next
time.
B
We
were
running
out
of
gen,
so
we
I
think
it
was
geronimo
bridged
over
some
gen
2xsty
deposited
into
the
xdx
style
base
on
xi
and
then
now
is
requesting
a
reimbursement
for
that
on
mainnet.
B
The
third
is
tony's
second
month
payment
tony
was
working
with
the
swapper
team,
and
so
this
is
completion
of,
I
think
the
second
month.
I
don't
think
he's
continuing
with
us,
but
this
is
a
payment.
I
think
for
the
work
he's
he's
already
done
and
then
next
is
convert
a
hundred
each
to
die
and
bridge
to
xdx
tao.
B
So
this
would
just
be
another
deposit
into
xdx,
dow
for
general
operating
funds.
So
we
made
we
last
made
the
first
deposit
into
x
die.
I
think
it
was
almost
a
month
ago
and
so
we've
had
about,
I
think
fifty
thousand
dollars
worth
of
worker
payments
that
have
come
out
of
that
original
deposit.
So
this
is
just
going
to
start
the
process
of
re-upgrading
that
with
about
170
000
or
whatever
he
eats
that,
and
then
there
are
the
next
rounds
of
liquidity
deposits
into
swapper.
B
So
there's
another
250,
each
proposal
to
deposit
to
bridge
over
liquidity
across
those
same
four
pairs
into
swapper
on
xdi.
I
think
that'll
pass
on
like
sunday,
maybe
and
then
I
just
submitted
a
proposal.
B
I
think
it
got
accepted,
but
I
actually
wasn't
seeing
the
ui,
but
this
would
be
a
300
eth
deposit
into
swapper
mainnet,
and
so
this
would
be
actually
done
through
the
liquidity
relayer,
but
that
liquidity
really
is
still
currently
controlled
by
the
dev
multisit.
So
we
did,
I
think,
a
test
deposit
last
week
of
a
little
under.
B
I
think
it
was
100
heath,
so
we
have
some
existing
liquidity
on
swapper
mainnet
and
then
this
would
be
an
additional
300
each
just
on
the
die
eighth
pair,
and
that
would
kind
of
give
us
a
a
nice.
I
guess
about
six
hundred
thousand
dollars
worth
of
liquidity
in
that
pair
and
that
will
be
transferred
to
once
the
relay
is
transferred
to
dx
style
base.
B
Then
that
then,
the
liquidity
that's
in
the
relay
now
will
be
transferred
there,
and
so
this
is
kind
of
just
all
part
of
the
process
of
of
building
up
liquidity
in
in
swapper.
So
those
are
the
mainnet
proposals.
I
think
right
now
any
thoughts,
comments.
B
B
Cool
and
then
looking
at
x
diabase
a
couple
things
on
x
I
base.
So
I
think
we
are
like
45
minutes
from
this
proposal.
Closing
so
the
dx
does
dxdow
support
eip
1559.
B
We
think
we
are
24.95
percent
in
favor
across
11
votes,
and
this
closes
the
next
hour
and
a
half.
So
if
you
have
rep
on
xti
make
your
voice
hurt,
I
think
it's
good.
We've
got
11
people
voting
for
this
and
got
about
a
quarter
of
the
rep
on
x
dot.
B
So
that's
the
that's
a
proposal
there's,
I
think
five
different
proposals,
one
for
hexel
from
omen
team
lee
from
mesa
venky's
proposal,
fluid
drop,
who's
dave
has
been
helping
out
with
some
of
the
treasury
stuff
and
then
sky
and
then
there's
also
a
reimbursement
for
dxo
ens
management.
So,
of
course,
like
geeksdale
owns
a
lot
of
enss
and
these
have
to
be
renewed
from
time
to
time.
B
So
I
think
that
proposal
is
reimbursing
some
someone
who
had
renewed
the
the
ens
domains
on
behalf
of
dx
dow,
and
then
there
is
a
couple
proposals
related
to
swapper
and
xdi.
There
is
a
proposal
to
add
tokens
to
the
dxdoll
list
on
xdi.
That
would
be
the
third
proposal
for
that
third
proposal:
that's
added
list.
B
I
think
we
have
20
different
tokens
on
that
list
now
and
then
there's
another
test
proposal
to
unpool
liquidity
from
swapper,
just
to
make
sure
that
we
can
do
that
and
then
in
the
next
day
or
two,
there
will
be
a
couple
different
proposals
related
to
the
swapper
xdy
liquidity
deposit
from
the
250
east
proposal
that
we're
bridging
we
should
bridge
over
today,
because
once
we
get
that
2x
died,
then
we
have
to
figure.
B
We
have
to
go
through
the
proposal
process
on
xdi
to
get
it
into
swapper
owned
by
dx,
dow,
so
yeah
questions
thoughts.
Anything
on
xdi
proposals.
B
So
I
guess
there
was
a
little.
The
the
ui
was
was
acting
up
a
little
bit
yesterday
and
I
don't
know
if
that
was
related
to
yeah.
Was
that
just
on
xdi
or
was
that
like
alchemy
in
general?
I
don't
know
if
nico
is
on
the
call.
C
Yep
so
as
far
as
I'm
no
but
I'm
not
100
sure
it
was
just
an
issue
on
the
x-ray
base.
John,
do
you
know
if
it
was
affected
on
maynard
as
well.
D
E
Yeah
they
update,
they
updated
the
the
version,
but
not
the
sub-graph
version
and,
and
it
messed
things
up.
I
think.
B
The
only
reason
I
care
is
because
I
had
a
proposal
that,
like
I
thought,
had
failed
and
I
was
like
kind
of
upset
because
I,
like
is
like
to
add
to
the
token
list
and
I'd
use
the
simulator
before
so.
I
was
like
really
sure
that
this
proposal
was
going
to
go
through
and
then
it
just
like
didn't
do
it
and
I
was
like
oh
no.
What
did
I
mess
up?
So
I'm
more
actually
relieved
that
it
was
alchemy.
F
F
F
F
Like
I
had
trouble
like
going
to
xdi
with
brave,
you
know,
how
do
you
do
that,
like
I,
I
have
metamask
on
mobile,
but
they
don't
have
exact
there
to
connect
with
well
connect.
F
E
E
E
Think
it's
in
the
live
store
now
at
least
on
ios,
and
I
imagine
google
it
shouldn't
be
test
flight
now.
E
B
B
H
H
How
can
we
add
the
cell
line
to
the
graph
where,
whether,
if
we
are
going
to
show
it
or
not,
there
are,
of
course
a
few
other
things
that
we
can
that
we
can
add
in
the
dab,
but
the
main
idea
was
to
update
the
new
design
based
on
what
said
share
with
me
on
on
january,
that
has
been
done
and
to
update
the
cure
when
we
set
the
minimum
investment
to
a
max
unit
is
allowing
future
buys.
H
The
idea
was
for
the
that
to
show
that
the
buy
was
disabled,
we
tested
and
wrinkle
on
wrinkle
and
it
worked,
and
I
added
I
created
a
pull
request
with
the
change
removing
the
cell
line.
So
overall,
I
think
we
are
good
to
go,
and
I
did
I
added
the
how
the
process
will
be
in
the
in
the
topic
on
dow
talk.
It
will
be
merging
two
po
requests.
Once
we
merge,
one
is
going
to
make
the
deployment
to
ipfs,
we
can
check
the
ipfs
deployment
and
then
we
will.
H
We
will
need
to
assign
the
new
ens
address
of
the
app
okay
of
the
extras
that
that,
once
we
update
the
cure
with
the
setting,
the
minimum
investment
to
max
unit
is
going
to
show
that
the
buy
is
disabled
in
the
lab.
So
we
will
have
to
create
two
proposals
on
mainly.
H
We
can
we
can,
we
can
do
it,
it's
we
already
have
the
options
there
I
was.
I
was
already
trying
to
feed
the
trying
to
submit
the
proposal
like
fill
the
proposal
to
submit
or
seems
to
work,
so
we
should
be
ready
to
go
and
the
the
only
thing
that
I
that
I
need
is
some
assurance
from
the
rest
of
the
community
and
the
workers
who
don't
take
the
individual
initiative
here.
B
Well,
of
course,
it
will
only
be
approved
on
chain,
so
it
has
to
be
ratified,
but
it
gets
out,
but
so
just
for
kind
of
clearly
there
so
they're
really
like
two
different
things
that
are
happening.
One
is
changing.
The
minimum
buy
amount
and
that's
like
dx
doubt
interacting
with
the
bonding
curve
contract
and
then
two
is
updating.
B
The
ui
at
dxtrust.eth
to
show
that
buying
is
disabled
and,
like
the
multi-call
scheme,
can
interact
with
the
the
contracts
and
then
typically,
we
would
update
the
website
through
the
ens
scheme,
which
is
only
three
days,
but
the
only
reason
I
guess
it
matters
to
update
the
site
is
when
the
bonding
curve
is
disabled.
So
I
think
it
would
make
sense
to
do
those
like
both
within
the
same
proposal
and
I
think,
brought
like
there's
pretty
broad
consensus
that
we
want
to
move
move
forward
with
this.
B
So
I
don't
know
if
anyone
else
has
any
thoughts
or
objections
or
questions
about
the
logistics
of
being
able
to
submit
this
proposal.
H
B
Cool
all
right,
well,
that'll,
be
exciting
and,
like
so
that'll
propose
I'm
just
assuming
everything
kind
of
goes
ahead.
That
means
we're
like
around
eight
days,
maybe
the
end
of
next
week
when
the
bonding
curve
or
when
that
proposal
would
pass.
Presumably
it
gets
through
rep
holders
and
so
keenan.
Maybe
we
we
probably
will.
Maybe
I
don't
know
if
we'll
just
do
a
tweet
about
it,
because
that's
also
like
the
same
day
that
we
were
thinking
of
going
out
with
the
month
in
review.
B
So
maybe
we
just
like
kind
of
lead
with
that
in
there,
but
we'll
we'll
wait
for
the
yeah,
we'll
see
what
the
proposal
and
kind
of
organize
some
type
of
comps
off
of
that.
I
I
I
had
a
bit
of
a
connection
issue.
This
is
referring
to
eip159
right.
B
No,
this
is
a
bonding.
This
is
the
bonding
curve.
Okay,
awesome.
We
should
do
that
like
in
that
I
think
it's
just
a
simple
tweet
like
yeah
and
deep
style
supports
eip
one
five,
five,
nine
or
whatever,
but
then
this
is
maybe
for
next
week.
So
august
is
talking
about
the
bonding
curve
proposal
that'll
submit.
So
once
that
passes,
we
want
to
have
some
comms
off
of
that.
So
I'm
trying
to
think
of
what
that
looks
like,
but
we
can.
We
can
chat
about
that
offline.
I
Yeah
absolutely
we'll
touch
base
and
I
think,
before
the
month
review
or
on
the
day,
I
would
be
great
yeah.
H
H
B
Sweet
and
then
moving
along,
I
wanted
to
talk
about
governance,
refunds,
gas
refunds,
so
we
had
calculated
them
for
january
and
february,
and
we
kind
of
posted
that,
but
we've
actually
not
deployed
the
contract.
For
that,
and
so
I
want
to
talk
about
the
logistics
of
that
and
then
also
dave
is
taking
over
this
kind
of
gas
reimbursement
role
from
nico
and
so
he's
kind
of
doing
a
couple
things
with
this
in
terms
of
like
putting
it
together
so
dave.
B
J
Exactly
yeah,
I
think
well,
the
question
is
like:
do
we
do
the
refunds
for
the
main
net
on
the
main
net
and
the
refunds
for
x
die
or
next
time
or
because
of
gas
fees?
Should
we
do
everything
on
x-tie
now
and
then
yeah,
as
you
said,
like
the
frequency
just
to
kind
of
get
general
consensus,
what
you
guys
think
if
it
should
be
done
monthly,
if
it
should
be
done
every
two
months,
three
months?
C
I'm
not
100
sure
but
yeah.
It's
definitely
some
bugs
to
deploy
and.
B
Maintain
I
mean
the
thought
being
like
and
that
just
the
addresses
that
are
paying
are
like
paying
in
eath
on
main
net
right.
So
like
a
lot
of
like
the
reimbursement
like
it's
just
going
to
go
right
back
to
eth,
to
pay
for
like
those
additional
proposals,
and
so
I
guess
it
does
like
on
the
facebook
it
does
kind
of.
It
makes
sense
that
reimbursement
would
be
on
main
met.
But
I
can
understand
that.
That's
just
like
a
cost
that
we
would
be
like
incurring.
K
B
Could
obviously
like
avoid
yeah,
I
don't
know
if
other
people
have
thoughts
about
whether
just
reimbursing
exercise
would
be
enough.
E
I
I
I
I
I
don't
think
the
cost
is
huge
for
like
the
claiming
of
these
refunds,
and
I
think
it's
important,
like
people
are
spending
the
eath
so
like
everyone
needs
basically
like
a
pot
of
gas
money
to
do
stuff
in
governance,
and
so
they
actually
need
the
eats
so
just
getting
back
a
porsche
a
high
portion
of
that,
so
that
you
can
then
use
it
again
for
the
next
two
months
on
gas
is
like
quite
important,
so
I
think
doing
it
in
ethon.
Mainnet
is
where
that's
being
spent.
E
J
B
Yeah
and
I
think
it's
like
the
same-
probably
the
same
dynamics
there,
because
it's
like
the
re
I
mean
the
reason
you're
getting
reimbursed
is
because,
like
your
main
net
eat
account
is
like
drained,
and
I
mean
we
obviously
need
to
track
this,
but
it
just
seems
like
for
reimbursement
costs,
it's
easier
to
do
them
on
the
same
network
that
the
cost
is
being
incurred,
but
I
could
understand
wanting
to
minimize
that
cost.
So
maybe
we
do
switch
to
like
a
three
month
or
two.
K
J
I
was
just
gonna
say
like:
are
we
also
starting
to
do
it
now
on
next
time,
because
I
mean
the
refunds
would
be
a
couple
of
cents
per
person?
Probably
right
like
does
it
make
sense
to
do
it
at
all
on
x-tie?
It's,
I
think
it's
more
a
question.
If
we
do
it
on
one
chain,
should
we
also
do
it
on
the
other,
or
are
we
just
doing
it
because
god's
calls
are
so
high,
like.
G
Yeah,
I
will
say
that
I
would
like
to
redeem
my
mainnet
gas
refund
on
xdi.
Well,
that's
what
we're.
G
E
J
E
G
B
I
think
the
redeem
is
is
more
like
five
to
ten
dollars,
but
like
there's
cost
to
redeeming
on
mainnet
for
sure.
C
Just
just
one
additional
note
that
we
should
keep
keep
track
of
like
let's
say
if
we
want
to
refund
on
x
die.
We
should
take
care
that
we
have
a
lot
of
gnosis
safe
users
on
mainnet
that
actually
don't
have
the
same
address
on
x-style.
So
we
would
actually
need
some
process
to
map
mainnet
to
x-style
on
a
constant
basis.
C
If
we
would
want
to
do
that,
that
would
work
for
sure.
But
if
we
don't
want
users
on
mainnet
to
actually
pay
something
on
the
redeem
function
of
the
contract,
we
could,
in
theory,
just
modify
the
contract
like
just
a
little
tiny
bit,
so
that
the
contract
itself
pays
the
gas
out
within
the
transaction
itself.
J
C
H
Another
another
thing
that
we
can
that
we
can
do
is
to
change
the
refund
contract,
use
only
one
contract
forever
and
ever
where
every
two
or
three
months
we
are
going
to
be
adding
how
much
any
every
the
exam
account
can
claim.
This
way,
you
will
be
accumulating
your
refund
over
over
the
time,
and
even
if
your
refund
is
very
low,
you
can
wait.
H
For
example,
I
know
six
months
to
claim
your
refunds
from
your
last
six
months,
so
you
can
claim
your
refunds
at
any
time
and
we
won't
need
to
deploy
a
contract
any
every
two
or
three
months.
This
will
solve
the
problem
where,
right
now,
your
the
the
refund,
you
have
like
two
months
to
claim
it.
So
if
I
can,
if
we
can
change
it
that
way
where
we
are
adding
how
much
every
the
excel
account
spent,
the
refund
will
be
cumulative
and
you
can
claim
it
whatever
you
want.
H
Whenever
the
gas
prices
is
fair
for
you
and
again,
it
will
be
super
cheap,
but
yeah,
taking
account
that
the
refund
per
account
is,
I
think,
no
less
than
50
dollars
and
the
refund
co
should
cost
between
five
and
ten.
It
is
going
to
be
that
way
where
you
send
the
index
of
the
account.
You
want
to
claim
this
way.
You
won't
have
to
look
through
all
the
other
accounts,
which
is
more
efficient.
B
Yeah
I
mean
I
do
think
we're
not
going
to
have
as
much
as
complicated
of
a
main
net
reimbursement
system
or
we're
not
going
to
need
it.
Just
because
we're
going
to
have
less
proposals
and
less
like
you
know
we're
not
going
to
propose
where
people
are
voting
on.
10
people
are
voting
on
it
at
least
like
right
now
we
do
want
to
encourage
people
to
voting
but
like
in
scalable
ways,
so
I
imagine
like
we
would.
B
B
We
could
probably
talk
about
this
a
little
bit
more
in
the
forum,
but
I
think
the
I
think
one
thing
we
should
probably
should
feel
comfortable
with
is,
I
think,
the
multi-sig
reimbursements,
I
think,
can
happen
on
mainnet
and
the
most
recent
proposal
actually
included
some
heath
for
those
reimbursements
and
then
dave
actually
put.
B
I
think
it
was
on
the
governance,
refunds
forum
posts,
put
the
gas
cost
incurred
by
each
of
the
addresses,
and
so
we
should
figure
out
some
process
for
like
when
the
multi-stake,
when
people
from
the
multi-state
get
reimbursed
for
gas
costs,
because
there
will
be
like
starting,
I
guess,
a
border.
We
redeem
this
proposal.
There
will
be
eth
in
the
multi-sig
for
those
addresses
to
get
re
imbursed.
H
H
Or,
if
not,
we
added
to
the
the
excel
refund.
Like
again,
we
add
to
the
excel
refunds
contract
that
can
also
work.
Whether
we
can
we
can
add
to
the
script
that
generates
the
the
refunds.
We
can
add
the
multi-signature
address
and
also
take
the
fees
of
how
much
each
account
in
the
multisignature
spent
on
boarding
on
or
on
executive
proposals,
so
that
can
be
added
to
the
script
and
yeah
we
can
refund
it.
B
Cool
and
like
that
yeah,
maybe
that's
like
the
the
long-term
solution,
so
we
kind
of
have
a
short-term
solution
to
do
some
of
these
immediate
reimbursements
and
then
like
having
a
more
robust
system
that
can
automate
this
so
yeah
cool,
we'll
follow
up
in
the
forum.
I
think
here,
because
we
gotta
figure
out
a
little
bit
more
of
the
process,
particularly
for
this
next
round,
but
I
think
at
least
for
we'll
figure
out
as
someone
who's
getting
reimbursed.
A
lot,
I
think
skye
also
is
too.
B
B
Cool
and
then
just
wanted
to
give
a
kind
of
brief
update
on
the
like
hr
and
recruiting
point
actually
right
before
the
call.
Martin
was
chatting
a
little
bit
about
how
melanie.
K
B
His
friends,
I
think
tammy,
has
been
poking
around
a
little
bit
and
looking
to
help
out
a
little
on
hr
and
he
had
talked
to
her
about
some
of
the
the
the
issues
or
or
confusion
or
obstacles
that
his
team
is
facing
and
really
just
around,
like
people
find
it
difficult
to
do
worker
proposals
and
get
these
things
through,
and
we
need
like
a
better
like
process
for
this,
and
so
we
know,
we've
talked
a
lot
of
hr
stuff
in
the
past
and
so
just
a
couple
things
with
both
melanie
and
ali
we're
trying
to
meet
with
them.
B
I
think
tomorrow
to
go
over
like
what
are
some
low-hanging
fruit
that
we
can
get
started
on
now,
that
kind
of
like
automates
this
and
just
to
kind
of
go
over
what
what
I
I've
been
thinking
of
what
we
need
kind
of
three
main
things:
one
help
workers
through
the
existing
proposal
process,
two
track:
dxd
and
rep
payments;
three
build
out
contributor
hub
on
documentation
book,
so
the
first
one
help
workers
through
the
existing
proposal
process.
B
That's
just
we've
got
somewhat
processed,
it's
kind
of
like
hamstring,
a
couple
different
ways,
but
just
having
someone
that
is,
like
you
know,
reaching
out
to
you
a
couple
weeks
before
your
last
proposal
expires
and
say:
hey,
you
need
to
work
on
your
new
proposal.
This
is
the
format
we're
doing
help
people
along
the
process.
We
do
have
a
list
of
like
workers,
so
we're
trying
to
go
through
and
figure
out.
B
I
know
some
people
have
not
submitted
working
proposals
and,
like
the
dow
is
in
literally
in
debt
to
to
you,
but
we
want
to
like
get
those
up
to
date,
so
we
actually
know
like
the
cost
for
for
geek
style
and
everything
everything
like
that.
So
we
will,
I
think,
like
getting
a
hold
on
like
worker
proposals,
both
in
terms
of
like
helping
individuals
through,
but
also
having
like
some
spreadsheet,
that
we
can
track
this
a
little
bit
more.
It
should
be
a
liability
in
books.
B
This
is
exactly
it's
a
great
great
point
and
then
two
is
like
track
dxd
and
rep
payments,
and
so
this
is
something
I
know
has
been.
I
think,
frustrating
confusing.
Is
you
know
we
as
part
of
the
compensation
guidelines?
We
have?
Everyone
gets
paid,
ether
ether
die
and
also
gets
vested
dxd,
but
we've
never
had
a
very
good
system
about
getting
an
issuing
vested
dxd.
B
So
we
really
most
a
lot
of
workers
haven't
done
this,
and
this
is
also
a
liability
on
dx
dao
that
we
have
a
lot
of
dxd,
that's
currently
in
the
treasury
that
is
allocated
or
should
be
like
earmarked
for
vested
dxd,
like
to
my
like
me,
myself
is
like
one
of
these.
B
I
did
not
deploy
a
vesting
contract,
and
now
it's
kind
of
like
a
ship
is
sailed
in
terms
of
gas
cost
and
also
working
on
another
system,
but
I
think
it's
really
important
that
we
keep
track
of
this
for
the
dow
zone
financial
space,
but
it's
also
really
important
that,
like
we
all
know
and
feel
comfortable
that,
like
we
are
getting
paid
in
like
dxd
and
then
that's
just
not
some
like
you
know
false
promise.
So
I
want
everyone.
B
People
like
no,
like
I'm
getting
x
amount
of
dxd
every
month,
and
that
goes
back
to
these
months.
I'm
this
is
the
total
that
we're
going
to
get
so
we're
hoping
to
get
that
we'll
have
to
go
retrospectively
back
in
order
to
calculate
this,
and
but
I
think
that
will
hopefully
get
some
clarity
in
like
the
dxd
front
and
then
the
second
and
then
rep
right.
B
This
is
the
same
thing
we
talked
about
with
xdi,
so
rep
is
turning
into
dxd
into
the
kind
of
confusion
and
problems
we've
had
with
dxd,
which
is
basically
like.
We
want
to
issue
and
give
give
workers
and
contributors
this,
but
we
like
can't
do
it
right
now,
so
we
have
to
track
it
and
then
be
able
to
do
it
later.
But
when
we're
tracking
it
we
need
a
way
to
track
it.
We
also
need
a
way
to
communicate
that
it
is
being
tracked
and
it
is
like
updated
to
people.
B
So
I
think,
like
that,
that's
a
really
important
thing
and
then
the
third
is
just
contribute
to
build
out
the
contributor
hub
documentation
book.
So
this
is
just
actually
the
plug.
I
think
this
is
here.
No
yes,
a
little
bit
later,
but
tammy
did
like
a
very
simple
but
like
great
thing,
which
is
just
create
a
simple
google
drive
for
a
lot
of
different
documents
that
are
helpful
in
terms
of
like
proposal
process,
different
things
related
with
hr.
B
Hopefully
this
will
be
in
like
the
documentation
book
in
a
different
way,
but
this
is
like
a
good
start
to
get
there,
so
I'm
hoping
milly
and
ali
can
kind
of
help
in
this
area
yeah.
So
those
are
kind
of
like
three
big
things
and
wanted
to
and
are
hopefully,
gonna
get
started
on
those
soon
and
just
wanted
to
like
check
in
to
see.
If
there
are
other
things
we're
missing
things
we
should
be
doing.
B
Obviously
we
need
to
crawl
before
we
we
walk
here
in
terms
of
like
setting
up
structure,
but
I'm
hoping
that
these
are
low-hanging
fruit
and
will
also
provide
some
value
and
comfort
and
make
life
a
little
bit
easier
for
all
the
contributors.
So
anything
else
that
we
should
be
looking
at.
Thank.
L
You
for
starting
starting
the
process
off
chris,
so
well,
two
things.
I
think,
I'm
relaying
this
on
behalf
of
melanie
and
I
completely
forgot
to
tell
her
that
she
should
be
on
this
call
today.
So
she
would,
I
think,
say
this
otherwise.
I
talked
with
her
briefly.
She
wanted
to
set
up
just
10-minute
meetings
with
each
contributor
to
kind
of
talk
about
pain,
points
and
just
get.
You
know
just
introduce
yourself
and
just
like
get
familiar
with
like
everything
she
needs
to
know
about
them.
L
As
far
as
like
the
hr
related
stuff,
you
know
and
then
start
the
payment
process
issues
as
well,
and
then
the
other
thing,
though,
is
she
was
asking
about
the
recruiting
stuff.
I
know
you
were
also
talking
to
a
recruiter,
so
I
would
want
to
make
sure
that,
like
if
there's
some
sort
of
coordination
there
just
so
you
know,
however,
that
needs
to
work
out.
They
could
be
in
contact
with
one
another
to
figure
out
what
needs
to
be
done
on
that
front
as
well.
L
So
I'll,
let
her
know
to
like
maybe
circulate
some
like
time
that
we
could
like
figure
out
what
everyone
want
to
meet
just
for
10
minutes
and
then,
of
course,
the
squad
leads
who
have
like
real
needs
as
far
as
like
personnel
needs,
specifically
like
she
kind
of
met
with
martin
she'd
want
to
just
like
get
a
list
of
like
specific
needs
to
kind
of
work
from
there
on.
You
know
filling
those
issues
as
well.
L
I'm
sorry,
I
know
my
volume
is
so
low.
I
don't
know,
what's
going
on
with
my
computer
I'll,
like
yell
into
the
mic,
so
yeah,
sorry,
but
I'll
repeat
quickly,
just
melanie
is
going
to
try
and
be
in
contact
with
everyone.
Every
every
contributor
and
she'll
message
you
directly
for
like
a
10
minute
meeting
just
to
like
get
your
pain
points.
B
I
actually
thought
it
was
very
effective
because,
like
you
were
soft
but
like
I
could
hear
you
and
it
just
forced
me
to
like
really
zone
in
on
on
what
you're
on
what
you
were
saying,
but
yeah
I
mean,
I
think
that
that's
great,
like
I
think,
just
like
getting
the
like
kind
of
pain
points
from
everybody
and
just
like
getting
that
down,
as
we
can
start
that
process
of
just
like
what
are
things
that
people
are
running
into.
Where
can
we
like?
Do
that?
I
think
that's.
B
A
great
process,
I
think
recruiting
is
like
a
huge
thing
that
is
like
somewhat
internal
in
terms
of
like
onboarding
and
processing
people
like
how
do
we
know
what
we're
missing
and
like
how
do
teams
know
what
personnel
they
want?
I
think
is
really
important
and
so
like
checking
with
them,
but
it's
also
just
like
I
mean
it's
like
a
huge
thing,
so
we
can
figure.
B
I've
talked
to
a
friend
of
a
friend
of
mine
that
has
been
doing
that
that
maybe
you
could
do
more
like
targeted
searches
for
us,
but
I
think
we
need
to
have
like
a
general
like
outward-looking
approach
to
that,
but
any
like
thoughts
on
things.
Like
other
big
issues,
that
we
I
mean
big
issues
that
are
also
a
little
bit
low
hanging
fruit
right.
So
we
can
try
to
put
some
structure
anything
else.
People
have
have
in
mind.
B
Cool
and
then
just
as
a
plug,
the
contributor
book
is
coming
along
too,
and
I
think
that's
I
feel
kind
of
one
of
those
is
it's
not
finished.
We
haven't
really
like
published
it.
Everything
like
that,
but
I
think
that's
going
to
be
a
big
help
whenever
we
kind
of
get
all
that
through.
I
Yeah,
I
should
have
a
ipfs
up
today
to
share
cool.
B
Cool
and
then
the
other
thing
is
augusto
dx
vote
update.
H
Yeah
yeah.
Basically,
I
just
wanted
to
share
my
idea
of
how
do
I
or
how
do
I
see
that
we
can
proceed
with
the
export.
H
What
is
my
vision
there?
What
I?
What
I
would
like
to
try
to
do
and
here
and
see
if
the?
If
there
is
some
consensus
here
on
how
she
will
proceed,
because
it's
something
that
it
already
started
and
it's
kind
of
working
on
rinkeby.
We
were
able
to
test
and
do
stuff,
but
it
is
not
usable
by
a
by
the
final
user,
which
is
what
we
need
to
do
now.
I
think
so.
H
My
main
idea
would
be
to
create
the
a
testing
group
of
users
of
people
who
is
going
to
be
using
the
app
and
who
understand
it,
who
understands
what?
What
is
our
need
and
what
is
which
are
our
pain.
Our
pain
points
on
on
using
our
our
current
governance
structure.
H
So
the
idea
of
this
this
user
group
would
be
to
test
all
the
new
features
and
new
things
that
we
are.
The
developers
are
going
to
be
adding
on
the
on
the
dab
and
to
find
bugs
and
request
more
features
or
all
the
time
we
want.
We
want
this
feature
to
be
requested
by
the
by
the
final
user
by
the
voters,
by
the
by
the
user,
calculating
the
proposals
who
are
seeking,
who
are
doing
everything
right
who
are
using
the
app
and
then
hub
developers
right
now.
H
It's
only
me
who
is
working
on
on
ds
boat,
which
is
is
not
the
idea,
and
I
will
be
focusing
on
trying
to
automate
as
much
as
possible
the
development
process.
Some
contribution
and
developer
guidelines
also
some
rules
on
what
the
what
future
contributions
should
should
achieve.
Technically
and
what
do
we
don't
want
like
if
a
new
feature,
if
you
find,
if
you
are
a
developer
and
you
are
solving
an
issue
or
you
are
solving
a
future
request,
but
you
are
adding
a
centralized
point
to
the
top.
H
That
is
something
that
it
won't
be
accepted
in
in
the
export.
So
we
are
going
to
have
some
strong
technical
requirements
on
what
the
dap
should
be
able
to
do,
and
it
should
be
up
to
date.
It
should
be
up
online,
a
hundred
percent.
It
should
be
a
hundred
percent
decentralized.
We
should
have
complete
control
over
it.
So
the
idea
is
to
have
something
like
that:
adapt.
That
is
with
very
clear
contribution.
H
Guidelines
where
a
testing
group
or
even
every
user
can
go,
can
go
use
the
app
and
if
they
find
an
issue
or
they
want
to
request
a
feature,
they
create
an
issue
following
a
certain
template
and
then
a
developer
is
going
to
pick
it
up
and
add
what
is
missing
or
or
fixing
the
valve
on
on
the
app
I
created
some
my
submissions
on
amazon
that
is
called
dx,
volt
1.0,
where
the
idea
is
to
create
something
standalone
and
flexible
that
it
won't
need
a
lot,
a
lot
of
maintenance,
because
if
we
want
to
create
to
make
a
call
to
a
new
contract,
let's
say
to
I
know,
to
a
token
or
to
an
e
onto
or
to
an
ens
registry.
H
You
are
just
going
to
have
to
request
the
permission
registry-
let's
say
in
a
security
layer
over
the
app
to
allow
this
function
to
be
called,
so
everything
will
be
designed
to
kind
of
work
on
its
own
on
on
kind
of
on
the
sentinel
hundred
percent
decentralized
app.
This
is
what
I
envision.
We
have
a
lot
of
work
already
done
and
yeah.
I
would
like
to
hear
what
other
people
think
here.
If,
if
someone
disagrees
on
that,
we
shouldn't
pursue
the
the
current
up
and
finish
it
or
yeah.
H
H
The
idea
here
is
to
do
something
very
independent,
and
how
can
you
say
it
like
organize
on
its
own
with
clear
rules
where
anything
that
you
find
that
you
wanna
add
you
create
an
issue
and
any
other
developer
in
here
in
in
the
exile,
can
pick
it
up
and
work
on
it
because
it's
going
to
be
written
in
the
same
language
following
the
same
structure
of
our
dubs
of
swapper,
of
mesa
of
all
men,
everything
is
on
reactions
and
using
v3
yeah.
F
I'm
just
wondering:
is
this
app
meant
to
be
used
just
by
us,
or
is
it
meant
to
be
like
use
by
any
project
that
wants
to
have,
like
you
know,
holographic
consensus,
governance
right?
What
is
the.
H
The
my
the
idea
will
be
not
it
to
be
a
to
be
a
product
that
we
can
sell
or
a
service
that
we
can
provide
setup,
that
we
are
going
to
use
ourselves
and
it's
going
to
be
design
our
needs
or
around
our
needs,
where
we
are
going
to
be
able
to
test
our
new
governance
systems
in
multiple
networks
and
to
grow
technically
on
on
the
government
side.
H
So
what
I
would
like
to
hear
here
is,
if
who
will
be
interested
in
joining
this
testing
group?
Reviewing
the
the
current
state
in
the
app
came
up
with
the
with
the
requirements
that
we
need
for
the
minimum
version
that
can
be
used
by
the
users.
We
need
to
prioritize
certain
certain
issues
and
features
that
we
want
yeah,
mainly
to
listen
and
hear
what.
D
D
I
mean,
I
think,
it's
valuable
to
have
something
that
does
not
have
the
middleware.
That
alchemy
has
and
like
the
alchemy,
not
working
on
x-dia
yesterday
and
the
day
before
is
like
a
good
example
of
like
why
a
dx
vote
would
be
useful
yeah.
So
to
me,
that's
like
a
big
reason
why
it's
it's
everything
you
have.
M
And
we
probably
actually
needed,
for
example,
emptying
I'm
thinking
about
arbitrary.
As
of
now
it
has
no
subgraph
support
at
all.
So
probably
we
need
something
that
can
work
with
the
dallas
tech
contracts
without
the
middleware
of
the
sub
graph.
So
yeah
I
mean
I
personally
I'd
be
interested
in
contributing,
but
I
don't
know
if
right
now,
I
have
enough
time,
but
it's
like
maybe
some
things
here
and
there
I
can.
I
can
contribute.
H
Exactly
this
is
also
idea.
The
the
the
entry
barrier
to
start
right
now
contribute
on
the
expo
is
super
high,
because
I'm
the
only
one
who
wrote
and
I
understand
the
code,
but
my
idea
would
be
to
document
as
much
as
possible
and
to
have
clear
contribution
guidelines
and
help
everyone
else
who
even
kind
of
start
with
a
small
feature
or
with
a
small
bug,
fix
because
again
it's
all
on
the
it
will
be
written
on
the
same
code
that
we
use
on
the
rest
of
our
dab
yeah.
H
It
would
be
awesome
to
to
see
all
of
us
working
on
on
on
the
same
dab,
something
truly
standalone
and
100
decentralized,
that
again
we
we
shouldn't
be
needing
sub
graph
and
and
and
all
the
stuff
this
will
be.
H
H
B
Yeah,
I
think
I
think
mackinac
likes
to
use
anti-fragile,
but
I
like
resiliency
right,
like
the
deep
stuff
needs
to
be
like
resilient
in
a
lot
of
different
ways
and
like
resiliency
or
like
redundant,
is
like
another
word.
So
it's
like
yeah,
like
if
alchemy,
goes
down
like
we're
resilient
anti-fragile
to
that,
because
we
have
other
options.
B
I
also
think
this
kind
of
highlights
you
know,
as
we
kind
of
think
about
how
we
should
be
working
and
developing
different
things
like
I
think
governance
is
a
is
a
very
much
a
like,
not
urgent
problem.
That
is
very,
very
important
right,
so
it's
not
urgent.
It's
like
it
actually
doesn't
require
our
attention
like
right
now,
there's
not
like
a
bleeding.
You
know
body
on
the
floor
that
we
need
to
address,
but
it
is
something
like
we
need
to
think
about
like
long
term
so
like.
B
B
We
can
like
act
quickly
and
then
yes,
as
someone
who,
like
uses,
alchemy
all
the
time
and
I
feel
like
I'm
getting
pretty
intimate
with
it,
I
would
be
happy
to
like
kind
of
test
and
give
as
much
like
feedback
on
this
because
yeah
in
the
end.
This
is
just
like
the
tools
that
we
end
up
end
up
working.
We
use
to
work.
A
H
Alchemy,
well,
I
think
the
first
step
will
be
having
it
on
excite
and
start
testing
it
there.
But
the
first
thing
we
do
will
be
to
set
a
clear
issues
and
and
things
that
need
to
be
solved
for
the
version
1.0.
H
The
later
we
can
again
test
in
the
next
day
and
when
we
see
it
work
and
we
like
it,
that's
it
then
we
can
see
how
we
can
move
to
mainnet
or
continue
using
alchemy
on
mainnet.
But
I
think
xi
here
will
be
like,
like
a
very
good
place,
to
to
start
testing,
even
with
a
small
amount
of
money
where
we
can
really
show
every
everything
that
everything
that
the
expo
can
do
and
how
resilient
it
can
be
to
other
systems.
H
So
I
think
I
will
be
creating
a
call
next
week
to
decide
which
are
the
priorities
and
the
features
that
we
need
for
the
first
version
on
excite,
and
then
we
can
estimate.
Then
we
can
estimate
it
can
be
a
month.
It
can
be
two
three,
I
think
not
more
than
three
months.
I
will
go
for
two
months
to
cut
something
something
on
alchemy.
A
Is
anyone
like
is
any
death
able
to
work
on
dx
votes?
Besides
gosu
like
on
the
omen
side,
we
have
worked
for
one
year,
at
least
like
how
do
you
envision
that
other
teams,
I
think,
literally,
everyone
is
extremely
busy
and
it
looks
like
we
need
our
like
in
an
own
team
for
the
export.
H
Yeah,
this
is
exactly
what
what
I,
what
I
don't
want.
I
don't
want.
I
mean
like
I,
I
imagine
it
a
setup
that
can
be
contributed
by
anyone
and
again
it
will
be
very
standalone,
one
that
we
build.
It
will
be
designed
where
you,
though,
you
won't
need
to
change
that
much,
even
even
on
the
blockchain
level,
to
make
it
work
because
it
will
be
safe
and
secure
as
it
is
where
we
will
have
again
a
security
layer
where
any
action
that
you
wanna
do.
H
It
should
be
approved
before
being
able
to
be
executed
on
chain.
Then
it's
not
that
hard.
It's
just
voting
staking
and
showing
and
creating.
D
Proposals
and
okay,
so
I
think
federico's
point
is
interesting
about
arbitrom
because
I
don't
think
it's
that
they
don't
have
subgraph
support
at
all,
but
they
didn't
have
like
full
archived
note,
support
or
whatever
like
something
that
alchemy
needed.
It's.
I
don't
think
we're
super
clear
on
when
arbitrary
launches,
but
it
might
be
a
case
where
we
actually
like
need
an
alternative
to
alchemy.
A
G
I
mean
technically,
it
just
depends
on
the
graph
and
if
the
graph
decides
to
deploy
an
arbitrary,
then
alchemy
can
be
deployed
there.
There
is
also
the
option
of
running
our
own
graph,
server
and
yeah
on
on
arbitrary.
Connecting
to
that,
but
I
think
that's
that's
just
going
to
be
like
a
bunch
of
overhead,
so
I
mean
I
mean
technically,
no
real
dapps
can
actually
go
to
arbitrary
without
like
the
graph
like
90
something
percent
of
the
apps
actually
use
it.
So.
A
You
know
the
question
is
like
I
think,
doesn't
put
out
a
blog
post
about
yeah.
We
we
will
go
to
the
questions
it.
A
B
G
Like
there's
been
like
like
what
a
change
of
workforce
since
then
so
not
sure
like
who
will
be
able
to
deploy
it,
but.
D
B
Yeah
yeah,
it's
almost
like
this-
is
like
downside
risk
insurance
in
a
way
like
we're.
Kind
of
this
is
something
that's
really
important
to
us
and
like.
We
need
to
make
sure
we
have
like
backup
options,
and
it's
not.
B
Like
a
fully
like,
you
know,
operable
dap
that,
like
is
great
like
right
now
but
like
if
we
had
to
move
quickly
or
if
something
like
kind
of
do.
I
think
this
like
gives
us
flexibility,
but
again
it
doesn't
seem
like
urgent
right
now.
Well,.
D
I
mean
it
depends
like
if
archer
launches
and
like
just
I
can't
like
it,
could
become
urgent
right
right
quickly,
but
in
order
for
the
expo
to
like
fill
that
need,
it
does
need
to
be
like
more
usable
than
like
just
going
to
ether
scan
or
like
block
scout
or
something
right
like
it
needs
to
be
like
something
that
an
average
user
can
do.
It.
A
Yeah,
what
like
we,
the
dig,
still
paid
the
the
development
for
dx
volt
and
we
are
still
in
the
state
where
it's
like
just
alpha
product
and
literally
no
one
is
using
it,
and
I'm
worried
that
we
continue
with
that.
Even
with
this,
this
behind
the
back
thinking
that
it
is
like
a
okay,
if
alchemy
is
exploding,
we
can
just
jump
ship.
B
D
I
would
agree
that
we
need
we
need
to
care
about.
It.
Lego
is
like
probably
the
main
yeah,
I'm
terrible.
I
mean
there
is
doubt
stack
like
desktop's,
not
like
completely
dead,
there's
lego,
but
I
would
agree
with
you
and
I
think
that,
but
the
other
question,
though
too,
is
like
what
is
the
priorities
for.
Is
there
other
governance,
efforts
that
are
kind
of
incomplete
and
underway,
as
well,
so
like.
A
I'm
not
saying
like
dx
vote
is
is
like
completely
not
important.
I'm
worried
like
each
working
each
product
and
each
team
is
dependent
on
each
other,
like
we
are
completely
interconnected,
and
now
it's
like
the
governance
module.
A
The
governance
stuff
is
like
joining
the
whole
game
and
like
what
I
need
to
make
sure
of
like
for
in
terms
of
women
development.
The
guild
is
like
100
percent
priority
and,
like
my
point,
is
every
like.
We
can
keep
keep
the
ex
vote
on
idle
with
low
priority
and
everyone
who
has
like
some
bandwidth
can
work
on
it.
B
B
H
H
So
this
is
one
I
want
to
first
define
and
then
I
can
estimate
how
much
time
is
going
to
take
me
with
also
also
taking
mind
that
I
need
I,
I
still
have
to
help
on
other
side,
like
writing
the
the
smart
contract
for
the
online
guild,
but
again
this
is
where
I
want
to
work
on
on
the
exile.
This
is
where
I
always
wanted
to
work,
and
this
is
how
I
do
I
don't
I
I
don't
want
to
be
contribute.
H
H
Exw
it
all
together,
maybe
it's
too
crazy
what
what
what
I
have
on
mine
but-
and
maybe
I'm
a
perfect,
so
I'm
a
perfectionist
and
I'm
asking
too
much
to
too
much
technical
requirements
of
what
of
what
I
want
to
create.
But
for
me
it's
crazy
that
we
are
relying
on
the
centralized
service
on
governance
like
right
now,
where
we
have
30
million
dollars.
We
have
already
a
year
running.
H
This
should
be
our
focus
first
well,
it
will
open
the
doors
for
us
to
test
more
stuff
to
to
make
other
investments,
to
spread
more
money
around
to
spend
this
money
bowling,
creating
proposals
testing.
So
I
think
overall,
it's
going
to
it's
going
to
help
a
dot
the
excel
and
this
required.
This
is
why
I'm
proposing
and
pursuing
it.
D
Yeah
another
way
to
look
at
this
right
is
you're
kind
of
like
leading
up
the
internal
so
to
speak,
governance
efforts
right
because
you've
done
the
erc20
guild,
the
dx
vote
and
some
other
stuff
right
yeah.
So
I
mean
I.
D
H
Yeah
I
just
I
just
need
to
know
how
much
important,
for
example,
is,
do
we
want
to
be
able
to
to
make?
I
know
to
decode
any
call
on
the
when
we
are
creating
the
proposal,
or
is
it
more
important?
No,
we
want
to
signal
votes,
we
don't
care
how
how
the
propose
is
going
to
be.
We
signalling
balls
is
more
important.
H
I
mean
if,
if
I
have
a
pre-understanding
of
which
are
our
requirements
from
the
users,
we
can
estimate
that
we
can
plan
around
the
next
version
of
roadmap,
at
least
for
the
next.
I
know
six
months,
and
then
we
can
do
it
again
in
the
next
in
in
half
a
year
and
something
where
anyone
else
can
contribute,
not
just
me,
but
anyone
has
come,
can
work
on
it.
L
That's
better
or
maybe
not,
but
so
it
seems
to
me
like
this
is
like
the
governance.
2.0
question
fits
really
well.
As
far
as
like
parameters,
I
mean.
Obviously
the
guilds
are
different.
We've
discussed
how
the
formula
for
the
guilds
versus
the
the
governance
2.0
initiative-
I
mean
this
could
be
a
beautiful
opportunity
to
you
know,
have
a
gusto
do
governance
2.0
as
the
parameters
and
coordinate
with
I
don't
know
lego
in
trying
to
you
know,
maybe
beat
expectations
and
executing
our
own
dx
vote
governance,
2.0
solution.
L
D
Yeah,
throwing
guardians
2.0
into
the
mix
is
interesting.
Obviously
that
is
important.
I
think,
there's
almost
like
three
things
here.
There's
the
expo
like
the
current
underway
effort,
which
is
like
a
bare
bones:
alchemy,
like
no
middleware,
no
graph,
no
separate
servers.
It's
centralized
servers
like
a
more
like
decentralized.
If
you
will
like
alchemy,
then
there's
guilds
like
omen,
killed,
dxd,
guild,
etc,
and
then
there's
like
governance
2.0,
which
we
haven't.
We
don't
even
really
have
a
great
idea
like
how
that
would
be
an
evolution
from
the
existing
efforts.
L
Well,
luckily,
I
don't
know
not
like
chris
isn't
too
busy
or
anything,
but
I
mean
it
would
make
sense
to
think
about
kind
of
doing
what
we
did
with
omen
guild
but
start
thinking
about
this
with
a
gusto
about
how
we
go
about
executing
this.
How
do
we
meet
the
the
outline
that
we,
you
know
presented
to
dxd
holders,
and
you
know
executing
this
while
gusto
with
the
gusto
basically
and
I'd,
be
happy
to.
B
Yeah
definitely,
and-
and
it
kind
of
time-
because
I
want
to
jump
over
to
this
call-
but
just
I
thought
john's
kind
of
those
three
points
and
what
like
that's,
the
the
different
things.
We're
like
building
and
kind
of
operating
right
now
and
like
the
guilds
are
so
crucial
to
the
omen.
Token
right.
So
it's
a
really
great
that,
like
we
agree
to
be
building
that
over
the
last,
you
know
last
year
and
kind
of
set
us
up
position
for
that.
I
agree
completely.
B
This,
hopefully
can
like
flow
into
like
gov
2.0
stuff,
and
it
kind
of
like
gives
us
the
ability
to
start
like
building
our
own
governance
stuff.
So
I
hope
it
does
like
set
the
stage
for
that
and,
like
I
actually
feel
somewhat
optimistically
confident
about
that,
because
I
think,
like
augusto,
you
know,
is
involved
in
the
machine
and
kind
of
do
a
bunch.
And
then
we
have
a
lot
of
people
from
you
know.
B
Dow
stack
that
are
involved
in
that
that
or
from
exile
stack
that
are
interested
in
helping
us,
and
I
just
think
like
if
we
can
get
those
people
and
like
kind
of
push
this
forward
like
we
will
be
able
to
like
build
something
that
is
customizable
for
dx
dow,
like
on
a
host
of
different
areas,
but
anyway
any
ago.
So
you
want
the
last
word.
H
Yeah
yeah
about
governor
2.0,
we
discuss
on
the
working
group,
for
example
the
the
new
reputation
model
that
we
want
to
have
yeah.
They
know
they
know
technicalities
behind
the
protocol,
but
what
about
the
technical
requirements
for
the
users
for
us?
H
For
us
as
an
organization
of
application
that
we
are
going
to
use,
I
mean,
is
it
not
a
requirement
of
governance,
2.0
200,
to
have
a
hundred
percent
decentralized
up
that
we
can
trust
that
we
it's
not
going
to
break
and
it's
going
to
be
working
all
the
time
where
we
have
control
and
we
can
iterate
and
we
can
add
features.
I
think
that
is
a
requirement
of
governance
2.0.
H
Where
the
working
group
we
decided
on
yeah
the
technicalities
on
behind
the
rep,
but
what
about
the
technical,
the
technical
application,
the
technical
requirement
for
the
user?
B
G
H
Yeah,
actually,
the
best
way
I
mean
the
best
product
will
be
something
the
expo
that
we
built
that
you
will
be
running
for
an
entire
year
with
no
maintenance
with
no
one
working
on
it
at
all.
And
that
will
be
the
goal
I
think
for
dx1
1.0
or
something
that
you
pop.
You
should
put
it
there
and
you
know
that
it's
going
to
be
working
and
it's
going
to
be
there
for
a
year
and
it's
going
to
work
as
it
always.
G
Yeah,
I
I
think
the
question
here
is
like
what
what
features
your
governance
needs
to
have,
because
I
think
this
vote,
or
you
know,
alchemy
for
that
matter.
You
know
it
doesn't
have.
I
think
the
necessary
features
that
digs
down
needs
from
a
governance
system.
G
So
there
should
be
another
like
lego,
dao
meeting
for
anyone
to
join.
That's
like
two
hours
before
the
general
call
tomorrow.
G
B
Cool
all
right,
we
need
to
run
over
to
this
other
call.
If
you
have
thoughts
on
the
branding
now's
your
chance,
andre
casa,
so
all
right
guys
thanks
bunch.