►
From YouTube: Bisq Q2 2020 Update
Description
A look back at Q1 2020: achievements, progress, and challenges...as well as a look forward at Q3 2020 and beyond.
See the deck here:
https://docs.google.com/presentation/d/1iTeumZKw1GrWFZv3XPnozYewVc9RDjzJWQo_73KxPI8/edit?usp=sharing
A
A
And
we
did
a
call
like
this
about
four
months
ago
at
the
end
of
February.
So
for
a
few
reasons,
it's
a
good
time
to
do
another
one
and
we'll
keep
this
to
an
hour.
Maybe
bless
and
wrap
up
the
end
of
the
QA.
But
the
main
points
are
reviewing:
what's
happened
so
far
this
year
in
q1
and
q2
we're
just
at
the
end
of
q2
right
now
and
talk
about
what's
what's
happening
right
now,
a
few
announcements
and
what
going
into
q3
might
look
like.
A
So
what
have
we
done
so
far?
I
wanted
to
start
by
talking
about
some
trading
numbers
because
I
don't
know
about
you,
but
if
you're
somebody
who's
in
bisque
a
lot
right
working
on
it
or
using
it
or
both,
you
tend
to
see
this
chart
a
lot.
Alright,
let
me
see
volume
and
BTC
charting
that's
the
monthly
chart
since
the
inception
of
the
project
way
back
in
April,
2016
or
the
going
live
of
the
project
right,
and
you
know
just
to
map
that
out
zooming
zooming
in
a
little
bit
right
before.
A
We
all
know
that
image
I
just
heard
some
artifact
make
sure
you're
muted,
if
you're
not
already,
but
just
to
plot
that
out
a
little
more
visibly
right.
This
is
you
know
this
is
what
things
looked
like
over
the
years
and
probably
most
of
us
know
what
this
big
spike
is
all
about
right.
These
are
the
Monaro
I
think
if
this
is
the
Monaro
spike
right.
A
So
this
is
when
we
had
a
whole
lot
of
manera
BTC
trading
on
the
platform
and
that
and
that
stopped
late
last
year
right
and
we
sort
of
reverted
to
the
mean,
if
you
will
so
at
a
glance.
That's
like
not
such
an
exciting
story
right.
All
of
a
sudden,
our
our
total
BTC
volume
is
back
down,
of
course,
no
nevermind
overlayed.
Here
we
haven't
overlaid
here.
A
Well,
what's
the
Bitcoin
price
right
I
mean
our
Bitcoin
volumes
are
always
going
to
have
a
whole
lot
to
do
with
the
value
of
Bitcoin
itself,
but
let's
just
never
mind
that
for
a
moment
we
kind
of
know
the
narrative
right
that
Manero
volume
went
away
so
well.
What
does
that
mean?
Well,
I
think
it's
just
worth.
Looking
at
it
from
a
different
perspective,
if
you
haven't
already
been
watching
the
numbers
this
way,
we
don't
graph
them,
you
don't
chart
them
in
the
in
the
app
and
we
don't
necessarily
tweet
about
them
all
the
time.
A
It's
quite
constructive
to
look
at
the
total
number
of
trades
happening
on
a
monthly
basis
here
right,
so
each
grade
bar
is
you
know,
you
see
the
total.
There
is
2,000
right
coming
into
you
know.
March
of
this
year
we
had
you
know
thirty,
four,
thirty,
five
hundred
that
number
at
the
top
is
the
average
number
of
trades
per
day
in
that
month.
So
on
on
that
long
trend,
you
know
this
is
just
a
steady
uptick
with,
of
course,
some
variance
month
to
month,
but
that's
something
that's
really
going
in
the
right
direction.
A
So,
even
though
we're
not
seeing
these
these
relatively
massive
yeah
volumes
of
BTC
with
you
know
just
sometimes
dozens
of
bitcoin
trades
between
manera
and
bitcoin
happening
every
day
that
it
actually
hides
the
the
story
that
there's
more
and
more
and
more
usage,
more
actual
trading
happening
all
the
time,
and
you
can
see
this.
This
bears
out.
These
are
the
coin.
Dance
grabs
and
people
may
be
familiar
with
just
looking
at
a
few
Fiat
regions
right.
So
let
me
take
you
know:
alt
coins
out
of
the
mix
entirely
and
they
forget
about
manera.
A
You
know
this.
This
story
bears
out
in
the
individual
fiat
markets
as
well.
So
this
is
the
euro
market
nevermind
this
gap.
For
some
reason,
coin
dance
doesn't
have
that
data.
But
but
again
you
can
see
that
kind
of
just
general
trend
line
going
in
a
nice
direction.
Right
more
and
more
Europe
volume,
generally
speaking
whatsoever,
run
same
thing
with
dollar
just
happened
to
have
had
the
best
best
month
ever
there
in
dollar
terms.
Last
month,
Brazil
has
been
quite
a
standout
there
and
yeah,
and
these
are
just
selecting
a
few
of
the
markets.
A
A
These
are
some
of
the
newer
metrics
have
gotten
in
place
that
we
plan
to
put
in
place
in
q1
and
have
rolled
it
out,
since
this
is
because
estimated
network
size
and-
and
you
know,
you
see
lots
of
lines
here-
nevermind
the
detailed
lines,
but
just
kind
of
look
at
the
top
line.
If
the
total
number
of
nodes
on
the
network
again
estimated,
this
data
is
not
perfect,
but
the
methodology
here
is
pretty
solid
leads
us
to
believe
that
it's
gonna
be
something
like
between
two
and
three
hundred
nodes
on
the
network
at
any.
A
Given
time
got
this
data
blip
here
recently,
not
quite
sure.
Why?
But
again,
even
these
numbers
are
still
200
so
somewhere
in
between
two
and
three
hundred.
You
can
think
of
it,
as
you
think,
those
users,
but
it's
really
measuring
nodes
right.
So
this
nodes
that
are
online
at
any
given
time
and
that
number
has,
since
we
started
measuring,
been
on
an
uptick
right
and
then
kind
of
you
know
steadying
out.
So
that
again,
you
know,
there's
not
necessarily
a
causal
relationship
here
between
the
uptick
in
the
number
of
trades
and
the
uptick
of
nodes.
A
On
the
network,
but
it
kind
of
makes
sense
that
they
would
be
related,
so
growth
continues
right,
even
even
if
not
in
you
know,
compared
to
all-time
high
total
PTC
volumes,
growth
continues.
So
what
did
we
ship?
What
did
we
do
over
q1
and
q2?
What's
new
and
noteworthy
we'll
talk
about
a
number
of
these
in
a
little
bit
more
detail
later,
but
you
know
in
general
we
didn't
ship
a
lot
of
big
new
features
in
it.
So
far
in
this
half
of
this
year
right,
it's
been
a
lot
of
under
the
hood
work.
A
It's
been
a
lot
of
looking
after
security
and
privacy
issues,
some
sticky
things
in
there,
and
sometimes
it
takes
a
long
time.
But
you
know:
we've
approved
the
trade
protocol.
We've
added
validations
into
the
trade
protocol,
where
necessary,
we're
working
on
account,
signing
signed,
witness
improvements
which
ultimately
helps
not
only
security,
of
course,
but
can
also
help
improve
liquidity.
Talk
about
that
later,
privacy
right.
We
discovered
that
we're
publishing
certain
IDs
in
you
know
in
offer
data
and
so
on.
A
You
know
onion
addresses
and
so
on
see
now
see
the
really
long
onion
whirls
for
new
users
and
that
we've
found
has
been
a
general
improvement
in
both
startup
time
connecting
to
the
throw
Network
and
we
believe
it's
responsible
for
us
and
improved
message,
delivery,
so
fewer
fewer
trades
ending
up
in
mediation
and
arbitration
because
something
failed
with
the
trade
protocol.
Some
message
didn't
get
through.
What
have
you
there
seems
to
be
an
improvement,
not
that
we
can
relate
this
change
or
we
believe
is
related
to
this
change,
at
least
and
in
general.
A
We're
up-to-date
with
you
know
the
changes
in
tor
right,
so
we're
not,
you
know,
lagging
behind.
That's
always
a
good
thing.
Staying
staying,
up-to-date,
their
reliability,
just
like
I,
was
mentioning
a
moment
ago,
making
trade
protocol
messaging
more
robust,
both
in
the
sense
of
like
at
the
network
level
at
the
tor
protocol
level,
but
also
we've
given
users,
just
the
manual
ability
to
click
a
button
and
resend.
A
Certain
trade
protocol
messages
like
that
the
payments
received
so
sometimes
that
message
would
get
dropped
for
whatever
reason,
and
that
would
end
up
meaning
the
trade
would
go
to
mediation
right,
yes,
for
the
only
way
to
resolve
it.
Now,
if
that
seems
to
be
the
case,
users
can
just
click
about,
and
then
resend
and
very
often
that
solves
the
problem.
A
Various
wallet
improvements
talk
a
bit
about
more
those
later
we
saw
what
we
called
the
ghost
offer
problem
old
offers.
We're
still
showing
up
were
no
longer
relevant,
so
we
reject
expired
data.
That's
what
that's
about,
and
one
of
the
big
ones
recently
was.
We
saw,
as
you
know,
big
feast
bike,
for
you
know,
number
of
weeks
in
a
row.
Just
you
know,
men
pools
were
relatively
speaking,
filling
up
and
fees
were
spiking
and
our
our
old
fee
estimation
back
in
which
was
earned.
A
Calm
was
failing
miserably
to
give
good
estimates,
so
they
were
way
too
high
and
we're
paying
way
too
much.
We
fixed
that
moved
away
from
earn
two
men
pool
to
be
not
to
the
general
notion
but
to
the
project
called
men,
pool
minimal
API
and
are
getting
much
better
estimates
on
that,
and
we
also
saw
that
that
subsequently
improved
the
decentralization
that
that
was
a
single
point
of
failure.
A
They
were
just
talking
to
her
and
calm,
and
then
we
were
just
talking
to
one
then
pull
back
end
and
now
we're
talking
to
a
number
of
different
men
pull
back
in.
So
we
have
that
resiliency
in
in
decentralization
there
and
we
shipped
11
times
since
January.
First,
so
I've
had
a
pretty
steady,
cadence
there,
okay,
so
when
we
did
the
q1
call
in
February,
we
laid
out
a
number
of
goals
and
I
want
to
review.
How
was
it
gone
there
right?
A
What's
the
progress
been
like
well,
one
of
the
one
of
the
biggest
levers
that
we
have
potentially
to
increase
liquidity
is
rolling
out
an
API
right,
making
accessing
bisk
trading
on
disk
programmatic
or
opening
up
programmatic
access,
and
that
work
has
been
underway.
It
was
called
for
quite
some
time
and
it's
been
actually
in
progress
now
for
for
some
months,
just
slowly
and
steadily
chipping
away
one
in
points
after
another,
so
from
being
able
to
check
your
balance,
to
ultimately
being
able
to
publish
an
offer
right,
locking
and
unlocking
your
wallets
and
so
on.
A
All
the
things
that
need
to
be
done
in
order
to
accomplish
you
know
the
most
basic
kind
of
end
to
end
trading
scenarios
so
that
people
can
write
plots
against
bisque
or,
ultimately,
even
possibly,
you
know,
write
a
kind
of
web
front-end
for
bisque
or
something
like
that,
so
that
work
goes
on
yeah,
but
it's,
but
it's
not
released.
Yet
we
haven't
had
any
sort
of
initial
release.
A
Some
people
may
have
noticed
that
we
sent
out
some
tweets
and
a
forum
yesterday
just
to
begin
kind
of
engaging
with
the
community
and
making
sure
that
we're
building
what
they
want
and
getting
some
feedback.
So
we
can
expect
don't
have
a
date
here,
but
can
expect
the
kind
of
MVP
write
a
Minimum
Viable
Product
version
of
the
a
the
API
to
ship
in
the
near
future
and
so
stay
tuned.
A
For
that,
like
I
mentioned
account
aged
witness
account
sighting
improvements
underway
now,
that's
both
security
right,
like
things
like
avoiding
you
know,
bank
account
fraud
and
scams,
but
it
also
the
more
we
propagate
you
know,
account
signing
and
so
on.
The
more
people's
limits
can
increase
and,
of
course,
that's
good
for
liquidity,
because
people
can
make
you
know
larger
trades
right.
So
it
increases
the
depth
of
liquidity
and
March
was
a
big
push
for
liquidity
in
the
growth
team,
and
that
was
certainly
successful
by
some
measures.
A
But
it's
hard
to
draw
real
conclusions
about
it,
because
that
was
right
when
all
things
coded
started
to
happen
and
became
pretty
difficult
to
keep
pushing
like
we
were
pushing
on.
You
know,
market
makers-
and
you
know
in
all
these
efforts
when
you
know
the
whole
world
was
shoving
down
and
freaking
out,
so
mixed
mixed
results
makes
success
and
there
are
some
takeaways
there
that
all
I'll
get
you
later.
A
That
kind
of
inform
us
about
what
we'll
do
going
forward
and
growth
and,
like
I,
mentioned
in
terms
of
increasing
liquidity,
we've
seen
this
steady
uptrend
in
the
number
of
trades
right.
So
that's
important
for
liquidity
too,
if
you
think
about
liquidity
and
these
kind
of
like
two
major
factors
right,
you
know,
there's
there's
depth
like
you
know
how
much
Bitcoin
can
I
trade
against
whatever
pair
on
bisque
and
then
there's
just
what's
the
likelihood
that
I
can
find
a
counterparty
right
for
any
amount?
A
How
many
offers
are
there
and
so
on
how
many
people
are
involved,
so
certainly
that's
been
getting
better,
more
offers
more
users,
okay
and
improving
support.
This
was
an
area
where
this
is
a
goal
that
we
focused
on
a
lot
like
right
out
of
the
gates
around
the
time
that
key
one
call
and
made
a
bunch
of
progress
right.
So
we
rolled
out,
you
know
a
more
mature
support
escalation
process,
so
we
kind
of
have
a
level
one
and
level
two
teams
now
level.
One
is
now
really
well
staffed.
A
You
know,
we've
got
full
coverage,
you
know
more
or
less
around
the
clock
around
the
world
right
where
you
know,
when
people
come
into
key
base
and
then
go
into
the
support
chain,
then
they
have
a
question.
Operators
are
standing
by
right.
Support
agents
are
standing
by
and
so
that's
that's
been
I
think
a
win.
I
think
that's
something
that's
working
and
we
have
a
coverage
calendar
for
that
and
so
on,
and
the
level
to
support
is
really
just
a
formalization
of
escalating
things
to
Deb.
A
So
you
know
a
number
of
disk
dev
members
right
are
also
on
the
support
calendar.
They
have
a
daily
shifts.
You
know
every
so
many
days
this
dev
is
on
is
on
call
that
Deb
is
on
call
and
they're.
Simply
there
you
know
just
promising,
essentially
if
something
needs
to
be
escalated,
I'll
be
on
points
right
and
I'll
help
carry
that
support
case
out
and
so
far
so
good.
This
seems
to
be
a
situation,
that's
working
well.
A
We
now
have
more
mediators
right
and
better
coverage
of
mediators,
better
responsiveness
among
the
years.
So
when
people,
when
traders
do
have
a
trade,
you
know
it's
not
working
and
goes
into
mediation
again
now,
mediators
are
standing
by
rights,
helping
them
quite
reliably.
We
established
a
critical
bugs
board
and
a
process
around
the
right,
so
a
way
that
we
can
see
what
are
the
most
important,
the
most
pernicious.
Those
problematic
bugs
or
other
issues
right
that
are
causing
them
just
basically,
loss
of
service
or
inability
to
complete
use
cases,
and
so
on.
A
That
process
is
all
there
that
was
delivered,
say
that
there's
work
to
go
to
having
it
really
integrated
deeply
into
how
we
prioritize
and
so
on,
and
we'll
get
to
that
in
the
kind
of
going
forward
plan.
Toward
the
end
of
this
call,
we
built
out
the
Bisquick
e
right
over
these
last
months.
They've
been
lots
of
activity
in
there
and
from
the
perspective
of
supports
right
it.
Basically
he
does.
You
know,
addresses
a
number
of
things
right,
but
from
the
perspective
of
support,
it
acts
as
a
kind
of
knowledge
base
right.
A
So
when
we
have
really
common
things,
we
want
to.
You
know
that
we
often
need
to
refer
users
to
those
things
are
now
increasingly
in
the
wiki.
In
just
a
link
away
and
the
process.
There
is
much
easier,
you
know
to
add
contents
and
change,
content
and
so
on.
Then
it
then
it
was
under
the
docs
dot,
mist,
Network
sort
of
paradigm,
which
is
a
much
more
rigorous
kind
of
change.
A
Control
process
both
have
their
place,
both
are
still
up
and
we'll
see
some
exciting
new
stuff
on
the
docs
side
in
a
moment,
but
the
wiki
is
there
and,
as
you've
seen
developments
where
you
know
getting
ready
to
announce
the
really
the
launch
of
that.
So
it's
kind
of
you
know
sort
of
ready
for
primetime
in
the
public
to
know
about
it
and
use
it.
A
Okay
and
so
lots
of
other
progress
right.
One
of
the
things
that
we
said
that
we
would
do
in
q1
is
we
would
roll
out
the
kind
of
detailed
support
case.
Tracking
efforts
where
you
can
imagine
just
like
sort
of
any
support
organization
has
a
ticketing
system.
That
kind
thing
we
plan
to
use,
github
issues
where
every
you
know,
support
agents
would
log.
A
You
know
that
that
case
came
their
way.
What
the
problem
was,
what
the
resolution
was,
what
any
relevant
bugs
were.
You
know
new
bugs
that
they
created
because
of
it
how
long
it
took
to
close
the
issue
and
so
on,
and
we
went
a
good
distance
toward
like
designing
that
and
rolling
it
out,
but
it
just
got
dropped
right.
It
just
didn't.
Have
the
kind
of
priority
it
was
necessary
to
take
precedence
over
lots
of
other
things
and
in
practice
it
seems
that
we
don't
really
need
it.
A
A
This
remains
a
pain
point
and
I'll
get
into
that
later
and
what
we're
trying
to
do
about
it,
but
simply
there
are
just
too
many
of
these
cases
coming
our
way.
So
we
want
to
resolve
that.
Okay
and
just
to
give
you
a
sense,
you
know
I
have
these
bullet
points
here
and
so
on.
But
where
is
all
that
information
coming
from?
It's
not
just
in
my
head
right,
but
you
know
we're
actually
tracking
this
in
what
we
call
the
master
projects
board.
This
is
part
of
the
overall
project
management,
infrastructure
and
process.
A
It's
been
rolling
out
over
last
month's
talk
about
that
explicitly
in
a
moment,
but
I
just
wanted
to
give
a
quick
screenshot
here
for
context
right
here,
we're
looking
at
the
master
projects
board
and
and
focused
in
on
the
goal
to
improve
support
right
size,
just
a
label
and
github.
You
have
issues,
but
you
can
see
that
now
all
the
labeled
issues
like
rolling
out
the
Bisquick.
You
know
it
was
a
kind
of
improved
support
effort
case
tracking
project
process
was
aborted.
The
support
team
scheduling
escalation
process
was
delivered
right.
A
These
things
that
I've
been
mentioning,
so
those
are
actually
all
tracked
on
this
board
as
an
agile
project,
and
so
you'll
see
another
couple
of
screenshots
of
this.
But
that's
something
you
can
kind
of
keep
in
mind
if
you're
not
aware
of
the
infrastructure,
as
we
continue
to
care
for
that.
That
can
be
a
place
to
go
and
really
get
a
high-level
view
of
well
what's
going
on
in
the
team,
okay
and
so
back
to
the
goals
France.
That
was
improving
support.
A
Various
wallet,
improvements,
kind
of
small
things
like
how
we
managed
dusts
right,
but
they
all
add
up
to
making
a
better
experience
and
having
fewer
fewer
disappointing
experiences
for
users
right
got
a
kind
of
nasty
bug
about
too
long
transaction
chains,
right,
really
kind
of
detailed
stuff
down
to
the
coin
protocol
level.
We've
spent
time
routing
these
things
out
and
like
I
mentioned
improving
fee
estimation,
then
in
the
process,
removing
a
single
point
of
failure
or
a
central
point
of
failure.
A
Okay,
so
on
to
the
next
goal:
improving
onboarding
right,
if
you
remember
from
if
you
attended,
the
q1,
call,
give
a
kind
of
sneak
preview
of
a
really
beautifully
designed
step-by-step
onboarding
wizard.
That
will
take
users
through
if
the
process
of
doing
everything
from
setting
up
your
seed
and
so
on
in
a
very
modern
way.
So
they
just
end
up
with
a
working
ready
to
go
ready
to
trade.
This
node,
we
have
not
made
progress
on
integrating
that
that
UI.
A
What
we
have
done
is
some
of
the
preliminary
work
that
we
identified
to
get
metrics
in
place
so
that
we
can
actually
measure
how
well
that
works
and
I'm
going
to
show
you
some
of
those
in
a
moment.
But
what
you're
about
to
look
at
is
monitor.
It's
up.
Bisk
network
and
I
have
a
feeling
that
a
lot
of
people
watching
this
video,
maybe
you've
heard
of
it,
but
you
haven't
like
actually
really
dug
into
it's.
A
Really
this
cool
stuff
there
now
so
I
wanted
to
just
take
a
little
little
digression
and
give
a
very
quick
tour
right
dashboard
at
not
a
novice
Network.
Just
telling
you
I
was
trading
going
high
level
numbers.
Okay,
we
did
about
six
Bitcoin
in
the
last
24
hours,
with
the
trading
cetera,
how
many
sell
offers
buy
offers.
But
if
you
scroll
down
there,
you'll
see
one
of
these
one
of
the
you
know.
Detailed
kind
of
dashboards
is
key
performance
indicators
and
that's
some
stuff
that
we
built
out
over
the
over
the
last.
A
You
know
months
since
that
last
call
to
support
that
change
when
onboarding
does
get
integrated,
so
you
already
saw
the
estimated
network
size.
Okay,
how
many
nodes
are
on
the
network?
We've
also
got
information
about
how
many
offers
are
there
relative
to
how
many
nodes
are
offers
per
node?
So
you
can
see
that
number
right
now
is
0.7.
So
that
means,
of
course
there
are
some
nodes
out
there
that
don't
have
any
published
offers.
A
Of
course
there
are
right,
but
it's
approaching
one
right,
that's
kind
of
a
good
number,
okay,
so
most
people
who
have
a
disk,
no
doubt
there
have
one
offer-
or
maybe
there,
maybe
it's
more
lumpy
right.
Some
disc
notes
have
lots
of
offers
can't
tell
from
that
number,
but
that's
one
important
data
point
and
then
there's
trades
per
offer
right.
A
So
how
often
are
people
actually
finishing
the
process
like
so
it
doesn't
matter
if
somebody
just
publishes
an
offer,
if
nobody
ever
takes
it,
but
how
many
people
are
actually
taking
those
offers
which
you
know
can
be
interpreted
in
different
ways
like
how
confident
are
people
to
actually
click
that
button
right
and
go
through
the
process
of
the
trade?
So
the
more
the
more
successfully
we
onboard
people
getting
them
from
zero
to
ready
to
go
ready
to
trade
understanding
what's
necessary
to
do.
We
would
probably
see
trades
proffer
go
up
right.
A
A
So
what's
the
progress
there
like
again
a
lot
of
activity,
so
we
rolled
out
the
new
team
structure
that
I
think
everybody's
familiar
with
right:
admin,
team,
dev
team,
ops,
team
support
team
etc,
and
we
established
the
growth
team
and
we
established
and
budgeting
across
all
of
those
teams.
In
the
total
rolled
up
budget,
we
started
really
putting
that
budgeting
into
practice,
both
at
the
level
of
you
know
when,
through
the
project
management
process,
people
are
putting
up
estimates
for
their
projects.
A
This
is
about
what
I
think
it's
going
to
take
I
kind
of
denominated
in
u.s.
dollars.
This
is
what
you
know:
sort
of
level
the
estimate
and
then
team
leads
are
taking
that
into
account
right
when
they're
helping
to
approve
those
those
projects
and
so
on.
Granting
them
budget
making
sure
that
they
don't
go
over
budget
and
and
we're
also
keeping
the
budget
in
mind.
A
Now
when
it
comes
to
compensation,
team
leads,
are
responsible
for
reviewing
compensation
requests
from
members
of
their
team
or
people
who
have
done
work,
sort
of
organized
under
that
team,
and
you
can
see
you
know
again,
not
necessarily
a
perfect
causation
story
here,
but
it's
interesting
to
see
what
the
SQ
issuances
looked
like
over
the
last
here.
We
see
the
last
eight
cycles.
A
A
Thinking
about
how
to
do
it
already
the
number
drop
down
very
significantly
in
cycle
nine
and
in
cycle
10,
we
instituted
the
compensation,
request,
review
process
right
under
the
new
budget,
and
so
you
know
I
see
these
kind
of
this
kind
of
trend
line
like
you'd
want
I
mean.
Of
course,
we
don't
want
that
to
go
to
oh,
we
want
people
to
do
good
work
and
get
paid
right.
But
with
this
kind
of
you
know,
extra
level
of
you
know
judicious
it
was
about.
A
A
He
also
established
the
project
management
process,
we'll
talk
about
that
in
a
minute
and
we
generally
cleaned
up
roles
and
bonding.
So
if
you
rewind
four
five
six
months,
there
were
quite
a
few
roles
that
people
were
playing,
but
they
hadn't
put
up
bonds
for
myself,
included
and
and
just
over
the
last
month's
and
just
step
by
step
role.
A
My
role,
you
know,
we've
gotten
just
tightened
everything
up,
made
sure
the
things
of
documents
and
make
sure
people
are
actually
playing
the
roles
that
they
say
they
are
if
bonds
have
been
put
up
and
so
on.
If
things
are
in
better
shape,
okay-
and
here
we're
just
seeing
again
a
glance
at
the
master
projects
for
this
time,
we're
filtering
on
things
that
have
been
labeled
to
improve
management
right
so
back
bowl,
and
you
see
the
thing
that
I
talked
about
like
establishing
the
budgeting
process.
A
That's
still
in
progress
and
the
other
things
like
cleaning
up
roles
and
bonding
and
so
on,
like
I
mentioned
okay,
so
so
much
for
a
review
of
the
goals
that
we
laid
out
in
q1.
Let's
talk
about
the
security
incident
that
happened
this
April,
probably
most
people
in
the
call
will
recall
that,
just
to
recap
the
facts
right
so
35
34,
almost
35
Bitcoin
worth
at
the
time.
Two
hundred
and
thirty
six
thousand
dollars
was
stolen
from
seven
victims
and
we
were
in
touch
with
all
those
victims.
You
know
direct
lines.
A
Would
that
be
one
of
them?
Ultimately,
this
was
caused
by
a
failure
to
validate
the
pay
out
address.
That's
used.
We
call
this.
The
donation
address
right,
that's
really!
The
pad
address.
That's
used.
When
cases
go
to
arbitration,
it
became
possible
for
the
for
the
attacker
here
to
spoof
that
address
right
to
change
into
their
own,
and
we
were
just
failing
to
validate
that
on
both
sides
of
the
peer-to-peer.
You
know,
transaction
right.
Trade
fix
that
immediately
shifted
immediately.
Problem
is
solved
right
so
that
that
won't
happen
again.
A
We
also
done
some
additional
validations
right,
patching
up,
potentially
other
holes
and
the
repayment
of
those
victims.
So
we
agreed
that
we
would
repay
that's
going
to
begin
in
version
136,
so
we
just
shipped
one
three
five
and
we're
finishing
up.
You
know
review
and
testing
of
the
pull
request
for
the
change.
That's
actually
going
to
programmatically
automatically
payout
those
victims
using
the
Bitcoin
using
trading
fees
that
are
paid
in
Bitcoin.
A
A
All
of
those
hard
questions
have
led
us
to
create
a
new,
a
new
team
right,
in
addition
to
the
teams
that
we
already
laid
out
and
I
already
mentioned
a
moment
ago,
a
security
team
I'll
talk
about
that
a
bit
more
in
a
moment,
I
just
double
check
again
everybody
that
you're,
muted
I,
occasionally
hear
an
artifact,
so
somebody
seems
to
be
having
their
mic
on
okay,
so
I
want
to
talk
a
bit
about
challenges
right
still,
sort
of
in
the
mode
of
looking
back
at
q1
and
q2.
Where
are
we
right
now?
A
What
are
some
of
the
challenges?
This
is
not
comprehensive
right.
There
are
other
things
it
could
be
on
this
list,
but
particularly
with
a
view
toward
what
I
want
to
talk
about
going
forward.
I
want
to
mention
these
in
particular.
I
already
mentioned
this
problem
of
too
many
arbitration
cases
are
too
many
refund
agent
cases.
A
One
thing
that
seems
to
be
happening
right
is
what
we've,
what
we
call
future
trades
right,
where,
where
people
are
essentially
gaming,
the
system
taking
an
offer
and
then
waiting
to
actually
complete
the
offer
to
see
what
the
price
does
and
if
the
price
moves
against
their
favor,
they
cancelled
right
and
now
should
be
a
situation
that
gets
appropriately
penalized
from
their
security
deposit.
But
the
way
things
are
working
in
practice
after
the
v12
arbitration
and
mediation
changes
that
that
penalty
isn't
happening
like
it
should
certainly
not
as
often
as
it
should
so.
A
People
are
kind
of
getting
away
with
this,
and
it
seems
to
be
you
know,
essentially,
a
misalignment
of
incentives
or
a
Miss
or
failure
of
checks
and
balances
could
lead
to
too
many
of
these.
What
we
call
future
trades.
So
we
definitely
want
to
lock
that
down.
There
are
other
reasons
that
things
go
to
arbitration
as
well,
like
you
know,
failed
protocol
messages.
You
know
somebody
made
the
payment,
but
they
couldn't
click
the
button
because
of
a
technical
failure
right
and
they
end
up
unnecessarily
going
into
arbitration.
A
So
on
so
there's
a
combination
of
bugs
that
leads
that
leads
to
this,
and
some
essentially
design
problems
right
and
we
want
to
we're
gonna,
really
attack
those
and
cut
down
the
number
of
these
cases.
It's
not
that
there
is
a
huge
number,
but
really
almost
any
number
is
too
many.
We
when
we
designed
the
new
one,
the
two
changes.
We
knew
that
the
assumption
was.
We
would
have
a
very,
very
low
number
of
arbitration
cases
like
one
or
two
a
month
say
right
everything
more
than
that.
A
So
we
really
want
to
crush
this
problem,
and
one
way
that
we'll
do
it
is:
will
increase
fiat
security
deposits,
MV
136
and
we'll
make
sure
that
they
that
the
penalty
actually
gets
enforced
right
if
somebody's
engaging
this
kind
of
future
trade
gaming
situation,
so
it'll
be
really
painful
right.
If
you
don't
follow
the
rules
of
the
protocol
and,
of
course,
you'll
get
your
full
security
deposit
back
and
so
on
when
things
are
completed
properly,
but
this
is
one
of
the
things
that
we
do.
A
We've
identified
it's
just
sort
of
almost
obviously
necessary
to
do
in
order
to
curtail
this
behavior.
The
other
thing
that
we'll
certainly
do
there's
a
number
of
things
we
may
do,
but
the
second
thing
that
we'll
certainly
do
is
just
put
much
more
prominent
messaging
into
the
app
about
what
it
means
to
violate
the
protocol
and
what
you
should
expect,
and
we
won't
do
this
as
a
pop-up
right,
because
you
know
this
has
quite
a
few
pop
ups
and
it's
all
too
easy
to
just
click
them
away
and
say.
A
A
Now
that
we'll
get
to
in
a
moment
is
just
how
we're
how
we're
managing
ourselves
as
a
dev
team,
so
I'm
calling
out
you
know
resourcing
and
prioritization
and
productivity.
It's
just
a
simple
fact
that
we
have.
You
know
relatively
few
people
very
few
people
that
are,
you
know,
sort
of
waking
up
every
day.
Thinking
about
this
can
work
on
it
like
a
like
it's
their
full-time
job
right,
that's
a
you
know
on
the
order
of
3
or
4,
people
tops
right.
A
We
have
a
number
of
new
newer
right.
Some
have
been
around
for
months
already,
newer
developers
in
many
cases
are
really
promising
have
been
doing
great
work,
maybe
aren't
as
fully
dedicated
but
are
in
some
cases
wanting
to
be
can
be
in
the
work
that
they
do
do
is
great
I
want
to
do
a
much
better
job,
going
forward
of
coordinating
those
resources
and
really
working
as
a
team
right
now
we're
not
making
the
kind
of
progress
that
we
think
we
can,
and
so
it's
a
kind
of
back
to
this.
A
You
know
improving
if
you'd
like
to
call
it
management,
but
it's
just
asking
a
question:
what
do
we
need
to
do
to
make
the
fullest
use
of
the
people
that
we
have
right
against
some
pretty
sticky
challenges
right,
like
with
the
code
base
itself
right?
This
is
a
complex
application
and
no
one
of
us
really
has
breadth
and
depth.
A
You
know
understanding
a
mastery
of
all
of
it
right,
so
we
really
want
to
build
up
that
muscle
inside
the
team
of
you
know
collective
understanding
in
depth
about
how
Fisk
works
so
that
it's
possible,
for
you
know
when
things
come
up
right,
one
of
us,
a
couple
of
us
can
really
get
in
there
and
make
changes
very
effectively
right
and
have
it
take
a
minimum
amount
of
time.
These
things
are
really
challenging
right,
and
so
we
have
some
ideas
about
how
to
do
it.
A
Talk
about
that
and
all
the
project
management
process
comes
into
it
and
some
new
developer
calls
is
your
hope.
Can
it
be
a
key
aspect?
So:
okay,
that's
q1,
q2
in
a
nutshell,
I'm
sure
I've
missed
some
things.
Sorry,
if
I
missed
anything
of
great
importance
to
you
but
I,
think
that
gives
it
kind
of
gist
rights
of
what
we've
been
up
to
and
what
we've
done,
how
we
did
with
our
goals,
etc.
And
so
now,
let's
talk
about
this
moment
right
and
going
forward,
it's
a
q3
themes
and
maybe
some
updated
goals.
A
I
think
from
you
know
all
the
conversations
that
we've
been
having
over
the
last
over
the
last
days
and
weeks.
Here
are
some
themes
not
necessarily
complete
or
comprehensive,
but
some
things
that
have
been
have
been,
you
know
really
floating
around
and
team.
One
is
let
let's
stay
the
course
right.
You
know.
A
number
of
those
goals
are
still
totally
relevant,
increasing
liquidity
and
so
on,
and-
and
you
absolutely
want
to
implement
that
onboarding
workflow
yeah.
A
Let's
keep
those
goals
in
front
of
us
and
do
everything
we
can
to
to
continue
carrying
them
out,
redoubling
our
security
efforts
hugely
important
from
a
lot
of
time
limits
like
I,
mentioned
the
new
security
team,
etc
and
improving
dev
teamwork,
focus
and
productivity
like
I
just
mentioned
and
growing
the
user
base.
So
I
mentioned
before.
Like
you
know,
we
did
this
big
liquidity
push
in
March,
where
a
lot
of
the
focus
was
around.
You
know,
market,
making,
right
and
incentivizing
market
making
and
rallying
market
makers,
which
makes
a
lot
of
sense
right.
A
So
it's
a
strategy
that
makes
sense-
and
you
know
just
talking
with
Steve
right-
the
lead
of
the
growth
team
like
one
of
his
takeaways,
is
it's
not
that
doesn't
work
and
it's
not
that
those
efforts
aren't
worth
investing
something
into,
but
that
what
seems
to
be
even
more
effective
right,
certainly
for
like
that,
the
effort
involved
and
so
on
is
delivering
more
content.
More
often
right,
so
you'll
see
in
a
moment
some
of
that
content.
Work.
A
That's
been
done,
but
you
know,
there's
a
there's
a
seems
to
be
a
pretty
good
relationship
between
you
know
what
we
put
out
there
for
people
on
Twitter,
particularly
right.
You
know
new
content,
new
how-to
things
are
gonna,
be
in
the
wiki
videos,
getting
started
guys
I've
seen
a
moment.
That
seems
to
have
a
pretty
good
a
kind
of
return
on
investment,
and
indeed
we
do
see
more
more
users,
more
trading
on
the
platform
now
exactly.
What
is
that
right?
A
Probably
something
you
do
at
the
market,
making
efforts
Minh
seems
to
just,
as
a
kind
of
you
know,
big
takeaway
from
these
months
of
just
being
in
the
trenches
doing.
This
seems
like
it's
about
at
least
as
much,
if
not
more,
delivering
great
conference
people
and
really
getting
the
word
out
and
providing
people
with
ever
sort
of
easier
resources
to
get
going
with.
This
can
understand
this
consoling.
So
that's
a
theme,
so
I
just
want
to
take
a
moment
to
try
to
update
the
goals.
A
These
are
the
five
that
we
already
talked
about
and
I
think
they
largely
stay
the
same,
but
I
would
probably
scratch
out
improving
support
now,
not
because
it's
not
ongoingly
important
support
is
ofcourse
very
important
right,
but
rather
just
to
indicate
that
it's
largely
working.
So
it's
not
something
that
needs
to
be
necessarily
a
top-line
goal
for
us
to
continue
improving
it
in
radical
ways
right.
You
need
to
keep
doing
what's
working,
keep
making
incremental
improvements
as
we
identify
those
things,
of
course,
but
I
would
put
in
its
place
security
right.
A
Okay,
so
a
few
announcements
what's
going
on
right
now
talked
about
the
Bisquick
II
many
people
may
be
mostly
people
on
this
call.
I've
seen
it
in
some
way
or
even
tribute
into
it,
but
we're
really
ready
to
have
it
be
prime
time
and
be
more
public
about
it.
You
link
to
it
more
prominently
and
so
on.
So
this
is
the
I
think,
as
of
today,
even
just
a
few
hours
ago,
an
updated
main
page
right.
It's
really
kind
of
a
nice.
A
You
know
central
point
that
you
can
go
and
find
out
all
the
top
level
resources
and
so
on
bit
of
a
different
flavor
right.
Then
the
the
main
website
is
got
network,
of
course,
that
remains
that
has
its
own
utility
and
so
on.
But
for
the
kind
of
you
know,
people
who
are
more
familiar
with
this
maybe
just
need
to
get
in
there
and
like
get
access
to
all
the
different
things
right.
A
This
is
a
you
know,
a
nice
kind
of
where
main
page
to
do
that
and
you'll
see
this
getting
started
link
but
I'll
dig
into
in
a
moment.
That's
something
new
as
well.
So,
like
I
mentioned,
it
serves
as
a
support
base
as
a
kind
of
knowledge
base
for
support.
There's
lots
of
documentation
of
pertaining
to
the
DAO
in
there,
particularly
if
I
can
role
specifications.
So
that's
where
the
documents
live.
Let's
say:
ok,
you're
playing
a
role
like
github
admin
or
mediator,
or
a
support
team
lead
or
whatever
it.
A
You
know,
I
think,
40
or
so
active
roles
and
the
DAO
how
all
the
responsibilities
get
taken
care
of.
So
what
do
those
roles
mean?
What
are
their
duties?
What
are
their
rights,
etc?
Like
all
of
that
stuff
is
in
the
looking
now
and
we
turned
off
account
creation
when
we
open
it
up,
we
had
you
know
just
anybody
can
create
an
account
it's
for
the
wiki
spirit
right,
but
unfortunately
we
had
some
a
couple
of
like
vandalization
issues
and
so
on.
So
we
we
turn
it
off.
A
But
if
you're
interested
in
contributing
just
come
talk
to
us
in
cubase,
there's
a
wiki
channel
and
you
know
happy
to
grant
access
to
people
who
want
to
add
value
to
that
need
who
knows?
Maybe
when
we
have
more
maturity
around
it,
we'll
open
it
up.
What
we're
missing
right
now
is
like
the
tea.
You
know
the
individual
or
the
team
of
people
like
like
think
about
like
Wikipedia
editors
right.
We
don't
really
have
people
standing
behind
it
like
make
it
their
business
every
day,
so
to
review
and
patrol
new
pages
and
changes.
A
We
do
have
people
watching
that,
but
they
have
other
responsibilities
right
so,
like
the
Vandal
is
a
vandalism,
you
know
it
just
it
happened
and
you
know
I
mean
we
was
responding
pretty
quickly,
but
there's
also
just
just
really
standing
on
top
of
even
other
contributors
making
changes
to
the
wiki
and
making
sure
that
they're
like
the
right
changes,
there's
actually
like,
really
sensitive
information.
Then
it
really
matters.
So
we
want
to
be
careful
to
some
degree.
A
We
at
least
want
to
have
some
systematic
review
process,
and
you
don't
know
that
right
now,
so
if
this
is
something
if
you're
watching
this
and
you're
like
really
into
this
sort
of
thing,
you
know
like
you
know
you
loved
working
with
wiki
is
you're.
You
know
great
with
documentation,
and
this
is
your
profession
and
that
kind
of
thing
like
we
want
to
hear
from
you,
because
this
is
a
sort
of
open
role.
You
know
playing
that
role
of
editor,
reviewer,
Patrol
or
etc.
A
Mostly,
you
just
want
to
get
in
there
and
add
valuable
content,
but
if
you
are
also
inclined
to
do
that
kind
of
work
like
couldn't
definitely
like
talking,
okay,
so
on
that
getting
started
front,
this
is
something
pretty
exciting.
I
think
the
getting
started
page
on
the
main
site
has
been
completely
redone
and
you'll.
See
here.
If
there's
just
four
steps
right,
download
and
install
backup
the
keys
right
down,
you
see,
create
a
payment
account.
Do
a
trade
and
you'll
notice
is
like
very
little
text.
A
So
it's
light
on
text
and
it's
heavy
focus
on
walkthrough
videos.
And
again,
if
you
look
at
that,
you'll
see
you
know
each
one
of
these
has
several
different.
You
know
variants
right
depending
on
what
it
is
that
you're
interested
in.
Are
you
looking
at
a
Fiat
trade
or
all
coin?
Are
you
on
Windows,
or
are
you
on
Linux
right?
So
there's
really
a
carefully
design.
You
know,
I
think
a
lot
of
effort
went
into
this
and
it's
not
easy
to
do
a
comprehensive
and
easily
digestible
getting
started
guide
for
bisque.
A
You
know:
we've
had
walls
of
text
in
the
past,
we've
been
incrementally
getting
better
and
better
better
this,
and
this
is
now
the
you
know,
the
current
apex
of
how
we
want
to
introduce
people
to
it
so
check
it
out.
You'll
notice
that
that
resource
on
the
main
site
links
into
the
wiki
in
a
number
of
places.
A
Please
share
it,
I
tweet
about
this,
whatever
okay
and
so
project
management,
which
I've
already
mentioned
a
number
of
times,
I
just
want
to
reiterate:
why
does
this
exist
right
so
want
to
have
mechanisms
in
place,
structures
in
place
that
help
us
make
sure
ensure
that
we're
working
on?
What's
most
important?
We
actually
finish
what
we
start,
that
we
stay
within
the
budgets
that
we've
established
or
adjust
them
as
necessary
and
we're
not
spreading
ourselves
too.
A
It's
really
key
that
we
don't
do
too
many
things
at
once,
thereby
not
doing
things
with
enough
quality
or
not
finishing
things
or
what-have-you.
So,
project
management,
kind
of
infrastructure-
that's
in
place,
is
part
of
that
part
of
ensuring
that
there's
the
master
projects
board,
which
you've
seen
now
you're
seeing
it
without
any
filters
on
it.
A
You
can
see
all
those
goals
right,
you
can
see,
there's
actually
an
improved
security
goal,
so
I
just
added
that
today
I
closed
the
improve,
supports
goal
and
replaced
it
with
this
one-
and
you
know
what
are
the
different
projects
that
are
currently
in
flight
like
rolling
out
the
Bisquick
II
we're
just
wrapping
that
up
right
now.
What
have
we
done?
What's
kind
of
in
the
backlog?
You
know
here
some
the
new
newer
projects
that
haven't
yet
been
triage,
just
to
make
sure
that
they're,
actually
projects
that
make
sense
or
a
lot
fulham.
A
Don't
have
you
so
there's
a
whole
process
that
and
that
process
is
documented
in
the
wiki
all
right.
So
if
you
haven't
checked
that
out-
and
this
is
something
that
might
pertain
to
you-
you
know
give
it
a
look.
This
is
certainly
part
of
how
what
we
do
in
this
can
be
influenced
right
and
then
another
big
piece
of
this
I
think
is
going
to
be
the
upcoming
dev
calls
which
we'll
get
to
in
just
a
moment.
A
So
this
is
an
in-flight
effort.
Right
proposal
has
just
been
created
for
it,
so
nothing
is
totally
concrete
yet,
but
I
just
wanted
to
give
a
in
the
moment
kind
of
update
here.
I
think
this
is
pretty
exciting
and
really
pretty
necessary
that
we
do
it
in
order
to
kind
of
achieve
what
are
our
highest.
You
know
kind
of
capabilities
as
a
team.
We
actually
need
to
do
calls
like
this
done
them
in
the
past.
A
I've
done
them
in
different
ways
in
the
past,
and
so
one
thing
about
this
dev
call
as
something
different
right
and
probably
do
a
weekly
cadence
again
still
thinking
about
that.
But
I
start
with
a
weekly
cadence.
So
imagine
a
weekly
one-hour
call
everybody's
welcome
anybody
can
join,
but
certainly
the
people
who
would
join
on
a
regular
basis
are
the
people
who
are
actively
working
in
a
development
capacity
with
disk
right,
so
team
lead.
You
know
Christophe
will
be
there
and
everybody
who's.
A
You
know
got
an
active
task
or
active
project,
or
is
somebody
who
just
wakes
up
every
day
and
works
on
bisque
would
attend
that
call
right
and
the
goal
again.
I,
don't
wanna,
say
anything
too
concrete
right
because
we're
still
working
it
out
and
you
can
help
work
this
out
by
attending
the
first
calls,
but
I
think
what
we
want
to
do.
A
A
We
need
to
execute
that,
so
that's
like
gonna
be
right
at
the
top
of
the
list
or
near
it,
and
then
there's
everything
that
comes
next
and
there's
gonna,
be
you
know
some
discussions
to
be
had
and
so
on
about
what
that
priority
order
should
be,
but
when
we
have
that,
then
it's
about
taking
ownership
of
it
right,
assigning
people
to
those
issues
recruiting
the
participation
of
people
who
are
gonna
help
with
those
issues
right.
So
maybe
you
know
developer.
X
is
gonna
own.
This
task,
but
they're
gonna
need
help
in
reviewing
it
right.
A
They're
gonna
need
testing
it.
They're
gonna
maybe
need
help
just
having
a
pair
to
program
with
it
right
and
go
back
and
forth
on
exactly
how
to
implement
it,
how
to
design
it
etc.
So
I
think
these
calls,
and
you
know
some
work
will
get
done
offline,
but
the
work
to
be
done
on
those
calls
is
like
actually
committing
to
things
for
prioritizing
committing
to
work
and
really
getting
that
kind
of
thumbs.
Up
from
other
people
like
hey,
I'll
help.
You
review
that,
like
I'll,
make
a
commitment
to
take
the
time
to
do
that.
A
You
know,
and
it's
gonna
show
up
real
quick
as
a
problem
if
somebody
commits
to
review
ten
things
because
they
nobody
has
that
kind
of
time
and
they
have
their
own
work
to
do
right.
So
we
want
to
create
this
kind
of
situation
where
people
are
committing
we're
holding
each
other
to
account
right,
hey.
You
know,
you
said
you
would
help
me
with
this.
Please
do,
and
this
is
getting
stalled,
whatever
I'm
blocked,
because
I
don't
have
any
reviewers
and
people
said
they
would.
A
You
know
like
that
kind
of
thing
where
we
can
really
start
moving
forward,
because
all
too
often
things
get
held
up
in
review,
there's
just
too
much
going
on
the
review
that
we
do
is
only
cursory
because
we're
too
busy
right.
All
these
things
are
the
default
state
like
just
chaos,
is
the
default
state.
So
we
have
to
work
really
hard
to
reverse
the
entropy
of
things
here:
okay,
an
ADD
order
to
the
system.
A
So
that's
that's
kind
of
the
thrust.
Right
is:
how
can
we
work
much
better
together
as
a
team
when
new
people
come
on
or
right
when,
like
promising
new
developers
show
up
misuk
hey?
How
can
I
help
I
think
we
want
to
get
into
a
situation
where
we
can
say,
hey,
join
the
call
right.
It's
just
a
few
days
away.
We
do
it
once
a
week
could
take
a
look
at
what's
going
on,
you'll
see
what's
going
on
is
most
important
and
you'll
hear
from
people
who
need
help
say
you'll
help
help
test.
A
How
helped
you
know,
write
tests,
help
do
manual,
testing
help
you
know
implement
whatever,
whatever
needs
to
be
done,
as
opposed
to
the
kind
of
default
state
that
we're
in
now,
which
is
like
well,
you
can
go
check
out
the
good
first
issues.
You
know
you
can
go
scratch
a
little
itch
over
here.
Here's
a
small
project
that
might
work:
it's
not
there's
not
room
for
that
stuff.
Of
course
there
is,
but
the
default
state
know
we're.
A
Asserting
here
is
maybe
better
that
we
really
take
people
into
the
fold
right
away
and
say
this
is
the
most
important
stuff,
and
in
doing
that,
we
help
chip
away
at
this
kind
of
shared
knowledge
problem.
We
have
like
people
start
to
really
understand
bisque
in
depth,
because
they're
working
on
the
most
important,
which
are
often
the
most
sticky,
most
difficult
issues,
and
if
that's
where
they're
starting
well,
that's
a
powerful
start
right,
they're,
not
just
making
a
cosmetic
change
or
what
have
you
again?
A
There
can
be
room
for
that,
but
we
have
to
design
it
in
the
developers
really
get
deeply
integrated
and
onboard
it
in
a
way
that
makes
a
difference.
It
really
matters
and
helps
them
feel
included.
It
helps
them
feel
valuable
right
because
it
actually
really
help
lend
valuable
deliverables.
So
that's
kind
of
the
whole
thrust
right
and
exactly
how
we
do
that
again.
A
It's
work
in
progress,
but
you
can
you
can
help
craft
that
right
just
by
attending
the
calls
and
giving
feedback
and
so
on
so
stay
tuned
proposal
is
out
there
and
you
know
yeah
I
think
that's
really
exciting.
Like
like
it's
been
mentioned
a
few
times,
you
have
a
new
security
team,
so
it's
just
it's
about
taking
risks.
You
know.
Security
has
always
been
important
to
bits
right
from
day
one
we
wouldn't
be
where
we
are
today.
A
If
we
didn't,
if
we
weren't
security
minded
just
like
we
weren't
privacy
minded,
this
could
have
failed
miserably
a
long
time
ago,
but
clearly
we
have
to
take
it
to
another
level
right.
We
cannot
let
things
like
happen
in
April
ever
happen
again.
We
have
to.
We
have
to
at
least
be
able
to
look
ourselves
in
the
mirror
and
say
we
did
everything
that
we
possibly
could
do
new
to
do.
You
know
to
prevent
that
right.
So
what
does
that
next
new
level
look
like?
A
Well,
that's
what's
being
expect
out
and
rolled
out
as
we
speak
under
the
auspices
of
this
new
team
right,
so
Florian
is
the
lead
there
and
you
know
if
you
have
ideas,
questions
about
this
etc.
Talk
to
him
question,
bring
it
up
anywhere
in
key
base,
but
you
know
stay
tuned
for
that,
because
that'll
be
an
important
part
of
what's
getting
prioritized
and
so
on
and
so
forth.
A
Okay,
and
just
a
couple
of
things
I
wanted
to
mention,
be
remiss
if
I
didn't
mention
if
you're
a
contributor
and
you're
issuing
a
compensation
request
today
is
actually
the
deadline
for
cycle
14.
So
probably
already
noticed
it
was
a
new
compensation
request
format.
It
allows
us
to
programmatically,
parse
and
Tahlia.
You
know
how
much
people
are
asking
for
and
according
to
which
team-
and
this
is
all
in
service
of
helping
us
actually
manage
this
budget.
So
it's
pretty
cool.
If
you
haven't
done
it
yet,
try
it
out
the
issue
Templars
there.
A
You
do
it
by
default
and
it's
just
a
tabular
format,
so
using
kind
of
markdown
tables
instead
of
a
free-form
prose
to
request
your
compensation.
Of
course,
this
will
be
a
trial
run
in
cycle
14
and
in
cycle
15.
If
it's
going
well
enough,
we'll
say:
okay,
it's
mandatory.
Everybody
needs
to
do
it
this
way
and
should
really
help
streamline
things,
update
on
segment,
support
and
bisque
right.
The
long
Most
Wanted
feature
by
many
we've.
A
We've
done
an
analysis
right,
Oscar,
wins
burg,
came
back
into
the
project
and
did
an
analysis
and
I
kind
of
write
up
a
plan
for
how
we
can
implement
seg
would
support
in
a
way
that
makes
sense.
So
that's
out
there
there
is
not
a
clear
you
know,
assignment
of
who's,
going
to
do
that
and
when
and
priority
and
so
on.
But
this
will
be
one
of
the
things
we're
going
to
talk
about
on
the
dev
calls
and
identify
people
to
do
that
from
so
on
and
so
forth.
A
But
it's
just
worth
mentioning
that
we've
been
making
some
progress
forward
on
seg
wit
and
I
wanted
to
mention
Bitcoin
2020.
Maybe
a
lot
of
people
know
that
that
was
gonna
happen.
It's
been
cancelled.
We
plan
to
have
a
big
presence
there
this
year
and,
of
course,
that
all
didn't
happen
because
of
Kovan
stuff.
There
are
still
you
so
while
I
think
details
aren't
fully
known
and
certainly
are
inflate.
Public
conversations
are
going
on
about
how
you
know.
A
Bitcoin
2020
or
whatever
its
equivalents
is
going
to
happen
when
it's
going
to
happen
where
it's
going
to
happen
so
on,
and
we're
certainly
involved
in
those
conversations,
and
we
certainly
plan
to
have
a
presence
at
whatever
that
is
whenever
it
happens,
just
FYI,
because
I
was
going
to
be
a
big
splash
for
us
this
year.
So
we're
looking
forward
to
it
and
the
final
thing
in
the
talk
tonight
is
an
update
on
my
status
I.
A
This
actually
is
my
last
day
in
my
last
act
with
the
project
I'm
going
to
step
away
from
disk
and
the
reason
for
that
I
think,
as
maybe
many
know
that
are
on
this
call.
I
just
had
a
heck
of
the
last
couple
of
years
with
my
health
and
while
I'm
happily
I'm,
doing
pretty
well
now
my
journey
there
is
not
at
all
finished
and
while
I'd
hoped,
when
I
came
back
to
the
project
after
being
away
because
those
health
issues
I
came
back
and
like
November
sort
of
last
year,
it's
been
about
six
months.
A
My
hope
was
okay.
You
know,
I
can
kind
of
balance
this
out
in
some
way
and
do
what
I
love
to
do
here
and
manage
all
the
other
new
things
that
I
need
to
manage
in
my
kind
of
new
life
after
my
health
issues
and
that
just
hasn't
been
working
and
what
I
really
need
to
do
in
the
final
analysis
is
intensely
focus
on
my
health
and
my
mobility
and
my
family
for
some
time
to
come
for
the
foreseeable
future
anyway,
and
I'm
excited
about
that.
A
You
might
notice
that
sort
of
internally
a
couple
of
weeks
ago
and
spent
that
time
just
checking
boxes
and
trying
to
hand
things
off.
For
example,
one
of
the
things
I
was
responsible
for
was
the
API
work
and
the
bisque
daemon
I'm
glad
to
say
that
I've
handed
that
off
to
to
G
hubs
dead
right,
maybe
know
his
handle
and
he's
been
working
with
demos
and
that
process
and
that
project
and
so
on.
That
will
evolve
right
and
that
becomes
that
becomes
theirs
now
so,
but
keep
an
eye
provide
feedback.
A
Try
things
out
right,
you
know
like
we
started
to
be
a
little
public
about
this
and
last
week
with
tweets
and
so
on.
I
wanna
start
getting
users
involved
when
it
makes
sense
that
that
I
think
is
just
some
of
the
most
exciting,
most
important
work
and
its
really
beyond
the
opportunity
of
that
work,
for
you
know,
increasing
liquidity
and,
just
you
know,
potentially
dramatically
growing
user
base
and
all
of
that
stuff.
It's
also
really
a
moment
for
us
to
get
right.
A
number
of
things
that
we
know
we've
been
needing
to
get
right.
A
You
know
like
every
endpoint
that
we
implement
in
that
API
if
you
think
about
it
in
a
kind
of
adversarial
way
right.
You
know
just
thinking
with
your
attacker
having
every
every
endpoint
we
open
up.
If
there's
a
bug,
if
there's
an
exploit,
if
there
is
a
security
issue
behind
that
functionality
within
that
functionally,
we
are
now
opening
a
programmatic
access
to
it
right.
So
there's
a
there's,
a
level
of
diligence
and
rigor
that
we
want
to
bring
to
this
project.
A
It's
both
just
demanded
in
order
to
do
it
well,
but
is
also
now
in
many
ways
for
the
first
time
possible
to
do
well
right,
what's
been
missing
for
so
long
and
disk
is
the
ability
to
do
automated,
end-to-end
integration
testing?
Why?
Because
bisque
was
built?
Is
it
that
desktop
UI
right,
so
everything
you
do
in
so
many
cases
you
do
manually,
you
click
buttons.
Well,
that
doesn't
work
for
automated
end-to-end
integration
testing,
but
every
endpoint
we
light
up,
gets
us
closer
to
being
able
to
do
that
in
an
automated
way
right.
A
So
we
can
really
build
the
kind
of
tests
and
testing
infrastructure.
The
bisque
is
always
needed
and
just
up
the
level
right.
So
you
know
more
power
to
everybody.
There
I'm
super
excited
I'll,
be
watching
that
one
and
go
team,
so
the
admin
team
so
of
the
team's
admin
obstetric
support
security
will
decommission
the
admin
team
for
now.
My
role
as
admin
team
lead,
which
is
really
kind
of
like
an
alias
for
you
know,
project
lead
for
bisque,
and
so
on
that
that
role
that
I've
been
playing.
A
It's
not
obvious
that
that
that
role
should
be
taken
over
at
all
right.
You
know
did
that,
especially
in
q1,
it's
kind
of
really
bootstrap
all
these
organizational
changes-
and
you
know,
have
a
sort
of
position
that
could
just
call
some
shots
and
say:
let's
try
this.
Let's
do
that!
Listen
that
much
of
that
work
has
been
done,
certainly
not
all
of
it.
It
would
maybe
be
nice
to
have
that
role
going
forward
in
some
ways,
but
it's
also
a
risk
right.
A
That
kind
of
you
know
centralization,
or
you
know,
sort
of
real
hierarchy
right
and
you
know
top
dog
or
CEO
kind
of
role.
That's
ultimately
antithetical
to
what
bisque
the
bisque
doll
wants
and
needs
to
be
right.
So
it's
also
maybe
a
good
time
to
decommission
that
and
say:
okay
now,
it's
about
the
you
know
more
distributed
set
of
team
leads
to
carry
some
of
those
things
forward.
A
Take
some
shared
responsibility
for
it
increasingly
pushing
down
that
responsibility
to
you
know
every
contributor
making
sure
that
you
know
people
are
handling
roles
well
and
so
on
and
see
if
we
can
get
that
stuff
done
without
an
admin
team
lead,
as
as
we
had
so
that's
the
status
of
that
anybody
who
is
under
the
admin
team,
like
just,
for
example,
compensation,
maintainer
roles,
maintainer,
etc.
They'll
have
their
compensation
requests
reviewed
by
other
by
other
team
leader
in
peer
review.
So
I
was
doing
those
reviews,
but
that
won't
happen
anymore.
A
Just
as
a
side
note
details
the
roles
that
I
play
I
have
about
six
different
roles.
You
know,
including
the
admin
team,
so
that
one
will
go
away,
but
some
routine
need
certain
of
those
roles
all
continue
to
play.
I've
bonded
into
them.
They
don't
have
an
obvious
replacement,
so
I'll
carry
things
like
owning
our
domain
name
or
DNS
admin.
Things
like
that
they're,
basically
totally
passive
roles,
very,
very
infrequently
needed.
You
know
for
action
to
be
taking
it
all.
I'll
continue
those
I'll
hand
them
off
more
slowly.
A
Somebody
else
will
bond
and
but
there's
sort
of
no
rush.
So
while
it's
my
last
day
of
general
availability-
and
you
know-
you
won't
see
me
around
the
key
base
actively
and
github
actively
and
so
on,
I'll
still
have
a
couple
of
threads
going
on
at
least
for
a
little
while
yeah
thanks
thanks
for
you,
know,
really
use
of
something.
That's
just
been
a
total
labor
of
love
for
me.
A
A
Yeah
also
thanks
for
my
site.
It's
there
was
very
essential
for
this
critical
time
and
yeah.
You
contributed
so
much
to
base
yeah.
It
will
never
be
forgotten
and
yeah,
even
if
it's
now,
for
a
longer
time
that
you
won't
be
here,
I
was
asked
yeah,
yes,
Never,
Say
Never.
Maybe
we
can
welcome
you
back
to
the
peace
family
at
some
point,
mm-hmm
thanks
for
them.