►
From YouTube: Bisq Q1 2020 Update
Description
A look back at 2019 and a look forward at 2020. Join us as we look back at the exceptional progress Bisq made in 2019, analyze where Bisq is now, and plan for its future.
This call is particularly important for current contributors, prospective contributors, and stakeholders—it details a number of key organizational changes (effective immediately) that affect day-to-day work, compensation, and priorities.
See the deck here:
https://docs.google.com/presentation/d/1xSV0EUrCaT7YaCsaolPzF1Hr68i0QMA7Yb2NqbQYTUQ/edit
A
So
welcome
everyone
to
this
call.
This
is
the
bisque
q1
2020
update,
called
it's
the
first
time.
We've
done
anything
like
this
in
quite
a
while
and
there's
a
lot
to
cover
a
lot
to
share,
so
I
want
to
jump
right
in,
but
first
I
want
to
get
a
sense
of
what
we're
gonna
cover.
So
we'll
look
at
2019
in
review.
What
happened
last
year?
Would
we
accomplished,
etc?
I
want
to
lay
out
bisques
mission
and
vision.
A
This
won't
be
anything
too
new.
We've
said
things
like
this
before,
but
I
think
it's
gonna
be
good
to
refresh
our
memory
about
that
and
take
a
moment
to
articulate
it
newly
opportunities
and
challenges
that
lay
before
us
goals
for
2020.
It's
the
most
important
part
right.
This
is
what
we're
gonna
focus
on
going
forward
and
some
organizational
changes
that
we're
making
effective
immediately.
A
So
this
call
is
primarily
intended
for
current
and
prospective
contributors
and
vsq
stakeholders,
but
you
know
we
opened
up
the
invitation
to
everybody,
because
I
think
a
lot
of
what
you
see
here
is
gonna
be
very
interesting
to
users
as
well
traders,
market
makers
etc.
So
really
it's
for
everybody,
and
my
intention
is
to
go
about
45
minutes
with
the
content
and
then
we'll
open
it
up
for
Q&A,
afterward,
okay,
so
2019.
A
What
did
we
do?
Well,
we
shipped
19
times
right.
If
you
look
at
how
many
release
tags
are
the
repository
we
shipped
19
times
so
one
and
a
half
bisque
releases
per
month
and
that's
an
up
stat
from
2018,
we
shipped
about
we
shipped
11
times
in
2018.
So
at
some
points
it
actually
becomes
too
many
releases
right
and
more
is
not
necessarily
better
year
but
with.
But
the
point
is
that
we
certainly
had
a
cadence
and
we
shipped
very
regularly
last
year,
so
down
loads.
A
A
So
we
had
a
hundred
and
five
unique
contributors
right,
I,
just
look
at
the
git
log
stats
and
that's
up
a
little
bit
from
last
year
from
92
we
merged
592
pull
requests,
which
was
a
considerable
up
stat
from
last
year
about
four
hundred
last
year
and
total
number
of
commits
just
to
get
a
gauge
of
things
right
about
2000.
We
also
did
a
little
over
2000
last
year,
so
very
similar,
and
what
did
we
actually
ship
features
etc?
Well,
we
launched
biscones
auto
major
milestone
right.
A
We've
been
live
in
production
since
2016
right
been
developing
since
2014
live
since
2016,
and
last
year
2019
we
shipped
one
dot.
Oh
because
we
shipped
the
bisque
down
right.
All
the
technical
infrastructure
of
the
Dow
has
been
live
since
April
of
last
year
running
running
pretty
smoothly
right.
This
whole
thing
actually
works,
the
SQ
works
and
has
had
a
really
pretty
impressive
run
for
it.
A
You
know
the
first,
however
many
months
of
its
life,
that
is
so
that's
huge
right
and
we
launched
a
new
trade
protocol
right,
significant
changes
to
the
trade
protocol,
where
we're
no
longer
two
of
three
multi-sig
with
a
with
an
arbitrator
holding
the
third
key,
which
is
which
introduces
some
centralization
centralization
risk.
We've
always
known
that
it's
always
been
a
bit
of
a
weakness
in
the
protocol
and
now
we've
eliminated
that
we're
in
two
of
two
of
multi-sig,
with
a
moderation
model
now
and
so
on
and
so
forth.
A
You
can
read
about
this
if
you're
not
familiar,
but
the
trade
protocol
got
even
more
secure.
We
simplified
and
reduced
trading
fees
right.
So
it
used
to
be
kind
of
complicated
to
estimate
what
you
were:
gonna
pay,
depending
on
how
much
of
a
premium
they
put
on
your
trades
in
the
distance,
from
market
price,
etc.
That's
been
reduced
and
simplified.
A
We
introduced
account
signing
as
yet
another
measure
against
potential
bank
account
scammers.
We
had
a
couple
of
incidents
last
year
and
we
responded
swiftly
and
promptly
and
really
innovated
here.
I
think
we
came
up
with
a
pretty
clever
solution
with
account,
signing
and
that's
been
rolled
out
and
continues
to
roll
out
as
new
users
come
in
and
get
their
account
signed
by
existing
users
with
signed
accounts
and
so
on
and
so
forth.
A
We
introduced
Raider
chat
alright,
so
you
can
now
track
chat
with
your
counterparty
in
a
trade
that
you've
taken
or
that
has
been
taken
at
any
time
right,
and
this,
of
course
reduces
the
need
to
go
to
mediation.
We
need
to
open
up
support
cases.
You
can
just
resolve
things
amongst
yourselves
in
many
cases
and
of
course,
the
most
important
feature
of
all
dark
mode.
A
Every
good
app
has
to
have
the
dark
red,
and
this
certainly
does
No,
and
you
know
we
had
new
highs
for
trading
volume
across
the
board
really
in
Fiat,
and
you
know
many
other
currency
Paris,
especially
Manero
right
people
who
have
been
around
this
can
spend
a
lot
of
time.
Paying
attention
to
the
project
know
the
20:19
was
absolutely
enormous
and
mineiro
trading.
A
We
introduced
instant
trading
right,
so
instant,
altcoin
trading,
which
essentially
narrows
down
the
trading
window
to
an
hour
right.
So
people
can
you
know
trade
much
more
quickly,
lots
and
lots
of
bug,
fixes
performance,
improvements,
etc.
And
you
know
this
isn't
a
feature
per
se
right.
But
something
really
important
to
note
is
that
if
you
go
back
a
couple
of
years,
even
to
sort
of
mid
2017,
there
was
a
whole
lot
of
the
Bitcoin
community.
A
You
know
serious
bitcoins
people
really
dedicated
to
the
space
just
didn't
know
what
this
was,
even
though
we've
been
working
on
it
for
years
and
it's
been
live
for.
You
know
more
than
a
year
at
that
time,
and
that
was
always
a
surprise
to
me
and
and
and
now
in
the
intervening
couple
of
years.
That's
really
changed
right.
A
If
you're
somebody
who
pays
attention
to
Bitcoin
odd
casts-
and
things
like
that-
you
know
that
this
gets
mentioned
very
very
frequently
and
there's
a
just
a
widespread
awareness
of
the
project
amongst
those
who
care
most
about
Bitcoin,
so
I.
You
know:
we've
checked
that
box
in
a
way.
That's
never
really
done,
but
you
know
we're
on
the
right
side
of
that
situation.
Now
so
certainly
worth
noting.
Okay,
some
trading
stats
right.
We
did
91
percent,
more
total
trades
in
2019
and
2018.
A
So
a
pretty
big
up
stat,
we
did
2.6
times
the
total
Bitcoin
volume
right.
So
Bitcoin
is
always
the
base
face
currency
in
every
trade.
So
we
often
de
nominate
statistics
like
this
in
BTC,
so
we
did
nearly
14,000
BTC
worth
of
trading
last
year
up
from
about
5,000
in
2018
and
then,
if
you
adjust
all
of
those
Bitcoin
trades
to
USD
at
the
market
price,
the
time
the
trade
was
taken,
we
did
four
times
the
USD
adjusted
volume,
so
116
million
in
2019
versus
just
30
million
in
2018.
So
really
you
know
enormous.
A
You
know
difference
not
too
bad
right,
pretty
pretty
good
2019,
but
I
want
us
to
zoom
out
and
you
know
think
about
what
are
we?
What
are
we
really
doing?
And
what
is
this
all
about
and
I'm
gonna
talk
about
bisques
mission.
You
know
in
a
way
this
I
think
this
goes
without
saying,
because
I
think
the
people
who
have
shown
up
to
this
project
historically
especially
contributors
and
many
many
users
they
show
up
at
this
because
they
are
aligned
with
this
mission
right.
A
We
use
peer-to-peer
technology
to
match
buyers
and
sellers
without
any
central
authority,
servers
or
databases.
Our
audiences
individuals
around
the
world
who
wish
to
claim
and
preserve
their
right
to
financial
freedom
and
privacy
and
bisque
is
the
exchange
network
that
Bitcoin,
in
its
growing
user
base,
needs
to
realize
a
future
of
individual
financial
autonomy.
A
I'd
like
to
hear
your
feedback
about
that
mission,
if
you
have
any,
if
it
already
hits
the
sweet
spot,
great
we're,
aligned
and
vision,
Ryan,
what's
a
difference
between
mission
vision,
vision
is
kind
of
the
you
know.
Mission
is
what
we're
building,
who
we're
building
it
for
why
we're
building
it?
Why
it's
valuable
the
vision
articulation
is
like
what
really
motivates
us
in
the
morning
right
like
what
are
we
achieving
accomplishing?
A
What
are
we
doing
for
ourselves
in
a
way
really
as
the
contributors
who
are
building
this,
who
make
up
the
bisque
Bao
and
so
on,
so
one
to
become
the
widely
accepted
exchange
layer
of
the
Bitcoin
protocol
stack?
Now,
that's
not
something
that
we've
talked
a
whole
lot
about
in
public.
If
you
hang
around
me
long
enough,
you've
heard
me
talk
about
it
right.
I
think
this
is
a
real
opportunity
for
us.
If
you
look
at
the
emerging,
Bitcoin
protocol
stack
right,
obviously
bitcoins
the
core.
A
You
know
first
layer
right,
lightning,
showing
up
is
the
second
layer
for
fast,
cheap
transactions
prior
to
transactions,
etc.
There's
a
kind
of
bisque
shaped
hole
in
that
stack,
which
is
how
do
you
get
into
that
stack
right?
The
Bitcoin
protocol
stack
really
needs
an
exchange
layer
and
right
now,
bisque
provides
that
in
a
way
right,
but
it
provides
it
as
a
as
a
particular
application,
with
a
p2p
network
and
I
think
there's
a
real
opportunity
to
evolve
bisque
toward
becoming
a
first-class
protocol.
A
That
has
lots
of
implications,
don't
get
into
it
in
detail
here,
but
I
want
to
lay
that
out,
as
part
of
it's
part,
of
the
vision,
too,
is
to
be
among
the
world's
first
successful
decentralized
autonomous
organizations.
Now
we
already
are
one:
we
really
do
function
as
a
doubt.
You
know
if
you
go
look
up
the
Wikipedia
definition.
We
need
it
right
now.
A
Are
we
successful
by
some
measures,
but
we
can
be
a
lot
more
successful
for
sure
I
wouldn't
say:
we've
exactly
proven
ourselves
just
yet
three
to
do
great
work,
building
privacy,
protecting
free
and
open
source
software
that
the
world
needs.
This
definitely
motivates
me
every
morning
right
to
be
accountable
to
our
users
and
our
stakeholders
alone
and
to
see
our
contributors
and
stakeholders
flourish
and
prosper.
Those
are
all
things
you
know
this
whole
vision.
A
It's
really
something
that,
for
me,
it
makes
sense
that
I'm
spending
my
time
on
this,
and
if
it's
the
same
for
you
too
then
great.
Let's
keep
going.
We've
got
work
to
do
right
to
realize
fully
that
mission
and
vision,
there's
much
to
be
done
and
that's
what
the
rest
of
this
deck
is
going
to
be
about
right,
so
opportunities
right.
What
lies
before
us?
What
can
we
do?
Well,
this
space
right,
the
privacy
protecting
p2p,
decentralized,
distributed
Fiat
exchange,
space
right,
I,
say
Fiat
there,
because
that's
really
the
heart
and
soul
of
this.
A
Yes,
we
do
altcoin
trading
and
you
know
maybe
we
have
a
particular
focus
on
privacy
coins.
Maybe
in
the
future
we
have
a
bit
of
a
focus
on
stable
coins,
but
it's
really
about
providing
a
bridge
to
the
fiat
world
right
on
and
off-ramps
from
the
fiat
world,
their
safe
and
private,
for
people
that
space
is
wide
opened.
We
are
almost
the
only
player
there
right.
A
There
is
a
counted
on
one
hand
or
less
number
of
players
that
are
even
trying
to
do
anything
like
what
we're
doing-
and
you
know
people
are
beginning
to
know
and
I
think
we
can
really
grow
this
pie.
We
can
attract
massive
new
liquidity
with
the
API
that
we're
building
out.
This
is
key
and
the
goals
that
we're
coming
up
to
we
can
reach
more
users
by
building
light
mobile
clients.
The
a
guy
is
going
to
be
critical
to
being
able
to
do
that
as
well.
A
We
can
expand
to
non-custodial
trading
on
lightning
right,
there's
so
much
we
can
do
like
I
said
we
can
evolve
toward
becoming
a
first-class
exchange
protocol.
We
can
become
the
exchange
layer
of
the
Bitcoin
protocol
stack.
All
of
these
things
are
possible,
but
we've
got
challenges
over
hey.
We
have
some
things
we
need
to
work
out
in
order
to
be
able
to
achieve
those
kinds
of
things.
We
have
very,
very
constrained
def
capacity.
We
really
just
have
a
few
core
developers
who
are
capable
inside
the
code
base
of
getting
done.
A
A
Poor
liquidity
right
I
want
a
number
one
things.
People
say
when
they
try
out.
Bisque
is
where's
the
liquidity
where's,
the
liquidity.
Well,
of
course,
right.
It's
very
important,
plus
a
difficult
onboarding
experience.
Another
key
feedback
that
we
get
from
people
biscuits
too
complicated
too
hard
to
use.
I
can't
figure
it
out.
A
Right
means
a
lot
of
would-be
new
users
don't
and
abstain,
and
I
would
say
we
have
a
hit-and-miss
user
support
experience
very
often
it's
very
good
right
in
very
often,
or
often
at
least
we
hear
from
users
saying
they
can't
get
a
hold
of
somebody
or
they
didn't
get
response.
Or
what
have
you
right
throughout
the
history
of
the
project?
You
know
man
for
the
creator
of
bisque,
and
you
know
my
original
co-founder
always
was
quick
to
say
you
know
we
don't
have
a
professional
support,
we're
not
a
company.
A
We
don't
have
professional
support,
don't
expect
it
right
in
the
early
days
that
was
totally
appropriate
to
give
that
disclaimer.
You
know
it
was
the
best
effort
thing
right.
We
did
the
best
that
we
could
now
that
changes
right.
The
stage
that
we're
at
the
phase
of
the
project
is
in.
We
really
do
need
to
provide
professional,
kick-ass
user
support,
experience
right
so
more
to
come
on
that
and
reliability
issues
right.
A
This
cat
has
some
bugs
and
it
lands
people
and
support
too
often,
not
very
often,
but
often
enough
that
you
know
we
really
need
to
focus
on
this
and
squash.
Those
and
I
would
say
insufficient
management
right.
Really,
almost
no
management
has
meant
the
too
often
we
failed
to
do
what
is
most
essential
and
that's
an
artifact
of
you
know.
When
we
launched
the
Dow,
we
really
went
for
it
right.
We
said
okay,
but
this
is
a
totally
decentralized,
fairly
defined
all
of
the
roles
and
so
on.
A
All
of
the
infrastructure
of
the
Dow
we've
now
self-managed
right
and
we
tried
that
we
gave
that
a
real
try
over
the
last
many
months
since
the
Dow
launched
and
now
is
it's
time
to
call
the
shot
and
say:
okay,
good,
try
not
sufficient
all
right.
We
need
to
do
something
different
now,
so
we're
going
to
introduce
some
practical
management
and
administration
to
the
project
they
can
ensure
that
we
get
the
right
things
done.
A
These
are
user
feedback
now
mentions
you
know
we
give
a
survey
to
people
every
time
they
complete
trade
with
with
bisque
first
time
they
complete
a
trade
of
bisque
grass
and
I
think
if
they
want
to
fill
out
a
feedback
form
at-
and
this
is
some
of
the
common
mentions
in
what
people
bring
up
in
that
forum
right.
So
you
see
the
usual
suspects
right.
If
you
know,
bisque
people
want
a
mobile
app
right.
People
want
segment
support
liquidity,
liquidity,
liquidity,
user
experience,
user
experience,
user
experience.
These
are
huge
things.
A
So
when
we
talk
about
these
in
the
upcoming
goals
right,
this
is
really
based
on.
You
know
staying
in
touch
with
the
real
world
right,
we're
not
just
guessing
about
the
stuff.
We
do
actually
have
a
strong
sense
of
what
people
want
to
do
so
to
succeed
in
all
of
this,
we
have
to
take
on
both
these
opportunities
and
the
challenges.
At
the
same
time,
they
can't
just
stop
everything
and
try
to
fix
the
problems,
and
we
can't
ignore
the
problems
and
go
try.
You
know
for
the
moon
right.
A
We
have
to
do
the
most
important
of
these
things
at
the
same
time,
and
we
can
do
it
with
the
goals
and
the
changes
that
we're
making
that
fallen.
So
what
are
those
goals
for
2020,
simple,
increase
liquidity,
improve
the
support,
experience,
improve
bisques
reliability
and
improve
the
onboarding
experience,
so
I
want
to
walk
through
each
one
of
these
and
talk
briefly
about
okay.
What
are
we
going
to
do?
How
are
we
going
to
do
it
right?
This
is
the
strategic
goal:
increased
liquidity,
the
most
important
thing
ever:
okay
yeah.
A
But
how
are
we
actually
going
to
do
it?
What
are
the
tactics
and
then?
How
are
we
going
to
know
that
we
did
it?
How
are
we
going
to
measure
that
what
are
the
metrics,
so,
let's,
let's
cruise
through
each
one
of
those
at
a
high
level,
so
increasing
liquidity?
How
do
we
do
it?
Well,
one
is
that
we
need
to
focus
on
our
key
markets.
A
We
know
what
our
key
markets
are:
its
USD,
its
euro,
its
Manero,
a
lot
of
Zee
cash
trading
as
well
right,
but
let's
say
for
the
moment
these
three
and
we
really
nail
them
down.
No,
it's
not
that
there's
no
liquidity
here,
you
know
at
any
given
time
you
see
3040
offers
in
each
one
of
those
markets,
but
you
know
like
in
the
narrow,
it's
very
often
very
large
offers
no
small
offers
right
in
the
dusty
and
your
markets
same
thing.
A
There's
a
whole
lot
of
you
know:
kind
of
70
hundred
euro
dollar
offers,
but
not
necessarily
a
whole
lot
of
you
know
depth
right
if
you
really
want
to
go,
buy
a
bunch
of
bitcoin
worth
of
euros.
So
so
so
we
want
to
do
the
right
things
by
market
makers
right,
like
we're,
gonna,
attract
market
makers
to
help
build
out
the
right
kind
of
liquidity.
The
right
balance
and
liquidity
in
those
markets
and
like
I,
mentioned
before
absolutely
crucial
to
this,
we
think,
is
shipping
what
we
call
the
bisque
demon,
an
API.
A
A
Essentially
it's
a
headless
bisque
that
you
can
run
conveniently
in
any
environment
right
so
on
a
VPS
or
on
a
Raspberry
Pi
sitting
on
your
bedroom
shelf
or
what
have
you
know,
desktop
UI
bits
in
there
which
make
it
much
more
difficult
and
a
bit
more
heavyweight
to
run
in
certain
environments
right,
so
a
headless
bisque
that
can
run
anywhere
in
an
API
that
you
can
access
it
programmatically
with
right
that
you
can
script,
that
you
can
write
trading
BOTS
right.
The
technical
market
makers
can
come
along
and
automate
what
they
run
do
with
disk.
A
Today,
it's
all
clickety-click
in
the
UI
and
that
just
doesn't
scale
right
there.
There
are
better
ways
for
market
makers
to
go,
make
money
than
having
to
come
back
to
the
disc
UI
over
know
it
over
again.
So
we
think
the
API
is
absolutely
enormous
to
enable
in
this
and
at
the
same
time
right
it's
not
just
enough
to
shut
the
technical
bits.
A
We
really
have
to
do
the
footwork
in
the
community
growth
efforts,
liquidity,
bounties,
getting
out
there
and
really
connecting
with
market
makers
right
we're
pretty
good
at
connecting
with
bitcoiners
who
want
the
right
kind
of
privacy
solutions
for
exchanging
right.
That's
you
know,
that's
who
I
am
right,
so
I'm
pretty
good
at
finding
and
talking
to
them
and
understanding
and
building
something
for
them,
but
we
now
need
to
go
talk
to
these
other
audiences,
especially
marketers.
A
So
how
do
we
know
that
we're
going
to
do
that?
This
is
a
very
abbreviated
provisional
list
of
these
metrics,
it's
just
just
high-level
here,
so
we
want
to
measure
what
matters
to
users
essentially
right.
So,
whether
you're,
you
know
a
casual
user
who
just
wants
to
exchange
some
Bitcoin
for
some
euros
to
pay
bills
or
you're.
A
market
maker
who
wants
to
you
know
really
interact
with
bisque
to
make
a
profit
right.
What
do
users
care
about?
A
A
Gonna
pay,
one
percent
more
than
market
price,
am
I
gonna
end
up
paying
ten
percent
more
right,
so
that
cost
really
matters,
and
we
want
to
measure
that
the
better
the
liquidity,
the
lower,
that
cost
should
come
down
approaching
the
market
price
right
number
of
trades
that
are
required
to
take,
say
one
Bitcoin
worth
of
offers.
Well,
it's
gonna
be
at
least
for
right
now,
because
we
have
a
cap
on
fiat
trades,
at
least
a
1/4
of
a
Bitcoin.
A
A
Right
and
you
know
total
volume,
numbers
and
so
on,
but
we're
going
to
rigorously
track
this
and
publish
this
and
really
manage
to
this,
which
is
something
that
we've
always
had
certain
numbers
like
this
in
mind,
but
we
haven't
really
managed
what
we're
doing
to
those
numbers
we're
going
to
begin.
Okay.
So
that's
liquidity
in
a
nutshell,
improve
the
support
experience.
So
you
know
the
rationale
is
clear:
yeah
stuff
happens,
people
end
up
in
support.
That's
not
gonna
change.
It's
always
gonna,
be
some
new
bug.
There's
always
gonna
be
human
error.
A
That's
why
we
have
support
and
the
thing
is
you
know,
and
everybody
knows
it's
right,
like
a
company,
an
organization
can
can
screw
up
pretty
badly.
But
if
you
have
a
great
support
experience,
you
probably
stick
around
this
user.
If
you
don't
probably
go
on
right,
so
you
know,
organizations
live
and
die
on
the
quality
of
their
support
and
we
want
to
really
acknowledge
and
respect
that.
So
it's
time
to
professionalize,
right
and,
like
I,
said,
build
a
reputation
for
bisque
that
we
have
kick-ass
user
support
right.
A
People
know
that,
no
matter
what
happens
they
come
they're
gonna
get
taken
care
of.
So
how
do
we
do
that?
Well,
a
couple
of
quick
things
on
the
tactics
front
again,
very
simple:
the
things
that
kind
of
any
organization
would
do
right.
We
formalized
a
level
one
level
to
support
and
escalation
process.
We
already
have
level
one
we're
talking
about
a
term,
but
now
we
call
it
that
term.
That's
all
the
support
agents
that
we
already
have
right
just
doing
the
work
every
day
of
being
in
the
support.
A
You
know
ideally
every
day
of
the
week
right,
we'll
get
what
coverage
we
can
and
we'll
expand
as
we
have
more
developers,
but
we
want
to
give
support
agents
the
Lifeline
that
they
need
right.
They
know
who
to
go
to.
They
know
who's
responsible.
It's
not
a
it's,
not
a
crapshoot
right.
It's
not
haphazard,
and
you
know
to
support
that.
A
Will
you
know,
build
out
simple
coverage
calendars
and
just
additional
probably
Google
calendars
like
we
already
have
for
biscuits,
and
you
know,
support
agents
will
register
themselves
when,
when
they're
available
and
so
on,
I
talk
to
most
of
the
people
doing
support.
Everybody
is
aligned
with
this.
So
far,
so
you
know,
will
we
plan
to
roll
this
out
just
essentially
immediately
just
as
quickly
as
possible
and
begin
improving
us
right
away?
So
the
second
thing
that
we
know
we're
going
to
do
is
introduce
a
knowledge
base.
This
is
actually
already
an
inflight
project.
A
Essentially
just
you
know,
it'll
be
a
wiki.
It's
gonna
be
placed
where
you
can
go
quickly
as
a
support
agent
to
write
down
known
answers
to
you
know
known
problems
and
things
like
that,
and
it
also
gives
users
the
chance
to
self-serve.
Maybe
they
don't
even
need
to
talk
to
a
support,
efficient,
write
and
just
search
the
lake
and
the
feel
of
this,
but
we
know
where
we
want
this
to
go
as
it
begins
to
feel
something
like
the
Bitcoin
wiki.
A
Actually,
we
may
expand
that
wiki
beyond
a
knowledge
base
and
really
make
it
the
bisque
wiki.
It's
you
know,
has
more
than
just
kind
of
support
articles
knowledge,
base
kind
of
stuff,
but
the
the
template
there
is
the
Bitcoin
wiki
which
I
think
in
but
he's
familiar
with
knows
it's
quite
a
valuable
resource
and
I'm
gonna
have
the
same
kind
of
thing.
You
know
we'll
figure
out
the
relationship
between
our
existing
Docs
and
website
in
the
wiki
and
soul
and
we'll
make
sure
all
that
makes
sense.
A
But
you
know
we're
building
that
out
now
and
what
are
we
gonna
measure?
Well
again,
what
do
users
care
about?
How
long
does
it
take
me
to
get
response?
So
somebody
shows
up
in
key
base
and
says
help:
does
it
take
an
hour
or
doesn't
take
a
day,
all
right
and
we'll
measure
that
and
get
the
number
just
as
low
as
we
can,
of
course,
and
of
course
time
to
resolution?
A
So
yeah
got
a
first
response
now,
how
longs
it
take
to
actually
close
the
issue
and
that's
gonna
vary
widely
depending
on
the
problem,
but
it
will
figure
out
a
way
to
measure
it
that
makes
sense
and
reliability
right.
So
I
just
wanted
to
find
a
couple
of
things
here.
Just
turn
phrase
I'm
using
core
use
case
right.
This
is
anything
that
a
user
needs
to
do
in
bisque
to
successfully
trade
or
manage
their
funds,
like
you
know,
send
Bitcoin
to
get
Bitcoin
power
through
best
quality,
etc.
A
So
there
are
lots
and
lots
of
features
and
bells
and
whistles
in
bisque,
but
these
core
use
cases
that
have
to
do
with
managing
money
and
actually
successfully
trading.
That's
what
I
mean
I
say
this
and
I
define
that,
because
I
want
to
now
define
what
I'm
calling
a
critical
buck,
which
is
any
issue
that
prevents
you
as
a
user.
From
completing
court
use
case
right,
so
you
can't
get
a
trade
done
because
of
this
issue.
A
This
bug
this
problem
or
it
repeatedly
lands
users
and
support
and
or
it
puts
user
funds
of
privacy
at
risk.
So
what
we
want
to
do-
and
you
know
there
are
just
a
number
of
outstanding
bugs
like
this-
that
are
really
sticky-
really
tricky
hard
to
solve
problems.
Others
are
not
as
hard
they're
newer
right,
but
in
any
case
we
want
to
now
prominently
track.
That's
right!
You
know
like
picture
the
days
since
last
incident,
sign
that
you
see
in
a
factory
or
a
plant.
A
Like
I
mentioned,
we
put
Deb's
in
L
to
support,
so
we've
got
skin
in
the
game
right,
nothing's
more
irritating
to
a
developer
than
having
to
solve
the
same
problem
twice
right.
So
you
know
we
want
to
automate,
want
to
fix
things
and
by
forcing
ourselves
to
really
be
there
every
time
I
don't
think
only
things
are
gonna
get
fixed,
okay,
so
and
how
we
know
that
we
do
that
will
will
measure
things
like
how
many
critical
bug
incidents
happened
in
this
dau
cycle
right
yeah,
the
roughly
monthly
cycle
based
on
Bitcoin
blocks
right.
A
How
many
bug
instance
incidents
happen?
Essentially
this
month
and
critical
bug
incidents
portrayed
right,
so
a
kind
of
ratio
did
we
have
a
thousand
trades?
You
know
this
this
this
week
or
this
month
or
what-have-you,
and
were
there
three
critical
bugs
or
did
we
have?
You
know
a
thousand
trades
and
we
had
30.
You
know
something
like
that.
So
the
ratio
matters
because,
of
course
of
trades
differs
from
cycle
cycle.
A
Okay
and
the
onboarding
experience
right.
This
critical
user
experience
moment
that
the
first
my
journey
to
first
trade
with
bisque
experience
right.
What
is
that
like?
Well
right
now,
people
just
have
to
figure
it
out
right.
They
kind
of
open
up,
bisque
and
they're
presented
with
this
really
capable
looking
UI
that
looks
like
over
their
head
in
many
cases
right
and
it
ends
up
turning
people
away.
They
have
to
figure
out
how
to
set
up
trading
accounts
from
security
deposits
and
a
number
of
other
things.
A
That's
me,
and
just
not
trivial
right
for
even
for
an
experienced
Bitcoin.
It's
not
this
for
the
trivial
and
we
have
docs
on
this.
The
docs
aren't
enough
right.
That's
not
what
users
expect
these
days
to
need
to
go
the
manual
it's
important
to
have
the
docs,
but
they're
not
they're
necessary,
but
not
sufficient
right.
A
So
we
know
we
have
the
feedback.
It's
obvious
and
users
deserve
a
first-class
onboarding
experience
on
par
with
you
know
any
modern
desktop
or
mobile
application,
and
the
good
news
is
our
amazing
designer
Pedro
has
already
designed
all
of
this.
For
us.
He
has
this
knack
of
just
dropping
incredibly
great
design,
work
at
our
feeds
and
saying
go
for
it
right.
It's
you
know
just
brilliant,
so
Pedro.
If
you're
listening,
we
love
you
and
it's.
What
you're
about
to
see
is
a
part
of
a
larger
redesign
of
the
whole
desktop
UI.
A
Now,
in
practice,
we're
probably
going
to
separate
this
out,
probably
not
going
to
do
the
whole
redesign
and
the
onboarding.
At
the
same
time,
we're
probably
going
to
do
the
onboarding
flow
in
the
current
design,
which
is
also
Pedro's
work,
not
too
bad
and
and
then
we'll
do
the
full
redesign
later
right.
Just
in
the
name
of
you
know
getting
things
done
and
being
incremental
about
it.
So
you
know
we
need
to
implement.
We
need
to
prioritize
that
and
I
just
want
to
show
you
a
little
bit
about
what
it
looks
like
right.
A
So
you
can
imagine
very
first
user
opening
this
for
the
first
time
if
they
get
presented
with
something
like
this
right,
you
know
kind
of
the
kind
of
wizard
kind
of
onboarding
flow
that
you're
very
used
to
as
a
modern
user.
So
you
know
they're
gonna,
walk
through
step,
1,
step,
2,
step
3,
you
know
making
sure
they
set
up
their
seed
phrases
etc.
Creating
a
trading
account
right,
so
you
know
going
through
and
setting
up
your
payment
methods,
for
you
know
USD
trading
or
what-have-you.
A
Whatever
all
coins
are
on
trade
and
so
forth,
right
they
succeed
through
all
that
and
they
say:
ok
right,
you
ready
to
trade.
What
do
you
want
to
do
and
then
you're
presented
right
with
the
more
general
kind
of
UI
where
you
can
go
and
go
through
these
different
use?
Cases
create
an
offer,
find
good,
claim,
etcetera,
etcetera.
So
how
are
we
gonna
know
that
that's
effective,
we're
gonna
measure
up
well
new
offers
per
active,
node
right.
A
A
Ok,
so
these
are
these:
are
the
goals
right
and
there's
a
kind
of
theme
here
over
all
right,
the
2020
least,
the
first
part
of
it
needs
to
be
about
growth
needs
to
be
about
us,
focusing
focusing
identifying
the
right
stuff
and
getting
it
done
right,
focusing
and
executing
like
we
have
like
we
haven't
done
before.
I
need
to
up
our
game
in
that,
and
really
it's
about
nailing
the
fundamentals
right.
You
know
we're
this
works
right,
you
know,
and
and
and
it
has
users
and
but
we
need
to
nail
down
the
core
stuff
right.
A
There
really
does
need
to
be
sufficient
liquidity
for
people
when
they
show
up
to
actually
get
through
the
trade
or
trades
that
they
want
to
it
needs
it.
If
we're
not
getting
that
right,
we're
doing
it
wrong
all
right,
so
nail
down
the
fundamentals
and
from
that
base
right.
If
we
can
build
that
solid
foundation,
then
we
can
go
achieve
these
big
opportunities
right
and
we
can
have
much
bigger,
much
more
ambitious
goals,
but
this
you
know
we
need
to
start
here.
So
those
are
the
goals
right.
A
What
are
the
changes
that
we're
rolling
out
right
now
so
think
organizational
changes,
starting
now
we're
in
the
middle
of
Dow
cycle
10
or
toward
the
beginning
of
down
cycle
10.
So
these
things
are
going
to
take
effect
now,
but
they're
gonna
take
some
time
to
roll
out
completely
right.
So
let
me
tell
you
what
they
are.
So
the
first
thing
is:
teams
we've
been
a
totally
flat
organization,
particularly
since
we
launched
the
Dow,
and
now
we
want
to
introduce
a
bit
of
hierarchy
right,
just
enough
management.
A
A
So
you
know
managing
the
overall
budget,
etc.
Dev,
pretty
obvious.
That's
everything
from
development,
self
testing
bug
fixes
shipping
releases
exactly
what
you
would
expect
growth
team
has
been
around,
for
there
has
sort
of
been
a
growth
team
for
a
long
time
in
this,
but
now
we're
kind
of
formalizing,
running
the
website,
etc.
All
all
this
sort
of
liquidity
efforts,
events
that
we
put
on,
etc
and
ops
right,
so
keeping
all
of
the
biskits
works,
critical
infrastructure
running
now.
There's
a
number
of
operators
out
there
right
people
who
play
operators
roles
inside
of
the
Dow.
A
Are
you
know,
seed
node
operators,
price
node
operators,
people
have
control
over
our
different.
You
know
domain
names
and
DNS.
All
that
stuff
is
broken
out
in
roles.
So
it's
very
much
decentralized,
like
a
large
number
of
people
have
control
individually
over
these
different
pieces
in
parts.
So
we're
not
centralizing
that
stuff
but
we're,
but
we're
introducing
some
oversight
of
it
right
so
that
we
can
coordinate
those
players
a
little
bit
better,
we're
not
like
even
housing.
You
know
into
our
own
data
center
or
something
like
that.
All
of
our
operations,
not
at
all.
A
Okay
in
support
right,
which
we've
just
talked
a
lot
of
that-
so
that's
you
know
basically,
everybody
who's,
helping
users,
support
agents
right.
You
know,
try
primarily
working
in
key
base,
support,
channel
mediators
that
are
working
in
app.
Our
refund
agent
for
people
who
end
up
in
refund
cases
and
documentation
as
well,
especially
as
we
start
building
up
the
knowledge
base
that
that
kind
of
documentation
what
users
go
to
to
solve
problems,
and
so
on.
A
So
you
can
see
all
of
this
reflected
in
github
in
our
github
organization,
with
this
network
organization
is
now
broken
down
in
terms
of
these
teams,
and
there
are
sub
teams
right
for
all
different,
for
example,
operator
roles
and
so
on.
But
this
is
actually
reflected.
We
don't
just
have
to
draw
boxes
on
a
know,
each
other.
We
actually
have
a
system
to
support
this
kind
of
thing
and
so
leads
for
each
team
or
those
people.
A
Well,
I'm
Chris
beings,
I'm
leaving
the
admin
team
and
Christophe
is
beating
dev
Steve
James,
leading
growth,
as
he
always
has
essentially
Wiz,
is
running.
All
the
things.
Ops
and
support
is
a
is
a
TBD
right
that
doesn't
have
a
name
next
to
it,
and
currently
it's
a
shared
function
amongst
the
other
team
mates,
so
we're
definitely
pushing
that
ball
forward
and
we'll
see
who
ends
up
filling
that
role
in
a
first-class
way
down
the
road
okay.
So
what
does
a
team
lead?
A
Do
well,
primarily
they're
setting
team
priorities
right
sort
of
aligned
with
these
larger
priorities,
top-level
goals?
Okay.
What
does
my
team
need
to
do
to
support
that
right?
Making
decisions
about
the
budget
that
they're
allocated
we're
gonna
talk
more
about
budget
in
a
minute,
and
this
one's
really
key
I
think
for
scaling
the
Dow
it
reviewing
their
team's
compensation
requests
right.
So
right
now,
there's
a
kind
of
implicit.
A
You
know
obligation
or
expectation
that
you
know
all
contributors
are
potentially
reviewing
all
compensation,
requests
and
proposals
that
come
into
the
Dow
in
every
day
cycle.
You
know
this
last
cycle
there
was
I,
think
forty
three
proposals
of
one
kind
or
another,
and
it
just
doesn't
scale
to
have
every
contributor
sort
of
needed
to
look
over
all
of
those
things.
A
Everybody
still
can
do
that
everybody
can
still
load
every
stakeholder
can
still
vote
on
every
compensation,
request
and
proposal,
and
when
you
know
things
you
should
write,
if
you're,
you
know
educated
about
a
particular
proposal.
Well,
of
course
you
should
go.
You
should
weigh
in,
but
now
going
forward.
There's
a
you
know:
it
can
breed
a
big
sigh
of
relief,
because
the
the
ideas
that
we
count
on
team
leads-
that's
part
of
their
role
is
to
lead.
You
make
sure
that
the
things
that
are
being
know
when
compensation
is
being
requested.
A
It's
actually
delivered
work
right
for
our
definition
of
deliver
it's
within
budget.
It's
work
that
was
prioritized
ie
given
budget
right
and
you
know
anywhere,
there's
anomalies,
the
team
leaves
you
know,
gonna
jump
on
that
and
make
sure
to
to
smooth
things
out
or
clear
up
any
misunderstandings
or
what-have-you.
So
one
of
the
implications
of
this
is
that
you
know
if
you're,
a
contributor
submitting
compensation
requests
every
cycle
you're
going
to
want
to
do
it
earlier.
Probably
that
you
know
some
people
do
it
early
already.
A
You
won't
want
to
be
doing
it
on
the
last
day
anymore,
because
you
really
need
to
make
sure
you
clean
me
that's
time
to
go
through
everything
and
get
back
to
you
for
any
revisions,
and
so
on
so
team
leads
will
say
more
about
that
again.
Will
smooth
all
this
out
and
roll
all
this
out
as
we
go,
but
that's
just
kind
of
a
hint
and
of
course,
team
leads
are
responsible
for
coordinating
their
efforts
across
the
whole
organization.
The
other
team
leads,
so
no
big
surprises
what
a
team
they
do
all
right.
A
A
A
Most
of
the
time
right,
so
fifty
eight
thousand
dollars
worth
of
bsq
was
issued
in
cycle
seven,
so
we
denominate
here
in
USD,
because
the
price
of
esq
fluctuates
yeah
USD
is
more
stable
so
that
we
can
actually
manage
good.
So
we
issued
about
$60,000
worth
of
esq
in
compensation
in
cycle
seven
and
that's
been
roughly
consistent
with
the
previous
cycles
more
or
less
a
number
like
that,
then
in
cycle
eight
boom,
you
know
a
hundred
thousand
the
big
big
difference.
So
you
know
this
is
one
of
the
drivers
to
making
some
of
these
changes.
A
We
just
can't
let
that
happen.
We
cannot
let
it
happen,
but
you
know
from
one
cycle
to
the
next
we're
just
inflating
the
bsq
supply
in
an
uncontrolled
way.
So
so
you
know
that's
a
lot
of
what
this
budget
is
about
is
making
sure
that
that
sort
of
thing
doesn't
happen
right
and
then
we
stay
on
points
with
our
you
know:
kind
of
run
away
here,
cycle.
Nine
actually
turned
things
around.
A
Quite
a
bit
already
was
pretty
low,
and
you
know
we
just
looked
at
these
historical
x'
and
said:
okay,
what
do
we
think
a
reasonable
number
is
going
for
it
as
a
baseline
right.
We're
gonna
have
to
adjust
this
as
we
go,
probably
but
$60,000
worth
of
budget
for
the
org
in
cycle
10
and
onward
until
we
realize
that
that's
sort
of
a
little
longer
a
reasonable
number
and
it's
broken
down
across
the
teams
in
these
ways
and
I
won't
go
into
detail
about
it
here.
You
can
certainly
talk
here.
A
Okay,
so
priorities
talked
about
the
goals
right,
so
the
goals
are
sort
of
highest
level,
strategic
stuff
that
we
know
must
get
done
as
an
organization,
but
inside
of
those
goals,
were
you
know,
tactics?
What
are
we
gonna
do
to
actually
achieve
that
stuff?
Well,
this
is
where
it
gets
down
to
brass
tacks.
What
are
we
actually
going
to
give
priority
and
focus
on
to
the
exclusion
of
other
things
right,
so
I
just
want
to
define
priority
for
our
purposes
right.
A
The
priorities
are
units
of
work
that
have
been
allocated
budget
and
are
therefore
eligible
for
compensation
in
you
know
the
current
bestop
cycle,
for
perhaps
in
a
subsequent
out
cycle.
Whenever
that
work
actually
gets
delivered,
you
know
not
all
work
gets
done
within
a
single
cycle.
Some
things
may
take
longer,
but
it's
going
forward
gonna
be
very
important
that
you've
actually
gotten
a
green
light.
Hey.
This
is
on
point
with
our
goals.
This
really
is
a
priority.
A
A
So
that's
what
I
mean
when
I
said
priority
and
just
to
give
a
sense
right
like
there's
a
set
of
priorities
that
are
essentially
fixed
like
unchanging
right
things
like
keep
the
infrastructure
up,
provide
great
user
support,
fix
critical,
bugs
right
ship
regularly
and
okay,
assuming
all
those
things
are
going
as
they
should
work
on
whatever
the
current
cycle
priorities
are
are,
which
shift
over
time
right
as
things
get
done
and
new
things
get
prioritized.
So
what
are
some
of
the
current
cycle
priorities
now?
A
Well,
they
had
better
be
aligned
with
these
goals
or
the
goals
are
meaningless,
so
you
can
see
I've
kind
of
broken
it
down
that
way.
Well,
building
out
the
demon
in
the
API
certainly
a
priority.
For
all
the
reasons
we've
talked
about
the
growth
efforts
to
support.
All
of
that
like
really
getting
in
touch
with
market
makers,
attracting
them
to
the
project
etc
as
a
kind
of
experiment
in
liquidity
we
just
listed
lb
TC.
A
A
A
For
whatever
reason
you
can
now
kind
of
refresh
that
resend
that,
in
the
effort
of
you
know
in
for
the
sake
of
but
being
able
to
complete
that
trade
right
now,
have
you
thought
of
mediation
and
support
about
it
and
with
regard
to
onboarding
we're
still
mostly
in
the
conversation
fit
about
exactly
how
to
build
out
the
onboarding,
but
we're
already
looking
at
sort
of
prototyping
and
playing
with.
How
are
we
going
to
do
the
monitoring
and
the
metrics
that
we
need
to
actually
measure
that's,
but
that
effort
is
a
success.
A
You
know
kind
of
Kanban
board
style
that
that
you
know
get
support
for
now,
so
there's
a
priorities
board
that
I'm
currently
playing
with
it's
just
private
right
now,
I'll
make
it
public
soon,
but
I
think
we're
gonna
go
with
something
like
this,
which
is
basically
the
you
know
single
place
right
across
the
whole
organization,
processing,
all
repositories
etc.
Where
you
can
get
a
quick
look
at
okay,
what
has
priority?
What's
being
worked
on
right
now?
What's
sort
of
waiting
to
be
worked
on
right?
A
You
know
stalled
on
resources,
but
it
has
priority
if
only
someone
can
pick
it
up.
Okay,
and
what
have
we
gotten
done
right
so,
basically,
if
you're
working
on
something
and
you
want
to
get
paid
for,
it
should
probably
be
on
this
board
in
one
form
or
another
all
right,
so
that's
a
gonna
be
a
way
to
sanity
check
what
you're
up
to
so
on
that
point,
right
changes,
contribution
and
compensation
so
wanted
to
set
a
kind
of
new
default
right.
A
I've
already
articulated
this
a
couple
of
times
in
this
talk,
but
but
it's
a
bit
of
a
reset
right
that
you
want
to
think
about.
Contributions
are
not
by
default
eligible
for
compensation
unless
they've
been
prioritized,
unless
they
have
budget
right
and
there's
just
there's
just
no
way
to
manage
it,
otherwise
without
a
whole
lot
of
thrashing
right.
So
if
you,
if
you,
if
you
want
to
contribute-
and
you
want
to
issue
compensation
for
us,
simply
make
sure
that
you've
got
that
green
light
ahead
of
time
right,
this
is
a
lot
about
conversation
right.
A
This
is
not
like
super
heavy
process,
and
you
know
having
to
fill
out
a
bunch
of
forms
or
something
like
that.
It's
about
being
in
communication
with
the
relevant
team,
lead
or
team
leads,
maybe
and
really
making
sure
that
there's
alignment
that
this
is
important
enough
to
greenlight
for
the
limited
budget
that
we
have
right
to
the
exclusion
of
other
things
and
go
for
it
now,
of
course,
anybody
can
still
work
on
whatever
they
want.
It's
an
open
source
project.
A
Anybody
can
issue
a
pull
request
for
anything,
etc
right,
but
we
need
to
have
this
mental
shift,
but
there's
no
expectation
that
that
contribution
is
going
to
be
compensated
just
because
it's
there
just
because
you
did
a
good
job
right
really
doesn't
need
to
get
budget,
and
you
know
it's
it
to
that
same
n,
we're
gonna,
you
know,
death
is
gonna,
be
more
rigorous,
going
forward
with
new
piles
right.
We
have
a
pretty
steady
pulse
of
new
contributors
coming
along.
You
know
doing
this
work
or
that
work
not
necessarily
asking
about
it
beforehand.
A
Maybe
ask
me
beforehand
and
that's
all
great
right,
that
sort
of
shows
that
the
project
is
interesting
to
people
and,
of
course,
we've
in
a
way.
We
really
like
that
right.
You
want
that
kind
of
activity
around
the
project,
but
at
the
same
time
it
costs
to
do
that.
It
requires
review.
It
requires
conversation
that
requires
rework,
and
you
know
very
often
too
often
PRS
come
in
that
are
just
that
are
just
not
above
the
bar
right
they're,
just
not
good
enough
for
us
to
say.
Okay,
this
is
really
worth
my
time.
A
I'll
stop
what
I'm,
working
and
I'll
go
review
this
I'll,
you
know
sort
of
steward
this
into
getting
merged
right.
We
need
to
be
more
clear
upfront,
more
rigorous
about
this,
so
I
like
to
talk
about
being
both
direct
indecent
with
people
being
clear
right,
hey
this
probably
isn't
gonna
get
any
priority.
I've
taken
a
look
at
it
and
I'm
not
going
to
take
much
more
of
a
look
at
it
right.
We
have
to
figure
out
how
to
how
to
develop
that
capacity
that
culture
right
did.
A
We
just
must
not
waste
time
and
we
have
to
have
a
definition
of
what
is
wasting
time
right
what's
priority,
what
are
we
focusing
on
and
what
are
we
not?
If
we
don't
have
that,
then
we
get
distracted
and
cold
in
a
thousand
directions,
and
we
just
don't
have
the
people
to
allow
for
that.
Maybe
we
will
in
the
future
right,
we
don't
know
so,
changes
to
roles
and
bonds
very
quickly.
So
we
are.
You
know
after
this
call
we're
gonna
roll
out
a
just
a
review
of
all
the
roles.
A
A
The
role
owners
are
bonded,
where
appropriate
many
have
bonded
properly
and
many
happened
right,
and
so
that's
it.
You
know
a
case
of
failure
of
management
really.
This
is
this
is
on
us
to
make
sure
that
there's
rigor
and
there's
you
know
adherence
to
these
internal
structures
that
we've
built
in
the
Dow
so
we'll
do
that
right,
we'll
be
reaching
out
to
each
roll
owner,
we'll
be
asking
role
owners
to
be
responsible
for
their
role
documentation.
If
it's
not
present
role,
documentation
is
not
complicated.
A
It's
usually
just
a
few
bullet
points
of
what
are
you
do
T's?
What
are
your
rights
and
privileges
etc?
Right,
so
we'll
tighten
all
that
stuff
up
and
a
couple
points
on
communication.
One
lots
of
people
already
know
that
many
of
us
are
now
doing
a
kind
of
daily
stand-up.
You
know
in
the
sense
that
lots
of
software
teams
do
it
a
kindness
to
end
up
meeting
but,
of
course,
we're
distributed
so
we're
just
doing
it.
A
Mikey
based
channel
called
stand-up,
and
the
idea
is,
if
you're,
actively
working
on
bisk
post
an
update
every
day
that
you're
actually
working.
That
just
says:
what
did
you
do?
What
are
you
planning
to
do
tomorrow?
What's
in
your
way
of
getting
stuff
done
right,
just
classic
stand-up
stuff,
and
we
really
think
this
is
the
bare
minimum
for
a
team
like
ours
to
stay
in
touch,
and
it
has
this
magical
effect
of
actually
feeling
like
a
team,
you
see
everybody
around,
you
there's
a
pulse
right
and
it's
not
too
distracting.
A
It
doesn't
waste
a
bunch
of
time.
It's
just
a
couple
sentences
right
and
it
also
gives
the
opportunity
to
catch
something
like
oh
that's
already
being
worked
on
or
oh
hey
does
that
have
budget
right?
You
know,
like
a
team,
we
could
catch
that
and
say
you
can
say:
oh
no,
it
doesn't
that
it's
fine,
that's
what
I'm
doing
anyone
care
whatever
right,
but
you
need
to
be
in
communication,
at
least
that
level.
A
So
please
do
if
you're
not
already
start
that
practice
right,
just
post
something
and
stand
up
every
day
that
you
actually
are
contributing,
you're,
actually
working
yeah,
and
that's
just
what
it
looks
like
right.
You
know
I'm
sure
most
of
the
people,
it's
called
it
or
contributors
or
inky
base
or
any
and
and
I
want
to
talk
about
using
the
mailing
list
that
this
contributing
list
some
may
have
noticed
people
that
are
already
subscribed
there.
You
know
I've
posted
a
few
things
lately
and
I
think
that
we
are
essentially
missing.
A
kind
of
important
communication.
A
A
If
this
were
a
company,
we
would
have
a
list
all
mailing
lists,
and
you
know
big
important
announcements
in
the
company
would
be
made
there
and
of
course
everybody
reads
that
it's
total
expectation
that
everyone
reads
that
so
we
won't
have
something
like
that
and
the
structure
that
we
have
already
in
place.
Is
it
this
contributing
list?
So
you
know,
don't
introduce
anything
new
just
and
ask
to
everybody
here.
A
Please
do
go
subscribe
if
you're
not
already-
and
you
know
we
can
figure
out
from
there
and
your
future
kind
of
communication
changes,
but
you
know
a
place
to
make
important
announcement
announcements,
maybe
a
place
to
have
sort
of
more
discussions
and
ideas.
Write
me
another
mailing
list
for
that.
Let's
see
but
I
think
we're
kind
of
missing.
That
structure
I've
certainly
been
missing
me.
So
that's
that
and
just
takeaways
right.
So
these
changes,
you
know,
there's
a
number
of
changes.
A
I
just
talked
about
they're
all
works
in
progress,
wanting
to
announce
them
all
so
everybody's
on
board.
Everybody
can
ask
questions
about
it.
Whatever
it's
gonna
take
a
little
time
ready
to
really
roll
it
out
fully
integrate.
So
please
plication
with
that
share,
updates
and
stand
up
subscribe
to
this
contribs
priority,
and
you
know
in
communication,
if
you're
in
doubt
about
anything.
Any
of
this
just
ask
right.
Talk
to
your
team,
lead.
A
Ask
me
whatever,
and
you
know
feedback
welcome
please
so
last
thing
I
want
to
talk
about
is
what
does
bisque
need
as
a
project
right
if
you're
somebody
listening
space
and
you're,
not
already
a
contributor,
you're
thinking
about
it
or
etc?
Well,
it's
pretty
simple.
We
need
very
strong
Java
developers.
We
need
the
kind
of
developers
that
can
show
up
into
a
complex
project
like
this
and
figure
it
out
needs
to
be
done,
figure
out
how
to
solve
problems
right.
This
is
not
a
trivial
thing.
A
So
if
you're,
one
of
those
people
will
certainly
come
talk
to
me
and
come
talk
to
us
and
if
you
know
any
of
those
people
they're
like
yeah,
people
are
really
passionate
or
just
really
interested
in
Bitcoin,
like
they
think
they
want
to
get
into
this
space
and
maybe
they're
coming
from
a
career,
long,
super-strong,
history,
with
Java,
with
open,
sores,
etc.
Please
do
point
in
my
direction
and
we
need
additional
support
agents
right.
So,
if
you're
somebody
who
may
be
a
user
of
Biscay
would
like
to
get
involved,
you
know
something
about
it.
A
You're
familiar
with
the
app.
Maybe
you'd
like
to
really
learn
more
right
support,
it's
a
great
place
to
learn.
Actually
you
can
really
help
people
and
learn
at
the
same
time,
so
consider
that
and
like
I've
mentioned
all
throughout
this,
we
need
market
makers.
So
if
you're
somebody,
especially
if
you're
somebody
technically
minded-
and
you
think
you
might
want
to
be
using
this
API-
that
we're
building
come
talk
to
us
right,
come
talk
to
us
about
your
use.
Cases
come
be
an
early
adopter,
okay,
so
well,
I
hope
you
get
sense
right.
A
What
we're
trying
to
do
here
and
the
20/20
it
can
really
be
about
growth
for
us
in
a
nutshell,
right,
yeah,
I,
hope
you
like
what
you've
seen
come
talk
to
me
about
anything
in
here
and
thanks
very
much
for
attending.
This
call
has
been
recorded
and
will
be
published
to
YouTube
just
afterward,
that's
our
YouTube
channel
and
the
link
to
this
slide
will
also
be
published
in
the
in
the
show
notes
there.
So
you
can
come
back
and
review
everything
here.
A
A
Yeah
so
I
want
to
start
a
new
Q&A
session,
and
so
you
can
now
see
you're.
Probably
looking
at
my
yeah.
Let's
see
all
right,
are
you
I'm
not
sure
if
you're
looking
at
my
whole
screen?
Let
me
let
me
make
sure
so
I'm
going
to
show
you
my
whole
desktop
I.
Think
that's
the
only
way
to
do
it,
and
so
you
can
now
see
that
and
you
can
see
that.
So
if
you
want
to
ask
a
question,
you
can
go
here
and
just
type
it
in.
You
can
also
just
unmute
and
ask
it.
A
A
Who
decides
on
the
priorities?
You
know
good
question
so
ultimately,
at
this
point
it's
been
this
body
of
team
leads
right.
We've
got
this
together
and
called
some
shots
that
we
think
are
you
know
reasonable,
and
probably
everybody
can
get
aligned
with
and
it'll
continue
to
be
that
body.
But
you
know
it's
not
a
closed
our
door,
smoking,
cigars
or
whatever
right
it's
even
communication
with
everybody
right,
you
know,
team
leads
are
working
with
our
team
members.
A
You
want
to
stay
in
touch
with
the
community
right,
but
there
doesn't
need
to
be
some
function
that
determines
this
ought
to
be
done.
At
least
this
ought
to
be
budgeted
for
right
actually
eligible
for
compensation
to
the
exclusion
of
other
things,
or
you
know
we
get
the
kind
of
results
that
we've
that
we've
been
getting
so
I
hope
that
answers
the
question.
A
Does
the
budget
fixed
forever?
No,
certainly
not.
It
starts
at
$60,000
worth
of
bsq,
whatever
the
vsq
market
prices,
but
you
know
as
conditions
change
right.
You
know,
especially
if
we're
if
the
team
is
growing
right,
if
we
do
bring
out
some
of
those
strong
developers
that
we
would
love
to
have
and
we're
now
able
to
do
more
right,
add
more
value
for
users.
A
Well,
it
follows
that
we
should
have
a
bit
more
budget
right,
but
the
thing
is
we
want
to
be
want
to
be
very
consistent
here
right,
so
right
now,
$60,000
worth
of
bsq
is
more
revenue
than
we
make
right.
So
that
number,
even
though
it's
a
controlled
budget
is
going
to
continue
to
inflate
the
bsq
supply
in
in
a
controlled
way
right.
So
we
want
to
have
that
expectation
out
there
for
stakeholders
and
people
who
you
are
interested
in
esq.
They
should
know
that
right.
A
The
total
BS
q
supply
begins
to
trend
down
and
BS
q
becomes
deflationary
right.
We're
essentially
producing
more
value
right.
Users
are
paying
more
in
bsq
than
we
are
charging
to
do
our
work.
That's
the
game!
That's
the
idea!
So
we're
gonna,
you
know
manage
the
budget
in
accordance
with.
What's
prudent,
with
that
larger
overall
goal,
so
60,000
is
not
fixed,
can
grow
or
shrink
right
just
depending
on
what
we
need,
but
we're
gonna
keep
that
big
picture
in
mind
right,
attractive.
A
Okay,
how
do
we
join
T?
Well,
she
talked
right
now.
What
is
it
you
want
to
do?
Are
you
already
doing
something
like
if
you're
already
playing
certain
role
in
bisque?
Well,
then
you're
implicitly
already
part
of
whatever
team?
That
role
is
part
of
right,
so
that'll
just
sort
of
be
automatic,
there's
more
to
be
done
inside
of
github
than
the
details
of
all
those
teams,
but
if
you're,
asking
kind
of
from
coming
out
of
the
blue
right
like
you're
somebody
interested
in
contributing
you'd
like
to
join
and
say,
I,
don't
know
the
ops
team.
A
Well,
this
is
a
conversation.
You
have
to
have
what
needs
to
be
done.
Ops,
here's!
What
I'm
good
at
did
that
right.
So
I
hope
that
answers
that
and
noncustodial
lightning
trades
need
to
be
done
with
the
bisque
v
2.0
trading
protocol.
Maybe
maybe
not
right
the
reason
that
I
answered
that
in
the
opportunities
section
is
you
know,
lots
of
people
have
asked
that
lightning.
We've
all
thought
about
lightning
a
little
bit
at
least
right.
It's
a
kind
of
obvious
question:
what's
bisques
lightning
story
going
to
be,
will
this
have
a
lightning
story?
A
Does
the
way
this
does
things
comport
with
lightning
right?
Is
it
compatible
in
some
way
with
light,
and
can
it
be
adapted
to
lightning?
We
don't
know
the
answer
to
that
right.
We
we
simply
have
not
had
enough
time
and
resources
to
really
do
the
thinking,
that's
possible
if
we
can
move
through
these
challenges
right
and
we
can
grow
so
I
entered
that,
not
because
we
have
some
deep
plan
about
how
to
do
it,
but
really
to
make
the
point
want
to
have
such
a
plan.
These
are
things
that
are
real
opportunities
for
us.
A
You
know
if
we
can
build
this
foundation,
and
will
this
team
lead
structure
a
budget
around
forever
yeah
I
mean
everything
involves
right.
Everything
changes.
So
this
is
an
initial
structure
and
it's
subject
to
change
just
like
anything
else,
just
based
on
what
works
right,
so
all
about
figuring
out
what
works,
what
are
the
minimum
programming
skills
and
availability
to
be
useful
to
a
support
team
very
interesting
question?
A
Programming
skills
are
not
required
per
se
right.
It
helps
if
you're
technically
minded
helps
if
you
have
a
kind
of
model
of
how
an
application
works
and
how
bisk
functions
and
so
on
so
have
a
mind.
That's
capable
of
like
reading
about
that
stuff
and
kind
of
taking
it
on
board,
but
you
know
you
typically
support
agents
as
a
function
of
that
role,
I'm
not
doing
any
coding
really,
but
they
all
tend
to
be
more
or
less
technical
and
at
least
able
to
reason
about
bisque
and
availability
availability
varies
right.
A
You
know
kind
of
stop
by,
or
you
know
just
an
hour
here
or
an
hour
there
randomly
that
ends
up,
probably
creating
more
overhead,
and
it's
worth
I
can't
say
for
sure,
but
that's
a
gut
feeling,
but
especially
as
we
build
out
these
calendars,
I
mean
what
we're
gonna
try
to
do
is
build
24/7
coverage
right
so
anytime
any
day
any
customer,
you
know
or
user,
shows
up.
There's
somebody
there
to
at
least
initially
respond
to
them
right
and
help
guide
them
in
the
right
direction.
A
So
you
know
if
you've
got
three
hours
a
day
available
or
four
hours
a
day
three
times
a
week
or
something
like
that,
hey
that
can
be
very
useful
when,
though,
the
API
would
be
released
in
whether
it's
functions,
I'm
gonna,
let's
see,
we've
got
a
few
more
questions.
I'll
try
to
answer
the
ones
that
remain
and
we'll
go
for
five
more
minutes,
or
so
when
will
the
API
be
released
and
what
are
its
functions
so
the
so
I
don't
know
I,
don't
know
when
the
API
will
be
released.
A
It's
actually
stalled
right
now
on
dev
resources
is
that
this
is
actually
a
personal
responsibility
of
mine
took
on
that
work
starting
a
couple
of
months
ago,
but
I
put
it
on
hold
to
take
on
this
role,
and
it
remains
to
be
seen
it's
one
of
my
top
priorities
after
this
call
right
to
return
to
that
and
figure
out.
Okay.
How
do
we
push
the
ball
forward
right,
you
know.
A
Do
I
do
some
amount,
more
work
and
then
paint
off
simply
don't
know,
but
it
has
the
utmost
priority
to
me
and
what
are
its
functions
in
general?
You
want
to
think
okay.
What
can
I
do
with
bisque?
Well,
you
can
probably
ultimately
do
that
in
the
API
will
do
it
incrementally
right,
so
you
wanna
think
about
things
like
you
know
from
the
most
basic.
What's
my
back?
What's
the
balance
of
my
wallet
right?
That
would
be
like
the
most
basic
thing.
You're,
like
what
version
is
this
bisque
daemon
running?
A
You
know
a
get
version,
call
or
get
balance
calling
very,
very
simple
stuff
up
to
you
know
core
use
cases
right.
What's
you
know
you
want
to
place
an
offer
to
sell
this
many
Bitcoin
in
exchange
for
euros,
and
you
know
with
this
distance
from
market
products
and
so
on
and
so
forth.
Right
all
those
things
you
can
do
in
the
UI
will
be
represented
in
the
API
on
them.
You
know
as
needed,
most
important
stuff.
First,
iterative
kind
of
basis
will
release
an
MVP
where
the
Minimum
Viable
Product,
with
you
know
enough.
A
I,
don't
know
about
that
I'm,
not
sure
that
there's
such
a
danger
I'm
not
sure
that
any
such
thing
is
happening.
I'm,
gonna,
punt,
I
simply
don't
know,
and
if
you
want
to
talk
more
about
it,
please
come
to
key
base
it.
In
any
case,
that's
not
an
item
that
has
been
in
my
head
like
something
to
manager
or
something
to
mitigate.
Will
the
budget
automatically
be
adjusted
to
match
the
revenue?
Well,
yeah
certainly
have
an
effect
right.
You
know,
particularly
as,
as
you
know,
revenues
match
expenses.
Okay,
well,
yeah.
A
We
can
increase
the
budget
accordingly
right
as
we
actually
are
in
the
green.
Well,
of
course,
we
can
increase
the
budget
right,
keeping
in
mind
that
we
wanted
to
achieve
this
gradual
deflationary
trend
from
bsq
to
over
over
time
right
so
yeah
we
could
raise
it,
but
if
we
have
that
wherewithal,
if
we
have
that
you
know
if
we've
achieved
that
luxury
of
being
a
profitable
organization,
well
last
thing
we
want
to
do
is
get
crazy
and
start
inflating
the
supply.
A
All
right,
we
need
to
create,
for
everybody
involved
a
plausible
promise
of
a
deflationary
future
for
bsq
right.
That
really
is
the
game,
so
you
know
we
get
profitable.
Probably
the
last
thing
we're
gonna
do
is
you
know,
start
breaking
the
budget
and
going
above
our
revenues
right,
just
I'm,
just
giving
a
sketchy
I'm,
not
saying
never,
but
hopefully
you
get
the
thinking
yeah.
A
How
would
you
like
to
contribute
and
there's
certainly,
certainly
known
technical
roles
that
people
do
play
and
no
technical
contributions
and
people
make
so
absolutely
okay,
so
I'm
gonna
go
about
one
more
minute
and
as
far
as
feedback
goes,
is
bisques
app
resource
consumption,
satisfactory,
I
read
this
as
a
question
asking
about
like
are
we
do
we
think
it's
satisfactory,
like
the
resources
that
this
consumes
I'm?
You
know
typical
user,
the
Machine?
A
Well,
no
I
mean
we.
We
certainly
know
that
there
are
issues
that
people
are
experienced
with
lots
of
brand.
You
know
usage
and
possibly
memory
leaks,
causing
that
and
so
on,
where
you
know
tracking
this
things
down
like
as
we
speak,
some
are
pretty
tricky,
but
in
general
you
know,
I
didn't
list
it
out
here
explicitly
performance,
but
in
practice
performance
really
has
been
a
priority
for
us.
You
know
over
the
last
year
for
sure
and
it
will
continue
to
its
in.
In
the
most
important
cases,
it
is
essentially
falling
under
reliability.
A
You
know,
if
you
end
up
this
kinds
of
blowing
up
for
you
with
another
memory,
error.
Great,
it's
a
reliability
issue
I
mean
it's
an
extreme
case,
but
but
no
we're
you
know
hell-bent
on
on.
You
know
reducing
resource
consumption
wherever
we
can,
so
it
is
a
phone
going
priority
and
likely
to
be
greenlit
right,
especially
whether
it
where
it's
causing
real
pain
or
users.
A
Okay,
I'm
gonna,
miss
this,
but
any
news
on
back
32.
No,
unfortunately,
it
remains
stalled.
This
is
one
of
the
key
areas
where
we
really
need
developers
right
just
need
developers
right.
Like
I
said
we
need
a
strong
developer,
who
can
come
in
and
really
grok
the
situation
that
we
have
with
Bitcoin
J
right.
We
have
a
custom
fork
of
Bitcoin
jet.
We
have
done
things
to
Bitcoin
J
for
our
purposes
that
we
need
to
preserve
that
we
need
to
be
mindful
of.
We
cannot
simply
upgrade
to
the
newest
version
of
Bitcoin
J.
A
That
has
said
would
support
and
then
just
do
a
kind
of
vanilla
upgrade
to
it.
It's
more
complicated
than
that.
You
don't
have
a
Bitcoin
J
expert
on
the
team
right
now
and
we
need
one
okay.
So
that's
just
the
situation.
We
know
how
much
people
want
I
want
it
right
and
it
remains
on
a
dashboard,
let's
say
and
stop
asking
about
it.
But
unfortunately
the
answer
is
presents:
activity
okay
and
from
flicks
make
these
my
last
ones
will
bisque
do
any
marketing
outreach
communication
referral
program.
A
A
Remote
client
right
you'd
have
your
bisque
and
running
at
home
on
a
VPS
on
Raspberry
Pi.
Whatever
it
is,
he
going
to
do
and
you'd
be
able
to
access
that
in
a
fully-featured
way
remotely.
We
have
a
bisque
notifications
app
for
iOS
and
Android,
which
is
very
simple
and
just
pings
you
when
there's
any
change
in
your
trade
status
like
tradesmen
taking
ignore
next
step
in
the
trade
process
is
completed
it
or
you
have
an
arbitration
remediation
message,
etc.
So
that's
already
out
there,
but
this
sort
of
fully
featured
light,
client,
remote
client.
A
We
certainly
have
in
mind
it's
a
key
thing
going
build
on
top
of
the
API,
but
the
API.
It's
gotta
get
there.
Okay,
Wow
great
great
questions.
Thanks
everybody
for
attending
I,
see
there's
25
participants,
I,
don't
know
how
many
we
had
done
as
a
total
or
the
hype
area,
but
that's
great
yeah,
oh
my
god
just
say
hi
to
the
team.
Yes
it
just
so
you
know
the
face
is
behind
or
the
mediator,
and
thank
you
very
much
for
you
station
yeah
pleasure.