►
From YouTube: DXproductstrategy Gathering [2022-08-19]
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
Hello
and
welcome
to
dxdow's
weekly
strategy
call
friday
august
19th.
We
have
13
of
us
on
this
call
today
on
the
agenda.
We
got
an
update
on
expenses
squad
budgeting,
a
chat
about
the
recent
happenstance
with
the
fee
receiver
in
swapper,
a
discussion
around
the
upcoming
guild
operation,
decentralization
feedback
and
then
gxd
guild
front
end
versus
government
to
governance
2.0.
B
It's
probably
a
time
for
us
to
make
a
decision
so
that
the
devs
know
what
to
do
I'll,
be
asking
ross
what
the
timeline
is
for
us
to
make
the
call.
And
last
but
not
least,
we
could
be
brainstorming.
Some
topics
to
focus
on
during
the
retreat
and
the
dxbiz
huddle
had
a
meeting
this
week
and
we
we
came
up
with
a
few
we
could
suggest.
So,
let's
start
with
the
update
on
expenses,
chris
has
been
crunching
some
numbers
as
usual.
A
C
A
C
Yeah,
so
this
is,
I
just
been
working
on
this,
yet
I
don't
have
anything
to
post
in
the
forum
yet,
but
I
kind
of
want
to
see
what
cadence
kind
of
get
into
better
cadence
for
these,
and
I
think,
updates
like
every
two
months
or
around
that
time
is
a
good
way
of
just
like
keeping
the
conversation
going.
D
C
Like
you
know,
when
decisions
are
made
or
when
we're
reflecting,
we
kind
of
have
the
perspective
of
recent
events
or
whatever
so
yeah.
I
was
hoping
just
for
some
feedback
on
like
an
initial
stuff
that
I'm
been
compiling
the
expenses
as
of
like
last
week,
I
think
last
friday,
so
yeah.
Let
me
share
of
all
things
of
course
in
excel,
so
this
is
the
yeah.
C
So
this
is
the
sheet
that
I've
been
working
out
for
the
past,
and
so
you
can
remember
here
all
expenses
go
into
these
two
different
pages,
so
one
is
either
contributor
payout
or
the
other
is
other
expenses,
so
other
expenses
is
anything
that
is
not
compensation
to
a
contributor
there,
and
so
obviously
like
stipends
audits,
things
like
the
dev
shops,
anything
that
is
outside
of
the
compensation
guidelines
there,
and
so
I
just
kind
of
wanted
to
do
two
things
here
today
and
then
see
if
there's
like
any
questions
or
comments
for
things
to
like,
maybe
dive
into
a
little
bit
more.
C
I
did
update
this
as
of
right,
because
the
expense
is
always
going
to
lag
a
little
bit
because
it's
like,
for
instance,
hard
to
get
obviously
august
expenses
because
we're
still
in
august,
and
so
it's
normally
typical
of
30
days,
and
so
these
should
be
good
up
until
the
beginning
of
july,
which
means
we
have
like
monthly
data
for
june
going
forward,
and
I
did
make
some
like
estimates
to
kind
of
close
out
the
last
little
bit.
C
But
so
I
think
what
we
want
to
look
at
here
is
like
basically,
three
month
averages
and
the
best
month
we
have
so
far
for
the
or
the
latest
month
we
have
so
far
for
like
good
data,
that's
worth
looking
at
is
june,
and
so
this
is
kind
of
just
looking,
I
think
at
things
over
the
last
three
months
and
comparing
them
to
the
previous
three
months.
C
Here
again,
this
is
hopefully
like
not
too
surprising
or
different,
because
we've
been
looking
at
some
of
these
things
here
and
so
obviously
like
swapper
and
dxgov
having
around
just
under
100k
of
monthly
costs.
That
being
up,
obviously
in
may,
I
think
it
was
yeah.
May
there
were
some
big
audit
costs
for
geeks
gov,
so
that's
why
it's
absorbing
that
there
and
you
can
see
like
the
big
increase
there.
Also
the
same
thing
is
actually
true
of
swapper.
I
think
there
was
about
15
000
of
audits.
C
I
think
for
the
curve
wrapper
there
so
really
just
like
a
heavy
audit
time
period.
So
that's
why?
Actually,
if
you
look,
the
average
spend
of
the
last
three
months
is
actually
340k
because
it
was
so
lumpy
with
those
audits.
This
also
includes
like
112k
it
on
it
there,
and
so
without
the
audience
you
can
see.
C
I
think
there
were
yeah
there's
like
almost
300
000
worth
of
audits
over
these
three
months,
so
without
the
audience
we're
kind
of
at
this
293
figure
that
we
talked
about
before,
and
that
is
compared
with
the
previous
months
there,
and
I
also
think
this
is
a
little
bit
high
because
of
the
summer
months,
including
a
lot
of
the
expenses.
Sorry
a
lot
of
the
stipends
from
different
events
there.
C
So
I
thought
that
is
kind
of
where
we
got
that,
and
so
I
think
yeah
you
can
see
here
over
these
three
months.
There
was
just
under
90
000
on
expenses,
a
lot
of
amsterdam
stuff,
a
lot
of
paris
stuff,
and
then
you
can
see
the
january
marks
just
actually
36
k.
C
I
think
that
is
denver,
but
actually
not
catching
some
of
the
bigger
ones
there
and
then
yeah,
just
kind
of
like
doing
a
little
bit
more
high
level
here
like
adding
up
swapper,
dxgov
ecosystem,
film
security
and
carrot
like
this
is
kind
of
the
difference
here,
and
this
is
where
you
can
really
see
like
this
is
kind
of
the
the
big
audit
of
the
spring
there.
So
that's
kind
of
like
the
one
thing
that
wanted
to
look
at
and
then
the
other
thing
that
I
think
we've
been
thinking
about.
C
A
lot
is
like
events
and
how
people
how
we
pay
for
those
how
much
they
cost
like.
What's
the
value
added
you
know,
there's
you
know
a
whole
bunch
of
different
value
ads
from
you
know,
making
people
work
together
better
getting
education
and
learning
about
the
industry.
There's
also
a
whole
like
brand
building
recognition
for
geek
style
like
being
there
in
terms
of
for
sponsoring
things,
the
sponsors,
the
reason
we're
sponsoring
things
or
spending
on
sponsorships
is
to
spread
the
geeks
out
brand.
C
So
it's
like
you
know
a
lot
of
different
things
there
so
just
wanted
to
kind
of
look
a
little
bit
closer
at
those,
and
so
these
are
the
four
or
I
guess,
five
past
events,
one
upcoming
that
we
wanted
to
look
at
and
so
paris
is
the
or
the
ecc
in
2021
was
the
first
one.
C
That's
when
you
had
about
eight
contributors
that
attended
and
really
they
had
mostly
like
stipends,
and
there
was
a
little
bit
of
merch
there,
but
that
was
like
a
pretty
low
one
there
and
then
lisbon
was
like
definitely
a
very
big
one.
We
can
kind
of
see
here
this
one
they
cost
fifty
thousand
dollars
about.
Half
of
that
was
for
the
geeks
lisbon
retreat,
which
is
considered.
C
I
basically
just
said
that
the
stipend
stipend
is
basically,
I
think
anything
about
like
lodging
food
eating
kind
of
anything
in
that
one
is
just
kind
of
let's
type
in
category
there
and
so
yeah.
You
can
see
that
that
was
there.
There
was
no
actually
sponsorship
at
lisbon.
There
wasn't
really
anything
there,
but
there
was
some
merch
merch
created
a
t-shirt.
I
still
wear
a
black
t-shirt
that
is
defining
a
dao.
It's
a
fun
one.
C
I'm
excited
to
be
able
to
wear
it
again
when
it's
not
so
hot
out
and
then
looking
at
denver
denver
was
actually
the
most
expensive
one
to
date.
We've
done,
but
of
course
I
think
that
will
be
surpassed
by
columbia
upcoming.
So
it's
81
000,
you
can
see
there.
The
big
thing
with
like
kind
of
denver
was
there
was
both
sponsorship
was,
was
pretty
high
and
also
merch
was
pretty
high
there.
C
So
there
was
both
a
like
sponsorship
of
the
staff
of
denver
and
there
was
also
some
hackathon
prizes
there,
but
you
can
also
see
with
like
denver
and
we
had
like
12
contributors
attending
there.
Amsterdam,
you
know
very
similar
in
terms
of
stipend
and
contributors
right.
You
can
see
literally
12
and
41
42,
just
a
little
bit
cheaper
in
terms
of
sponsorship.
That
was
a
global
governance
gathering
and
then
yeah
merch.
Just
under
like
3
000.
paris
was
the
yeah
most
recent
one.
C
We
actually
had
tons
of
people
there.
The
fomo
was
high
15
people,
but
really
I
don't
know.
I
think
there
was
some
merch,
but
I
didn't
see
any
expenses
for
those,
I'm
not
sure
if
those,
if
I
missed
those
or
maybe
those
are
coming
in,
but
it
was
like
yeah
there
wasn't
a
sponsorship
or
as
much
going
on
there.
I
guess
there
was
the
happy
hour
and
that's
in
the
stipend
here.
I
think
it
was
from
skye's
proposal.
Yeah.
A
And
then
yeah
the
dx
voice,
multisig
paid
for
the
swag.
That's
why
it
didn't
come
out
of
the
treasury
got
it.
C
Yeah
because
I
heard
it
was
swag
that
inspired
other
artwork
yeah
and
then
just
looking
at
colombia.
This
is
the
upcoming,
and
so
you
know
one
of
the
ways
since
geeksdow
is:
is
people
can
claim
their
cybin's
before
time?
There's
actually
been
a
good
number
of
things
that
have
already
been
claimed
here
and
already
expenses
had
so
he's
about
71k
that
has
already
been
spent,
and
that's
14
contributors
have
already
already
claimed
stipends
for
geeks
colombia
and
then
yeah.
You
can
see
here.
There's
a
you
know.
C
With
these
columbia,
we've
got
the
the
hackathon
which
I
put
under
sponsorship,
which
I
think
is
still
kind
of
the
right
one,
because
it's
really
it's
kind
of
we
are
trying
to
build
both
the
brand
of
infinite
geek
style,
attract
other
kind
of
people,
and
so
you
can
see
that's
a
big
one
there,
and
so
we
have,
as
I
said,
71k
that
has
been
spent
so
far,
but
just
kind
of
projecting
that
out
a
little
bit
further
and
so
yeah.
C
I
think
just
looking
at
the
key
based
chat,
there's
like
26
27
or
something
people
in
there.
So
maybe
that
goes
up
to
25
and
then
there's
the
dx
retreat
proposal
that
if
it
passes,
I
believe,
there's
some
votes
on
it.
Now
that
would
be
25
000,
there's
infinite
another
payment
for
35
000.
merch.
This
is
kind
of
just
an
estimate
there
and
then
just
other
whether
that's
like
dinners
or
kind
of
other
things
that
happen,
and
then
the
stipends
for
the
remaining
11
people.
C
So
if
that
were
all
to
add
together
that
would
be
185
418,
you
can
see
like
the
number
of
contributors
would
be
pretty
high
and
it
would
also
be
a
pretty
high
a
little
bit
higher
spend
on
sponsorship
than
the
average
one,
and
this
is
kind
of
like
the
breakdown
in
general
across,
in
terms
of
when
we
say
we're
spending
money
on
events
when
people
are
going
to
events
like
about
a
third
about
two-thirds
of
it
just
over.
C
Two-Thirds
of
it
is
stipends
for
lodging
eating
kind
of
everything
there
and
then
sponsorships
20
a
little
over
20
and
then
merch,
just
at
nine
percent
there
yeah,
so
those
are
kind
of
the
two
things.
As
I
said,
I
haven't
like
posted
there's,
like
kind
of
some
broader
things,
maybe
of
like
putting
some
charts
that
we
can
put
in
the
forum
but
like
while,
before
I'm
doing
that,
I
wasn't
sure
if
there
was
any
thoughts
on
this
questions
or
maybe
like
what
else
to
look
for
or
kind
of
examine.
E
Just
on
the
columbia
one,
I
guess
well
at
least
the
hackathon:
that's
conservative,
because
we
are
look,
we
have
some
co-organizers
and
then
we
have.
We
might
have
some
more,
which
then
reduces
the
the
the
hackathon
cost.
But
then
we
may
have
some.
I
guess
some
cost
if
we
do
prizes
on
top
of
that,
so
maybe
it
balances
out,
and
then
this
is
all
like
on
chain
yeah.
This
is
all
on
chain
costs,
and
so
then
the
example
that
dave
gave
where
the
multi
the
dx
voice
multisig
paid
for
merch
in
paris.
E
I
guess
that
we
need
to
like
add
in
separately
or
we
dx
voice.
Smart
is
keeping
track
of
that.
So
if
there's
an
outlated
dx
voice
multisig,
you
could
then
include
that
and
then
then
the
multi-sig
will
at
some
point
report
how
all
of
the
money
from
the
multisig
was
spent.
I
imagine.
A
C
You
know
how
do
you
class
of
categorize
things,
and
so
I
think,
like
right
now
that
expense
that
has
been
refunded
from
the
multisig
is
already
been
incurred
as
an
expense
to
deke
style
when
the
multisig
was
funded,
and
so
that
was
kind
of
like
generic
expenses
for
dx
voice,
and
then
dx4
is
using
that
for
something
more
specific.
C
So
it
does
definitely
help
to
keep
records
that
can
be
compiled
into
one
when
we
want
to
get
more
granular
into
actually
knowing,
oh,
you
know,
we're
wondering
specifically
how
much
we
spent
on
you
know
everything
in
paris,
and
that
is
not
just
things
coming
from
deep
south
treasury,
but
like
could
be
other
things
so
yeah.
I
think
keating
has
been
keeping
track
of
that
and
everything
is
of
course,
unchained.
B
B
B
It
would
be
you
know,
given
the
amount
of
solutions
we've
seen
around
multi-sigs,
it
would
be
nice
to
have
some
dashboard
type
of
analytics
solution
that
is
really
flexible,
allowing
you
to
input
all
of
your
addresses,
give
them
specific
names
and
then
monitor
inflows
and
outflows
and
create
charts.
Based
on
that,
I
don't
think
there
is
one
existing
today
that
covers
all
that.
B
Maybe
something
we
could
incentivize
for
hackers
to
build
in
bogota
in
terms
of
dow
tooling,
it's
something
we
would
definitely
be
benefiting
from.
E
B
E
Chris,
just
that
well
that
the
colombian
number
is
is
big,
if
let's
say
that's
conservative,
but
it's
a
lot
of
people.
It's
almost
twice
as
many
people
as
potentially
going
to
any
other
event,
and
I
will
say
that
and
it's
a
lot
it's
a
longer
period
of
time
too.
A
E
Think,
as
many
people,
different
communities
and
projects
are
sending
like
their
full
teams
to
colombia
and
things,
so
this
is
a.
This
is
a
large
expense
compared
to
maybe
other
communities,
but
if
there's
actually
25
people
from
dx
dao
down
in
at
dev
con
and
all
the
events
and
our
our
own
event
and
all
those
things
I
have
a.
I
have
a
feeling
that
yeah
that
that
that
presence,
which
we've
seen
work
powerfully
in
the
past
of
of
getting
more
people
and
things
aware
of
dx
tao.
E
I
think
that
the
exile
would
definitely
stand
out
down
there
as
the
the
largest
force
from
any
project
that
I
can
think
of,
and
so
that
would
that
will
yeah.
That
would
be
a
very
powerful
thing
and
then
taking
advantage
of
that
will
be
the
important
part,
but
we
can.
We
can
cover
a
lot
of
different
events
and
communities
and
workshops
and
things
and
and
push
dx
down
into
all
of
those
conversations
with
that
force
down
there,
which
is
yeah.
I
I
can't,
I
don't
know
any
other
community.
B
All
right,
we
have
a
request
from
zed
to
bump
up
the
conversation
on
the
squad
budgeting.
He
may
have
to
hop
off
at
some
point
so
to
be
mindful
of
his
time
said
if
you'd
like
to
present
the
idea
and
then
we'll
take
it
off
with
a
conversation,
yeah.
F
Sure
yeah,
sorry
for
having
to
stress
you
guys,
but
there
is
one
topic
that
is
affecting,
I
think
all
squads
for
now
and
I
I
think
I've
talked
about
this
also
before
and
it
is
a
little
bit
uncomfortable
to
talk
about
and
I'll
kick
start
the
conversation.
So
basically
we
have
budgets.
We
have
people
working
for
us
and.
F
I
think
like
when
it
comes
to
our
products,
some
some
we
are
missing.
Some
key
key
people
to
drive
drives
forward.
So
as
an
example,
I'll
I'll
say
a
front
front
end
the
lead
developer
right.
This
is
something
swapper
needs
and
we
don't
have
one.
F
And
it's
really,
I
think,
in
my
opinion,
at
least
it's
stupid
of
us
to
deny
good
candidates
and
sometimes
better
than
the
people
we
work
with
and
from
from
the
product
perspective.
It's
it
hurts
us
if
we
deny
these
people
from
like
company
perspective.
I
do
understand
that
we
we
should
like.
We
want
people
to
contribute
for
these
style.
We
want
all
of
us
feel
like
a
family,
and
we
were
thankful
for
the
work
and
all
of
that,
but
in
reality
there
is.
F
I
think
there
is
a
problem
thinking
like,
oh
just
because
you're
early
you'll
have
this
position
forever
right.
So
I'm
I'm
right.
I'm
there
right
now
and
I'm
looking
at
these
candidates-
and
it
looks
like
these
candidates
would
would
actually
drive
and
help
swapper
as
an
example,
but
without
pushing
the
the
yeah
budget
even
more.
I
need
to
either
deny
them
or
replace
them,
or
we
just
keep
expanding
forever
right.
So
I
want
to
kick
start.
This
conversation
see
what
you
guys
think.
B
I
thanks
for
bringing
it
up.
It's
a
great
question
to
ask
ourselves
it's
a
very
important
topic
as
well.
There
is
some
serendipity
we
actually
touched
on
it
during
the
gx
biz
huddle
this
week,
that's
kind
of
like
what
I
hinted
at
when
I
said
we
should
be
thinking
of
topics
to
focus
on
during
the
retreat,
and
this
is
probably
one
of
the
major
topics
to
discuss
recently.
B
We
did
a
restructuring
and
we
kind
of
disbanded
a
team
and
focused
deb
resource
to
another
team,
and
now
what
you
just
brought
up
kind
of
hinges
on
it
like
if
we
are
to,
if,
if
there
is
a
need
for
a
specific
skill
set
like
and
you
find
someone
who's
qualified
like,
should
you
feel
pressured
expanding
the
team
and
adding
on
a
new
person?
Can
you
shift
resource
to
another
product,
so
you
could
accommodate
this
new
person?
B
Do
you
need
to
kind
of
like
tell
someone
that
they
they
no
longer
meet,
meet
the
standards,
so
they
they
have
to
either
somehow
skill
up
or
they
there's
no
kind
of
like
space
for
them
anymore.
B
So
I
think
we
are
in
a
good
position
with
new
products
being
developed
like
carrots,
so
we
could
probably
do
some
restructuring
shifting
resources
around,
but
at
some
point
will
probably
face
real
dilemmas
like
keeping
people
and
and
so
on,
and
so
forth.
It's
easier.
I
also
mentioned
it
recently,
it's
much
easier
for
me
to
say
that
or
like
someone
working
in
hr
or
marketing,
because
those
are
kind
of
like
it's
like
I've
worked
in
in
businesses
in
the
past
and
a
lot
of
people
come
in.
B
A
lot
of
people
are,
let
go
but
hr
and
marketing
stay
the
whole
time
and
it's
and
me
at
this
dev,
it's
easier
for
me
to
comment
on
it.
But
someone
who
is
doing
a
a
very
particular
specific
work
within
a
specific
product
may
feel
a
little
more
stressed
about
hearing
such
a
conversation
because
they
would
say:
okay,
am
I
getting
replaced.
Can
I
use
my
skill
set
to
start
working
on
this
other
product
within
the
organization
or
do
I
have
to
kind
of
leave
the
organization
altogether?
B
And
I
don't
want
to
put
anyone
in
in
such
a
stressful
position
to
wonder
whether
they
they
would
be
needed
by
the
dao
or
not.
I
think
we're
not
there.
Yet.
We
still
have
a
need
for
all
kind
of
skills
within
our
products,
we're
still
expanding
in
terms
of
product
development,
but
a
very
important
subject
to
tackle,
and
I
think
it
would
be
great
to
discuss
it
in
bogota.
E
If,
if
I
could
just
add
on
and
cover
it
a
lot
there,
but
if
I
could
just
add,
like
one
thing
that
we
were
thinking
about-
and
I
think
everyone
is
thinking
about
this
is
if,
if
the
swapper
squad
right
like
if
swapper
squad
was
more
of
its
own
product,
like
it
has
its
own
token,
it
has
a
product,
it
could
operate.
E
You
know
more
autonomously,
so
if
the
squad
actually
received
power
from
dx
dao,
which
is
like
agreement
and
budget
and
an
actual
deliverance
of
like
some
money
for
some
period
of
time,
like
a
like
a
separated
work
stream,
like
many
other
dials
like
maker,
are
doing,
then
the
swapper
squad
will
have
like
this
is
what
it
plant
proposed
to
deliver
to
dx
tao.
This
is
the
budget
it
requested
and
then
it's
its
squad
itself
operating
as
its
own
dao.
E
Maybe,
with
the
opinion
of
swapper
token
holders
could
make
decisions
to
hire
and
fire
people
within
its
t
its
squad,
basically
to
to
get
to
deliver
the
thing
that
it
that
it
said
it
was
going
to
deliver
to
dx
dao
and
so
instead
of
like
having
dx
dow
have
to
decide
like.
Is
this
person
going
to
help
this
part
of
building
the
thing?
That's
on
the
proposed
roadmap?
That's
supposed
to
be
delivered
to
the
ex-dow
like
this.
E
The
squad
itself
has
more
autonomy
to
to
make
those
decisions
itself
and
then,
at
the
end
of
the
let's
say
six
months,
it's
it's
evaluated
and
it
had
did
it
deliver
what
it
said
it
was
going
to
deliver
by
the
time
it
said
it
was
going
to
deliver
it
and
we
could
apply
that
same
logic
to
all
of
the
squads,
both
product
and
non-product
squads,
and
make
them
more
autonomous
with
more
concrete
deliverables.
And
that
way
the
dow
can.
E
Then
you
know
dxd
holders
we
can
get
signal
from
them
and
through
a
guild
or
snapshot
whatever
and
rep
holders
can
make
decisions
on
where
to
allocate
the
scarce
resources
of
dx
dao,
and
that's
we're
not
really
doing
that
now,
but
many
other,
like
even
maker
and
yeah
lots
of
other
other
communities
are
doing
that.
I
think
some
echoes
that
that
that's
kind
of
one
another
way
to
approach
that
first
question.
I
think
that
that
you
asked.
F
All
right
I
mean,
obviously
we
don't
have
hierarchies,
I'm
I'm
no
boss
of
of
swapper
or
anything,
but
I
I
do
see
some
like.
If,
if
I
could
give
an
example,
so
if
an
investor-
let's
say
a
dxd
holder
right,
a
big
dixie
holder
looks
into
what
we
are
doing,
we're
working
with
and
and
there's
some
things
that
is
purely
purely
performance
based
right
and
and
if
you
just
measure
without
feelings,
there's
stuff,
we
could
do
to
make
swapper
great
right.
F
F
I
just
wonder
how
do
we
proceed
now
versus
discussing
this
and
coming
up
with
something,
because
this
is
something
that's
happening
for
at
least
a
half
a
year?
And
it's
it's
just
a.
I
think
it's
a
change
of
things
like
back
one
year
ago,
when
we
tried
to
get
the
new
new
contributors
was
really
hard
getting
senior
people
right
right.
F
That
is,
that
has
an
experience
before
us.
It's
not
someone
that
needs
to
learn
this
stuff.
So
now
I
have
multiple
of
these
candidates
and
just
I'm
just
trying
to
look
at
as
a
squad
lead.
How
do
I
solve
this
problem
without
also?
I
don't
want
to
hurt
feelings.
I
don't
want
to
do
decisions
by
myself.
That
is,
might
seem
like
I'm
like
yeah.
I
don't
want
to
do
this
alone.
Basically,
I
want
the
dow
to
like.
F
I
think
I
I
think
when
it
comes
to
the
squads,
I
think
deke
style
like
when
I
say
the
style,
I
I
say
like
all
of
like
the
people
voting
usually
listens
to
their
squad
leads
right
at
some
point.
This
could
look
like
I
am
deciding
right.
I
say:
oh,
we
should
do
this
to
just
so
that
and
then
the
doubt
says
yes
or
no.
F
E
Which
is
why
I
think
that,
if
you,
I
think
that,
if
squads
like
because
the
question
is
hiring
these
people
is
going
to
build,
is
going
to
get
what,
like,
let's
say,
dxd
holders
have
all
the
voting
power
like
we
have
to
present
to
dxd
holders
what
so,
because
some
dsd
holders
are
saying
like
swappers
in
a
good
place
in
this
market.
We
could
stop
development
on
it,
but
that
wouldn't
that
would
that
would
be
extreme.
So
the
question
is:
if
we're
going
to
dedicate
x
amount
of
money
from
the
dow
towards
swapper.
E
What
is
it
planning
to
build
and
produce
over
the
next
six
months?
And
how
much
is
that
and
then
and
then
the
dow
says:
okay,
the
dow
votes
and
says:
okay,
that's
a
good
plan
here.
Is
the
money
allocated
towards
that
and
then
then
the
squad
has
to
fit,
has
to
take
that
money
and
get
the
and
use
the
current
people
plus
whatever
more
people.
It
needs
to
deliver
that
through
the
propo.
The
thing
that
it
proposed
right.
F
D
I
think,
because
skype,
what
you're
saying
is
like
a
budget
for
a
road
map,
then
what
zets
trying
to
say
is
like
now.
We
have
awesome
people
that
are
that
are
available
in
the
market
and
we
have
like
a
couple
of
people
that
are
much
much
more
better
than
the
current
set
of
people
in
swapper.
Let's
say
how
would
we,
how
would
we
take
them
in.
B
I
say
I
I
don't
think
it
should
be
a
big
issue
just
as
most
contributors
who
are
from
different
squads
and
are
not
intricately
familiar
with
or
intimately
familiar
with,
the
with
every
single
person
in
in
the
other
squads
trusts.
When
someone
submits
a
proposal
every
two
months
and
it's
most
often
the
squad
leads
chiming
in
in
those
proposals
commenting
affirming
that
they
agree
for
that
person
to
keep
on
contributing
and
it
kind
of
like
signals
to
other
people
in
the
dao.
B
So
I
believe
it
should
equally
work
the
other
way-
and
I
think
maybe
ross
and
and
john
could
say
a
couple
of
words
about
off-boarding
hamza.
It's
not
like,
we
haven't
done
it
already,
we've
done
it
and
it
hasn't
been
an
issue.
I
don't
think
it
should
be
an
issue.
B
I
think
it's
a
it's
a
normal
thing
like
we
don't
have
contracts
for
one
year,
two
years
we
have
two-month
proposals
and
and
when,
when
you
have
a
two-month
proposal,
you
should
be
kind
of
like
expecting
both
outcomes
at
the
end
of
each
proposal.
So
it's
something
natural.
G
I
mean
obviously
off-boarding
people
is
not
not
easy
and,
like
the
only
cases
where
we
really
done
it,
it's
been
almost
like
kind
of
extreme
examples
of
people
like
not
delivering
or
even
just
like,
not
showing
up
so
yeah.
It's.
It's
definitely
like
not
an
easy
thing
to
do.
Kind
of
like
in
a
flat
hurricane
right.
H
B
Yeah
I
mean
as
long
as
there's
no
ulterior
motive
and
it's
not
a
personal
decision
and
it's
purely
technical,
like
someone
shows
up,
and
they
have
a
better
skill
set
like
it's.
No
one's
fault
that
you
have
to
replace
one
person
with
another
like
who's
at
fault.
You
should
never
be
angry
at
anyone,
it's
it's
just
it's
just
how
it
is
and-
and
I
think
no
one
should
be
feeling
bad
about
it,
even
though
it
seems
like
something
negative.
It
isn't.
F
I
think
from
from
just
like
the
startup
perspective,
if
we
look
at
the
dig
style
as
a
startup,
I
know
the
answer
already.
You
can't
get
stuck
with
workers
because
they
were
early
like
if
something's
better
for
for
the
product
or
for
the
team.
I
think
you
should
make
that
decision
if
we
could
reallocate
or
whatever
it
is
or
what
this
person
could
like.
Yeah
try
to
take
on
other
tasks,
that's
possible,
but
I'm
not
sure
in
our
position
that
this
is
possible.
E
F
E
I
think
dx
okay,
so
this
is
yeah.
This
is
an
interesting
scenario.
If
we
ignore
the
like
well,
what
is
it
going
to
deliver
like
like?
What
is
the
swapper
squad
going
to
deliver
like?
Let's
forget
about
that?
The
road
map
and
the
budget
for
the
roadmap?
For
now
the
ability
to
bring
talented
people
into
dxdow
like
yes,
we
have
this
budget
we
made
but
like
the
budget
is
fluid.
E
So
if
we
can
bring
on
awesome
people-
and
we
can
shift
around
resources
and
coordinate
that
because
we
have
a
bunch
of
products
we
can,
you
can
have
more
than
we
are
have
working
right
now
and
then,
after
over,
like
two
months,
you'll
see
the
production
of.
What's
that,
what
that's
doing,
maybe,
then
you
can
reallocate
resources
or
you
can
remove
resources,
but
it
doesn't
have
to
be
like
binary.
E
E
E
B
Yeah,
I
mean
there's
another
side
to
this,
and
that
is
when
the
developer
is
not
happy
and
wants
to
leave
and
that's
what
happened
like
like,
not
actually
not
happy
just
they.
They
find
a
better
opportunity
in
their
own
view,
like,
for
example,
kaiden
or
nico.
They
got
presented
with
opportunities
to
work
for
startups
that
at
the
time,
felt
to
them
more
exciting.
Maybe
they
got
bored
so
that
that
is
the
opposite
to
this
kind
of
situation.
B
E
E
The
reason
why
to
bring
talented
people
into
the
dx
dial
ecosystem
in
the
in
the
you
know
in
the
next
quarter
to
see
how
it's
working
and
how
they
perform,
and
we
we
have
other
people
that
are
reducing
you
know
we
have
some
we're
losing
resources
too
or
or
time
towards
zx
dow
there's
a
balance
like
there's
a
fluid,
there's
a
balance
that
like
on
average
it
has
to
maintain
but
we're
yeah.
We
lose
people,
we
lose
people
and
we
gain
people.
C
It's
helpful
like
that
just
to
hear
this,
because
this
is,
I
think,
part
of
the
process
because
whatever
decision,
however,
we
like
geeksdown
moves,
it's
not
just
you
doing
something:
it's
not
just
swapper
squad,
it
would
be
some.
You
know
broader
decision,
but
the
question
is
like
how
can
rep
holders
get
informed
on
those
things
and
it's
kind
of
through
yeah?
There
needs
to
be
some
communication
about
these
and
then
that
will
help
bring
on
the
decision
that
can
truly
be,
like
you
know,
a
dow
decision.
B
B
It's
a
more
high-level
question
about
the
product
itself
like
if
you,
even
if
you
replace
that
person,
would
that
new
person
still
be
working
on
a
feature
that
will
bring
revenue
or
is
he
a
better
skilled
person,
but
still
work
would
still
be
working
on
something
that
will
not
bring
revenue.
Then
even
even
the
decision
that
will
be
taken
will
still
not
be
beneficial
long-term.
So
we
we
need
to
face
a
larger
issue
here,
probably
being
more
critical
of
the
road
map
itself
and
and
try
to
be
more
agile.
H
Yeah,
I
think
I'm
agreeing
quite
a
lot
with
what
nathan's
saying
like
having
going
with
the
process
of
asking
or
like
a
forward-looking
budget,
where
we're
asking
for
these
resources
and
then
justifying
them
with
the
roadmap
or
how
that's
going
to
affect
revenue
and
stuff
seems
like
a
better
process
to
me
than
the
way
we're
approaching
it.
Just
now,
which
is
kind
of,
I
think
the
budget
would
only
ever
go
up.
Basically,
if
we're
not
doing
it.
This
way.
H
F
I
I
agree
with
that.
I
I
think
we
just
we're
we're
stuck
on
a
like
a
legacy
problem
here,
because
we're
we
basically
took
in
too
many
junior
devs
right
and
I'm
I
mean
like
I'm
in
a
place
where,
where
we
don't
have
a
choice
to
to
take
in
a
dev
and
keep
all
the
depths,
because
we
already
did
that
too
many
times
right,
so
we
every
time
we
took
in
a
dev,
it's
like.
Oh,
what
should
this
new
dev
do
right?
F
We
took
like
we're
basically
expanding
faster
than
the
road
map
was,
was
planned
to
expand,
but
we
did
that
with
junior
devs
right.
So
so
we
kind
of
we're
kind
of
in
the
position
where,
where
like
this
is
kind
of
the
ceiling
of
taking
in
one
more
day,
it's
okay,
just
one
more
day
right.
We
already
did
that
too
many
times
but
yeah.
I
guess
I
just
wanted
to
share
my
thoughts
and
I'm
I'm
happy
to
update
on
how
how
I
will
proceed
with
this.
F
I
mean
thank
you
talking
about
this
and
obviously
I
need
to
look
at
what's
best
for
swapper,
but
at
the
same
time
we
kind
of
want
to
have
a
good
working
environment.
We
don't
want
people
to
feel
like,
oh,
I
can
be
replaced,
but
that
is
that
is,
I
think,
part
of
a
doubt
right.
I'm
not
sure
how
how
else
it
should
be.
It's
not
a
company
where
you
have
one
one
year
old,
one
year
contract.
F
I
think
I
don't
know
if
people
are
afraid
of
being
replaced,
maybe
they
should
push
themselves
to
be
the
best
self
and
and
and
like
obviously
we're
not
we're,
not
dictators.
We
we
the
dow
votes
on
this
stuff,
so
as
long
as
you're,
confident
of
what
you're
doing
and
you
feel
useful,
there
should
be
no
problems
but
but
yeah,
I
think,
yeah,
it's
a
it's
the
legacy
problem
we
took
into
any
junior
devs,
and
here
we
are.
B
All
right,
I
don't
want
to
push
this
any
further.
This
is
a
good
beginning,
of
course
it's
nothing
to
brush
under
the
carpet.
It
needs
attention,
but
it's
kind
of
enough
for
today,
so
we'll
move
on
to
the
next
one.
I
put
it
on
the
agenda,
I'm
not
sure
like.
We
should
like
highlight
it
so
much,
but
if
anyone
wishes
to
update
everyone
else
on
what
happened
with
the
fee
receiver,
maybe
we
could
just
mention
it
for
a
few
minutes
and.
G
Try
to
abstract
it
a
bit
here,
like
you
know,
federico
was
the
first
to
really
get
into
like
understanding
the
full
picture
of
how
it
worked
and
he's
actually
working
right
now
on
like
demonstrating
the
the
attack
in
code
and
we'll
also
put
together,
you
know
I'll
write
up
I'll
work
with
him
to
make
it,
like
you
know,
make
sure
it's
like
worded
well
and
abstracted
and
we'll
post
something,
and
I
think,
if
you
want
to
understand
it
at
some
point,
that
will
be
the
best
way
way
to
do
it,
but
yeah
just
a
little
context
on
the
fee
receiver.
G
It
was
like
the
last
thing
we
built
and
we
kind
of
rushed
it
at
the
right
before
launching
swapper.
We
didn't
get
a
formal
audit
done.
The
thinking
kind
of
like
in
a
more
abstract
sense.
There
is
that
we
could
revisit
it
if
it
got
to
a
point
where
there
was
like
a
significant
amount
of
funds
exposed
like.
So.
If
you
look
at
like
the
cost
of
this
attack,
it's
like
8k
right,
like
that's
less
than
you
would
have
spent
on
an
audit
easily,
but
but
that's
not
like
really
great
or
anything
anyways.
G
In
terms
of
what
happened
with
with
the
attack,
it
was
pretty
sophisticated.
The
attacker
created
a
fake
lp
token
and
then
created
a
pair
on
swapper
with
a
target
like
lp
against
the
native
currency.
So
like
say,
for
example,
gno
weth,
lp,
plus
wrapped
x,
die,
and
then
it
calls
the
take
protocol
fee
on
the
fee
receiver
contract
passing
in
the
address
of
the
fake
one,
which
then
returns
some
things
which
essentially
like
tricks,
the
fee
receiver
into
dumping.
G
The
real,
no
weth
protocol
fee,
lp
tokens
that
are
sitting
in
the
fee
receiver
into
that
new
pool
that
nobody
really
uses
that
the
hacker
like
put
a
small
amount
of
liquidity
in.
So
it
basically
like
dumps
without
kind
of
any
kind
of
protection
on
slippage.
Those
lps
into
this.
This
pool
controlled
by
the
hacker
and
effectively
like
losing
those
lp
tokens
to
the
hacker.
Don't
necessarily
expect
people
to
like
understand
that,
but
but
we'll
have
a
write-up
that
goes
through
real.
D
G
Well,
so
what
normally
happens
is
it
say
for
a
geno
west,
for
example,
it
will
have
an
lp
token
of
genome
with
and
what
it
will
try
to
do
on
like.
If
this
was
like
mainnet,
it
would
burn
the
lp
tokens,
get
the
gno
on
the
west,
back
trade,
the
gno
for
more
wealth
and
then
send
the
you
know,
and
then
it
would
unwrap
the
weft
and
send
the
eth
to
the
bonding
curve
contract.
G
G
I
mean
so
again
like
we
like,
I
don't
think
we
should
try
to
like
explain
this
on
the
call
it's
like.
I
said
it's
pretty
difficult,
even
if
you
already
know
what
you're
talking
about
like
and
the
write-up
should
like
give
you
the
information.
If
you
really
want
to
go
like
see
it
line
by
line
how
it
works
and
like
maybe
at
some
point,
we
can
do
a
demo
of
like
like
how
you
would
do
it.
B
Yeah
I
mean
we're
really
happy,
it
got
noticed
and
funds.
The
majority
of
the
funds
got
saved.
Some
some
of
the
funds
were
claimed
prior
to
to
this,
so
there
wasn't
much
in
there
to
begin
with
and
federico
is
working
on
a
write-up.
So
the
question,
a
follow-up
question
would
be
like:
are
there
any
gaps
in
terms
of
any
code
within
our
stack
that
we
are
using
and
has
funds
in
it
that
we
that
needs
auditing
or
we
we
good
on
that
front?.
G
No
everything
else
with
anything
with
like
funds
that
it
has
been
audited,
except
for
the
fu
receiver,
which.
B
G
I
suppose,
eventually
the
guilds
would
be
controlling
owning
the
few
receiver,
but
but
there's
no
like
direct
relevance
to
kills
yeah
chris
chris
asking.
Is
there
a
reason
to
have
it?
So
what
the
the
point
of
having
the
few
receiver
is
to
handle
this,
like
all
the
lp
because,
like
in
uniswap,
the
protocol
fees
when
they're
turned
on
like
are
sent
per
pair
in
the
form
of
that
paris
lp
token,
so
it
kind
of
like
grows
with
the
number
of
pairs
that
are
like
active
enough
to
have
meaningful
fees
right.
G
So
you
just
have
a
bunch
of
lp
tokens,
and
if
you
actually
want
to
do
something
with
those
funds,
you
probably
want
to
exchange
it
to
a
currency.
You
would
use
like
the
native
currency
or
stablecoin,
and
so
the
point
of
the
few
receiver
is
to
like
help
with
that
process.
Right
actually
like
do
it
instead
of
having
to
you
know,
pass
a
proposal
for
the
you
know,
you.
C
D
G
Yeah,
if
we
feel
like
the
fee
receiver
is
just
like
unusable
right
now,
that
is
like
a
quicker
fix
would
be
to
like
update
the
the
fee
receiver
address
to
just
be
the
treasury
itself.
Yeah
I
mean
that's.
That
is
an
option.
I
think
our
current
plan
was
to
like
think
he
already
kind
of
watches
the
fees
on
a
daily
basis.
G
I
guess,
and
if,
if
they're
meaningful,
we
can
call
like
the
take
fee
and
get
the
fees
out,
but
if
that
feels
like
it's
like,
if
it
gets
exploited
again
and
we're
like
okay,
we're
actually
losing
money
doing
this
like
we
could
do
that.
Actually
just
change
the.
B
And
the
the
the
economics
of
this
as
swapper
being
a
product
of
dx,
dow
and
gxt
token,
given
owners
a
claim
on
the
the
protocol
fee
and
it
kind
of
goes
to
the
treasury-
probably
buyback
reserve.
So
on
so
forth.
Now
recently
someone
asked
if
we
are
starting
a
swapper
guild.
Is
there
actually
an
a
treasury
for
swapper
and
like
this
new
fee,
receiver
should
probably
be
sending
funds
to
that
one
and
no
longer
jake's
down.
G
Yeah,
I
guess
those
are
questions
that
we
haven't
really
like
specified,
but
I
think
if,
if
the
idea
is
to
you
know,
spin
out
swapper
into
like
where
swapper
token
has
all
the
governance,
or
at
least
most
of
it
delegated
to
the
swapper
token,
then
it
makes
sense
for
the
swapper
guild
to
have
a
treasury.
Yes,.
B
So,
okay,
a
bit
of
a
an
ice
breaker,
op
d
feedback
operation,
decentralization
feedback.
How
did
you
guys
find
the
experience
listening
to
the
podcast
yesterday?
Were
you
on
twitter
spaces?
Were
you
on?
I
always
forget
the
name
of
it.
B
Watching
the
video
podcasts,
like
any
suggestions
of
anything
you
liked
didn't
like.
E
Unique
yeah,
what's
unique
about
like
in
general,
most
podcasts
I'd
say
in
the
world
are
not
live,
so
this
is
unique
because
it's
a
live
broadcast.
So
it's
it's,
it's
creating
a
podcast,
but
it's
I
wouldn't
even
call
it
a
podcast.
I
would
call
it
a
show.
It's
a
live
show
that
live
show
takes
place
on
riverside
with
guests
and
there's
video.
E
Then
the
question
is
like:
how
do
you
distribute
that
to
a
a
wider
audience?
It's
like
replaced.
Our
community
call
there's
discord,
there's
twitch,
there's
twitter
spaces.
What
we
did
is
we.
E
We
took
the
audio
from
that
experience,
which
is
a
video
show,
and
we
pumped
it
through
one
speaker
which
is
keenan
speaker
onto
twitter
spaces,
so
it
doesn't
actually
we're
using
twitter
spaces
as
a
distribution,
single
audio
distribution,
which
is
a
little
confusing
for
people
that
are
familiar
with
twitter
spaces
because
it
usually
you
would,
when
you
use
twitter
spaces
all
the
time
you
see
who's,
a
speaker
who's
a
listener.
You
see
who's
speaking
at
the
time,
you're
interacting
with
their
twitters
you're
following
them.
E
That
is
not
so
much
the
case
when
you're,
just
using
it.
As
an
audio
distribution
mechanism,
so
I
think
if
you
followed
it
just
on
twitter,
you
might
be
a
little
confused
if
you
followed,
if
you
actually
just
tuned
in
for
the
riverside
video,
show
live
video
show,
then
you
would
have
seen
what
you
were
expecting
and
then
we
had
some
internet
issues,
mainly
in
lisbon.
I
guess
lisbon
internet
didn't
work
that
well,
but
other
dudes.
E
E
But
if
I
guess
anna
lost
her
internet
altogether,
that
I
don't
know
what
happened
but
the,
but
the
ending,
the
ending
podcast
should
still
be
a
higher
quality.
I
think,
but
overall
yeah
it
was
an
interesting
first
show.
B
Yeah,
I
actually
like
chris's
suggestion
that
we
could
probably
drop
twitter
or
maybe
use
it,
but
make
sure
people
understand
that
it's
riverside.
That's
the
main
thing,
because
riverside
is
pretty
cool.
It
has
a
chat.
It's
it's
very
similar
to
jitsi.
I
really
enjoyed
the
experience
watching
the
videos
of
all
the
speakers.
B
B
B
Let's
see
next,
we
got
yeah
ross
shared
an
awesome
post
on
dell.
Talk,
oh
we're
at
the
top
of
the
hour.
Okay,
let's,
let's
give
this
like
five
minutes
and
then
we'll
disband
it's
friday.
After
all,
so
ross
posted
a
really
nice
post
on
doubt
talk
regarding
gxd
token
holders
having
a
voice
in
governance
and
question
is
whether
that
should
be
through
the
through
a
gxd
guild
or
go
straight
for
governance.
2.0
one
requires
just
some
front-end
updates.
B
The
other
one
is
tackling
very
heavy
smart
contract
work
and
it
will
take
quite
a
while
another,
two
or
three
quarters,
so
we
kind
of
have
to
make
the
decision,
and
my
question
is
ross
at
what
stage
are
you
with
the
development
and
when,
when
should
this
decision
be
taken?
B
H
Yeah,
so
I've
only
had
good
reception
so
far,
but
there's
also
not
been
any
comments
directly
on
the
forums
basically
sort
of
liked
it
in
discordance
about
it
all.
So
I
think
it's
I
need
some
time
to
sit
on
there
for
anyone
with
potentially
an
issue
to
raise
it
but
yeah.
So
the
the
a
lot
of
the
work
is
already
done.
Just
because
it's
guilds
there's
nothing
there's!
No.
There
is
there's
one
feature
that
needs
to
be
built
essentially
to
make
it
work
well,
which
is
explained
in
the
post.
H
But
if
you
haven't
read
it
yet
we
we
basically
need
to
create
a
feature
that
we're
planning
on
implementing
anyways,
which
allows
one
dial
or
one
guild
to
vote
in
another
tao,
which
is
fine.
It's
like
a
very
cool
feature
that
eventually
can
lead
to
some
revenue
generation
as
well
for
davi,
and
so
the
question
was
basically
asking
is:
is
this
something
worthwhile
to
do
holders?
H
If
this
takes
us
a
little
bit
of
time
to
implement
and
in
theory
it
could
take
away
some
time
or
they
could
reduce
or
extend
the
time
it
takes
for
governance
2.0,
just
because
it's
taking
development
resources
and
so
yeah
the
decision.
I
guess
I
think
it
makes
sense
for
it
to
sit
for
a
while.
Obviously
we're
a
bit
focused
right
now
on
just
preparing
the
v4
production
and
there's
like
plenty
of
other
stuff
to
do,
and
so
I
don't
think
we
need
to
rush
the
decision.
H
I'll
probably
spend
a
bit
more
time
fleshing
out
the
architecture
of
the
actual
feature
itself
and
coming
out
with
some
estimations
on
how
long
it
will
actually
take
for
us
to
influence.
But
I
don't
think
it
will
be
more
than
a
couple
of
weeks
of
development
time,
depending
on
how
we
prioritize
it
with
other
stuff
and
then
launching
the
hd
killed
itself
is
very
simple,
just
the
same
as
launching
any
other
guilds.
B
All
right
so
basically
having
a
dxd
guild
is
half
a
month
or
say
a
month,
and
and
it's
not
like
a
pending-
it's
not
like
you,
you
don't
have
much
to
do
and
you
have
to
start
working
on
either.
You
still
have
stuff
that
you're
actively
working
on
that
will
take
some
time
and
and
then
you
need
to
kind
of
like
take
the
make.
The
decision
yeah
like.
H
Possibly,
but
hopefully
not
if
I
flesh
out
the
feature
properly
before
we
dedicate
time
to
it,
it'll
also
be
after.