►
From YouTube: Bisq developer session 16.01.2019
Description
Bisq developer session 16.01.2019
See: https://github.com/bisq-network/growth/issues/84
A
Session
of
our
developer,
we
click
developer
calls,
or
these
sessions
are
mainly
intended
for
active
developers
to
disclose
your
pure
developer
topics.
We
try
to
keep
it
produce
with
topic.
Of
course,
when
there
is
a
burning
question
we
can
discuss
about
this
as
well.
Anybody
is
welcome
to
join
also
in
the
Hangout
or
watch
us
on
the
YouTube,
like
livestream
yeah.
Let's
check
directly
into
it,
we
have
defined
a
rough
agenda.
A
What
we
want
to
discuss,
yeah
just
to
say
a
little
bit
quickly
as
we
we
expected
a
little
bit
more
developers
but
or
yeah
one
is
expecting
it
or
his
wife
is
expecting
a
baby,
so
he
cannot
join.
Another
is
sick,
sick.
He
was
at
least
a
few
days
ago,
and
one
one
is
just
joining
by
chat
for
privacy
reasons
and
yeah
crack
is
missing
and
I'm
on
he's
not
really
active
developers.
A
We
would
not
join
each
call
at
least
and
Devon
has
probably
hi
Chris
I
welcome
nice
to
see
you
yeah
Devon
are
has
problem
with
with
the
time
zone.
At
this
event,
it
was
very
hard
to
find
it
in
many
times
where
every
developer
is
able
to
China
yeah.
We
just
I
just
started
with
basic
introduction
risk
yeah.
The
main
that
Canada
would
be
to
talk
a
little
bit
about
the
arrest
and
commit
policy
or
Chris
is
a
specialist
on
that
than
he
has
written
a
very,
very
well,
very
good,
blog
entry.
A
Keep
your
commits
small
and
contained
with
one
thing,
but
they're
doing
also
try
to
give
a
good
describing
name
for
commit
at
when
they're
a
little
bit
more
complex.
Add
some
description
about
the
commit
is
really
doing
and
yeah
I
think
that's.
The
main
aspects
will
later
add
the
link
from
Chris
block,
which
is
much
more
detailed
or
Chris.
Would
you
like
maybe
jump
in
here
and
give
her
your
yeah
you're
coming.
B
Yeah:
okay,
because
we
just
stopped
hearing
you,
or
at
least
I
did
not
good.
Maybe
that's
just
my
thing,
but
yeah
I
mean
if
you
share
the
link
that
says
it
all
about
to
commit
messages,
and
it
doesn't
really
tell
you
about
poor
requests,
but
what
you
just
described
is
completely
sufficient
I
think
so
I,
don't
think
all
had
anything
else.
A
A
C
Regarding
so
I'm,
not
hundred
percent
true,
because
the
audio
was
a
little
choppy
on
my
set
as
well.
Regarding
naming
of
the
pull
requests
to
make
it
small
as
small
as
possible
is
because
for
them
their
visa,
we
missed
trying
to
create
a
kind
of
release,
notes
document
and
it's
quite
difficult,
if
there's
just
general
full
requests
to
go
in
there
and
to
find
out
what
what
kind
of
feature
was
was
integrated
and
to
compile
it
into
a
nice
release.
C
A
You're
really
shooting
of
this.
When
you
make
a
pull
request,
it
should
be
a
feature
which
is
added
in
release
mode
and
a
use
of
phasing
features,
even
if
it's
the
pure
development
stuff,
but
it
should
be
something
which
makes
sense
in
the
release,
not
for
user
language,
even
if
it's
something
like
improve
testing
framework
or
whatever
hayek
right
away.
Yeah
Craig
we
just
started
and
or
I,
think
you
didn't
miss
too
much.
Just
was
talking
about
the
pluralist
and
commit
policy.
A
Maybe
you
watch
the
live
stream
afterwards,
when
it's
published
to
not
repeat
that
part
or
nothing
really
very
complicated
yeah
I
mean
there.
The
second
point
I
want
to
discuss
is
about
testing
frameworks.
We
got
quite
a
few
different,
that's
it
for
him,
but
basically
everything
that
comes
with
it's
his
preferred
testing
framework
and
that's
probably
not
very
good
for
the
project
to
get
so
much
mix,
but
because
fluorine
is
not
here.
C
A
Hamlet's
bonus
for
our
next
session,
I
want
to
give
a
little
bit
of
overview
about
the
different
domains.
What
is
really
different
to
me?
What
we're
working
on,
as
you
know,
yeah
Jana,
is
working
on
the
API
Craig
is
working
on
the
new
trade
protocol
together
with
Nyman
Florin
is
working
on
at
the
moment.
A
A
monitoring
of
basic
area,
network
improvements,
auspice
working
under
bit,
country
domain
and
crystals
on
the
UI,
mainly
but
also
all
kind
of
stuff,
in
the
application,
and
as
few
and
myself
are
mainly
I,
should
assess,
who
is
focused
on
the
DAO
stuff
and
I
should
also
be
focused
on
this,
but
have
to
jump
around.
All
the
different
selves
and
I
want
to
keep
it
yeah,
as
maybe
it's
a
twister,
easy
one
or
Weser,
where
I
don't
need
to
say
so
much
I,
don't
know
so
much
to
update
here.
That's
the
yeah
with
the
network.
A
What
we
have
in
our
current
moniker
page,
which
is
very
rudiment
error
and
very,
very
basic
monitoring
and
I'm,
not
I'm,
not
too
bad
to
date
about
the
state.
But
us
yeah,
he's
working
on
this
already
and
I
think
before
he
got
sick.
He
had
a
really
good
progress
on
that
yeah.
He
used
for
the
UI
for
the
display
to
use
the
framework.
I,
don't
remember
the
name,
but
there
is
a
proposal-
everything.
Oh,
it's
called
Griffin
yeah
prevalent
in
his
proposal
at
leas
published,
or
he
has
described
everything
very
very
well
by
the
way.
A
It's
really
a
top
proposal
from
the
quality.
Also,
when
all
proposals
would
be
like
this
would
be
perfect
and
yeah
I
think
much
more
basic
milestones.
Whatever
the
targets
in
that
domain
are
that
we
get
first
proper
monitoring
so
that
we
know
that
the
notes
or
receipt
notes
are
really
delivering
the
correct
date
and
on
the
right
state
and
are
responsive
and
to
know
more
about
the
network.
How
many
peers
are
life
and
how
is
the
network
traffic
and
so
on?
A
And
then,
when
we
have
a
good
monitoring
and
we
will
start
to
improve
peer-to-peer
network
from
optimizing,
it
performance,
improvement,
refactorings
and
more
protections
against
the
DDoS
attacks
or
whatever.
Yet
it's
good
to
have
first,
some
measurements
where
we
can
see
when
there
are
changes
first
to
test
if
the
changes
are
not
breaking
anything
and
also
to
see
if
they
will
improve
the
metrics
of
the
peer-to-peer
network
or
not
because
it's
a
very
dangerous
area
where
this
can
easily
break
something
or
decrease
performance
by
yeah.
A
By
doing
something
where
you
think
you
increase
it
in
the
yeah
to
get
the
testing
framework
for
the
European
network
is
also
on
the
midterm
or
long-term,
a
roadmap
that
will
be
quite
complex
and
difficult
about
which
something
work
we
want
to
get
as
well.
At
some
point,
then,
I
jump
to
the
Bitcoin
trading
main
Oscar
is
yeah
since
many
years
a
very
active
development
bit
machine
was
in
all
his
project
in
the
last
year.
A
He
worked
in
some
extent
to
which
bit
country-
and
it's
all
after
next
to
the
main
contributors
to
the
maintain
us,
is
one
of
the
main
contributors
to
bid
country,
and
the
first
thought
was
that
he
investigated
alternatives,
because
we
wanted
to
get
basically
rid
of
this
country.
Many
for
many
reasons.
One
reason
is
the
privacy
leaks
with
bloom
filters.
The
other
reason
is
that
many
teachers
from
bitumen
who
are
not
implemented
by
exec
with
replace
bethey
and
many
other
current
maintenance
of
bit
country
is
not
really
great
as
very
little.
A
Progress
going
on
and
Cedric
is
in
development
and
should
be
released
someday,
but
it's
already
more
than
a
year,
I
think
in
development
and
not
really
so,
unfortunately
turned
out
that
there
are
no
other
room
of
notice.
What
we
can
use
I
mean
the
target
was
to
use
Bitcoin
core
in
fbb
mode.
It
was
a
project
from
your
nationally.
Unfortunately,
it
doesn't
meet
our
requirements
from
resource
and
usability
perspective
and
all
the
other
project
like
North
Reno,
are
basically
not
production,
really
not
well
tested
or
not,
or
have
enough
features
what
we
require.
A
So
it
turned
out.
We
need
to
stick
with
bit
country
and
our
mid
and
long
term
goal
is
that
we
are
improving
the
library
and
mainly
maybe
piss,
cologne
or
incorporation
is
not
approach.
It
like
Samara
wallet
or
mycelium
kind
of
taking
over
maintenance
or
not
officially,
but
at
our
branch
really
implements
all
the
missing
bits
from
Bitcoin
core
and
again
bring
this
project
forward
again
and
fix
the
privacy
issues
and
so
on.
It's
a
long
and
very
challenging
task,
and
probably
not
do
it
by
one
develop
alone.
A
So
that,
probably
when
we
go
more
in
distraction,
we
need
either
cooperation
with
other
projects,
so
we
share
the
resources
or
yeah
where
we
hire
more
developers
in
that
space
for
short
term
at
the
moment,
ease
yeah.
We
used
the
not
the
latest
release
branch,
what
0
14
7,
but
the
one
before
worked
in
for
there
was
not
a
ton
of
changes,
but
the
few
changes
and
yeah
they're
the
way
how
we
added
our
features
was
not
very
nicely
done
it.
A
He
checked
that
as
we
created
a
new
work
based
on
0
14
7
us
on
the
latest
release,
which
is
already
I,
think
two
years
old
as
well
and
then
apply
our
changes
to
that
release
in
the
teen
commit
history.
I
think
he's
already
pretty
far,
but
I
mean
yet
important.
Part,
of
course,
was
a
refill.
All
these
changes
have
been
a
few
more
complex
changes,
mainly
for
supporting
on
n
addresses
for
peers
and
for
and
some
improvements
in,
the
PIA
handling
and
those
are
yeah
and
I.
A
A
That's
the
current
go
to
to
basically
get
our
changes
are
updated
to
the
0
14
7
release
French,
and
then
we
would
switch
to
that
refresh.
Because
of
that
would
be
that
we
get
rid
of
lip
Dolce
and
the
alternative
base,
currents,
lists,
torch
and
and
fashion
light
Quinn,
or
it
no
plans
that
we
would
use
this
anymore,
and
it's
just
that
food
at
the
end.
So
we
want
to
clean
this
out
as
well
and
specially
it
makes
that
difference
management.
A
We
don't
have
middle
chain
between,
so
that's
basically
there
at
this
milestone
or
for
him,
and
after
this
area
we
will
go
on
to
to
work
on
our
Bitcoin
package
in
core
and
start
reviewing
everything
and
improving
refactoring
and
cleaning
up
there.
I
mean
if
he
didn't
refill.
That
was
his
first.
Basically,
it
didn't
really
of
the
people
working
for
implementation,
but
I
did,
and
it
seems
that
everything
is
okay,
I
think
he
had
one
or
two
minor
things,
but
nothing
critical.
A
So
that
was
done
already,
but
then
there
would
be
a
bigger
I
mean
it
would
be
longer.
Task
for
ya
were
improving
the
Bitcoin
package
and
one
part
of
the
task
will
be
to
find
out
the
issues
with
transactions
which
doesn't
get
published
or
in
time.
We
don't
have
many
I'm,
not
aware
that
the
arbitrator's
have
reported
any
issues
with
missing
transactions
anymore.
So
it
seems
that
it
works,
but
we
still
get
interlocks
that
sometimes
transaction.
A
We
don't
hear
that
they
get
published
in
reality,
but
we
don't
get
back.
So
there
is
still
some
be
sure
that
would
be
one
of
the
areas
where
you
should
work
on
and
yeah
and
then
the
midterm
called
wiki
to
get
me
proof
bit
country
as
well
as
the
first.
But
the
next
video
will
be
true
power,
Bitcoin
related
code
and
then
yeah
to
help
to
get
features
implemented
replaced.
But
he
would
be
very
important
but
of
course
edit
and.
A
Yeah
assign
I
was
always
in
contact
with
lead
developer
from
mycelium
Leo,
mantis
lab
and
I
wanted
actually
get
him
into
this,
but
or
for
whatever
reason.
You
never
join
us
and
I'm
locked
in
at
the
moment,
I'm,
not
in
compact
with
him,
so
take
it
with
anything
that's
real
ago,
I
think
that
was
contact
with
Samara.
Well,
that
was
never
entire
contact
with
one
developer,
who
worked
at
lockscreen
I'm
in
context,
he
was
not
working
direct,
but
boxspring
used
also
done
British
equality
for
their
mobile
wallet
and
build
on
top
of
that.
I.
A
Don't
know
much
about
this
and
it's
a
normal
company
and
of
the
company
with
a
very
good
reputation.
Many
of
you
deserve
some
insights
I
think
that's
not
the
target
where
we
want
to
get
cooperation.
As
far
as
I'm
aware,
it's
mainly
mycelium
and
some
red
wallet,
Vasavi
wallet
would
be
interesting
that
they
have
completely
different
technologies
that
they're
not
using
bit
country.
It's
a
c-sharp
and
plus
some
implemented
stuff.
So
I
think
there
is
beside
conceptual
overlap.
A
There
is
probably
no
way
to
work
together
and
not
to
really
wear
any
other
pic
approach,
but
will
be
for
sure
a
single
non
rate,
probably
all
wallets,
which
are
as
beaming
wallets,
are
based
on
more
lesson
on
the
Android
and
on
the
younger
ship.
I
call
it
we
might
have
different
goals
because
those
are
usually
very
focused
on
the
mobile
area.
A
Often
they
use
at
the
end
some
yeah,
some
dedicated
server
or
some
federated
server
model
I
mean
we
also
have
now
a
Catholic,
a
federated
server
model,
but
in
a
different
way
like
like
my
mobile
providers
program.
So
there
will
be
different
requirements
and
so
on
and
we'll
we'll
see
how
this,
if
there's
enough
incentives
for
different
projects
who
are
clicking
away,
we
just
try
to
find
more
developers
to
get
this
done,
but
that's
long
term.
That's
for
sure.
We
cannot
solve
this
in
the
next.
C
Six
months,
I
think
yeah
just
one
task,
because
I
saw
that
there
are
more
than
1800
forks
of
the
bit
crunchy
library
and
I
guess
some
some
projects
might
also
have
updated
and
improved
their
own
fork
and
their
own
branch.
So
so
we
don't
start
to
reemployment
too
much
stuff
if
there,
because
going
through
all
the
forks,
is
kind
of
impossible.
It's
it's
so
much
to
go
through,
but
yeah
yeah.
A
I
think
the
number
probably
maybe
1%
of
the
folks
are
doing
real
stuff
and
the
other
that
just
watching
and
working
I
assume
I
assumed
that
anybody
who
would
have
done
some
serious
work
like
samurai
wallet
they
got
implemented
check
with
in
some
way,
which
is
probably
different
like
until
shoot,
but
he's
doing
it
now.
I
just
followed
very
superficially
the
discussion
and
it's
a
little
bit
complex
how
to
deal
with
it,
I
think
with
regarding
backward
compatibility
and
so
on,
not
truly
trivial
to
find
the
best
concept.
How
to
support
it.
A
I
assume
that
any
wallet
which
would
have
done
extra
work,
valuable
work.
They
would
use
it
for
their
marketing
and
PR
and
I
never
heard
of
anything,
but
we
will
for
sure
a
research
and
shout
out
to
the
community
and
ask
anybody.
We
asked
already
like
how
yeah
we
were
considering
also
to
switch
or
a
to
the
master
branch,
but
there
are
tons
of
changes
or
the
latest
release
at
the
current
master.
That's
there
it's.
A
It
would
be
a
huge
risk
and
there
was
very
few
feedback
and
from
the
little
the--but
it
was
basically
a
do
it
on
your
own
risk.
It's
no
we're
really
in
production,
some
people
use
it
more
or
less
for
themself
and
so
far,
I
think
it
would
be
too
risky
the
moment
at
least
to
do
this
I
think
changing
lock
is
somehow
working
at
least
he's
active
on
the
mailing
list
as
well.
I,
don't
know
exactly
what
he's
doing,
but
he
seems
to
be
using
Bitcoin
chain.
A
A
Did
the
new
trading
protocol
Excel
would
use
tomorrow's
grouse
Hall
to
discuss
and
explain
a
little
bit
the
new
trade
protocol,
because
I
think
not
many
people
have
really
read
the
proposal
and
have
heard
of
it
and
the
crack
and
diamond
our
work
is
correct.
On
development
site
and
I'm
on
the
conceptual
site
are
the
yeah
all.
A
We
have
this
feature
that
the
pea
transaction
can
be
sent
to
a
donation
address
that
can
be
the
business
foundation
address
or
anything
which
is
defined
in
about
and
by
that
the
funds
get
well
at
the
end
for
the
users,
so
they
cannot
take
out
the
funds
anymore
and
then
can
make
a
reimbursement
request
and
thou
will
it's
a
little
bit
early
insurance
model
at
the
end?
So
when
you
really
would
get
burnt
by
having
a
trade,
mrs.
Cameron?
A
Who,
who
don't
pay
you
and
he's
not
cooperating,
then
he
will
lose
his
security,
the
person
you
can
ask
for
reimbursement
to
get
your
losses
covered
and
yeah
the
progress
may
be
correct.
Do
you
want
to
say
yourself
something
about
the
current
state,
the
program,
the
progress
of
the
development
right
now
still
early
on,
so
hopefully
more
to
take
soon,
yeah.
A
No
I'll
take
over
the
third
neck.
I'll
have
a
better
answer
next
time:
okay,
yeah,
okay,
so
one
thing
is,
it
will
depend
on
the
Tao,
so
we
cannot
whole
life
before
that
are
always
at
least
life
and
stable,
because
the
other
important
feature
in
this
concept-
I
mean
I,
think
if
background
or
feedback
about
what's
already
implemented,
as
we
created
a
branch
for
for
the
new
trade
protocol
as
well
as
well
for
the
API.
A
The
reason
why
I
first
we
tried
that
those
developers
are
having
known
foreign
branch
and
I
do
the
review
there
and
they
are
doing
immersion
so,
but
in
practice
it
turned
out
that
didn't
work
well
and
yeah.
I
didn't
have
time
to
really
follow
up
Terrance
on
so
I
decided
that
we
get
better
progress
when
the
code
is
running
in
and
then
be
to
get
merged
into.
This
branch
has
basically
the
same
requirements
like
to
get
merchant
master,
so
it
has
to
be
basically
production
hold,
of
course,
with
new
feature.
A
A
One
big
request
at
the
end,
the
books
of
the
API-
and
this
is
a
long-running
project
and
it's
very
difficult
to
estimate
the
way.
We
then,
when
there's
a
few
months
worker
with
the
API,
it's
even
much
long
array
and
to
avoid
this.
Yet
we
have
such
big
packages
where
the
contributors
or
the
stakeholders
need
to
walk
down.
I
prefer
that
we
have
every
months
the
delivery
and
I
would
treat
it
the
same
or
like
merge
two
masters
when
it's
merged
to
just
branches.
A
We
would
need
to
manage
all
this
domain
objects
from
the
trade
like
the
office
to
open
office,
the
trades
and
trade
protocol
classes
in
two
versions,
basically
the
normal
version
that
the
new
version-
and
it
would
be
a
nightmare
to
maintain-
and
the
goal
is
anyway,
that
we
stopped
the
old
trade
protocol.
As
soon
the
majority
of
the
users
net
start
have
moved
over
because
we
don't
want
to
run
the
arbitrator's
too
long,
maybe
two
months
or
something
and
basically
all
create
protocol
to
be
done.
A
So
it
would
not
be
worth
it
but
to
add
a
lot
of
risk,
end
and
death
toad
and
which
we
need
to
clean
out
in
two
months
late
anyway.
So
that
was
the
main
reason
why
we
decided
to
make
a
hard
work
at
the
end.
The
users
can
still
when
they
update
they.
Don't
need
to
do
anything
or
they
have
all
their
data.
A
A
I
mean
all
these
details
about
the
conceptually
from
the
neutrals,
all
the
still
questions,
open
people
question
and
how
we
do
the
housework,
especially
how
we
communicate
the
output
to
the
users.
I
got
already
their
feedback
and
so
that
people
are
very
negative
with
anything
new,
because
logical
I
mean
any
and
it
changed
carries
risk
and
when
it's
with
money,
people
want
to
avoid
risk
and
they
got
used
and
understand
now
the
old
protocol
and
that
you
need
to
learn
and
understand
the
new
protocols
which
the
challenge
I
have
not
thought
about
more
articles.
A
How
to
how
to
do
this?
How
the
process
is
how
long
it
will
work
and
so
on
I
mean
I
could
say
one
thing
as
far
as
I
know
that
if
as
soon
as
basically,
if
there
were
no
more
trades
going
on
or
actually
if,
okay,
if
there,
there
were
more,
no
more
arbitrators,
so
if
all
the
arbitrators
remove
themselves
from
the
system,
then
no
more
trades
would
be
able
to
be
done
after
that,
because
to
do
a
trade
you're
right
now
an
arbitrator
is
required.
So
that's
one
way
to
see.
A
Communes,
using
the
old
version,
yeah
I
mean
one
way
could
be
to
make
it
not
so
hard,
because
when
we
stopped
the
arbitrator's
after
two
months
so
and
some
people
want
to
use
it
yeah,
it's
forcing
and
basically
a
easier
way.
Maybe
would
be
that
we
increase
the
seats
because
I
mean
the
arbitrators
are
more
expensive.
That's
one
reason
why
we
want
to
move
the
way
because
of
them
included
risks
with
the
arbitrator's
and
when
the
arbitrator
make
a
mistake,
he
can
lose
one
Bitcoin
and
luckily
it
never
happened,
but
we
had
cases
where
earth.
A
A
So
we
could
increase
the
fees
a
lot
in
that
version,
which
is
maybe
a
little
bit
problematic,
because
we
only
can
increase
it
by
updating
the
software
and
then
people
will
not
have
to
produce,
but
that
might
be
at
least
one
way
how
we
can
have
the
soft
pressure.
Do
we
have
to
stop
users
using
the
old
version
and
move
them
to
the
new
version?
I
think
the
best
is
good
education
that
they
really
understand.
Why
we
want
to
move
away
in
other
would
be
that
we
basically
say
this:
we
are
not
supporting
it
anymore.
A
Anybody
can
run
it
work
and
provide
arbitrators,
but
then
you
have
to
trust
program
why
you
should
trust
somebody
who
is
not
with
not
building
it
up
any
reputation
or
and
with
some
random
or
anonymous
arbitrators,
so
that
might
be
maybe
even
a
better
approach
when
we
see
that
the
certain
percentage
has
more
personal
issues
still
want
to
stick,
and
they
are
very
help
to
convince
that
they
can
do
it
anyway.
Anything
anybody
could
do
this
anyway.
A
So
whatever
it's
a
open
question
or
conceptually
our
we
deal
with
this,
there
was
even
one
idea,
but
I
have
not
so
deep
about
this
to
keep
the
arbitration
in
the
new
protocol
and
by
default
they
arbitrate.
The
key
is
the
lien
on
existing
key,
like
all
theorems
or
whatever,
so
there
is
no
public
key
for
creating
this
key,
because
this
two
three
three
multi-sig
windows,
third
key-
is
invalid.
A
He
thought
I
have
not
talked
deep
about
this,
but
maybe
it
could
be
an
interesting
opportunity
to
add
flexibility
at
them
because
then
for
when
we
would
want
to
go
back
to
the
two
or
three
move
to
seek
for
whatever
reason
we
still
have
everything
in
place
and
then
the
insurance
part
is
then
just
aired
on
which
is
not
used.
Usually
those
are
the
reimbursement
thousand
so,
but
we
had
a
Greek
man,
so
there
is
more
conceptual
soft
before
getting
too
serious
about
this.
C
A
A
It
just
has
a
very
minimum
implementation
for
gate
version
or
that
works,
and
it
has
some
restrictions
like
when
you
have
set
up
a
wallet
password.
You
cannot
run
the
headless
version
at
the
moment,
because
the
support
for
this
is
missing,
but
that's
the
next
option
and
that
all
is
basically
yeah
to
get
a
minimum
version.
A
Minimum
viable
version
of
the
API
production
ready
as
soon
as
possible,
with
very
small
steps,
I
mean
the
minimum,
while
viable
version
would
be
basically
to
do
full
trade
also
to
create
an
offer
and
to
get
the
steps
required
in
the
trade
process
not
to
set
up
a
payment
account
to
make
a
transfer
from
a
wallet
or
anything
else,
but
it's
not
absolutely
required
and
before
when
we
get
it
deep
into
the
implementation
out
there.
We
want
to
softer
way
to
find
the
solution
for
secure
access
to
the
API
ends.
A
When
you
have
run
it
somewhere
in
the
cloud-
and
you
want
to
access
this
from
your
mobile
or
whatever,
how
to
do
it
in
a
secure
way-
and
we
would
like
to
that
still
in
discussion
as
I
cannot
say
how
much
about
this,
but
the
preferred
version
would
be
something
over
to
our
hidden
services
and
yeah.
We
would
like
to
get
Florian
involved.
A
Beside
that,
yeah
I
asked
Piana
to
investigate
a
little
bit.
The
effort
to
switch
through
TR
PC
Chris
would
prefer
to
not
have
a
cheapy
API
at
all
and
move
directly
to
trio
PC.
It
was
much
more
modern
and
I
cannot
say
too
much
about
that.
I'm,
not
an
expert
in
API
domain,
but
maybe
Chris
can
give
his
comments
afterwards
to
investigate
himself
or
I
started
a
very
basic
GOP
implementation
about
like.
A
If
it's
not
terrible,
much
effort,
I
would
prefer
altars
do
this
when
or
when
we
see
that
so
that
approach
otherwise
I
would
prefer
to
go
on
to
not
run
a
few
weeks
or
months
or
even
by
starting
again.
Freshly
is
implementing
another
API
and
it
could
be
any
way
when
doing
construction.
Everything
is
there.
We
could
do
that.
The
same
entry
OPC
later
as
well,
but
that's
still
up
to
discussion
and
Anna
and
Chris.
Maybe
you
at
your,
you
know,
input
to
do
something.
B
Yeah
I
can
I
can't
say
too
much
in
the
end,
because
I'm
not
doing
the
work
so
I,
you
know
I
reviewed
the
pull
request,
got
merged
I'm,
just
adding
some
of
these
thoughts.
There,
mostly
I,
want
to
make
sure
that
we're
just
carefully
considering
these
options
before
we
go
too
deep
on
on
on
anything,
I
think
we're
just
at
a
high
level
quickly.
The
idea,
with
focusing
on
on
an
RPC
based
interface
and
ERP
C,
tends
to
be
one
that
people
in
space
are
using,
but
RPC
in
general,
modern
RBC
in
general.
B
Is
you
know
it's
just
different
assumptions
when
you're
dealing
with
peer-to-peer
node
based
software
than
it
is
when
you're
dealing
with
the
centralized
web
service
that
needs
to
open
things
up,
programmatically
right,
you
know
rest
and
JSON.
They've
evolved,
like
they've,
evolved
with
certain
sort
of
flexibility,
trade-offs
and
things
like
that
and
with
an
RPC
based
infrastructure.
B
You
know
you
can
generate
typesafe
clients
in
any
programming
language
and
especially
the
G
RPC,
and
all
the
bindings
are
there
for
all
the
different
languages,
and
it's
just
you
know
with
how
important
it
is
to
do
things
correctly.
In
this
domain,
having
type
safety
across
language
boundaries
and
being
able
to
generate
clients
and
do
all
of
that
stuff
for
free
is
just
miles
better.
In
my
opinion,
bad
you
know
whatever
you're
gonna
do
to
spin
up
to
connect
to
a
quasi
restful
interface
right.
B
There's
just
lots
of
you
know
ambiguities
that
you
can
just
avoid
all
classes
of
errors
that
you
can
eliminate
in
an
hour
to
see
kind
of
environment.
So
that's
sort
of
one
thrust
for
pressing
on
that
a
bit
and
the
other
one
is
just
seeing
what
other
people
are
doing
in
the
space
right.
I've
mentioned
it
a
bunch
of
times
about
what
lightning
is
done.
You
know
you
just
see
people
who
are
you
know,
building
this
kind
of
software,
that
it's
Bitcoin
itself
or
lightning
itself.
Or
what
have
you
you
know?
B
It's
RPC
calls
all
day
long
right,
so
just
let's
not
ignore
that.
Basically,
and
with
all
that
said,
completely
agree
with
the
kind
of
follow
up
in
that
PR.
That
says,
you
know
hey
look!
A
lot
of
this
is
just
groundwork
and
infrastructure
to
get
any.
You
know
sort
of
headless.
You
know
demon
style,
eight,
the
eye
style
mode,
it's
a
fist,
all
good,
so
we
start
there
and
if
we
want
to
hit
it
to
the
Erica,
see
now
great,
it's
not
fun.
Yeah.
A
It's
a
fun
reason
why
I
push
her
a
little
bit
more
at
the
moment
was
because
people
are
using
it
already
to
HTTP
API,
and
we
had
a
reason
for
their
top.
Six
series
was
because
we're
is
receives.
The
trade
trade
sophistic
object
with
incorrect
data
with
zero
for
price
and
amount,
which
never
happened
before
and
shouldn't
be
possible
from
the
UI.
A
They
should
download
the
mobile
client,
which
probably
will
be
only
ungrate
only
so
that's
the
issue
and
problem
or
that
we
are
by
default,
going
over
tour
and
you
will
yeah
I,
don't
know
yet,
but
I
mean
to
have
excess
of
HTTP
yep.
You
need
HCBS,
let's
encrypt
doesn't
work
with
dynamic
IP
addresses,
but
you
get
a
lot
of
troubles
and
restore.
A
Everything
is
just
much
much
sure,
clean
and
and
easier
and
yeah,
but
when
we
go
with
word
and
basically
we
don't
want
that
the
users
has
to
install
it
or
browse
and
whatever
it
would
be
done
really
good
that
we
have
provided
basically
yourself
to
to
access
the
API
and
Android
application
basically,
but
the
other
problem
is
that
it
probably
will
not
easily
be
doable
on
iOS
or
not
at
all.
So
there
are
yep.
There
are
different,
open
questions
and
trade-offs
among
doin.
Well,
does
anybody
else
want
to
add
something
I
just.
C
Wanted
to
ask
regarding
because
I'm
not
so
familiar
with
G
RPC
itself,
if
it's
conceptual
wise
so
far
off
an
HTTP
API
that
we
can't
use
so
real
most
softer
and
allows
you
to
be
users
kind
of
passes,
kind
of
failure,
objects,
it's
a
I,
put
about
four
classes
back
and
forth.
With
this
binary
code
is
GRP,
see
that
the
one
from
google
yeah.
A
Yeah
yeah,
basically
defining
protobuf
objects
for
for
your
value
up
trip.
So
at
the
end
it
would
be
I
mean
it's
different
now,
they're
writing
their
custom
value
objects,
for
it
should
be
access,
and
then
you
write
it
in
the
least
effort
at
the
end
or
one
question,
maybe
Chris
you
can
say
a
little
bit
more
about
the
web,
RTC
or
Suffern
not
really
familiar
with
this
I.
B
Really
I
just
know
that
it
exists.
I
just
started
following
your
project
is
see
when
they
finally
released
it,
but
this
the
the
one
missing
piece
from
the
GRDC
puzzle
has
been
basically
HTTP
bindings.
If
you
will
you've
got
all
these
language
bindings,
you
know,
so
we
generate
a
Python
client
for
your
GRDC
application,
that's
built
in
Java
or
whatever.
It
is.
That's,
that's
all
great,
but
there's
been
no
way
to
to
programmatically
interact
basically
by
a
JavaScript
write
like
something
in
web
and
that's
and
that's
there
now,
I
really
don't
know
much
about
it.
B
I
certainly
haven't
not
taken
for
a
spin,
but
I
know.
That's
been
a
big
ask
right.
You
know
everybody
wants
to
use
your
PC
in
the
first
question.
I
ask
is,
you
know,
is
there
a
sort
of
in
a
web
client,
JavaScript
friendly
way
to
interact
the
stuff
and
until
October
of
last
year,
the
answer
was
no
in
elements
was
yes,
so
I
think
I
think
we
should
it
sort
of
one
thing
that
has
always
rubbed
me
a
little
bit
the
wrong
way
about,
starting
with
an
HTTP
API
like
I,
was
putting
that
out.
B
There
is
it's
this
in
a
way:
it's
like
a
tacit
endorsement
of
running
bisque
somewhere
in
the
cloud
right
and
and
I.
Just
don't
think
that
that's
what
we
want
to
push
on:
that's
not
sort
of
them
and
I
don't
and
I,
don't
maybe
I'm,
maybe
I've
missed
it
right,
but
I
don't
think
we
have
a
lot
of
people
a
lot
of
real
users
out
there
asking
for
this.
We
I
think
we
know
pretty.
Clearly
people
want
to
write
bots
against
bisque
and
that's
a
classic
use
case
for
the
RPC
style
approach.
B
C
A
A
I
I
have
not
looked
to
it,
how
it
works
when
you
need
to
basically
run
your
framework
in
with
some
JavaScript
library
or
whatever,
and
it
could
be
that
it
requires
more
overhead
to
get
anything
done
and
not
just
type
in
some
or
a
comment
into
the
browser
with
some
treatment
you
in
it
works
already.
So
that
might
be
a
concern
to
consider
a
little
bit
I'm,
not
sure
if
it's
important
one
but.
C
D
For
me,
my
choice
was
the
JSON
API,
because
this
is
like
really
popular.
Like
everybody
knows
about
it,
you
don't
need
any
special
introductions.
I,
don't
need
to
fetch
any
additional
libraries
or
generated
bindings
for
my
language
so
and
I
can
write
with
very,
very
well
defined
and
understood
by
everybody,
very
small,
simple
queries:
we've
got
very
nice
other
documentation
out
of
the
box
so
and
really
good
support
for
documentation,
and,
yes,.
A
A
I'm
also
wondering
how
much
effort
it
will
be
to
switch,
because
it's
only
one
small
layer
and
how
you
listen
to
requests
on
how
you
erecting
with
where
your
kids
are-
and
I
think
that's
not
the
biggest
set,
but
I
mean
I'm
a
night
for
this
year
to
get
everything
connected
with
the
Bisco
main
and
so
on.
That
can
be
an
reused
easily
I
would
I
mean
that's
a
question.
You've
got
a
lot
more.
How
much
happen!
A
It
will
be
good
to
have
a
second
version
of
the
current
or
HCP
API
development
as
a
GOP
seal
may
immediate.
When
it's
not
a
lot
of
effort,
maybe
we
can
do
it
really
parallel
that
which
every
new
feature
what
we
were
rolling
out
now
there
is
the
second
working
with
GOP
sealant
and
when
it's
not
terribly
much
effort,
why
not
do.
C
A
A
Sophistication
to
work
with
the
trio
PC
like
or
HTTP
API
I
think
that's
the
most
simple
when
a
developer,
multi
users,
and
sometimes
specially
market
maker
they're,
not
really
developers
they're,
just
they
can
figure
out
a
little
bit
with
scripts
to
get
something
working.
But
when
you
tell
them
more
sophisticated
tasks,
we
feel
that
might
be
in
elemental
Gelade.
She
being.
B
Yeah
sorry,
I
I,
just
I
personally,
have
to
run
at
the
moment,
so
I
just
want
to
say
goodbye
properly
before
I.
Do
that
one
thing
I
wanted
to
join.
This
call
for
a
few
reasons.
One
I
think
doing
the
dev
calls
starting
us
off
like
a
regular
thing,
is
a
great
idea
and
and
I
wanted
to
say,
hi
to
new
faces,
Craig
I
haven't
met
before
and
to
anybody
who
watches
this
afterward.
B
That
I
haven't
yet
met
hello
song
for
sure
no,
that
are
on
the
call
that
that
I'm
kind
of
hiatus
away
from
this
right
now.
The
reason
for
that
has
been
going
through
the
kind
of
last
phase
of
this
treatment
for
leukemia
I've
been
dealing
with,
which
is
a
bone
marrow
or
stem
cell
transplant,
and
that
was
scheduled
for
a
few
weeks
ago
and
that
actually
fell
through
the
the
donor
fell
through
there.
There's
another
donor
and
I'm
now
scheduled
to
do
that
same
transplants
at
the
end
of
this
month.
B
So
I'm
gonna
go
in
back
into
the
hospital
24th
of
this
month
in
them,
so
it
would
be
another
roughly
unfold.
Six
weeks
could
be
much
longer
could
be
a
little
less,
but
so
this
is
kind
of
a
hiatus.
Veneman
will
continue
for
a
considerable
amount
of
time,
so
I
also
wanted
to
let
everybody
know
that
and
in
the
meantime
it's
a
it's
just
great
to
to
watch
everything
happening.
I'm
not
as
plugged
in
as
I
have
been
in
the
past.
A
C
Yeah
regarding
Manfred
the
shout
out,
because
also
for
the
the
minimal
feature
set
we
want
to,
we
want
to
focus
on,
for
the
API
might
also
help.
If,
if
we
know
who
wants
to
use
it,
how
yeah
it
has
to
be
really
focused
on
a
feature
set
that
we
want
to
bring
out
because
we
know
if
it's
live,
people
are
going
to
use
it.
Yeah.
A
D
D
A
A
Soon
as
possible,
basically
we
have
this
proposal
soon
and
then,
where
you
will
input
from
experts
and
implemented,
but
ya
know
I'm
also
thought
of
I
created.
This
branch
is
to
get
it
free
contract
now
and
not
get
lost
all
the
time
and
and
and
of
course
it's
it's
I
mean
the
main
bottleneck,
because
I
need
to
do
the
review
at
the
testing
and
so
on.
A
C
A
A
Think
there's
no
way
around
this
and
the
only
solution,
but
I
find
that
the
moment
is
to
have
a
second
or
release.
So
the
users
can
be
fine
if
you
want
to
release
a
standalone
desktop
or
two
desktop
a
CPI
which
carries
a
little
bit
more
risk
from
all
this
dependences
and
yeah.
It's
not
a
clear
opinion,
but
just
a
gut
feeling
that
I
don't
like
to
get
too
much.
A
Dependence
is
from
huge
frameworks
where
we
have
no
clue
what's
going
on
in
those
frameworks
in
which
winner
billet
is
they
might
carry
and
by
reducing
it
to
just
those
few
users
who
are
using
the
API
stats.
Maybe
a
few
percent
of
the
excuses.
We
would
reduce
a
lot
to
attack
the
risk
surface
for
this
and
x-ray
for
this,
of
course,
that
we
have
to
double
effort
with
releases.
A
But
when
it's
better
automated
that
you
just
click
a
button
and
maybe
also
there
the
VM,
startup
and
everything
could
be
maybe
done
more
automated
by
docker
containers
or
whatever.
And
then
it
doesn't
really
matter.
And
if
you
wait,
10
minutes
or
15
minutes
for
getting
books
releases
out
might
be
a
way
to
go.
But
we
had
discussed.
C
A
It
could
be,
you
would
an
able
API
by
a
special
program.
Element
use,
HTTP
I
is
true,
and
then
you
could,
then
you
could
access
you're
yeah,
all
the
features
which
are
open
with
API
over
the
API,
and
you
run
your
desktop.
So
you
have
your
desktop
running
and
you
can
type
in
get
balance
and
you
will
see
the
balance
in
its
statement.
A
You
cannot
use
it
in
parallel,
so
you
cannot
start
the
headless
version
on
the
same
machine
and
the
desktop.
That's
the
same,
like
you
cannot
start
two
times
the
desktop
and
there
would
be
a
danger
in
risk
and
we
have
to
be
make
sure
for
our
users
to
not
run
the
scene
tape
the
director
in
parallel
on
the
server
headless
and
locally
desktop
and
then
doing
parallel
stuff.
We
get
Auto,
sick
and
messed
up
pop
quiz.
So
that's
one
challenge
to
communicate
this
very
clearly
that
users
are
doing
this
mistake
yeah.
A
C
Say
for
a
near
future
on
plan
is
bug
fixing
list,
so
we
still
have
a
couple
of
back
reports
and
issues
in
our
github
repository
and
I'm
trying
to
go
through
and
fix
everything
before
I
was
studying
thing
you
I'm
going
to
the
first
user
interface,
which
will
be
a
bigger,
bigger
task
or
feature
set.
I
also
want
to
focus
on
performance
in
parallel,
so
we
we
do
have
from
time
to
time
reports
regarding
CPU
usage
or
memory
usage,
and
especially
if
people
want
to
use
bisk
on
devices.
C
However,
devices
that
have
lower
half
available
I
think
we
can
still
put
a
squeeze
out
some
lots
of
performance
from
the
existing
client,
but
yeah
I
would
just
kind
of
time
box
and
to
see
if,
if,
if
there
are
some
easy
steps
where
we
can
get
in
some
performance
and
yeah
after
that,
actually
I'm
I
will
just
have
to
think
about
again.
After
the
first
user
experience
is
done,
then
I
have
to
sit
back
and
to
see
what,
where
we're
going
next,
but
think
if
the
experience
to
implement
in
a
proper
way.
A
Yeah
great
yeah,
mr.
new
design,
everything
went
super
well
and
only
super
positive
feedback,
I
think
April
or
seemed
to
be
a
little
bit
more
available
and
at
the
moment.
So
maybe
we
can
use
this
time
for
getting
feedback
that
he's
reviewing
or
the
current
application
and
good
happy
that
I
can
change
forever.
That's.
C
A
Great
another
erase
yeah,
we
didn't
have
a
lot
of
time,
unfortunately
relay
to
do
a
lot.
There
I
mean
we
fix
this.
There
was
a
bigger
other
into
how
nothing
really
crazy
about
for
a
user
pretty
good,
because
you
got
error,
messages
displayed
lieutenant,
that's
fixed,
so
everybody
who
is
updating
its
updated
to
the
latest
version,
and
maybe
they
need
to
clean
up
their
local
safe
during
in
the
forum.
A
Our
instructional
do
that
everybody
is
very
welcome
to
how
testing
or
it
just
looks
before,
and
there
were
only
one
or
two
other
persons
who
have
created
proposal.
So
at
least
every
body
who
is
a
contributor
used
at
our
intestinal
and
help
us
testing
its
your
you
out
of
this
when
we
up
or
when
we
go
live
Mississippi.
A
If
you
will
might
have
no
value-
and
you
have
not
done
anything
so
please
help
us
to
avoid
this
scenario
and
yeah.
We
are
still
mainly
focused
at
the
moment
on
stupidness
stability
issues
with
the
seed
nodes
with
the
explora
nodes.
I'm
started
yesterday
to
build
their
own,
monitor,
node,
based
on
the
old
monitor.
A
What
I
have
to
monitor
important
states
of
the
Tau
and
at
monitor
all
the
two
signals
into
to
explore
notes
what
we're
running
at
the
moment
and
also
we
would
like
to
get
the
kind
of
in
a
chain
of
hashes
of
the
state
of
the
tower.
So
with
every
new
block,
when
a
block
has
been
passed,
there
is
a
unique,
unique,
unique
state
of
the
whole
thousand,
and
that
can
be
hatched
in
the
hash.
A
Hashes
are
basically
chained
together
in
a
kind
of
like
a
block
chain,
and
we
can
compare
and
you
to
your
client
could
be
if
you
request
this
hash
chain
of
hashes
from
many
other
nodes
and
see
if
you're,
up-to-date
or
if
you
have
to
think
and
if,
if
they
don't
match,
something
went
wrong.
But
we
will
help
us
to
detect
earlier
when
anything
goes
wrong,
and
sometimes
our
Altos
link
or
whenever
just.
A
Yeah,
so
this
will
be
a
kind
like
a
custom.
I
just
call
it
an
option,
because
yet
it
will
be
dedicated
to
each
block
if
there
is
a
hash
which
represents
the
holdout
and
they
are
chained
together,
one
bucket
to
follow
the
other
blocks,
and
that
would
be
a
network
data
object
where
it's
more
long,
because
it
basically
contains
only
this
hash
and
maybe
the
pointer
to
the
to
the
block
cache
block
height.
A
A
So
when
you
make
a
transaction
in
PS
q,
if
we
only
verified
when
the
block
when
it's
mined
in
a
block
and
that
would
decrease
usability,
especially
for
fee
payments,
when
you
create
a
lot
of
authors
in
parallel
and
your
PS
q
are
taken
for
as
impotent
and
as
a
change
output,
the
change
output
is
not
verified
until
it's
confirmed
and
you
cannot
reuse
it.
So
we
want
to
allow
this
that
your
own
change
output
is
trusted
and
you
can
use
it
as
an
input
for
the
next
transaction.
A
That's
a
little
bit
tricky
and
or
complex
and
dangerous,
but
hopefully
we
get
this
animals
before
the
main
that
release
and
another
open
who
regrets
is
to
avoid
that,
because
Q
get
burned.
If
anything
goes
wrong.
Yeah
we
had
seen
already
some
packages
which
were
not
intended
attacks
or
whatever
we're
just
something
was
messed
up
because
of
usability
or
behavior
and
then
PS
q.
The
transaction
became
invalid
because
something
was
wrong
and
then
we
don't
want
to
go
into
these
two.
It
should
be
basically
a
cut
like
a
Arabic
yeah.
A
What
winter
is
new
state
irregular
state
as
it's
a
transaction
like
a
compensation
transaction
where
the
payload,
the
PPO
network,
data's
missing?
So
it's
not
really
a
well
it
transaction.
It
will
not
be
considered
for
a
compensation
request,
but
we
still
don't
want
to
burn
it,
and
the
piece
few
which
are
included
here
have
to
be
available
for
normal,
something,
and
so
on
that
mean
another
main
thing,
and
the
emergency
tools
have
not
sought
deeper.
C
A
I
don't
expect
it
will
be
before
March
or
I
mean
I.
The
moment
I
only
can
spend
something
like
20%
of
my
time
under
Tao
is
required
for
managing
other
contributors
and
all
these
other
projects,
and
so
on,
and
that's
needed
as
well
and
I
cannot.
I
cannot
be
kept
on
like
for
the
other.
Coaches
at
the
end
cannot
proceed
and,
unfortunately,
that's
doesn't
help
a
lot
to
get
progress
on
the
table,
but
it's
the
situation.
A
Otherwise,
maybe
let's
wrap
up
here
yeah
for
any
developer
with
listening,
it's
called
feel
free
to
join
us
to
learn
more
about
the
pissed
about
the
peace
project
itself.
There
are
a
lot
of
documentation
cells
on
our
talks.
Web
page
was
a
talks.
This
network,
you
will
find
introduction
for
a
new
developer.
What
to
read
up
and
to
get
run
about.
We
have
the
Tau
already
running
since
more
than
a
year.
It's
not
really
money
at
the
moment.
A
You
cannot
sell
it
on
the
market,
but
you
can
run
already
feels
to
you
and
we're
doing
this
monthly
compensation
request.
So
whatever
you
want
to
earn
you're
making
a
request
for
this
and
the
other
stakeholders
will
decide
if
they
accept
or
reject
this
request,
and
so
you
can
run
already
potential
money.
It's
not!
You
cannot
convert
it
to
Bitcoin
at
the
moment,
but
when
we
go
live
you
can
sell
it
them
and
yeah.
We
are
looking
only
for
senior
developers
at
the
end.
A
We
don't
have
resources
to
get
on
board
or
two-year
developers
and
how
to
new
developers,
because
it's
mediate
as
well
for
the
whole
ecosystem
to
help
junior
developers
to
get
deeper
into
this
topic
sells
on.
But
we
don't
have
the
time
and
resources
to
spend
time
on
this.
So
are
anybody
who
is
already
experienced
with
one
of
those
domains
where
we're
working
on
Bitcoin,
peer-to-peer,
basic
application,
development
or
UI.
A
Cryptocurrency
system,
design,
like
with
the
Dow
and
general
Java,
was,
is
very
welcome
to
join
us.
We
could
need
more
deaf
power,
even
we
already
now
pretty
really
good,
with
five
full-time
developers
and
three
four
out
on
developers,
not
so
bad,
but
a
lot
to
do
still
and
any
helping
hand
is
very
welcome.
A
Goodie
then,
let's
stop
in
here,
or
we
will
have
our
next
call
next
Wednesday
at
two
o'clock:
Central
European
Time
again,
if
anybody
want
to
change
the
time
for
another,
just
feel
free
to
initiate
for
finding
out
that
another
slot
slot
where
it's
possible.
Unfortunately,
Devon
cannot
join
at
this
time,
would
be
nice
exciting
here
as
well,
but
it's
very
difficult
to
find
a
slot
which
works
very
about
it,
but
I'm
a
community
open.