►
Description
Bisq developer session 06.02.2019
https://github.com/bisq-network/growth/issues/98
Presentation:
https://docs.google.com/presentation/d/1FvTaOmnqtz2woL9LlwG
Hdd3a6jOpYAajurGWa8QMuxA/edit#slide=id.g4e2e27d048_0_400
A
Hello,
everybody
welcome
to
this
week's
developer
session
this
week.
We
want
to
cover
the
viticulture
part
in
bisque
how
bit
country
is
used
and
how
the
current
state
of
development
meant.
This
I
will
give
just
a
very
quick
introduction
that
I
hand
over
to
Oscar.
He
forgot
a
presentation
Oscar.
Maybe
you
can
share
the
link
to
the
constantly
IFC
shared
already
in
the
in
the
chat
here
and
the
hangout
yeah.
A
So,
as
everybody
know,
bisque
uses
its
own
wallet,
which
is
based
on
the
different
trade,
as
we
are
using
a
fork
of
bid
country
where
we
did
some
smaller
changes
mostly
have
been
related
to
privacy.
Improvements
and
RF
have
been
related
to
tour
that
we're
supporting
onion
addresses
and
yeah.
Luckily,
we
found
after
a
long
time
we
found
a
bit
country
expert
with
Oscar.
A
He
joined
Fiske
a
few
months
ago
and
he
started
to
to
improve
stuff
to
review
existing
code
at
the
moment
here,
to
update
to
the
latest
bit
country
wreath
and
as
just
recently,
our
operation.
It
shield,
after
maintaining
a
bit
country,
announced
that
the
psychic
sacred
and
the
master
is
now
ready
for
we're
releases
in
the
last
testing
stage.
A
Probably
will
move
soon
as
well
to
that
area.
Another
important
thing
which
I
would
ask
them
to
Oscar
to
to
cover
a
little
bit
as
well,
is
yeah.
We
had
we
had
plans
to
move
away
from
each
country
for
various
reasons,
mainly
because
of
all
this
privacy
issues,
but
also
because
many
of
the
newer
features
in
Bitcoin
are
not
implemented
like
SEC,
with
mainly
effort
also
replaced
by
fear
and
and
other
improvements
and
yeah.
A
We
were
looking
in
all
the
alternatives
from
watch
it
without
that
non-israeli
production
rate
so
was
not
feasible
to
at
least
in
the
foreseeable
future
to
an
alternative.
So
we
probably
won't
stick
with
potentially
longer
and
yeah.
I
think
I
and
now
over
to
oscar,
and
maybe
you
can
share
your
presentation.
B
B
Yes,
all
right,
so
I
I
am
off
the
the
Hangout,
so
I
will
read
in
my
presentation,
so
this
is
I
I
plan
to
speak
for
around
half
an
hour.
This
is
what
I
1
2
%
like
about
me
in
Chinese,
and
how
do
you
sit
in
this
cube?
Then
I
will
present
what
I've
been
working
on
in
the
last
few
months
and
what
we
like
to
do
in
the
future,
so
I've
been
working
with
beacon
choice
in
2014
and
I
began
using
it
and
contributing
it
for
a
couple
of
projects.
B
Here,
I
left
a
couple
of
links
on
projects
I
contributed
to.
If
you
want
you
to
check
them
after
the
call,
and
so
what
bitcoin
J
is
first
so
big
enjoy,
is
a
framework
to
implement
SPB
bit
condo
so
built
enjoy,
is
a
beacon
all,
but
it's
not
a
regular
bit.
Cannot
because
it
it's
kind
of
a
light
way,
know
that
use
blown
filters
and
fpv.
That
means
that
it
retrieves
just
information
once
it
needs
instead
of
retrieving
the
Daiya
blockchain
and
that
way.
B
A
B
B
We
using
that
bloom
filters,
you
tell
the
other
nodes,
what
information
you
are
interested
about
and
the
other
nodes.
Instead
of
sending
every
single
block
and
every
single
transaction,
they
shall
send
you
the
transactions
that
you
are
interested
in
and
well
that's
one
thing:
one
of
the
goals
of
that
VIP
was
to
protect
privacy.
B
A
B
Yes,
so
when
the
the
the
beacon
Channel
has
kind
of
a
partial
validation
of
the
Bitcoin
consensus,
so
it's
partly
validates
that
the
blockchain
is
valid
and
that
in
it
does
that
by
reading
the
blog
hitters
and
retrieving
that
well,
the
transaction
that
she
is
interested
in
and
the
way
it
knows
that
the
transactions
are
part
of
the
block.
Hitters
is
using
Merkle
trees
or,
as
I
will
say,
that
partial
Merkle
tree,
which
is
a
structure
to
prove
that
the
transaction
is
included
in
a
block.
B
B
Was
that
is
that
what
you
meant
for
any
earrings?
Okay,
so
to
move
on
with
be
conscious?
So
the
if
you
look
at
the
source
code,
there
are
three
main
group
of
classes.
There
are
classes
related
to
the
wallet
plus
is
related
to
the
peer-to-peer
protocol
or
connected
to
peer.
Exchanging
information
appears
and
classes
related
to
keeping
blockchain
store
in
the
blockchain.
B
A
blockchain
relate
because
she
was
created
like
six
seven
years
ago
by
Mike,
Byrne
and
receiveth,
and
also
got
contribution
from
Mitrano
and
his
he's
one
of
the
core
developers
of
beacon
core
and
back.
Then
it
was
one
of
the
most
important
beacon
projects,
because
it
was
the
first
to
implement
the
SPP
mall
in
Bitcoin,
and
it
also
it
was
pioneered
by
implementing
payment
channels
protocol
and
it
was
used
by
the
most
Fed
world
finalists
at
one.
A
Okay,
have
you
heard
something
about
this
security
vulnerability
regarding
payment
channels
that
have
been
a
few
weeks
ago?
Some
announcement,
but
Pacific
was
not
revealed
yet,
but
it
seems
that
this
regarding
the
premium
payment
channels
had
some
security
vulnerabilities.
Do
you
know
anything
about
this?
No.
B
Right
shall
I
move
on
or
there
are
ok.
So
how
do
you
use
Bitcoin
Jamie
missed
you?
So
did
you
have
a
wallet,
a
Bitcoin
wallet
in
inside
the
disk
you
know
and
that
is
used
to
store
bitcoins
receive
transaction
science
and
transactions
and
Bitcoin
Shea
is
also
used
for
the
pc
q
wallet
and
B
skew.
The
biscuit
token
is
implemented
as
a
collar
coin
and
yeah.
The
visco
wallet
is
also
a
bit
country
wallet.
B
A
B
B
So,
let's
review
the
the
work
that
diving
wing
related
be
change
in
the
last
few
months,
so
this
is
kind
of
a
list
of
things
and
then
we'll
go
into
each
detail
so
well,
there
were
a
number
of
bug
fixes
that
I
worked
on
then,
as
Manfred
said,
I
I
lead
a
research
to
base
beacon
chain
with
something
else.
I
revealed
the
big
44
implementation.
B
So
let's
go
to
the
details.
I
will
skip
all
the
bug,
fixes
some
of
that
I
included
them
here
just
for
completeness
and
if
anyone
wants
to
go
to
the
links
after
the
call,
but
I
will
skip
all
the
bug
fixes
and
all
that.
So
let's
talk
about
replacing
Bitcoin
chain.
So
one
of
the
things
mantras
such
as
to
me
is
that
big
gun
J
had
a
couple
of
issues.
B
One
is
that
well,
there
was
no
release
for
two
years,
which
is
like
it
shows
that
the
project
kind
of
lost
is
steam
and,
at
the
same
time,
the
Segway
it
was
not
implemented
and
well
or
not,
release,
at
least
and
at
the
same
time,
the
this.
The
concept
that
Bitcoin
she
was
created
for,
which
is
SBB
and
bloom
filters,
proved
to
be
broken,
meaning.
B
A
Something
else
interesting,
it
may
just
add
something
when
somebody
who
is
not
so
familiar
with
biskits,
so
also
the
way
how
we
are
yeah,
mitigating
this
privacy
issue
with
speed
country,
is
that
our
basic
developers
are
running
Bitcoin,
full
notes
and
those
that
are
provided
notes
which
software
by
default
connects
to.
You
can
change
this
in
a
settings
if
you
want
to
connect
to
the
public
network,
but
when
you
only
connect
to
the
Bitcoin
four
nodes
which
are
runs
by
this
developer
are
yeah.
A
You
can
be
sure
that
there
are
no
chain
analysis,
company
spying
on
you
and
with
that
this
privacy
problem
is
at
least
mitigated.
Of
course,
it's
not
solved
and
you
have
to
trust
to
disconnect
this
developers.
So
those
who
are
running
such
nodes
that
they
are
not
selling
the
data
and
to
the
chain
analysis
companies
it's
much
better
like
when
you
would
connect
to
the
public
network.
Basically,
you
can
be
sure
that
all
your
wallet
data
ends
up
energy
analysis
company.
B
Okay,
so
well
I
investigated
for
alternatives
for
replacing
beacon,
J
and
what
I
what
a
phone
is.
Well,
there
is
a
mature
story
and
there
is
no
good
alternative,
in
my
opinion,
surprised,
VidCon,
China
and
when
analyzing
alternatives,
I
always
found
kind
of
a
trade-off
between
privacy
and
full
consensus,
validation
versus
the
resources,
the
the
wallet
and
then
for
the
nod,
use
so
the
more
privacy,
the
more
resources
that
you
need.
The
more
you
want
to
make
sure
that
you
are
following
the
right
chain,
the
more
resources
that
that
you
need.
B
B
B
The
benefit.
Is
you?
Don't
expose
your
addresses
to
every
single
location,
analysis,
company
and,
like
you
eventually
do
when
you
use
bloom
filters,
but
you
are
trusting
one
server
of
someone
you
may
not
know
or
may
not
trust.
So
it's
not
it's.
It
still
have
privacy
issues
because
you're
trusting
electron
servers.
B
B
A
B
B
So
well,
those
are
the
alternatives
that
I
analyzed
it
here
on
the
link
that
I
posted.
It
contains
like
a
very
long
explanation
of
the
alternatives
that
I
mentioned
in
a
couple
of
other
alternatives.
I
look
at
so
well.
That
is
my
analysis.
All
for
placing
Bitcoin
shape.
Are
there
any
questions
about
it
or
comments?
Could.
A
You
explain
a
little
bit
or
the
concept
of
instance
also
not
I
mean
it's
quite
complicated,
but
maybe
to
give
a
little
bit
better
idea.
Probably
most
don't
really
know
at
all
what
bloom
filters
are.
So
what's
the
function
of
a
bloom
filter
for
what
it
is
good
and
how
it's,
basically
on
a
high
level
working
on
a
technical.
B
Level
right
so
as
a
summary,
the
idea
of
bloom
filters
is
being
able
to
tell
another
node
which
transactions
you
are
without
exposing
your
Bitcoin
analysis.
So
it's
a
way
to
tell
the
other
node
which
Bitcoin
addresses
you
are
interested
in,
but
without
revealing
them.
So
that's
kind
of
the
tricky
part
and
the
way
it
does
is
it
creates
a
bloom
filter
which
kind
it's
a
way.
B
What
what
are
the
addresses
you
might
be
interested
in,
so
the
other
node
will
send
you
transactions
that
are
relevant
to
you
and
transactions
that
are
not
relevant
to
you
and
it's
your
job
to
discard
the
transactions
that
are
not
relevant
to
you.
So
the
bigger
the
the
filter
is
I
mean
the
the
more
broader
kotori's
is
the
is.
B
And
bandwidth
consumption
at
this
at
the
same
time,
I
have
I
was
saying
before
bloom
filters
proved
to
be
broken
because
well,
my
friend
can
explain
better
and
made
this
point
because
I
think
he
analyzed
it
up
in
more
detail,
but
eventually
other
nodes
can
find
out
what
your
addresses
are.
If
they
see
will
attack
you,
and
so
that's
it
I,
don't
know
Manfred
if
I
explain
it
well
or
maybe
there
are
other
comments
that
you
want
to
watch
yeah.
A
Maybe
they
add
a
little
bit.
The
bloom
filter
is
basically
a
data
structure.
You
could
compare
different
to
a
hash,
but
basically
it's
similar
like
a
hash.
When
you
get
the
hash,
you
can
verify
the
original
data,
but
the
hash
is
much
much
rosier,
its
big
size,
for
instance,
when
to
buy
it,
doesn't
matter
how
big
your
original
database
and
with
a
bloom
filter
yeah,
you
can
compress
a
different
data
like
different
at
resinous,
together
and
depending
on
the
setting
on
the
parameters
of
the
bloom
filter.
A
You
can
create
a
very
large
bloom
filter
which
is
very
accurate,
and
then
you
don't
receive
much
false
positives.
So
when
you
would
send
a
bloom
filter
with
ten
different
addresses
to
a
four
node
and
the
bloom
filter
has
a
very
high
quality
and
bloom
filters
quite
a
bit.
Maybe
it
becomes
as
big
as
ten
addresses.
A
When
you
just
would
set
the
same
data
to
the
node,
then
you
would
be
basically
perfect
and
you
would
not
get
any
false
positive,
but
I
give
the
bloom
filter
is
to
reduce
the
data
size
and
taking
account
that
you
receive
some
false
positives.
It
guarantees
that
you
receive
the
current
correct
addresses
where
it's
not
address,
Israeli
its
public
keys
and
when
the
full
node
sees
the
transaction
which
contains
this
public
key.
A
Then
it
knows
you
are
interested
in
that
in
that
transaction
and
it
sends
you
the
transaction,
so
any
transaction
which
contains
this
public
key
you're
guaranteed
to
receive,
but
you
might
receive
more
transaction
which
are
not
matching
your
wallet
at
the
end
because
because
of
the
false
positive
rate
and
yeah,
you
can
define
these
parameters.
So
basically
the
more
you
compress
the
hood,
the
bloom
filter,
the
more
you
get
false
positives.
A
The
smaller
is
to
take
the
size
and
I
think
for
when
you
yeah
I
think
it
contains
30
the
way
that
you
are
trading
the
Bloomfield's.
Are
you
putting
in
all
your
public
keys
into
it
and
tell
the
whole
note
what
you're
interested
in
and
with
the
client
I
with
the
server-side
loop
with
the
pips?
It's
the
opposite.
A
Every
full
node
is
creating
the
bloom
filter
for
every
block,
and
then
you
are
yeah
you're
downloading
all
those
bloom
filters
for
each
block,
and
then
you
are
checking
locally,
which
block
is
relevant
for
you
and
then
you
regress
in
the
world
block
and
by
that
the
process
is
much
better.
Because
then
that
will
note
only
knows
you
might
have
one
transaction
in
this
book
because
you
want
to
get
the
block,
that's
one
of
two
thousand
transactions
and
the
other.
A
But
there
never
a
time
to
do
it.
Reliant
might
be
at
least
one
thing.
It
might
be
a
little
bit
complex
to
fix,
and
the
second
part
is
that
conceptually
it's
it's
already
broken,
because
even
if
you
would
have
missed
all
these
implementations
issues
perfectly,
the
full
node
can
derive
from
the
transaction
graph
can
arrive.
B
Alright,
so
I'll
I'll
switch
to
the
next
thing.
So
another
thing,
I,
didn't
last
couple
of
months,
was
review
their
beep
44
implementation
that
we
have
so
beep.
44
is
a
way
to
to
create
like
protocol
on
the
derivation
path,
to
use
multiple
coins
with
the
same
wallet
so
basically
using
as
Montford
was
explained
at
the
beginning,
using
the
same
seal,
you
can
derive
many
addresses
for
different
coins,
so
when
I
mean
the
bid
cons,
I
released
that
you
based
at
what's
not
really
ready
for
beep
44
and
beat
the
the
word
changed.
B
His
show
to
our
bit
crunchy
pork
to
allo,
to
use
both
a
wallet
and
so
I
reviewed
implementation.
Just
minor
problems
for
phone,
no
big,
big
issues.
Here's
a
lick,
the
link
to
the
full
analysis,
and
now
that
point
15
becomes
iPod
15
is
announced
we'll
have
to
review
our
implementation,
because
the
new
release
asks
like
like
couple
of
features
to
make
be
44
users
easier,
so
we'll
probably
have
to
modify
our
implementation
probably
will
have
to
simplify
our
implementation
and
remove
a
couple
of
things
that
were
done.
B
Another
problem
that
I'd
found
was
the
JDK
version.
A
couple
of
months
ago,
bisque
you
asked
was
moved
to
JDK
10,
but
VidCon
shy
is
still
built
using
JDK
8,
so
is
built
with
JDK
head,
but
run
with
JDK
10,
which
is
what
miscue
needs
and
that's
kind
of
problem,
because
there
is,
there
was
a
problem
on
bit
conge
like
a
couple
of
years
ago,
when
closing
file
on
Windows
and
HUD
was
implemented.
That
relies
on
some
JDK
8
specific
stuff
that
when
you
run
it
in
JDK
10,
it
doesn't
work.
B
So
that
means
that
recover
from
seed
fails
on
Windows
on
piece
cube
and
so
I
I
did
a
research
to
fix
that.
It's
not
easy.
I
try
to
migrate.
Jdk
from
the
sorry
I
tried
to
migrate,
VidCon
shape
from
J
decade
to
JDK
10.
It's
not
that
easy.
Also
I
would
like
to
removing
the
hack
the
windows
hard,
but
I
found
that
the
problem
is
still
there
and
it's
still
an
open
issue
on
the
link.
I
turn
here,
there's
a
full
explanation
of
all
the
research
and
the
problems
that
I
found.
B
A
B
Okay,
so
then
another
thing
that
working
on
was
updating
big
conjecture.
The
latest
release.
Well,
the
latest
release
something
this
week.
So
the
first
thing
was
to
clean
up
the
commit
history.
The
commit
history
of
our
beefs
Kubek
enjoy
grant
to
us
a
bit
of
a
mess
so
I,
starting
from
the
source
code
I
compared
to
the
to
the
beat
cone
shape,
release
that
we
base
on
and
I
created,
like
one
commits
per
change.
So
now
the
commit
history
is
very
clear
and
then
the
next
thing
was
update
from
point.
B
B
What
I,
mostly
phone,
was
many
unnecessary
changes
and
I
I
suggest
should
try
to
avoid
changes
to
should
be
to
enjoy
or
any
third
party
library
fee
that
we
modify
because
the
less
changes
we
have,
it's
less
it's
easier
to
upgrade
to
a
newer
version
like
we
are
going
to
do
when
one
fifteen
is
available.
So
most
of
the
work
I
was
that
I
did
was
trying
to
understand
whether
the
changes
that
we
did
I
actually
needed,
or
not
so
on.
The
links
that
I
posted
here
is
the
world.
B
B
You
know
what
sink.
Okay.
This
is
still
not
Murshid
into
the
into
the
main
project,
so
it's
yeah.
Well,
we
need
you
to
merge.
These
two
matter
would
request
from
baton
shy
upstream
or
things
that
we
working
on.
So
when
a
new
release
is
done
on
bit
Concha,
we
don't
have
to
update
them
again.
I
left
the
the
links
here.
B
If
you
want
to
check
them
after
the
call
as
I
say,
I
remove,
lighter
shade
library
that
was
used
in
the
bus
used
to
be
able
to
start
a
piece
queued
at
work
where
collection
or
were
using
advise
parents
even
trolley
I,
think
that
he
didn't
happen
like
it.
There
was
no
necessity
to
use
them
as
base
country.
Sorry
base
currencies,
so
I
ended
up
removing
little
chain
and,
as
I
said,
I
was
about
writing
using
Bitcoin
J
master.
B
B
Then
there
are
a
couple
of
things
that
were
changed
on
our
Bitcoin
shape,
front
branch,
but
I
didn't
pop
it
and
still
me
to
be
around.
As
I
said,
the
the
Bitcoin
shiny,
updated
branch
is
not
merged
to
master,
so
we
need
to
merge
it,
and
once
there
is
a
new
release
on
Bitcoin
chain,
the
fifteen
release.
We
probably
want
to
use
that
one
and
then
we
will
have
say
we
support.
B
We
will
be
able
to
remove
a
couple
of
hugs
that
we
implemented
and
we'll
have
an
up-to-date
source
code
with
bug
fixes
and
a
couple
of
new
features
that
that
are
new
on
point
15,
for
instance,
being
able
to
send
a
section
where,
where
their
receiver
pasted
the
Bitcoin
network
fees,
so
that's
all.
My
summary
is
that
nowadays,
beacon
J
is
a
lesser
evil.
That
means
that
it's
not
perfect,
but
in
my
opinion
there
is
no
third
alternative
that
we
can
use.
A
Chris,
a
few
muted,
just
one
question
regarding
there
was
some
activity
in
our
on
one
of
our
issues.
As
far
as
I
remember,
of
two
developers
who
want
to
help,
or
at
least
testing
or
supporting
the
bit
country,
development
or
the
integration
that
we
that
the
folk
that
we
use.
What's
the
current
state
on
that
or
I
just
I
think
I
remember
they
were
from
wasabi
wall.
That
is
right.
B
A
I
can
take
a
little
bit
of
yours
a
day.
Vasari
Paulette
use
only
the
back
32
address
format
which
is
used
for
cyclic
and
they
want
to
push
durable
ecosystem,
all
the
wallets
which
don't
have
our
sacred
support
yet
implemented,
and
the
trials
do
not
directly
on
the
development
site,
so
they
offer
to
help,
which
is
great.
A
I,
as
one
thing
is
that
at
the
moment
we
have
had
a
priorities
and
only
one
developer
working
at
this
cent
sec,
which
is
not
the
highest
birth,
even
if
we
are
big
fans
of
set
with
and
so
on,
and
we
would
like
to
support
it.
It's
just
not
on
our
top
priority
list
and
we
can't
really
don't
make
time
on
this
another
thing
what
I
wanted
to
ask
Oscar
have
not
talked
yet
about
this,
but
I
read
repeatedly
from
Luke
death.
A
If
it's
really
such
a
good
idea
to
motivate
our
users
that
they
are
preferring
separate
addresses
because
at
the
end
it
leads
to
bigger
blocks
and
leads
to
more
mobility
issues
and
as
long
bitcoin
is
not
really
in
trouble
that
the
capacity
is
not
enough
with
one
megabyte
the
sink,
it's
better
to
be
able
to
control
with
this
side.
Oscar
do
you
have
any
opinion
or
any
comments
on
that.
B
A
A
B
A
A
A
Yeah
there
are
from
Luke
chair,
looked
STR.
There
are
some
concerns
and
critics
to
use
sequi
addresses
if
you
don't
really
need
it
like
for
lightning,
because
at
the
end
are
more
people
using
second
at
resistor
bigger.
The
blocks
are
because
they
accounted
at
a
different
space
for
the
block
size
and
when
you
use
a
normal
Bitcoin
address,
it's
it's
still
using
the
one
megabyte
limitation
and
at
the
end
it
yeah.
It
helps
to
keep
the
proc
size
smaller
or
I,
have
not
read
or
discuss
more
about
this.
B
B
B
B
A
Sure
yeah
I
mean
Luke
sure
I
said
he
is
a
proponent
of
even
reducing
the
block
size
to
half
a
megabyte
or
something
like
this
and
I
understand
his
point
of
view.
I'm
not
decided
on
which
side
was
a
little
bit
more
moderate
size,
I
think,
but
a
thing
yeah
anyway,
I
think
it's
interesting
aspect
to
keep
in
mind
and
the
transaction
sizes.
Sync
is
not
really
small.
It
just
doesn't
count
to
the
normal
block
size
because
it's
thought
in
a
different
data
structure,
but
I'm
not
sure
if
you
really
get
this
small
transaction.
A
When
you
take
all
the
data,
what
you
need
for
the
transaction
provides
more
or
less
the
same
data
size.
The
fisa
are
probably
a
smaller
because
of
this
calculation
of
the
field
is
done
differently.
You
can
say
fees
yeah
anyway,
I
just
found
it
a
little
bit,
I
mean
from
Vasavi
wallet,
they're,
very
strong
with
privacy
and
very
good
intention,
and
so
I,
just
yes,
sometimes
or
even
with
good
intention.
You
can
do
something
which
is
actually
not
so
good
for
ecosystem
and
I.
A
I
personally
feel
when
would
be
now
for
megabyte
with
the
segment
part,
you
would
have
more
scalability
issues
running
a
full
block
costs
or
any
more
than
200
gigabytes.
In
one
year
we
are
making
300
gigabyte
and
yeah
as
when
everybody
push
hard
core
to
seg
wit
with
bigger
blocks.
At
the
end,
we
are
getting
earlier
to
the
troubled
zone
like
like
without
so
I
I'm
more
on
the
on
the
side.
A
A
So
it's
oh
yeah,
no
drama
developers,
but
they
have
to
developers
listening
who
are
dedicated
to
work
on
that
a
sink
or
aunty
discuss,
also
based
on
where
shield
bug
so
I
think
they
helped
testing
another
release,
which
is
great
from
our
side
I
before
we
are
getting
really
closer
to
start
to
integrated,
which
will
not
happen
in
the
next
one
or
two
months
at
least
I
stink,
erm
yeah.
There's
nothing
really
what
they
can
help
us
directly.
A
A
There
any
other
questions
or
you
I
mean
a
small
thing,
which
is
maybe
a
little
bit
missing
in
the
plans.
Another
important
part
which
we
would
have
prioritized
actually,
when
the
other
psychic
release,
will
not
be
mail
ready,
is
to
review
and
reflect
the
bit
the
Beast
code
as
a
Bitcoin
package
in
core
of
bisque.
So
all
the
Bitcoin
related
code
to
improve
there
is
yeah.
A
Doesn't
it
has
mainly
one
issue
which
is
a
little
bit
problematic
or
should
be
improved
and
where
we
know
there
are,
but
that's
the
way
how
we
are
managing
the
wallet
internally.
We
need
to
know
in
it
to
trade
protocol.
So
when
you
are
putting
some
funds
for
your
offer,
you
need
to
ensure
that
this
you
take
zone
where
you
found
that
your
offer
is
not
used
for
anything
else.
A
When
you
create
another
offer,
when
you
take
an
offer,
when
you're
just
sending
out
Bitcoin
from
your
wallet
that
accidentally,
you
are
not
taking
this
money
away,
because
when
somebody
would
take
your
offer
and
the
money
is
not
there,
it
would
fail,
of
course,
and
to
achieve
this
I
added
a
data
structure
which
is
handling
this
address
and
it
released
and
that's
yeah.
But
there
are
some-
you
know,
boxes
that
sometimes
users
have
some
issues
as
far
as
I
heard
from
the
arbitrator's.
A
Think
when
there
is
anybody
anything
in
the
trade
protocol,
you
have
something
breaks
and
then
their
state
of
this
data
structure
is
not
updated
correctly,
because
here
we
have
basically
two
data
structure,
the
normal
wallet
and
then
this
internal
data
structure
and
it's
not
hungry
business,
guarantee
that
they
are
always
in
sync
and
when
they
get
out
of
sync,
your
mother
gets
your
internal.
This
collet
get
screwed
up
that
you
show
you
get
display.
The
wrong
balance
or
offer
will
fail
when
somebody
tried
to
take
it
off,
because
your
money
is
not
there
anymore.
A
So
that's
the
main
issue,
the
kind
of
problem
what
we
have
and
we
should
consider
to
change
this
concept,
how
we
are
managing
the
funds
or
the
trace,
maybe
included
in
the
wallet
or
the
wallet,
can
be
extended.
There
is
a
kind
of
a
framework
where
you
can
add
metadata
to
the
Kabala,
so
maybe
that
might
be
an
option
and
beside
that
I
generally
go
over
the
code,
improve
reflector
and
on
it,
cross-check
hold
all
the
stuff.
A
So
that's
the
bigger
area
as
well,
which
will
take
for
sure
minimum
two
months
or
so
so
that's
as
well
on
the
roadmap,
but
we
have
to
see
now
with
Bitcoin
Qi
0:15
release,
probably
the
higher
priority
to
get
to
get
ready
to
be
able
to
update
to
that
trees,
which
have
to
be
very
well
tested.
Of
course,
especially,
we
set
out
that
will
probably
happen
when
the
towers
already
out
needs
to
be
hundred
percent
sure
it
doesn't
break
anything
with
the
bsq
wallet.
A
Yeah,
just
one
quick
question
regarding
the
bloom
filter:
these
fake
addresses:
where
do
they
come
from
other
just
this
public,
these
other
generated
because
they
know
okay,
there
are
no
fake
addresses
in
reality,
it's
just
random
bloom
filters
is
a
yeah.
You
have
come
like
a
bit
mask
so
you're
compressing
your
data
down
to
a
series
of
bits
and
you
are
adding
those
bits
up
with
different,
remember
exactly
how
it
works
and
you
are
adding
some
randomness
to
it.
So
when
we
surrender
you
will
match
with
other
addresses
or
public
keys
at
the
end.
A
B
A
That
was
the
misunderstanding:
I
thought
you
sent
kind
of
the
fake
fake
information
public
yeah.
There
is
one
riskless
it
can
be
because
it's
it's
completely
random
and
when
you
get
an
address
from
a
gambling
site
where
there
are
millions
of
transactions
connected
to
and
by
chance
you
have
such
a
public
heatin
matching
your
bloom
filter.
B
A
So
it's
it's
a
real
problem
and
suppose
discuss
also
in
the
business,
a
minister
so
that
you
know
it's
it's
a.
He
chose
that
egg
trader.
The
concept
is
not
the
basic
idea
of
using
bloom
filters
for
privacy.
It
doesn't
work,
it's
not
proof.
Eaters
were
never
intended
as
a
solution
for
privacy.
It's
just
for
optimizing
space
that
you
sent
something,
and
you
are
you
have
a
smaller
footprint
and
potato.
What
you
sent
tutor
to
a
server
and
the
dancer
is
that
you
get
more
false
positives,
but
that's
the
intention
of
doing
good.
A
B
A
Is
it
using
SPD
mode
as
well
or
yeah?
As
on
the
pitch
countryside,
the
BS
humor?
It
is
exactly
the
same
like
the
Bitcoin
wallet,
the
only
different,
it's
it's
on
another
element
in
the
peso,
so
the
HD
wallet
is
a
tree
of
Earth
of
keys
and
from
one
branch
you
go
to
the
next
branch
and
the
big
44
added
a
layer
of
branches
or
different
coins.
A
A
The
only
different
on
the
bit
country
side
is
that
they're,
the
keys
of
the
peaceful
addresses
living
on
different
branches,
but
they
have
the
same
root
of
the
same
secrets,
and
it's
country
basically
doesn't
know
anything
about
the
color
coin
or
be
as
few
or
whatever
there
is
actually.
But
in
the
biscuit
code,
where
we
are
where
we're
dealing
with
the
bit
country
framework.
A
There
is,
of
course,
then
quite
a
bit
of
code
for
handling
there,
the
bsq
stuff-
and
it
main
important
part
we
have
to
combine
at
every
psu
transaction-
is
created
with
bitcoin
and
with
be
as
few
because
for
the
mining
feel
you
need
bitcoin.
We
don't
want
to
pay
mining
fees
which
be
as
few
that
would
be
very
expensive,
so
we
always
have
to
create
first,
a
partial
transaction.
A
There
are
a
few
classes
which
are
living
in
a
static
space
and
where
you
get
some
conflicts,
when
you
have
two
wallets
which
are
are
committing
the
same
transaction
to
their
wallet
pot
and
so
far
we
could
live
with,
as
we
didn't
account
the
big
problem.
But
we
aware
that
there
are
potential
issues
and
we
should
fix
this,
but
it's
quite
a
big
refactoring
in
bit
country,
basically
to
be
able
to
separate
this
two
wallets
very
cleanly
or
yes,
that's
it
basic
and
the
rest
of
psq
or
the
rules
for
validation.
A
A
When
you
run
be
askew
or
as
a
wheel
node,
then
you
will
need
to
run
Bitcoin
core
locally
and
you
are
connecting
with
a
PC
to
your
Bitcoin
core
node
and
you
are
requesting
all
the
blocks
from
there
and
you
get
notified
about
the
new
block
when
you
run
it
as
a
light
note.
What
most
people
probably
will
do,
then
you
run
just
basic
right
now
without
any
extra
setup,
and
then
you
receive
the
blocks,
they're
already
filtered
blocks,
which
only
contains
be
askew
transactions.
A
You
receive
those
from
signals,
so
at
the
first
startup
you'll
receive
a
whole
patch
south
of
those
blocks,
and
you
are
validated
on
all
blocks
and
then,
when
you're
online
at
every
new
blocks,
the
signals
are
broadcasting.
The
new
psq
block
to
the
network,
and
this
piece
cue
block,
is
basically
a
saying,
like
a
biscuit
block,
just
removes
all
the
non
fields.
A
Few
transactions,
and
only
the
transactions
which
are
relevant
for
psq,
which
contains
some
psq
inputs,
are
in
there,
so
usually
a
problem,
the
contains
up
one
or
two
or
five
transactions
or
zero,
and
if
the
model
is
a
little
bit
similar
like
SPV,
so
the
seed
node
cannot
cheat
that
he's
sending
you
an
invalid
transaction
or
whatever,
because
you
will
verify
the
transaction
need
to
be
a
little
bit
contraction
and
then
it
meet
you
every
light.
No,
they
still
doing
the
full
validation
of
this
block
that
it
really
matches
the
PSU
rules.
A
The
only
thing:
what
does
he
look?
A
malicious
even
could
do
is
to
omit
transaction
and
that's
the
same,
our
secured
issuance
in
SPD
mode
and
as
as
a
server
or
Bitcoin.
Full
node
cannot
send
you
an
invalid
transaction,
but
he
can
hold
back
some
transaction
and
you
never
learn
about
transaction,
and
that
could
lead
to
some
issues.
I
never
thought
that
they
were
freely
exploited
or
there
was
any
any
actual
security
issue.
Is
this
wispy
as
Hugh?
A
We
will
that
still
not
there,
but
that
will
be
implemented
to
suppress
you
get
these
blocks
from
multiple
signals.
So
then
the
problem
is
only
when
all
those
hip
nodes
are
either
are
out,
have
failed
and
they
are
not
up
to
date.
But
we
had
a
few
routine
errands
ago
when
there
was
many
issues
with
signals
with
stability
or
when
they
would
call
in
loot
and
would
maliciously
hold
back
some
blocks
or
some
transactions,
but
actually
very
low
risk.
But
as
a
bigger
risk
is
stability.
A
When
the
signals
have
some
problems
and
all
a
broken,
then
you
will
not
get
the
transactions
and
we
will
add
some
extra
stuff
that
basically
your
eyes
from
monitoring
monitoring
will
become
more
important
here
that
we're
discovering
very
quickly
when
one
signal
is
out
of
sync.
It
could
be
because
of
relax.
A
That's
why
we
have
the
break
between
the
volton
and
the
proposal
and
then
between
the
boat
reveal
and
the
blind
boat
and
then
again
to
the
result
face
to
avoid
this
issues
with
rework
so
that
you
could
get
out
of
consensus,
because
you
receive
different
data
because
all
this
relevant
tape
to
have
to
be
done
before
the
break
starts.
The
break
is
at
the
moment
the
same
ten
rocks,
but
maybe
we
can
increase
it
for
a
minute
and
it's
very
unrealistic.
A
A
That's
something
you
a
question:
yeah
thanks
and
in
peacefull
we
actually
not
really
it's
a
little
bit
of
mixtos.
We
are
using
some
parts
of
bit
country,
but
we
try
to
avoid
it
for
anything
which
is
consensus
relevant.
So
we
are
using
it
to
see
what's
the
chain
tip,
for
instance,
and
for
the
sinking
and
for
the
balances.
When
you
get
unconfirmed
transactions
because
you
miscue
at
the
moment,
we
are
not
supporting
on
confirm
transactions.
A
That's
why,
when
you
made
it
any
transaction
or
a
proposal-
and
you
don't
have
other
you
take
so
where
you
have
some
bsq,
you
have
to
wait
until
it's
comfortably
before
you
do
the
next
transaction,
which
is
a
little
bit
annoying
and
we
try
to
fix
this
before.
I
may
not
release,
but
a
little
bit
complex
and.
A
Yeah
in
big
country
you
receive
Duncan
from
transactional,
usually
transplant
them
in
this
queue
at
the
moment,
not
but
I
said,
and
we
try
to
support
this,
at
least
for
their
own
change-
addresses,
because
you
don't
want
to
cheat
yourself
this
with
Apple
spent
that
we
can
spend
your
own
unspent
change.
Header
change,
few
pixels
in
from
the
PHP
world.
A
A
A
The
seat
is
only
chopping.
The
receipt
noticed
that
there,
instead,
you
are
getting
their
blocks
from
the
full
note
and
getting
the
full
block
with
the
2,000
or
more
transactions,
and
then
you
have
to
filter
to
see
which
transactions
are
olivia's
to
transactions.
The
seed
not
send
you
already
the
blocks,
which
only
contains
these
new
transactions.
Theoretically,
we
could
of
course,
send
this
blocks
also
entirely,
but
then
it
would
be
much
more
tight
and
doesn't
make
sense
that
when
a
c-note
already
knows
yeah
99%
of
those
transactions
are
not
relevant
for
you.
Why?
A
You
should
send
you
it,
it
would
increase.
It
cause
a
little
bit.
The
trust
situation,
that
you
are
security,
but
you
get
a
lot
of
resource
issues
and
especially
the
first
startup.
When
you
need
to
download
a
few
hundred
blocks
or
whatever,
then
it
would
become
a
problem
and
any
user
can
run
it.
Who
do
not
just
a
little
bit
of
effort
to
configure
in
the
settings?
You
can
do
it.
You
can
do
it
also
program
elements,
but
you
can
configure
it
in
the
settings
correctly.
A
You
and
in
the
talks
I
mean
they're
in
the
sewers
repository
penis
at
Oxford,
aware
it's
described,
but
you
need
to
do
exactly
and
how
you
need
to
configure
Bitcoin
core
to
be
able
to
be
used
as
a
full
note
for
us
as
a
important
document.
What
you
need
to
set,
which
is
disabled
by
default,
that's
transaction
index
and
the
space.
What
you
need
for
a
Bitcoin
core
will
be
a
little
bit
bigger
or
something
like
5
or
10%,
because
our
ethnic
war
would
create
an
additional
paper
structure
database
which
contains
then
some
information.
A
Anything
more
otherwise,
maybe
we
rock
up
here
for
next
week,
as
we
discussed
before
Cole
already,
maybe
depends
a
little
bit
when
they,
the
tax
paid
for
the
new
trade
protocol
is
updated.
We
could
discuss
the
new
trade
protocol,
but
Craig
has
a
little
bit
health
issues
with
his
back,
so
we
might
need
more
time.
So
maybe
maybe
it's
even
better
when
we
plan
all
ready
to
make
a
session
about
the
Dow.
We
are
getting
closer
to
the
reefs
and
publishing
all
the
their
information
on
the
webpage
and
documents
and
so
on.
A
So
maybe
it's
a
good
time
to
talk.
Make
it
deeper
dive
into
the
Dow
I
would
ask
you
to
avoid
that.
We
are
repeating
many
things
which
have
been
already
discussed
and
it's
a
quite
big
topic
er.
So
we
had
array1
def
session
about
the
Dow
we
post
it
and
in
their
github
issue
for
the
next
rows
before
the
next
def
session.
A
So
I
would
ask
you
that
everybody
who
participate
has
watch
this
video
it's
around
roughly
one
hour
a
half
hour,
but
we
said
we're
waiting
to
repeat
everything
would
not
make
sense
after
say
that
session,
but
we
had
a
few
months
ago
or
and
then
everybody
should
be
already
somehow
in
a
good
yeah,
more
or
less
a
nation.
We
can
discuss
more
what
still
not
well
understood,
yeah
anything
and
make
it
maybe
a
little
bit
more
like
a
Q&A.