►
From YouTube: Tech Session #4: Bisq wallet and BitcoinJ
Description
Manfred provides a technical overview of Bisq's Bitcoin wallet and use of BitcoinJ.
Slides: https://docs.google.com/presentation/d/1LLiQ55KT2hw9NOxlP-xIsMyke5CaMZsBx9e83JN72Wo/edit#slide=id.g3760b215e6_0_27
Previous tech sessions: https://www.youtube.com/watch?v=ulmUVh3XjRg&list=PLFH5SztL5cYOtcg64PntHlbtLoiO3HAjB
New contributor checklist: https://docs.bisq.network/contributor-checklist.html
A
Hey
welcome
everybody
to
this
fourth
bisque
text
session.
If
this
is
the
first
one,
you're
joining
we've
been
doing
this
series
now
for
a
few
weeks
couple
months,
even
starting
with
the
general
technical
overview
of
all
things
bisque,
then
we
went
on
to
talk
about
this
experiment
work,
that's
the
second
tech
session.
A
If
you're,
if
you
have
a
literally
running
core
node
and
much
more
to
say,
I'm
gonna
hand
this
over
in
just
a
moment
to
Manfred
whose
is
going
to
present
the
deck
on
it.
This
should
be
fairly
short.
Today
will
probably
go
30
minutes
or
45
minutes.
If
you
have
questions,
ask
them
as
you
go
along
and
maybe
keep
them
in
mind
and
we'll
go
through
any
questions.
We
don't
go
to
during
the
talk
toward
the
end.
A
I'll
also
write
me
in
the
in
the
show
notes
below
I
haven't
done
it
yet
I'll
put
a
link
to
the
previous
tech
session
so
that
everybody
can
see
that
we
also
just
put
together
a
contributor
checklist
on
the
new
Docs
that
this
got
Network
website
yesterday.
Maybe
some
people
have
already
seen
that,
but
that's
a
great
way
to
like
kind
of
fast-track
your
way
onto
getting
everything
you
need
up
and
running
and
ready
to
go.
B
We
yeah
there
are
some
ideas
and
considerations
to
move
away
from
bit
country
because
mainly
of
these
privacy
issues
and
can
talk
a
little
bit
which
outlet
is
out
there
and
then
about
open
tasks.
What
should
be
done
in
this
area
and
of
course,
at
the
end,
our
time
for
questions,
yeah
I,
don't
want
to
get
into
very
details
about
what
this
SPV
was,
is
HT
wallet
and
so
on.
If
you
don't,
if
you're
not
familiar
with
this,
there
are
plenty
of
resources
out
there
to
learn
about.
B
It's
a
think,
I'm
not
hard
person
to
if
it's
really
their
only
child
implementation
for
Bitcoin,
more
or
less
feature
complete
I
mean
Bitcoin.
Shake
could
also
run
as
a
completely
full
note,
but
I
think
it
was
never
designed
for
this.
It
was
never
really
test
it.
So
it's
probably
not
very
mature
and
feature
complete
in
that
area,
but
it's
pretty
mature
as
SPV
wallet.
B
It's
used
in
many
implementations
like
the
Android
or
Bitcoin
wallet
for
mobile
samurai
wallet
using
it
multi
bit
there
plenty
of
of
wallet
providers
which
are
based
on
Bitcoin
shape
and
it's
out
since
many
years,
so
it's
kind
of
like
battle-tested.
Unfortunately,
it's
not
very
well
up
up
to
date
with
the
latest
features
for
various
reasons.
Probably
main
reason
is
just
lack
of
resources,
but
I
think
other
reasons
are
a
little
bit
political
differences
to
the
camp
or
to
that
what
Bitcoin
core
is
pushing
in
and
and
representing.
B
B
Yeah
there
have
been
last
year.
They
have
been
this
attacks,
this
several
Forks,
especially
with
speed
two
weeks.
It
was
quite
the
serious
attack
where,
if
they
would
have
succeeded,
there
are
SPV
wallets
like
bit.
Country
would
could
have
moved
over
to
another
coin,
to
be
two
weeks,
because
it's
blindly
following
along
this
chain,
which
is
pretty
problematic,
which
would
not
be
very
difficult
to
fix,
but
it
seems
also
there
is
not
in
no
intention
so
some
people
say
no.
The
longest
chain
is
Bitcoin,
even
if
it
has
broken
their
the
other.
B
Their
basic
rules
like
their
limitation
after
one
megabyte
block
size,
and
that
was,
for
instance,
for
us.
The
reason
why
we
introduced
our
provided
note,
because
when
this
would
have
happened,
it
would
have
been
a
mess
suddenly
or
Bitcoin
would
have
turned
to
beat
weeks
without
notifying
you
and
without
your
knowledge
and
so
on.
B
I
don't
want
to
get
into
more
details
about
this,
because
that's
kind
of
like
a
past
story
and
it
doesn't
seems
that
it
seems
that
they
failed
with
those
attempts
and
I
hope
that
they
will
not
repeat
it,
but
they
showed
that
bit.
Crunchier
is
kind
of
like
a
a
weak
element
in
our
in
our
infrastructure,
because
yeah,
when
did
would
that
have
we
would
have
had
a
lot
of
troubles
and
security
risk
and
damage.
A
A
So
we
have
our
own
Federation
if
you
like,
of
Bitcoin
core
nodes
like
man
that
was
described
and
reasonably
just
wanted
to
pause
here
and
call
this
out
is
that
this
is
one
potential
way
that
somebody
could
contribute
to
bisques.
Overall
Bitcoin
support
is
is
being
responsible
for
making
sure
that
there's
you
know
common
configuration
that
those
nodes
are
tuned
and
always
taking
advantage
of
whatever
the
latest
options
are
and
so
on
whether
it's
dealing
with
sort
of
men
full
size
or
what-have-you.
A
A
B
After
the
next,
when
I
explained
a
little
bit
the
problem
with
the
bloom
filter,
it
gets
a
little
bit
more
clear
why
this
provided
node
makes
sense
for
us
I
mean
yeah
enter
problematics
around
it.
We
describe
also
yeah
bloom
filters
are
a
probabilistic
data
structure.
You
can
also
read
it
up
in
the
wiki,
it's
quite
complicated,
but
in
a
nutshell,
or
a
non-technical
description
which
is
not
correct
but
which
represents
more
or
less
for
how
and
why
they
are
used
in
bit.
B
Country
is
to
yet
to
have
a
more
compressed,
also
explain
it
how
they
are
used,
Pitkin,
a
sense,
a
bloom
filter
to
full
node
yeah.
It's
usually
connected
to
around
ten
full
nodes,
random
notes
in
there
in
the
Bitcoin
network,
and
and
tell
those
notes,
I'm
interested
in
all
transactions,
which
are
which
the
full
node
see
in
the
network,
which
are
relevant
to
my
addresses
in
my
wallet
when
Bitcoin
she
would
send
all
the
addresses
of
its
wallet
to
the
full
node.
Of
course,
you
lose
a
lot
of
privacy.
B
We
don't
yet
I
didn't
want
to
do
this,
so
they
introduced
the
bloom
filter.
Beside
of
more
compact
data
structure,
it
provides
a
kind
like
a
privacy
feature
that
you
can
at
a
false-positive
rate,
so
kind
of
like
your
blurring
your
data,
what
you're
sending
to
the
full
node
and
technically,
it's
not
correct,
like
I,
described
it,
but
it's
a
little
bit
like
you
are
sending
hundred
real
addresses.
B
Additionally,
with
hundred
fake
addresses,
the
full
node
doesn't
know
which
one
other
real
and
which
one
of
the
fake
as
a
technically
it's
it's
different,
because
it's
a
it's
it's
binary,
Gator
with
hashes
and
so
on,
but
conceptually
it's
somehow.
Some
are
like
that,
and
that
would
give
you
some
additional
privacy.
B
If
it
really
would
be
implemented
correctly
and
on
the
other
side,
I
mean
it
would
not
even
give
you
a
real
privacy
if
it
would
be
implemented
correctly,
because
it's
conceptually
problematic,
because
the
full
node
with
the
transactions,
what
you
get
over
time,
when
you're
receiving
new
transaction
yeah,
you
can
construct
the
graph
and
it
can
figure
out
which
really
or
transactions
your
addresses
and
which
are
fake,
addresses.
But
much
worse,
like
this
and
easier
to
understand,
are
a
few
terrible
flaws
in
the
bloom
filter.
B
One
is
that
there
this
this
integer,
which
is
used,
is
random.
Nonce,
which
is
used
for
the
for
this
random
factor
is
not
persisted
to
every
startup
of
the
wallet
you're,
creating
a
new
one,
so
the
random
part
will
be
always
different.
The
real
part
will
be
always
the
same,
a
full
note
which,
which
remembers
the
connection
from
your
note,
which,
especially
for
the
other
wall,
it's
much
more
problematic
because
they
don't
use
tor.
So
they
know
your
IP
address
to
just
can
map
it.
B
With
your
IP
address
one
day
you
sent
the
bloom
filter
with
those
hundred
real
address
in
hundred
fake
addresses
the
next
day
you
send
again
100
real
and
other
hundred
fake.
He
make
an
end
of
both
and
see
which
were
the
matching
one
which
are
the
same.
Those
are
the
real
address
in
all
those
which
were
not
matching
were
a
fake
address.
B
They
were
only
pay
to
pop
key
and
not
free
to
pop
key
hash
and
I'm,
not
aware
if
there
are
still
any
applications
which
are
using
pay
to
pop
key,
because
Peter
Parker's
private
security
issues
as
well,
and
it's
basically
considered
bad
practice
and
bit
conscious,
sending
both
to
the
full
node
and
the
full
node
can
when
it
gets
a
transaction.
You
can
derives
from
the
pop
key
in
the
transaction
to
pop.
B
The
hash
can
look
up
if,
in
the
bloom
filter
is
post
a
pop
key
and
the
pop
T
hash,
then
it's
a
real
address.
Otherwise,
it's
a
fake.
The
fake
is
not
really
address
it,
just
other
data
which
couldn't
randomly
met
to
some
transactions
or
to
some
addresses,
but
it's
very
unlikely
that
it
would
map
to
both
the
pop
key
at
the
pop
key
hash
of
another.
So
that's
another
very
efficient
way
to
basically
to
clean
up
the
there
intentionally
edit
randomness
and
remove.
Basically
all
the
privacy
features.
B
So
it's
pretty
bad
because
you
can
assume
that
there
are
plenty
of
chain
analysis
nodes
out
which
are
which
are
collecting
all
kind
of
data
for
data
analysis
and
selling
it
to
governments
and
banks,
and
they
are
running
full
nodes
when
you
are
connecting
blindly
to
the
peer-to-peer
network,
you
are
very
likely
get
connected
to
one
or
two
or
more
of
those
nodes.
They
are
collecting
your
bloom
filter
data
and
at
the
end
they
know
more
or
less
very,
exactly
which
addresses
belong
to
your
wallet.
B
They
don't
I
mean
with
other
implementations,
it's
even
worse
because
they
know
your
IP
address.
We
speak
yeah
we're
behind
tor
when
you
use
tor,
also
in
biscuits
optional.
It's
by
default,
enabled
that
you
go
over
tor
to
the
Bitcoin
network,
but
you
can
disable
it.
So
when
you
want,
when
you
have
very
bad
bandwidth
or
whatever,
or
when
you
don't
care
about
this,
then
your
IP
address
would
be
visible
as
well,
but
even
without
IP
address
or
as
long
as
one
address
is
identified
with
your
identity.
B
When
you
have
used
this
address
for
buying
Bitcoin,
honest
and
crossed
exchange,
and
to
get
this
data,
they
can
basically
derived
that
all
the
other
addresses
belongs
to
this
identified
person.
So
it's
really
a
serious
privacy
issue.
I
wrote
a
blog
post
about
this
year
ago.
I
have
it
at
the
end
and
the
links
in
the
references
you
can
read
about
more
in
details
and
yeah
this
Bloomfield.
B
The
problem
is
my
main
problem
with
bit
country:
try
to
fix
it,
but
it
was
a
little
bit
more
complex
and
I
didn't
succeed
at
the
end
and
it
didn't
had
time
to
step
deep
into
it
and
our
current
solution
for
navigating
around
this
as
well.
That
was
basically
in
started
with
this
attack
last
summer,
which
be
two
weeks
that
we
are
running
provided
nodes
by
trusted
bisque
developers.
Of
course,
we
introducing
a
centralization
issue
in
a
way
because
there,
now
you
are
trusting
some
developers
and
it
shouldn't
be
basically
the
case.
B
B
It's
on
so
when
the
new
users
downloading
disk
a
he
has
enabled
tor
and
using
only
those
provided,
Bitcoin
nodes,
because
it
would
be
enough
when
you
have
one
time
the
first
time
when
you
start
up
bisk
when
you
would
connect
without
torrent
to
the
public
network-
and
you
are,
you
are
connected
to
one
of
those
gene
analysis
nodes.
You
have
lost
already
a
privacy
and
you
cannot
undo
this
afterwards.
B
So
it's
important
that
we're,
starting
with
the
highest
privacy
when
user,
for
whatever
reason
want
to
go
back,
they
can
disable
this
and
connect
to
the
public
network
or
connect
to
the
localhost
or
to
their
own
Bitcoin,
core
node,
which
run
on
a
server
or
whatever,
that's
for
sure
the
best
version.
But
most
people
don't
do
this.
For
convenience
reasons
and
yeah,
that's
all
this
story
around
why
we
are
why
we
are
running
something
like
10
or
12
nodes.
B
All
those
people
who
are
running
those
nodes
are
well-known
from
from
me
from
the
core
developers
and
trusted,
and
so
we
can
be
sure
that
those
notes
are
not
operated
by
chain
analyzes
company
and
that
you
have
reasonable
privacy
yeah.
As
I
said
you
can,
when
you
have
a
local
Bitcoin
core
node
running
and
you
are
starting
up
bisque
then
you're
automatically
connecting
only
to
this
local
host
node.
So
that
gives
you
the
best
privacy,
of
course,
and
yeah
we
have.
B
The
way
how
its
implemented
in
Pitkin
shape,
the
the
most
important
or
extra
implementation
is
the
support
for
pip
44
a
year
ago,
when
I
edit
it
or
it
was
not.
It
was
just
started
a
supporting
bit
country,
but
it
was
not
feature
complete,
I'm,
not
sure
how
is
the
state
today?
That's
the
open
task,
and
especially
also
to
review
my
implementation,
because
it
was
done
a
little
bit
too
fast
and
probably
a
little
bit
open
risk
if
there
are
issues
there,
but
so
far
we
have
not
discovered
anything.
B
B
B
You
could
always,
you
would
always
lose
privacy,
so
even
if
it
would
be
perfectly
implemented,
it
would
be
still
bad
for
privacy,
and
there
are
it's
basically
in
the
Bitcoin
core
camp
and
I
ever
got
a
regretted
that
that
was
ever
added
to
Bitcoin
and
there
are
some.
There
is
some
work
in
progress
with
client
side
bloom
filters.
B
That
means
basically
that
for
every
block
a
bloom
filter
gets
created
when
you
are
starting
up,
you're
collecting
all
the
bloom
filter
from
the
whole
blockchain,
that's
quite
a
bit
of
data,
but
it's
not
super
terribly
bad
I.
Think
it's
something
like
maybe
a
gigabyte
or
less,
and
then
you
are
picking
up.
Then
you
can
make
a
check
which
transaction
which
blocks
interesting
for
you.
With
your
with
your
addresses
locally,
then
you
don't
need
a
false
positive
rate
at
all.
B
You
cannot
have
received
any
money
on
your
address
before
you
have
created
your
wallet
because
all
addresses
are
new,
so
you
basically
only
start
from
the
wallet
creation
page
and
in
practice.
I
think
it
would
be
really
too
evil
stuff
and
you
don't
need
to
download
a
gigabyte.
You
maybe
need
to
download
hundred
megabyte,
but
that's
also
which
country
when
you're,
not
in
sync,
it
can
take
quite
a
bit
of
time
to
download
the
required
data.
It's
quite
slow,
yeah.
B
This
other
implementation
flaws,
which
I
tried
to
fix.
Well
I,
think
it's
not
very
when
somebody's
really
familiar
with
speed
country
as
library
as
the
library
I
think
it
would
not
be
too
hard
to
fix
it.
But
at
the
end
of
course
it
will
never
be
a
perfect
fix.
So
it's
the
question.
If
we
should
really
put
effort
in
something
which
doesn't
really
help
too
much,
it
would
help
a
little
bit.
B
I
think
it
would
makes
it
will
make
it
a
little
bit
harder
at
least
to
to
find
out
which
addresses
belongs
to
one
user
and
maybe
reduce
sister,
the
ability
of
the
correctness
yeah
pip
44.
The
basic
idea
we
spit
44
is
that
there
was
added
extra
passes
in
their
structure
in
the
tree
structure.
After
after
derived
keys,
so
yeah
with
HD
wallet,
you
have
a
master
key
root
key
and
from
them
I.
B
Don't
remember
exactly
how
the
passes
are,
but
you
have
a
kind
like
a
few
layers
of
tree
branches
and
mp44
added
extra
branches
for
for
defining,
for
instance,
special
color
coins
like,
and
there
is
a
registration
page
where
you
can
do
this.
Where
can
register
your
coin?
We
did
this
as
we
have
the
number
142
for
psq
and,
and
it
helps
just
that
you
are
yet
that
you
are
separating
this
wallet
from
other
implementation.
B
I
explain
a
little
bit
why
we
use
it
for
for
us
with
PS
cube,
because
we
wanted
to
have
one
root
key
for
the
whole
wallet
as
one
seed
words.
We
didn't
want
that
the
user
need
to
have
maintain
two
seed
words
and
two
passwords
and
everything,
but
we
still
want
to
have
two
wallet
files
just
for
a
little
bit
of
extra
security
that
are
yeah
when
I'm
files
get
corrupted
or
whatever
then
packing
up,
and
with
this
we
have
basically
the
same
root
key.
B
But
then
we
have
two
branches:
one
branches
for
a
Bitcoin
apart,
which
has
a
reduced
the
coin,
tap
as
well,
I
think
it's
one
or
something,
and
then
we
have
another
branch
for
tour
for
142
with
for
the
bisque,
for
the
psq,
our
wallet
and
when,
when
a
user,
boot
would,
for
instance,
use
the
seat
words
to
recreate
a
wallet
on
in
another.
In
another
application,
then
he
would
not
be
able
to
access
their
psq
address
and
would
not
be
able
to
spend
and
do
any
any
mistakes
with
the
psq
address.
B
The
main
motivation
were
there:
we
avoid
that
users
who
are
not
well
enough
informed.
They
think.
Okay,
it's
HT
wallet,
I
just
put
in
my
seat
words
in
another
in
another
wallet
and
then
I
can
spend
my
psq
and
they
would
have
destroyed
the
bsq,
because
when
you
are
spending
the
PS
q
tokens
in
an
incorrect
way,
you
are
burning
them
you're,
making
them
invalid,
and
that
would
would
have
nearly
for
sure
what
happened
when
you,
when
you
user,
would
do
this,
and
with
this
model
we
have
a
built-in
protection.
B
It
would
be
just
not
recognized.
You
would
need
to
have
a
another
wallet
which
supports
before
44
and
then
you
need
to
know
there
is
in
this
coin
type
and
map
it
there.
Then
you
could
recreate
it,
but
then
you
already
know
a
lot
about
how
it's
done,
and
then
you
should
know
that
you
should
not
spend
our
the
addresses
from
another
wallet
where
it's
not
implemented
the
way
how
bsq
tokens
are
working
yeah
in
bisqui.
B
We
want
to
maintain
the
state
of
addresses
which
are
used
in
the
trade
protocols.
So
when
you
are
creating
an
offer,
you
are
your
yeah
you're.
Creating
this
take
this
maker
free
transaction
and
the
output
1
output
of
the
maker
free
transaction
is
exactly
the
money.
The
Bitcoin
amount.
What
you
need
for
when
somebody
is
taking
you
off,
because
when
you
would
not
reserve
this
and
in
the
meantime
you
would
spend
this
earth
defense
and
somebody
will
take
your
it
will
fail
because
you
don't
have
the
funds
anymore.
B
So
it's
important
that
we
are
kind
of
like
protecting
and
reserving
certain
our
transaction
outputs.
It
was
unfortunately,
a
mistake,
a
conceptual
mistake
that
I
used
addresses
instead
of
transaction
outputs.
Here
you
mean
it
didn't,
have
really
big
consequences,
but
regretted
F,
dentists,
that
way
and
yeah-
and
we
are-
we
are
keeping
track
of
those.
We
are
basically
attaching
a
context.
A
context
can
be
like
funding
or
funding
trade
or
reserved
for
offer
or
later,
when
it's
in
a
multi-sig
or
put
a
payout.
B
All
this
Etra,
which
are
used
in
one
trade,
get
a
certain
context,
get
basically
a
Maitre
tape
made
to
data
attached
and
we
are
maintaining
the
state
of
this
in
a
separate
in
a
separate
violence.
It's
just
a
protocol
for
file
which
gets
persisted
to
disk
and
that's
the
second
thing.
What
I
regret
to
have
done
it?
B
B
Yes,
as
it
was
already
our
audio
tipple
for
for
you,
I'm,
not
the
super
fan
of
bit
country
I.
Think
it's
for
Java,
probably
the
only
and
the
best
solution,
but
or
with
all
the
privacy
issues
and
also
a
little
bit
this
different
political
fuse
like
for
instance,
yet
they
are
not
supporting
where
I
I'm
not
aware.
B
If
there
are
plans
for
supporting
replaced
by
fee,
but
I
know
in
the
past,
bit
country
was
done
by
my
current,
and
my
current
was
very
opposed
to
to
beat
the
thought
to
was
the
main
driver
behind
replaced
by
fee
and,
as
we
know
now,
with
the
problems
with
high
fees
replaced
by
fees.
A
super
important
feature
for
a
working
feel
market
that
you
can
negotiate
better
on
your
site,
basically
and
yeah.
What
are
the
alternatives
and
one
alternative
for
me.
B
B
So
maybe
we
could
use
his
fork
and
it
would
work
sufficiently,
but
hopefully
it
will
be
completed
really
and
merge
into
Bitcoin,
and
it's
basically
that
he
tries
to
optimize
everything
to
make
to
make
it
possible
to
run
Bitcoin
core
as
a
light
client
in
a
way,
so
it
combines
pruning
at
compare,
apply,
combines
already
introduced
new
strategies,
block
download
and
a
block
header
download.
So
you
would
start
from
the
robot
as
far
as
I.
B
B
So,
basically,
for
Pisgah
would
like
to
have
it
optional
that
a
user
don't
need
to
download
the
full
production
even
later,
when
it's
not
so
critical
anymore
and
I'm,
not
hundred
percent
sure
how
they
deal
as
I.
Don't
have
bloom
filters,
I
think
they
probably
would
deal
with
this
client-side
bloom
filter
concept,
but
I'm
not
on
a
percent
or
sure,
and
it
would
need
some
more
investigation
to
see
if
it's
really
feasible,
if
it
really
would
be
okay
for
our
use
case
that
it
doesn't
require
a
lot
of
bandwidth
and
CPU
resources
and
disk
space.
B
B
We
would
just
are
at
the
binary
to
the
we
would
ship,
the
Bitcoin
co-op
binary
or
there
to
teaming,
and
we
would
come
communicate
over
RPC,
probably
or
something
else
with
this
binary
seem
like
what
we're
doing
with
tor
there,
where
we
have
a
TCP
channel
the
control
channel,
to
communicate
with
tor,
and
in
that
way
the
user
don't
see
anything
or
it
doesn't
need
to
install
Bitcoin
core
or
whatever
it
just
comes
with
application
and
free
user.
Basically,
it's
not
the
difference.
B
Another
option
might
be
nitric
neutrino,
which
is
used
for
a
lightning
application,
I'm
not
familiar
with
it
and
doesn't
know
anything
basically,
but
somebody
mentioned
it,
and
it
seems
that
interesting
or
SPV
implementation.
There
is
a
scholar,
implementation
out,
I
post
there,
the
github
link
at
the
end
of
the
slides
I
have
not
looked
to
it,
but
it
seems
it's
under
active
development,
so
might
be
interesting
to
check
out
one
day.
It's
probably
a
high
risk
to
move
to
a
to
another
implementation,
which
is
not
already
really
used,
because
there
could
be
tons
of
facts.
B
B
They
also
work
with
own
for
work.
They
have
already
implemented
SEC
with,
and
probably
they
have
fixed
some
of
the
privacy
issues
as
well
and
I.
Think
also.
We
are
sharing
a
lot
of
common
ideas
and
and
and
we
have
philosophy
about
privacy
and
about
decentralization
with
the
samurai
Wallach
guys,
so
it
might
be
also
interesting
to
join
effort
with
them
and
try
to
to
improve
all
the
weak
areas
and,
theoretically
also
this
blue
filter
problem
could
be
solved.
It's
just
a
lot
of
effort.
B
I
mean
could
be
implemented
to
use
this
client-side,
bloom,
filtering
and
and
change
all
this.
It's
just
huge
effort
and
we
at
the
current
set.
Of
course,
we
don't
have
the
resources,
but
when
we
find
the
dedicated
developer,
who
take
over
responsibility
for
that
error,
that
would
be
great,
and
then
we
can
work
on
improvements
on
this
and
we
have
basically
really
pressure
with
with
we
secrete
as
soon
as
bit.
Crunchier
has
full
sec
we'd
support.
B
B
We
don't
need
to
do
anything,
but
it
might
be
that
it's
still
not
fully
implemented,
and
then
we
have
to
port
our
changes
there
and
that
will
be
will
be
a
little
bit
a
problematic
approaches
and
to
get
our
changes
in
in
merchant
2
into
the
main
branch.
So
that's
also
quite
a
lot
of
effort.
I
will
not
really
have
time
for
this,
so
when
any
developer,
who
is
familiar
with
bit
country
and
bitcoin
and
java
is
highly
invited
so
yeah,
I
talked
already
about
this
open
task.
B
The
review
of
my
implementation
is
probably
the
highest
priority
to
check
if
there
some
open
issues
which
are
not
discovered
yet
in
parallel
or
after
this
check
out
the
current
status
of
the
people
44
in
pitch
crunchy.
Maybe
it's
already
feature
complete,
and
so
maybe
not,
maybe
some
parts
are
implemented
and
company
like
I've,
done
it
and
could
be
changed.
But
I
mean
it's
a
it's
a
working
wallet,
what
we
have
out
since
one
year,
so
it's
a
very
dangerous
area
to
touch
and
yet
investigate
these
alternatives.
B
What
I
talked
about
a
minute
ago
to
bring
our
fork
in
sync
with
the
master,
also
talked
about
to
make
pull
request
following
improvements
to
check
the
sacred
status
and
maybe
as
when
the
main
branch
in
Pitkin
say,
takes
too
long.
We
said
with
a
samurai
wall,
it
has
already
support
for
sacred
I'm,
not
sure
about
the
details
and
so
on.
B
Yes,
there
are
a
few
important
details:
what
some
implementation,
not
supporting
older
all
the
versions
and
all
the
pips
and
older
which
the
native
address
formats
and
so
on
so
I'm,
not
I'm,
not
up
to
date.
With
with
all
these
details,
and
of
course,
you
have
to
add
sacred
support
for
bisque
I-
think
when
Bitcoin
she
would
support
sacred,
it's
probably
pretty
trivial
for
disk
to
support.
B
It
may
be
no
effort
at
all
may
be
loaded,
but
I
don't
expect
it's
a
huge
effort,
I
kept
out
lightning,
because
that's
that's
a
a
complete
own
story,
and
maybe
in
future
we
make
our
own
tech
session
about
ideas
which
I
think
but
the
main
problem.
As
far
as
I
followed,
it
I'm
not
very
up-to-date
with
lightning,
but
what
I
heard
from
the
open
pass
archives,
which
are
using
a
similar
concept
like
we
are
using
in
the
trade
process
with
the
smoke
ii
security
deposits
is
that
are
in
lightning
network.
You
cannot
either.
B
Yeah
here
are
some
references
to
this
blog
post,
I
done
about
this
privacy
or
it's
more
broad
about
privacy
in
biscuit,
but
especially
about
the
Bloomfield,
because
that's
a
major
issue
or
the
only
real
big
issue,
which
is
kind
of
like
a
sink
whist,
is
provided.
Bitcoin
notes
we
have
navigated
around
it,
so
I
think
it's
not
the
burning
problem
anymore.
B
We
change
the
problem,
so
we
have
a
little
bit
more
trust
or
the
centralization
problem
which
it
may
I
my
opinion,
more
theoretical
problem
at
the
moment
like
a
very
practical
privacy
problem,
but
anyway
up
then
yet
this
site,
this
page,
where
you
register
the
Cohen
type
for
a
bit,
forty,
four,
the
SPV
mode
of
Bitcoin
core
and
the
Scala
implementation
yeah.
How
there
are
any
questions.
A
You
have
a
little
bit
of
experience
and
you
want
to
come
help
do
basically
the
the
unglamorous
work
right
of
you
know
getting
us
in
harmony
with
what's
on
master
of
the
canonical
Bitcoin
J,
for
you
know,
just
all
that
kind
of
like
low-level
work
and
just
incrementally
begin
to
take
care
of
and
ultimately
possibly
become,
the
maintainer
of
Fisk's
Bitcoin
integration.
However,
it
involves
whether
we
stick
with
Bitcoin
J,
whether
we
really
start
to
get
serious
about
maintaining
our
own
Florrick
and
making
it
really
a
first-class
work.
A
Doing
the
alternative
options
they,
the
man
who
talked
about
I,
mean
this-
can
ultimately
be
really
juice.
You
earth
I'd,
like
imagine
the
scenario
where
we
start
shipping
Bitcoin
core
running
at
an
STD
mode
like
men
from
described
and
we're
talking
to
that
over
RPC.
Obviously,
that's
all
going
to
be
happening
by
a
Java
could
be
a
nice
lightweight
little
layer
that
we
need
to
write
there
that
can
become
its
own
library.
A
I
mean
there's
all
kinds
of
stuff
that
can
be
done
and
we
tend
to
be
in
this
mode
where
ever
thinking
you
know
highly
prioritized
and
what
the
most
important
things
are.
These
kind
of
major
privacy
issues
and
of
courses
are
the
first
things
that
need
to
get
handled,
but
as
people
start
to
really
show
up,
especially
if
we
have,
we
have
basically
zero
people
dedicated
to
this
right
now.
But
if
we
have
one
or
two
or
even
a
growing
team
around
this
week,
it
starts
do
really
ambitious
things.
A
Who
knows
what
we
can
do
a
fight
minute?
Who
knows
what
emerges
with
all
of
that
right?
So
so
there's
I'd,
say
you
know
all
everything
in
Memphis.
It
was
great,
it's
all
perfectly
true,
but
it's
also
worth
kind
of
stepping
back
and
thinking
big
and
thinking
long-term,
and
that
all
starts
with,
of
course,
showing
up
them
and
just
submitting
some
very
small
fixes
to
right
now,
problems
the
end,
keep
all
that
in
mind.
I
could.
B
B
You
are
sorry
yeah
to
ship
Bitcoin
core
in
a
binary
to
have
a
interface
eat,
either
a
PC
or
a
serum
cout
I'm,
not
sure
if
that
would
work
for
for
this
needs
and
well
either
implement
or
some
some
extra
new
binding
and
and
has
a
special
version
of
Bitcoin
Qi,
which
has
fast
because
our
PC
is
a
little
bit
slow
but
depends
what
you're
doing
for
norm.
Wallet
usage
is
probably
good
enough
and
I
think
that
could
be
really
exciting.
B
Our
application,
where
other
projects
which
are
based
on
travel,
could
could
pick
up
and
use
I
mean
for
Android,
unfortunately,
probably
will
not
work
or
will
not
work
for
sure,
but
yeah
all
normal
desktop
or
applications
could
uses.
And/Or
could
get
them
the
best
of
the
best
inside
of
the
application
and
can
still
use
it
in
a
java
application
without
or
without
complicate
bindings
to
other
languages.
B
A
Maybe
we
could
somehow
you
know,
share
that
resource
or
whatever
I,
don't
know
how
that
would
work.
I
think
they'd
have
a
more
traditional
employment
model,
but
under
the
bisque
bow
it's
it's
all
task
oriented
compensation
which,
by
the
way,
I
should
mention
right.
You
know
I,
think
I,
think
we'll
really
try
to
circulate
this
video
a
little
bit
more
widely
than
we
have
these
other
text
sessions,
because
this
is,
you
know,
I
think
we
need
to
cast
a
bit
of
a
wider
net
to
catch
all
the
people
in
JVM
land.
A
Who
might
want
to
do
this
kind
of
work.
People
should
know
that
we're
looking
for
this,
so
if
you're
watching
this
and
you're
not
like
really
familiar
with
bisque
and
what
we
do
keep
in
mind
that
everything
we've
talked
about
here,
every
valuable
contribution
anybody
makes
to
bisque
is
subject
to
or
eligible
for
at
least
compensation
under
what
we
call
the
disk
down.
So
you
can
read
up
all
about
this
in
the
show
notes.
A
So
if
you
I
just
want
to
be
so
there's
a
little
bit
of
digression
with
the
point
is
that
somebody
who's
doing
this
level
of
work
could
potentially
be
doing
that
work
for
a
couple
of
projects
at
least
like
there
really
might
actually
be
something
we
can
do
with
the
samurai
team,
and
the
thing
is
just
a
huge
opportunity
for
projects
like
this
and
samurai.
It's
a
small
number.
There
are
the
kind
of
the
vanguard
on
the
JVM.
B
B
Also
for
this
project,
which
need
a
mobile
version,
there
is
probably
no
alternative
out
and
discolor
implementation
might
be
interesting,
but
it's
a
uterus
to
change
to
a
completely
new
version,
even
if
it's
great
implemented,
but
you
never
know
which
which
future.
But
you
you
repeat
that
list
and
people
who
have
a
running
application
out.
Don't
want
to
be
this
usually
yeah.
A
Okay
last
call
for
any
questions.
I,
don't
see
anything
else
coming
up
in
the
chat.
Of
course
you
can.
You
can
always
come
talk
to
us
afterward
in
slack
again,
contributor
checklist
below
you'll,
see
all
the
right
links
to
come
figure
out
how
to
say,
hi
and
introduce
yourself
and
and
although
up
so
yeah
thanks
for
thanks
everybody
for
attending
you've
got
10
or
11
people
watching
us
as
we
went
and
there's
always
these.
These
tech
sessions
always
get
a
I,
don't
know
dozen
a
couple
hundred
views
within
the
week.
A
A
B
Everybody,
the
UI
and
dress
up
that,
maybe
maybe
for
next
week
or
so,
and
maybe
kristef-
can
be
a
terror
domain.
Where
it's
like
mean
bring
me,
do
it
together
or
so.
I
would
like
to
make
one
also
about
the
towel
implementation,
but
I
want
to
wait
until
it's
more
more
complete,
maybe
in
two
three
weeks
or
four
weeks
yeah
but
yeah.
Let's
schedule
for
for
the
test
of
Nui
good,
so
will
will
roughly.