►
From YouTube: Bisq developer session 19.03.2019 - DAO Launch Planning
A
Hello,
everybody
to
this
week's
developer
session.
We
have
this
week
on
the
yeah,
we're
getting
very
close
to
the
Dow
launch.
Luckily,
and
once
second
I
had
my
playback
on
YouTube
as
well,
and
a
good
yeah
we're
getting
close
to
the
tower
launch.
So
that
will
be
the
focus
on
this
session
and
I
want
to
give
you
a
little
bit
of
overview
about
important
or
feature
which,
edit
recently
about
quickly
it
just
an
update
about
the
new
trade
protocol
status.
A
It
was
basically
on
our
agenda
to
to
have
a
review
and
a
discussion
about
the
tech
spec
and
it
was
delayed.
I
want
to
give
a
little
bit
a
background
and
about
the
next
releases
and
a
road
map
to
the
gone
to
the
tower
launch
and
then,
if
we
still
have
time
or
asada
preparations,
yeah
talk
to
duel
is
basically
are
where
we,
where
we
edit
all
the
deucer
on
different
errors
like
development
side,
organizational
side,
infrastructure,
side
and
so
on.
A
For
data
launch-
and
maybe
you
hope
everybody
has
time
to
have
a
look
to
this
and
add
anything
if
anything
is
missing
and
if
time
permits,
maybe
we
can
discuss
about
this
as
well.
Otherwise,
I
think
we
can
postpone
it
to
smaller
calls
with
concrete,
with
the
complete
contributor
who
is
working
on
something,
so
maybe
I
start
with
a
quick
overview
which
is
not
related
directly.
Regarding
the
new
trade
protocol
there
yeah
there
was
nine
Minh
and
Craig
who
started
to
work
on
this
a
few
months
ago.
A
We
shift
their
resources
and
so
on.
At
the
moment
we
don't
have
another
developer.
Who
could
take
over
this
project?
So
probably
will
I
have
to
take
it
up
once
the
Dow
is
life,
I
mean
that
thou
has
the
highest
priority
at
the
moment.
So
I
will
not
focus
on
this
at
all,
but
assume
we're
life
and
everything
is
good.
All
right
will
become
my
hyper.
Your
task
yeah
we
want
you
to
get
this
tech.
Spec
diamond,
has
worked
continue
to
work
on
the
tech
spec
and
it
was
close
to
final.
A
We
just
decided
because
they
will
not
work
on
this
as
a
team
anymore
and
when
I
work
on
it,
I
will
write
the
tech
spec
for
myself.
I
don't
need
somebody
else
to
write
me
a
tech
spec,
so
it
doesn't
make
sense
that
he
spends
more
effort
on
this
and
yeah
it's
just
more
efficient
when
I
do
it
than
myself
so
and
I
will
not
have
time
to
work
on
this,
so
there
will
not
be
a
tech
spec
before
we
are
really
good
with
our
launch.
A
I
could
still
internet
one
of
the
next
dev
sessions
when
there
is
time
can
give
a
little
bit
of
an
overview.
There
has
been
a
few
important
changes,
especially
regarding
the
arbitration
arbitration.
It
was
planned
initially
to
get
cut
off
completely,
but
then
we
decided
that
it's
maybe
too
radical.
So
we
found
a
solution
to
to
support
arbitration
system
option
on
optional
basis
and
try
to
fade
it
out
over
time,
but
more
Oh
a
few
about
all
this
in
one
of
the
next
developer
sessions.
A
So
it
will
be
just
that
I
explained
it
what
I
know
and
what
I
have
in
the
brain
I
mean
there's
a
basic
kind
of
text
back
there,
but
it's
not
updated
with
this
new
changes
and
so
on.
So
it
will
not
be
this
real
review.
Where
I
ask
everybody
to
really
have
the
clothes
did
they
look
on
it
because
yeah,
we
don't
have
the
documents
for
this
beside
that
yeah
I
want
to
give
you
an
overview
about
this
new
feature
with
this.
You
have
probably
seen
it
when
you
run
from
Swiss
Cottage
Master.
A
A
That
should
help
us
to
detect
any
concerns
or
issues.
So
if
any
node
is
out
of
consensus
with
any
other
node,
it
will
be
detected
the
way
how
it
works.
We
have.
We
have
basically
two
different
areas
of
important
data
for
consensus.
One
is
the
data
which
is
derived
from
the
Bitcoin
blockchain,
and
the
other
data
is
derived
from
the
peer-to-peer
network
data,
which
is
the
proposal
later
and
the
blind
wrote
beta
and
especially
those
data.
A
They
are
not
guaranteed
that
they
arrive
at
every
peer,
so
that
could
be
as
basically
expected
behavior
that
they
can
be
that
some
of
this
data
is
not
distributed
to
all,
and
we
still
need
to
get
to
a
consensus
in
such
situation
and
to
yeah
to
really
see
the
full
state
of
a
local,
node
and
home
can
be
able
to
compared
with
any
other
node
I
added
a
chain
hash.
Our
hash
change.
It's.
A
Basically,
it
takes
a
hash
of
your
for
now
state
at
one
main
model
for
the
tower,
which
called
tau
state,
and
we
made
it
now
deterministic.
So
all
the
data
sets
collections.
There
are
now
so
what
it
that
mystically,
so
that
everybody
is
when
you
create
a
hash
from
the
whole
data
model
that
this
hash
is
deterministic.
Lee
is
the
same
for
everybody,
this
hash
or
D
state
the
change
with
every
block.
So
with
every
block
that
can
be
a
new
new
transactions
that
can
be
changes
from
the
governance
side.
A
It
can
be
new
proposals
or
new
votes
or
revoked
result,
and
all
this
has
influence
on
the
tau
state,
but
it
happens
always
when
a
new
block
arrives
and
the
block
get
past
first
and
then
some
other
consensus
code
is
executed
when
this
is
all
complete.
So
when
all
this
code,
which
can
change
the
Doucet,
is
completed,
then
we
are
creating
a
hash
and
it's
basically
one
half
by
for
every
block
and
we
are
creating
and
a
chain
of
this
hashes.
We
were
taking
always
the
previous
hash
for
creating
the
new
hash.
A
So
we're
adding
the
previous
session
in
together
with
the
hash
of
the
Tao
state,
to
create
a
new
hash,
so
every
hash
is
is
carrying
with
that
the
whole
history
of
the
chain.
So
when
you
have
a
specific
block
height
to
hash
the
same
with
some
other
load,
you
can
be
sure
that
all
the
history
is
the
same
as
well,
because
when
there
would
be
any
change
of
a
previous
hash,
resulting
hash
will
be
completely
different
as
well.
A
So
I
must
know
new
idea,
that's
how
Bitcoin
works
basically
or
basic
idea
of
Bitcoin,
and
we
are
when
you
start
up.
You
are
requesting
this,
this
hashes
from
the
seed
nodes,
so
at
least
from
minimum,
usually
minimum
two
nodes
can
be
more.
You
get
already
a
hashes
and
you
see
if
you
are
in
consensus
with
those.
A
So
when
you
go
on
this
screens
of
this
network
consensus
or
monitoring,
you
will
in
the
first
time
when
it's
read,
then
you
out
of
consensus
and
you
see
which
notes
are
and
how
many
nodes
have
a
different
hash
and
then
it
depends
on
the
circumstance
bit
more
complex
how
to
resolve
it.
But
basically
the
best
way
would
be
to
just
rebuild
your
tau
state.
A
As
you
can
do
this
in
the
settings
to
rebuild
from
genesis,
then
you're
rebuilding
all
and
when
you're
still
out
of
consensus,
then
either
we
have
really
a
consensus
issue
or
one
of
those
nodes
which
delivering
you.
The
data
is
out
of
consensus,
not
your
fault,
and
it
helps
you
when
you
see
that
there's
just
one
node
out
of
five
which
have
a
different
state,
then
it's
probably
not
your
problem.
It's
the
problem
of
the
other
node.
A
When
it's
a
c-note,
we
can
fix
it
quickly
by
checking
the
signal,
then,
maybe
restarting
it
or
researching
it.
When
it's
a
random
peer,
we
basically
have
nowhere
a
to
tell
the
random
beer
at
the
moment.
Maybe
we
can
add
something
to
notify
him
or
whatever.
At
the
moment,
in
with
our
test
net,
we
have
not
seen
any
consensus
issues.
Everything
looks
good
yeah
and
then
there
are
two
other.
A
So
the
one
is
for
this
tau
state
and
then
there
are
two
for
this
peer-to-peer
network
data
for
the
proposals
and
for
the
blind
votes
here,
it's
a
little
bit
more
tolerance
possible
because
it's
it
can
be
valid.
As
I
said
before,
that
you
didn't
never
receive
one
of
the
proposals
and
then
you
would
have
a
different
state
like
synchro's,
that
made
a
screen
share
in
the
show
it
yet
technically
perfect
exclusivity.
A
You
would
yeah
it
could
be
well
it
basically
that
you
didn't
receive
one
of
the
proposals
and
then
you
create
the
different
hash,
because
the
hash
is
just
graded
from
the
list
of
proposals
for
this
cycling.
So
the
proposals
get
published
in
the
proposal
phase.
My
people
are
making
their
proposals,
but
we
ignore
all
those
because
at
this
time
for
both
will
come
and
go.
You
can
remove
the
proposal
only
at
the
beginning
of
the
blind
road
phase.
A
A
It
helps
us
here
to
detect
this
and
to
find
out
why
they
are
not
well
published.
We
have
the
issue
with
the
peer
to
peer
network
or
whatever,
and
there's
already
quite
a
lot
of
code
to
help
to
avoid
this,
so
that
you
have
to
republish
your
proposal,
and
you
have
to
get
a
lot
of
resilience
on
that
side.
A
They
are
at
the
reveal
phase.
We
are
making
the
snapshots
where
we
are
creating
the
hash,
and
here,
when
you
out
of
consensus,
usually
a
restart
health
because
with
restarting
you
are
requesting
the
state
again
from
the
seed
notes
and
when
you
miss
it
and
to
see,
do
not
have
it
then
you're
in
sync
again.
So
here
it's
less
critical.
A
It
just
helped
us
to
detect
any
issue
in
there
on
the
consensus
side
for
the
network,
so
I
think
that,
at
least
for
me
it
was
very
important
to
be
really
sure
that
it's
not
only
by
chance
that
result
are
the
same
for
everybody
in
the
world
result,
but
that
really
all
the
data
are
100%
to
sing
like
it
has
to
be.
We
will
add
those
monitoring's
also
to
the
monitor
framework
from
Florian.
A
I
have
not
discussed
with
him
the
details,
how
to
do
it,
but
it
will
have
basically
similar
like
here
but
more
in
a
broader
range,
also
not
only
for
the
cenotes,
what
you
are
connected
to,
but
with
all
seed
nodes,
and
maybe
even
with
the
whole
network
and
and
more
salsa.
But
yet
here
you
get
also
updated
as
well
with
every
new
block.
Every
peer
is
broadcasting
their
hashes
to
the
network,
so
with
all
your
connected
peers,
depending
how
many
peers
have
updated
now
to
the
new
version.
A
At
the
moment,
there
are
not
so
many
zombie
tools
who
are
running
from
suez
code,
but
basically
from
all
your
connected
peers
from
the
90s,
you
should
receive
also
the
hashes
and
in
the
best
case
you
have
basically
received
it
from
90s
and
serial
conflicts.
When
you
have
a
conflict,
you
can
click
on
on
it,
and
then
you
will
see
this
peer.
You
can
request
and
all
the
data
from
the
peer,
because
by
default
from
the
seed
nut,
you
only
get
the
hashes
of
the
last
ten
blocks.
A
It
would
help
to
find
out
that
which
block
the
consensus
issue
happened.
So
when
you
would
then
request-
and
you
see
ya
at
a
certain
block
height
the
the
conflict
started,
then
we
see
okay,
it
happened
here
and
we
can
investigate
a
white
happen
and
what's
the
problem
goody,
any
questions
to
this
topic
also
to
the
stuff
before
sorry
that
I
didn't
didn't,
make
a
break
and
asked
you
if
he
begged
me
not.
A
The
UI
is
a
little
bit
technical
at
the
moment
that
could
need
more
love,
and
maybe
Christopher
has
a
little
bit
time
to
polish
it
and
make
it
easier
to
understand.
It--And
take
a
lot
of
care.
For
me,
it
was
more
important
for
myself
to
have
a
control
about
the
tower
state,
but
for
the
normal
user,
I
mean
at
the
moment,
I
think
it
doesn't
alert
because
I
didn't
want
to
to
shock
the
network
when
there
I
want
to
look
sure
of
it.
A
A
That
I
mean
a
basic
risk
for
a
user
could
be
when
you're
on
on
on
a
different
consensus
that,
for
whatever
reason
you
get
a
different
result
and
somebody
who
requested
compensation
in
your
version
he
got
accepted
but
from
the
rest
of
the
network,
who
didn't
got
accepted
and
he
is
selling
me
obvious
queue
and
you
accept
it.
You
would
accept
it.
A
But
then,
when
you
want
to
send
this
PSU
to
somebody
else,
it
would
be
invalid
psq
because
at
the
end
it
was
never
issued
and
to
avoid
something
like
this,
it's
important
that
to
use
it
and
be
sure
that
they
are
insolent
with
the
network
and
not
getting
into
this
risk
zone.
It's
at
the
end
of
quite
a
small
risk,
because
a
lot
of
coincidence
that
you
would
train
with
disappear
and
so
on
and
to
get
this,
but
if
there
would
be
bigger
consensus
issues
would
be,
of
course,
more
time.
It's
basically
terrible
damage
versus.
A
That's
a
good
point
that,
with
mr.
Tao
step,
it's
actually
a
valid
situation,
so
it
can
be
that,
for
I
think,
the
deepest
really
works
on
main.
That
would
have
been
four
blocks
as
far
as
I
know,
but
also,
if
you
know
another
number,
please
let
me
know
so
it
can
be
that
in
the
worst
case
you
have
three
or
four
blocks
the
different
state
and
it's
red.
A
That
was
another
reason
why
I
prefer
to
not
make
too
much
about,
because
this
alert
should
only
come
when
you
are
continuously
after
four
blocks
or
so
still
out
of
sync.
Then
there
is
a
shoe
because
up
to
a
few
blocks,
it
can
be
well
it
that
you
are
on
another
chain
like
another
user,
and
then
you
get
a
different
ash
and
after
the
rework
is
resolved,
you
were
back
on.
The
same
reacts
are
handled
basically
by
rebuilding
the
Dow
State.
So
when
you
have
a
rework,
you
are
starting
from.
A
The
latest
snapshot,
try
to
rebuild
it,
and
so
it
should
resolve
by
itself.
I
tested
it
roughly,
not
100%,
maybe,
but
it
should
be
handled
for
their
proposal
and
the
blind
vote
phases.
We
are
basically
only
taking
the
height
of
the
block
chain
as
when
we
entering
the
certain
height
wearer,
where
the
blind
wrote
or
the
vote
reveal
phase
starts.
So
that
should
be
related
to
react.
We
have
also
the
break
with
the
ten
blocks
in
between
so
yeah.
A
So
any
rework
will
cause
basically
a
small
issue,
a
period
of
consensus
issue
and
maybe
in
the
UI.
We
should
explain
this
a
little
bit
better
because
it
might
be
a
little
too
shocking
for
you.
So
when
you
see
something
red
and
not
getting
the
information
that
it
might
be
a
valid
case
in
case
of
a
rework
Oscar,
do
you
know
what's
the
deepest
reworks
on
the
Bitcoin
main
that
has
been
in
history.
B
B
B
A
Then,
let's
jump
to
the
next:
that's
there
regarding
the
releases,
as
we
have
a
few
important
features,
what
we
still
want
to
get
in
for
the
launch,
mainly
a
new
UI,
where
we
show
facts
and
figures
like
the
charts
about
the
price
development
over
time.
The
burn
rate
over
time,
the
issuance
rate
over
time,
maybe
some
more
inclusive.
This
working
on
this
already
another
is
to
improve
the
proposal.
A
At
a
voting
few,
where
you
can
vote
on
proposals
and
the
result
view
at
the
moment,
you
need
to
scroll
down
specially
for
voting.
People
don't
see
the
button
at
the
bottom
for
voting,
and
it's
not
well
done
from
the
UI
at
the
moment.
So
crystal
will
work
on
this
to
find
a
better
solution
for
that
for
getting
a
better
overview
and
better
usability
beside
that
working
on
some
started
and
nearly
finished
with
some.
A
You
have
to
finalize
verification
stuff,
which
was
never
really
completed,
mainly
regarding
change
parameters
and
proposals,
and
a
few
other
smaller
issues
as
a
tribe,
basically
get
our
github
issue
list
completed,
which
are
still
pending
and
I
assume
we
could
get
from
development
side
more
or
less
ready
end
of
the
week,
maybe
beginning
of
next
week.
So
and
then
we
want
to.
We
needed
a
good
testing
phase,
because
there
have
been
a
few
important
other
changes
like
from
peer
to
peer
network
and
from
yeah.
A
V,
0
15
release
the
master
from
we
set
with
support,
that's
meat
plant
that
will
take
us
minimum
four
or
five
months
to
get
there
and
on
the
page,
Finch
a
stylist
thinks
things
are
not
really
complete
and
not
well
fast
idiot
and
specially.
We
support
for
different
work,
multiple
wallets
and
such
stuff,
so
I
don't
count
that
we
get
this
in
also
between
three
and
six
months.
I
would
estimate
roughly
yeah
this
branch.
What
we
have
now.
A
It's
mainly
a
kind
like
a
refactoring
range
and
a
clean
up
branch
and
few
improvements
and
missing
bug
fixes
which
also
supported
from
Bitcoin
Lawson
from
this
country
master.
But
it
shouldn't
contain
any
critical
change.
They
should
carry
any
big
risk,
but
of
course
we
need
to
be
sure
it
requires
a
little
bit
more
intense
testing,
but
especially
on
the
peer-to-peer
networks
that
we
had
a
few
more
risky
changes
as
we
as
developers
are
using
these
versions
and
have
not
found
big
problems.
There
shouldn't
be
anything
brokered
about
its.
A
That
should
be
basically,
then
the
last
feature
release
are,
and
basically
then
is
a
code
freeze
for
anything
critical
and
then
we
need
to
make
another
testing
round,
also
not
a
week
for
testing
that
out
features
because
on
the
Doucet,
I've
been
for
sure
some
critical
changes
to
be
sure
that
it
hasn't
broken
anything
and
that
we
get
to
as
compared
to
correct
result
face
again
and
when
there
are
no
bugs
are
no
reason
for
another
release.
We
will
go
straight
directly
to
their
launch
to
the
main
net
launch.
A
Otherwise,
more
likely
there
will
be
another
small
release
with
just
small
bug,
fixes
and
small
improvements,
nothing
criticalness
in
risky,
maybe
yeah
one
and
a
half
week
later
and
not
a
week
later,
and
then
we
are
basically
ready
for
life
and,
depending
on
the
other,
two
deuce
on
the
organizational
side,
communication
side,
infrastructure
side
that
we
need
to
get
everything
really
prepared
and
when
we
feel
that
we
have
forgotten
every
aspect,
we're
ready
for
launch
and
also
still
an
open
question.
How
we
do
the
launch.
A
A
It's
still
a
little
bit
open
question
also
how
much
we
want
yeah,
if
it's
more
soft
launch,
which
is
just
dedicated
to
our
community,
to
the
best
users
or
if
we
want
to
make
a
little
bit
more
communication
to
a
broader
audience
like
sending
out
press
release
messages
to
journalists,
or
so
probably
it's
better
to
keep
it
low
level
and
focus
on
on
the
bisque
users.
But
we
can
discuss
this
still
so
yeah,
that's
a
rough
plan,
so
anything
bigger
like
at
API
changes.
A
Unfortunately,
at
that
time
it
also
we
have
to
put
on
this
after
the
doll
launch
and
some
bigger
changes
planned
on
the
network.
European
Network
site,
but
as
Florian
also
has
at
the
moment
this
issues
with
dentist
he's
not
fully
available
and
it
would
be
a
bigger
riskier
change.
So
we
will
postpone
this
as
well
and
yeah.
Basically,
anything
which
carry
some
risk
will
be
postponed
minimum
one
months
after
the
doubt
large
when
everything
went.
Fine
yeah.
A
You
might
notice
I
started
already
a
main
that
Genesis
transaction
with
half
a
Bitcoin
chest
and
it's
more
account
like
a
small
private
testing,
because
it's
real
money
also
the
psq-
is
now
backed
by
relatively
Bitcoin.
So
it
spent
half
a
bit
offended
sup,
nothing
and
anybody
who
wants
to
test
and
helped
us
you
need
to
run
from
sua
students
on
to
be
able
to
test
here
is
welcome
and
to
get
in
touch.
A
A
So
far,
I
have
not
seen
any
issues
are
anything
which
can
break
content,
so
the
normal
testing
can
be
done
on
on
the
normal
test
that
there
shouldn't
be
no
difference
and
as
we
didn't,
we
don't
need
to
do
super
intensive
testing
on
this
mean
that
it's
called
beta
testers.
When
you,
when
you
go
to
the
settings
where
you
can
choose
the
network
where
you'll
find
the
towel
test
net,
there
is
now
a
new
one
which
is
called
tau
a
beetle
net.
A
Yeah
I
said
when
somebody
wanted
to
help
us
here
testing
we
have
very
short
faces
just
one
day,
one
day
working
on
the
proposal
and
so
on,
so
that
we
get
a
few
cycles
done
before
launch.
We
don't
do
intensive
testing
tough
to
get
a
few
proposals
and
a
few
roads
and
check
if
everything
works.
Okay
and
I
said
it's
mainly
focused
on
performance
issues
or
maybe
with
rework,
because
that's
maybe
I
think
what
we
still
should
work
on
to
try
to
mimic
reworks
on
our
towel
test
net.
A
So
artificially
creating
a
reacts
there
on
on
domain
that
when
we
have
some
luck,
there
will
be
some
reorg
in
the
in
this
meantime.
That's
another
thing:
it
would
be
good
to
have
contact
monitoring
for
historical,
a
turn
for
real
23
X
happened,
I'm,
not
sure,
that's
very
trivial
and
maybe
like
a
system.
So
this
is
where
you
can
look
up
this,
but
it
would
help
us
when
we
see
some
issues,
then
we
see
ok,
it
happens
because
of
a
real
girl
out.
B
No,
not
really
not.
The
only
thing
which
would
be
great
is
for
this
critical
changes
depending
on
the
bit
crunchier,
and
that
player
update
and
also
in
the
p2p
network.
Could
you
or
Oscar
check
the
test
cases
that
are
available
if
we
have
to
add
new
ones
or
if
it's
already
covered
by
the
existing
ones,
just
be
sure
if
we
have
more
people
getting
testing
cycles
that
we
are
not
missing
out
in
part
itself,.
A
I'm
pretty
sure
that
was
the
correct
me
if
you
have
another
opinion
that
are
on
the
pit
clean
site
is
nothing
basically
no
I
mean
yeah.
A
small
change
was
regarding
there.
We
restore
from
seat
words
before
the
restart
was
optional.
Now
it's
it's
done
automatically
and
there
have
been
some
bug
fixes
in
that
area,
but
I
tested
this
already
and
I
can't
cover
this
test
for
to
release
as
well,
but
I'm,
not
aware
of
anything
which
would
basically
represent
the
test
case.
A
It's
just
that
basically
smoke
test
that
everything
works,
but
also
some
users
are
using
their
life.
The
master
for
trading
also
I
think
when
there
would
have
been
a
problem,
it
would
have
been
if
at
all
program
quickly,
that
transaction
doesn't
make
it
created
over
ever
and
we
have
not
heard
anything.
B
A
And
on
the
peer-to-peer
network
side,
I
also
don't
think
that
it
will
be
covered
by
a
new
test
case,
basically
smoke
testing
that
everything
goes
fine
and
yes,
some
developers
are
running
all
the
time
most
anyway.
I
don't
expect
that
there
are
problems,
but
yeah,
then
I
will
move
over
to
this
preparations.
To-Do
list
I,
it's
just
basically
a
rough
to-do
list.
A
I
was
wondering
to
make
it
more
organized
in
github
or
whatever,
but
I
basically
want
to
leave
it
to
anybody
who
will
pick
up
some
of
those
tasks
and
work
on
this
I
tried
to
assign
some
persons
when
I
was
sure
that,
when
I
knew
that,
like
a
crystal,
will
work
on
this
facts
and
figures
UI
another
stuff,
I
left
it
open
to
me-
yeah
leave
it
to
the
people
that
they
put
a
name
to
that
task.
Dude
just
get
basically
overview.
A
A
B
A
A
A
A
A
Yeah
this
invalid
parameter
changes
I
did
already
not
completely
complete,
but
nearly
there's
open
draft
pull
request
for
this.
Yeah
I
mean
that
that's
done
already.
We
started
already
good
infrastructure,
everybody
who
runs
a
seed
node.
They
need
to
stop
prepare
it
so
that
you
run
Bitcoin
core
because
the
seed
nodes
will
be
in
full
download.
So
they
need
to
have
Bitcoin
core
with
a
special
configuration.
So
before
you
start
it
yeah,
you
have
to
check
out
the
documents
as
you
need
specially
the
transaction
index
enabled.
A
A
A
For
this
note,
instead
of
risking
that
all
the
signals
are
crashing
and
because
we
said
now,
it's
much
more
relevant,
they
are
delivering
the
blocks
for
every
light
note,
most
users
will
run
their
application
in
light
mode
note
where
they
get
the
PS
few
blocks
from
the
seed
note.
So
when
the
signals
are
not
delivering
this
paper,
it's
they
cannot
get
to
the
consensus
or
take
it
don't
get.
They
cannot
use
PS
q.
Basically,
so
it's
much
more
critical.
A
Now
the
seed
notes
like
it
was
before
so
I,
don't
want
to
save
money
on
their
infrastructure
side
like
to
pay
$40
instead
of
$50
to
save
a
little
bit
on
rum
and
then
risk
that
we're
running
out
of
memory
or
whatever.
So
later
we
can
improve
this
and
florrum
will
go
on
to
work
on
this
improvements
on
the
seed
note
that
they're
working
with
stable
and
and
that
the
memory
leak
is
hundred
percent
gone
before
we
are
there.
I
prefer
to
just
be
on
the
safe
side
and
then
with
Florian
is
a
monitoring.
A
That's
not
the
showstoppers
away
when
we
don't
get
there
before
they
launch.
We
still
we
launched,
but
we'll
be
good
to
have
as
soon
as
possible
to
be
sure
on
the
monitoring
site
that
we
have
a
good
few
about
the
health
of
the
Tau
in
the
network
and
especially
on
the
seat
node
side,
then,
on
the
communication
side
or
yeah.
One
important
document
which
is
missing
is
account
like
emergency
plan
when
anything
goes
wrong,
when
there
is
a
consensus,
but
when
it
is
a
hacked,
when
does
whatever
problem
under
tau?
A
Are
we
with
basically
plans
what
we
are
planning
to
do
and
we
have
a
few
security
features
already
built-in
or,
for
instance,
yeah?
We
can
stop
trading
by
disabling
psq,
so
nobody
can
use
psq
for
trading
anymore.
That
could
help
us
already
when
there's
any
problem,
that
we
are
basically
freezing
the
funds
that
nobody
can
sell
or
transfer
the
funds
anymore,
and
we
can
send
out
anyway
a
lot
message
to
everybody.
So
everybody
get
notified
about
this.
A
Another
flag
is
to
disable
it
out
completely,
so
that
now
is
basically
like
now
not
enabled
anymore.
That
will
stop
the
DAO
completely
the
network.
All
these
flags
can
be
overwritten
by
as
a
dyslexic
exist
already
for
other
stuff,
like
the
optic
message
and
where
we
can
pen
users
when
we
like,
we
had
our
very
few
chargeback
cases
as
when
there
is
a
clear
case
that
the
user
was
a
scammer
than
the
only
address
get
banned
or
that
payment
method
for
currencies
get
bent
like
with
it
with
cash
app
and
with
ring.
A
We
figure
out
that
ring
was
not
stable
enough
sent
and
we
removed
it
and
those
are
kind
of
like
we
are
centralized
messages.
I'm
I
have
the
key
to
be
able
to
send
out
this
messages.
I
only
do
it
for
very
serious
things
and
when
I
would
start
to
abuse
this
or
whatever
a
user
don't
agree
to
this,
then
they
can
override
it
by
ignoring
this
developer
messages
program
argument
and
when
they
ignore
it,
we
act
and
the
network.
A
This
message
doesn't
exist
for
him,
but
of
course,
when
we
figure
out
there's
a
big
problem
in
a
tower
and
we
are
stopping
the
tower
and
still
use
a
start
to
trade
we
set
out
because
the
ignoring
this,
then
it's
on
their
own
risk
and
when
we
have
to
restart
in
the
worst
case,
everything
over
and
we
have
to
roll
it
back
in
the
way.
How
we
can
do
it
or
whatever
it
is.
The
disaster
management
will
be.
A
We
don't
take
care
about
those
people
who
ignore
dislikes
because
yeah
when
we
try
to
protect
them
and
they
ignored
it,
then
its
own
risk
and
when
they
lost
money,
then
we
don't
care,
but
beside
that,
when
anybody
would
lose
money
because
of
a
park
or
because
of
a
hack,
we
will
try
to
recover
it
with
reimbursing.
Basically,
we
also
try
to
freeze
such
funds
when
we
can
be
sure
there
was
a
hack,
and
we
know
that
he
has
not
moved
his
funds
already.
A
Then
we
try
to
to
confiscate
it
and
block
it,
and
and
for
this
it's
important
to
react
quickly
as
when
we
see
there's
a
hacker
who
has
created
the
milli,
amperes
QR
codes
in
air,
and
he
still
has
not
sold
it
in
trades.
We
can
disabling
that
out
and
basically
like
this
YouTube,
so
s-band
then
making
a
new
version
out
and
then
he
cannot
move
this
funds
anymore
and
basically
confiscated
and
because
we
have
to
fix
the
bug.
A
So
we
don't
have
stupid
statement
like
hold
it
all
and
then,
when
back
happening,
then
we
are
changing
our
minds.
We
make
clear
when
there
is
a
problem,
we
try
to
fix
it.
The
intention
of
the
tower
is
that
it
works
for
the
project
for
bisk
as
the
governance
and
funding
model
for
transferring
value
from
traders
to
contributors
and
making
it
accessible
that
everybody
can
become
stakeholder.
A
You
can
burn
your
psq
when
you
don't
know
exactly
what
to
do
what
you
do
and
when
you
do
it,
it's
completely
your
own
risk
grown-ups
cube.
We
will
not
help
you
and
we
will
not
accept
the
reimbursement
request
for
some
people
who
are
hacking
around
and
don't
know
what
to
do
when
they
do
it.
They
play
with
fire
and
they
shouldn't
do
it.
Basically,
as
when
they
do
it,
they
have
really
have
to
study
the
source
code
and
know
exactly
the
consensus
food.
A
It's
not
enough
to
reach
the
tech
spec,
because
it's
not
100%
complete.
You
have
only
the
source
code
is
200%
documentation
which
again
are
not
many
people
who
who
would
have
the
knowledge
to
do
this
in
a
safe
way,
even
for
myself,
it
would
be
dangerous
than
it
would
be
very
scared
to
send
some
psq
to
another
wallet
and
try
to
send
it
somewhere
else,
and
there
is
a
in
the
very
early
days.
I
did
it
and
I
managed
it
to
use
tracer.
A
As
for
storing
my
Peters
cue
and
figure
out
how
what
I
need
exactly
to
do,
how
to
send
it
and
back
I,
don't
remember
the
details
again
and
it
will
require
a
little
bit
more
syncing
and
maybe
at
some
point
we
make
a
very
careful
document
about
the
exact
step,
because
it's
a
valid
use
case.
Of
course
people
want
to
have
kept
you
skewed
and
in
a
cold
storage
like
the
tracer
and
it's
just
a
little
bit
a
dangerous
area.
A
When
you
don't
have
hundred
percent
control
how
the
transaction
is
created.
Yeah
your
piece,
you
can't
get
burnt,
end
I
think
it's
possible.
It
just
needs
a
lot
of
care
and
the
very
well
tested
procedure
and
document
and
even
then
I
think
I
would
always
leave
it
to
the
user
or
because
also
to
make
it
clear
to
the
user.
Here
is
our
help,
but
when
you
do
it,
it's
your
risk
at
the
end
are
so
over
long
a
time.
A
Maybe
we
find
some
solution
to
to
support
crazy
directly
in
base,
because
that
would
be
my
or
to
have
some
I.
Don't
know
yet
have
not
much
about
it,
but
of
course
it
would
be
good
to
have
some
solution
for
cold
storage,
which
is
really
safe,
where
you
don't
need
to
delegate
the
risks
to
use
way,
delivering
software,
it
just
works,
but
that
will
take
a
while
and
will
not
be
on
our
highest
priority.
A
Yeah
then,
basically,
for
the
webpage
I
think
we
need
something
for
the
launch,
yeah
updates
from
some
pages,
and
maybe
our
own
page,
for
the
launch
or
whatever
I
have
not
thought
about
it,
but
I
think
that's
for
sure
bigger
to
do,
and
we
should
stop
to
focus
on
this
on
the
organizational
side
feel
free
to
interrupt
me.
I.
A
Just
move
on
to
the
next
step:
we
can
afterwards
can
have
a
discussion
about
some
details
also,
but
if
you
have
a
burning
question,
just
interrupt
me
yeah,
except
this
for
the
signal
operators
they
have
to
prepare
already.
It
takes
a
few
days,
at
least
to
sync
Bitcoin
core
I've
started
already
to
send
out
emails
all
past
contributors
from
the
original,
Genesis
distribution
and
collecting
the
Bitcoin
addresses
unfortunate
will
not
have
time
to
get
much
in
contact,
because
many
are
good.
Friends
and
I
have
not
been
much
in
touch
over
time.
A
A
A
There
are
a
few
proposals
regarding
the
bonded
roles,
as
which
bonded
roles
we
supported
it
out.
We
have
in
the
Kitab
issues.
We
have
a
lot
of
roles
in
Scylla,
a
blurry
area,
I
mean
not.
Every
real
role
in
in
the
pistol
is
a
what
people
are
doing
is
represented
as
a
role
in
github,
then
not
all
those
role
are
really
relevant
that
they
should
be
in
the
Dow
I
mean
my
my
main
rationale
when
I
edit
the
roles
so
that
ours,
which
role
can
theoretically
create
damage
like
the
one
who
controls
the
domain.
A
Of
course,
you
can
create
a
webpage
like
Bitcoin,
calm
and
create
damage
for,
for
the
project
like
a
roach
away,
is
created
for
a
Bitcoin,
and
then
he
should
be
punished
by
confiscating
the
bond.
A
seed,
not
operator,
who
don't
care
and
don't
have
a
stable
node,
creates
damage
for
an
apple
because
yeah
it
decreases
usability
so
I
mean
complications,
always
the
last
resort.
It's
only
really
for
bad
attention
and
severe
violations.
Usually
we
just
remove
this
when
a
signal
operator
doesn't
really
care.
We
remove
him,
and
somebody
else
will
take
over
this
note.
A
So
not
so
critical.
So
it's
a
question:
how
much
house
literally
I,
don't
assume
that
anybody
of
the
operators
is
malicious.
We
only
give
important
thing
is
that
becoming
a
role
owner
will
be
already
a
voting
process,
so
everybody
who
runs,
who
has
a
role,
will
basically
now
request
the
role
by
voting,
and
only
when
you
get
accepted,
then
you
need
to
to
lock
in
the
pond
and
then
he's
basically,
obviously
the
role
Horner.
A
But
one
issue
is
that
some
of
the
but
depending
on
the
amount,
how
much
we
require
for
the
pond,
which
is
a
little
bit
problematic
as
long
we
don't
know
the
psq
price.
At
the
moment
we
assume
it's
$1,
but
when
the
psq
price
is
$5
or
$10,
then
the
bonds
are
way
too
high.
The
bonds
are
locked
in
for
a
long
time.
At
the
moment,
we
don't
have
a
feature
that
you
can
basically
just
unlock
and
automatically
read
new
to
bond
with
a
new
change,
slower
required
bond
amount.
A
A
Also,
I
would
suggest
that
we
just
wait
a
little
bit
a
few
to
three
months
before
we
starting
implement
as
a
using
the
the
bonded
rows.
Then
also
the
contributors
have
more
time
to
earn
more
funds.
We
know
more.
What's
the
real
price
will
be
because
at
the
moment,
some
after
contributors
who
are
who
are
already
executing
some
roles
like
running
seed
nodes,
they
have
not
earned
so
much.
A
We
ask
you
that
they
would
be
able
to
pay
the
pawns
which
are
required
at
the
moment,
maybe
they're
just
too
high,
but
maybe
three
flavor,
because
I
mean
we
are,
and
it's
of
course
it's
always
very
difficult.
What's
the
maximum
damage
when
I
abuse
the
bisque
domain
I
mean
you
said,
ten
thousand,
this
is
hundred
thousand.
Is
a
million
dollar,
it's
very
hard
to
say
so.
A
I
would
yeah
it's
an
open
question
how
we
deal
with
this,
but
it
would
be
basically
good
when
we
get
them
when
you
have
time
to
check
out
these
proposals
to
see
if
there
is
missing
an
important
role,
basically
said:
I
want
to
limit
it
to
those
roles
where
you
can
create
damage.
Also,
everything
which
represents
bisque
to
the
outside
world,
like
the
Twitter,
account
the
domain.
Of
course.
Everything
which
gives
you
a
privileged
access
like
running
the
relay
note
for
her
notification
of
mobile
notifications.
A
Theoretically,
he
could
try
to
collect
data
and
abuse
the
stator
and
learn
a
little
bit
more
about
their
the
users
like
yeah.
We
want
to
do
so.
It
has
a
little
bit
of
trust
involved,
yeah
being
responsible
for
important
repository,
mainly,
of
course,
the
Bitcoin,
the
biskits
repository,
but
other
repositories
like
the
bit
country
talk
or
the
net
layer,
library,
extra
libraries,
which
are
very
essential
for
our
project
and
which
are
basically
already
now
like
the
net
layers
covered
by
Florian
Pitt
countries.
A
Already
Oscar
is
telling
a
basically
of
that
repository
already,
so
that
might
make
sense
to
add
that
one
for
this,
because,
basically
we
need
to
trust
those
persons
that
this
we
are.
They
are
own
of
the
codebase
there,
but
for
other
roles
like
for
the
top
setting
for
the
tox
page,
we
don't
have
their
own
role
because
we
have
I,
don't
think
that
you
can
really
create
a
lot
of
damage
and
when
somebody
would
start
to
publish
bad
content
there,
we
just
I
mean
the
github.
A
Admin
can
already
walk
there
access
there
and
we
can
fix
this
quickly.
I
think
it's
not
really
a
risk
that
can
happen
to
the
project.
So
I
would
like
to
to
limit.
Maybe
have
already
too
many
roads
define
it.
We
kick
out
a
few
I
test.
It
with
changes
that
we
are
a
little
bit
flexible,
like
the
bond
amount,
can
be
changed
without
big
problems.
A
We
can
add
new
roles,
I
think
I'm,
not
sure
if
we
can
remove
roles
that
probably
causes
troubles
when
they
have
been
used
in
past
comparing
past
proposals
or
voting
rounds.
But
there's
some
level
of
flexibility
here,
but
I
think
best
is
to
be
just
or
whoever
it
is
to
just
use
it.
Where
really
helps
us,
when
we
are,
we
really
needed
and
not
overuse
it
and
maybe
start
a
little
bit
delayed
and
slowly
and
not
the
heart
requirement.
We
are
not,
we
don't.
We
are
not
in
the
state
that
completely
anonymous
role.
A
Owners
take
over
some
roles
and
we
need
this
as
security,
because
there's
no
trust
relationship,
everybody
who,
who
executes
a
role
every
health,
the
trust
relationship
because
they
worked
already
seems
quite
evolved
for
a
project.
So
there's
no
reason
to
assume
that
it
carries
any
real
risk.
So
yeah,
then
another
sorry.
B
A
The
mediator
Swee'pea,
but
that
requires
a
new
the
new
trade
protocol.
As
soon
as
it's
out,
there
will
be
a
role
for
the
mediator
and
that's
for
sure
interesting,
then,
to
get
more
mediators
and
that
can
be
anonymous.
People
at
the
end
and-
and
there
are
contests
and
really
important
because,
of
course,
a
mediator
who
is
not
working.
Currently,
he
is
hurting
the
project,
of
course,
and
yeah
regarding
the
parameter
changes.
A
Another
area
I
don't
want
to
overuse
it
that
we
have
for
every
small
details
possible
to
change
it
over
working
to
be
only
limited
to
to
that
areas
where
it
makes
sense
where
we
can
assume
it
makes
sense
to
change
it
and
would
be
good
that
everybody
review
this
proposal
to
see.
If
anything
important
is
missing,
then
the
parameters
have
a
maximum
and
a
minimum
change.
A
Also
when,
when
it's
allowed
to
change
to
the
maximum
to
the
250
percent
of
the
current
value
and
the
maximum
decrease
is
to
also
you
can
go
down
by
1
over
2
and
the
maximum
increase.
When
it's
numbers
read-
and
it
means
you
can
maximum
increase
it
to
three
times
to
higher.
When
you
like
the
current
value,
it
always
reflects
to
the
current
value.
So
with
repeated
voting,
we
can
repeat
it
to
change
you.
A
So
when
the
maximum
at
amendment
minimum
is
two
like
for
many
of
the
parameters
you
can
double
up
or
double
down
with
every
voting
at
the
moment.
Probably
there
this
maximum
minimum
limits
are
maybe
too
high
will
be
yeah,
we'll
probably
change
it
to
a
little
bit
more
conservative
values
they
some
when
you
have
additional
protections
like,
for
instance,
for
the
percentage
required
that
the
proposal
is
accepted
cannot
be
below
50%.
It
doesn't
make
sense
that
you
accept
something
with
20%
protein
I
think
that's
not
logical.
A
A
The
required
percentage
for
for
most
proposals
is
50%,
but
for
some
like
compensation,
the
confiscation
requests,
I
think
it's
85
percent
and
for
changing
a
parameter,
75
percent,
and
when
we
want
to
change
it
to
a
lower
value,
we
can
go
down
a
little
bit,
but
we
cannot
go
below
50
percent
and
there
are
some
other
restrictions
as
well
which
overrule
basically,
even
if
you
would
directly
be
able
to
change
it.
20
percent
lower
and
you're
already
at
51
percent.
You
cannot
go
lower,
but
yeah.
A
A
But
basically
it's.
It
carries
some
flexibility,
but
we
shouldn't
come
too
much
on
this,
so
we
should
get
up
to
original
when
it's
as
good
as
possible
that
we
don't
need
to
change
them
and
also
I
mean
this
parameter
change.
It's
basically
exceptional,
it's
not
that
which
now
we
should
play
around
to
find
bugs.
But
when
we
alive
there
should
be
a
strong
reason
why
we
really
want
to
change
the
only
values
which
right
change
more
often
over
time
out
of
fees
and
especially
also
that
the
fee
for
the
arbitrator.
A
Initially,
it
will
be
zero,
but
over
time,
the
the
user
with
the
new
trade
protocol.
They
have
to
pay
a
higher
fee
when
they
want
to
still
have
support
of
arbitration,
to
create
a
little
bit
of
pressure
that
people
are
moving
over
to
the
new
system,
and
so
such
parameters
are
expected
that
they
will
change
more
frequently
other
should
yeah.
A
We
should
avoid
to
change
it
because
at
the
end,
all
those
changes
could
lead
to
a
consensus
back
when
we
miss
something
and
testing
and
better
to
not
risk
it
when
it's
not
really
required,
that's
why
they
have
also
very
high
quorum
and
very
high
percent.
Her
threshold
threshold
is
called
the
required
percentage
quorum
is
the
required
psq
for
voting.
So
when
only
when
took
the
quorum
is
100,000
psq
and
only
a
few
people
have
voted
on
this
at
all,
and
it's
only
50,000
PQ,
which
was
used
in
the
strict
and
it
will
be
rejected.
A
Then
yeah
the
list
for
the
genesis
distribution
might
ask
yeah.
We
still
need
to
discuss
a
little
bit.
We
had
a
right
in
the
past
discussion
about
how
we
are
treating
the
contributions
from
the
contributors
who
have
participated
in
their
inter
boating
and
in
their
app
after
the
genesis
launch-
and
we
had
some
discussions
regarding
this
will
keep
this
a
little
bit
up
for
closer
to
the
launch.
But
we
want
to
apply
some
factors
that
those
who
have
contributed
over
long
term
that
they
have
proved
that
they're
very
yeah.
A
They
stick
to
the
project
and
and
those
contributions
who
are
leading
more
into
the
past
that
they
get
the
yeah
that
they
get
the
factor
that
was
also
applied
in
the
original
Genesis
distribution.
It's
like
a
bonus
in
a
company
those
people
who
worked,
who
who
have
been
there
from
the
very
beginning
and
took
more
risk
and
at
the
end,
every
contributor.
A
It's
like
a
shareholder
in
the
company,
everybody
just
get
paid
in
this
kinda
like
equity,
so
everybody
takes
some
risk
and
those
with
taking
the
risk
one
and
a
half
year
ago
the
risk
was
much
higher
like
now
and
also
those
who
has
contributed
over
the
whole
time.
They
delivered
a
higher
value
like
other
contributors.
We've
just
worked
for
one
or
two
months
and
then
left
again.
A
Yeah,
we
still
I'm
not
sure
if
we
do
it
before
too
long
too
after
the
launch,
but
I
would
like
to
distribute
a
little
bit
more.
The
current
node
operators
I'm
still
running
a
little
bit
too
many
of
the
nodes
and
yeah
I
would
like
to
distribute
this
a
little
bit
better.
I,
don't
want
to
put
too
much
effort
into
this,
and
especially
with
the
seed
nodes.
A
I
prefer
to
have
more
direct
access
when
there
are
some
issues,
I
can
fix
it
quickly
and
don't
not
depending
on
somebody
else
who
is
maybe
sleeping
and
then
I
have
to
wait
10
hours
before
we
can
get
get
it
fixed.
So
that's
still
open
question,
but
basically
there,
if
you
nond,
are
related
areas
like
the
notifications
relate
the
markets
page.
B
A
They're,
not
super
critical
and
once
I
had
really
a
big
problem
where
all
signals
were
dead
because
of
out
of
memory
problems
even
end
of
the
network
recovered
as
long
as
there
are
other
nodes
which
are
life
for
a
longer
time,
so
the
data
is
not
vanishing.
It's
just
a
usability
decrease
when
a
new
node
starts
and
all
the
signals
a
town.
Yet
then
he
needs
longer
to
get
the
date
turns
on
and
when
it's
a
completely
new
node.
A
Of
course
he
cannot
connect
at
all
to
the
network
and
they
need
to
ask
for
some
only
on
addresses
on
the
forum
or
where,
but
provider
notes
are
very
no.
No,
basically
only
no
maintenance
needed
there
at
all.
It's
simple
to
set
them
up
here,
Mary,
don't
have
lot
of
resource
requirements.
Market
page
is
a
little
bit
a
bigger
effort.
Her
and
I
said
notifications
relay
support
similar,
like
the
provider
note
even
lower
yeah.
The
documents
are
because
it's
so
simple
at
the
end.
At
the
end,
you
just
check
out
it
up
your
thought.
A
Your
note
with
a
few
program
arguments,
that's
it
and
because
most
of
those
nodes
we
don't
need
20
people
for
those
are
provider,
notes,
I,
think
I
have
two
remaining
which
I
want
to
delegate.
So
basically,
when
I
find
one
or
two
developers
who
are
taking
over
those,
it's
fine.
It's
not
worth
to
write
the
document
for
this
Caesar
that
I
sent
them
the
list
of
program
elements
are
used
and
that's
it
notifications
relays
even
easier.
A
The
only
bigger
thing
is
to
markets,
but
that's
also
to
handover,
and
only
one
persons
will
run
this
and
we
succeed.
Notes.
I
would
want
to
wait
until
Florin
has
done
already
a
lot
of
improvements
also
how
to
run
the
note
as
a
service
and
so
on
and
I
want
to
wait
a
little
bit
until
this
is
complete
and
then
we
can
distribute
it
a
little
bit
broader
and
because
of
the
risk
for
at
all,
because
they
were
relevant
for
the
tower
launch.
A
A
Yeah
there
there's
one
open.
We
had
a
few
discussions
array,
mainly
with
Devon
how
we
deal
with
the
proposals,
what
you
do
on
github
and
theoretically,
you
could
change
the
content
of
the
propose
and
then
historically
would
be
good
when
people
can
look
up
the
proposals
and
can
see
what
people
have
voted
on
and
at
the
moment,
because
it's
out
of
the
system,
it's
on
github,
basically
they're
at
least
the
github
administrator-
always
could
change
history
later.
A
So
it
would
be
good
to
have
some
secure
way
that
has
physically
after
version,
which
was
used
at
voting.
So
as
soon
as
voting
starts.
Blind
vote
restarts
that
we
create
and
freeze
the
content
of
the
proposals
with
a
hash,
and
then
the
hash
is
somewhere
committed
or
wherever,
and
then
we
we
can
be
sure
that
they
cannot
have
been
changed
afterwards
at
the
moment.
Yet
a
the
issuer
can
change
it
himself.
He
always
have
the
right
access
for
his
proposal.
A
I
was
considering
maybe
to
use
a
pull
request,
but
then
it's
a
little
bit
more
complicated
people
have
to
make
it
work
of
the
project
and
non-developers
a
phenom
developer.
It's
a
little
bit
more
challenge
like
to
make
I'll
get
up.
I
think
that's
very
low
barrier
make
it
pure
gas.
It's
a
little
bit
requires
a
little
bit
more
knowledge
about
kids
and
so
on.
A
I
will
just
end
the
question
where,
in
which
format
we
are
committing.
It's
also
not
really
a
good
solution.
I
don't
want
to
to
breach
it
too
closely
that
it
becomes
part
of
consensus
of
whatever
I
think
it.
It's
good
enough
to
have
basically
a
separate
system
where
we
get.
It
could
be
basically
a
script
which
is
just
downloading
the
proposals
at
their
block
height.
A
When
the
blind
boat
starts,
then
they
get
frozen,
they
are
archived
somewhere
and
then
hash
is
committed,
maybe
even
to
the
blockchain,
and
we
have
a
transaction
where
this
is
hundred
percent
frozen
and
everybody
can
run
could
be
a
small
service.
Basically,
everybody
can
run
such
a
service.
We
run
bond
which
is
unavailable
at
some
address.
A
A
The
version
is
correct
when
yeah,
when
any
any
anything
happened,
would
anything
would
happen
that
the
one
who
is
running
this
would
cheat
and
rewrite
history?
Then
everybody
else
can
run
it
and
could
detect
these
problems.
So
I
think
that
would
be
good
enough.
We
don't
need
to
have
it
in
the
Tao
code
that
basically
we
would
use,
then
the
hash
of
the
of
the
github
page
and
then
put
it
into
there
into
a
transaction
or
whatever
at
the
moment.
A
That
would
show
that
people
are
just
voting
randomly
and
and
don't
think
about
it,
and
we
have
to
fix
this
on
a
social
level.
Basically-
and
I
would
see
this
with
this
yeah
to
be
sure
that
the
proposal
have
not
been
changed
in
a
similar
way.
We
have
to
to
do
our
due
diligence
and
controllers
are,
and
also
I
mean
when
somebody
would
fake
this
with
whatever
it's
a
question
what
he
can
gain.
A
So
that's
basic.
My
task
before
we
launch
to
have
more
or
less
a
clear
idea
and
then
when
we
implement
the
idea
is
probably
not
critical.
So
if
you
have
any,
are
yeah
I
need
to
add
there
another
idea
or
whatever,
because
maybe
there
are
oleum.
There
is
another
idea
to
bring
it
in
into
the
doll
and
then
it's
everything
which
will
affect
the
tower,
especially
consensus,
has
to
be
done
as
soon
as
possible.
It's
already
very
late
now,
yeah.
A
Do
you
have
anything
to
add
to
discuss
something?
What
I
forgot
feel
free,
I,
think
or
when
you
don't
have
access
to
the
document?
Just
ping
me
I,
hope
I,
send
it
to
everybody
already
but
feel
free
to
just
edit
in
their
document.
I
sign
your
name,
but
you
are
able
to
take
responsibility
of
this
task
and
yeah.
A
Yeah
and
as
soon
dos
get
earth
stroke
out
more
and
more,
we
are
getting
it's
our
countdown,
basically
as
soon
yeah
we're
ready,
I
synchronistically.
In
the
best
case,
we
could
be
ready
in
two
weeks:
morally,
physically,
it's
probably
three
weeks
but
I.
Think
when
nothing
critical
happens,
I
think
three
three
weeks
is
a
realistic
launch
date
that
will
be
done
roughly
the
first
or
second
week
in
April.
A
Yeah,
it's
said
before
it's
still
a
little
bit
the
question
from
the
communication
strategy:
how
how
far
we
go
out
if
you
want
to
keep
it
more,
a
soft
launch
in
our
community
were,
for
instance,
if
you
want
to
make
that
press
for
you
sending
it
out
to
journalists
as
well.
I'm
I
tend
more
to
their
soft-launched
low
risk
option
and
and
then
when
everything
goes,
went
good
and
everything
was
successful
that
we're
slowly
trying
to
increase
our
reach,
but
I
think
from
the
basic
communication
side.
A
C
A
B
A
B
A
C
A
A
Yeah,
that
would
be
great
I
mean
you
have
also
covered
a
lot
of
when
people
who
are
requesting
psq
for
testing.
Do
you
have
the
rough
cuts
estimation
over
the
last?
How
many
are
so
from
the
non
developers
of
how
many
new
contributors
or
users
traders
have
participated
in
the
testing
certificate?
A
50
I.
A
I
mean
I've
seen
from
the
number
of
proposals
a
number
of
floats.
It
was
20
30
at
each
round
yeah,
which
is
which
was
our
target
busy.
We
didn't
want
to
get
too
many.
That's
I
think
it's
more
less
in
the
range.
What
we
targeted
it's
hard
to
say
I
mean
it
would
be
good
to
find
out
how
how
many
of
our
traders
really
know
about
the
Tao,
how
many
we
have
reached.
That
would
be
an
interesting
number,
but
it's
I
don't
have
a
good
idea.
How
we,
how
we
manage
to
figure
out
this
or.
C
Yeah
one
thing:
one
thing
I
would
like
to
suggest:
if
we
could,
if
we
could
somehow
make
that,
maybe
just
add
some
additional
blocks
and
make
it
so
that
the
the
proposal
phase
is
goes
from
like
Wednesday
to
Friday
instead
of
Thursday
through
Saturday.
It's
really
it's
really
hard
to
reach
people
on
Saturday,
yeah.
A
Yeah,
oh
yeah,
just
remind
me:
I
will
push
it
up
a
little
bit.
I
can
speed
up
the
time
Alton
from
10
minutes
of
nine
minute
or
whatever,
and
we're
making
a
little
bit
faster.
The
faces
may
be
I,
don't
know
it's
gone
weakest,
maybe
also
it
may
be
not
a
bad
idea
to
speed
it
up
a
little
bit
now
you
get
this.
A
A
A
A
B
A
B
A
Especially
that's
the
box
set
for
the
towel.
Was
there
I
mean
a
starting
point
for
the
Tao
and
that's
why
old
for
the
videos,
maybe
a
Steve,
maybe
I-
can
check
on
YouTube.
What's
the
statistics
to
see
how
many
youth
we
had
on
their
introduction,
we
just
think
that
gives
a
good
number
of
the
people
who
have
really
become
interested
to
understand.
He
was
around
300.
A
Maybe
they
use
this
yeah
I
think
from
those
numbers.
Probably
we
can
derive
more
or
less
the
users
what
we
have
reached,
who
are
hookup
interest
in
a
tower
and
maybe
hopefully
understand
it
more
or
less
so
yeah,
it's
a
sink
here.
The
number
of
downloads
is
between
five
and
ten
thousand.
When
did
we
reach
500
users?
We
have
something
like
five
to
ten
percent
yeah.
A
It's
maybe
a
little
bit
below
our
our
target,
but
yeah
I
mean
I.
Think
in
that
direction
we
can
try
to
push
a
little
bit
or
I
mean
the
I
think
per
meter
height
for
you
to
get
everything
prepared
and
everything
done,
but
when
there
is
still
time
on
the
side
too,
we
are
to
go
on
to
push
to
reach
our
users,
because
it
seems
that
we
have
not
reached
them
very
well
when
we
only
have
maybe
two
to
five
percent
at
the
moment
with
300
users
from
ten
thousand
or
five
thousand.
B
A
B
A
With
alert
so
we
can
do
it
for
this
release
to
fix
this,
to
make
it
more
configurable
or
to
make
it
just
more
beautiful
and
that
it
doesn't
come
like
an
alert.
Does
it
just
like
a
message,
then
I'm,
fine,
but
that
we
have
to
do
in
this
release
and
only
sent
out
after
this
release?
Otherwise,
it's
more
yeah
at
the
moment.
It's
a
little
bit
as
far
as
I.
Remember,
it's
just
a
write,
a
lot
with
this
straight
present
and
I.
Think
you
cannot
edit
the
title.
You
only
can
edit
the
text.
B
A
B
A
It's
it
I
mean
can
be
done,
of
course,
but
it
the
word
system,
yet
it's
an
effort
which
maybe
not
worse.
Therefore,
at
the
moment
to
and
basically
I
didn't
want
to
overuse
this
because
I
said
it's
this,
it's
this
developer
messages.
The
update
is
one
part
of
this.
I
only
want
to
really
use
for
for
stuff,
which
really
is
so
important
that
nobody
complains
about
it
when
I
would
feel
I
get
not
all
the
time.
Update
message
is
a
little
interested
to
get
notified.
A
B
A
A
Yeah,
that's
a
good
point.
Yeah
I
think
that
would
be
good
to
have
just
something
like
yeah
that
this
is
basically
the
last
release
plan
last
planned
release
before
the
tar
launch.
Now
it's
the
last
time,
please
check
out
when
you
have
not
lunch,
it's
very
important
thing
for
the
Peace
Project
to
get
it
really
decentralized,
and
so
on.
Yes,
some
good
text,
some
good
UI,
a
good
design
for
this
I
think
that
would
be
good
idea
and.
C
Personally,
I
kind
of
agree
with
you
I
think
we
should
be
as
careful
as
possible
to
start
with
and
I
think
got
for
a
month
or
so
when
it's
going
well,
I
think
we
can
try
to
push
it
more.
This
is
there's
so
much
there's
so
much
negative
sentiment
from
certain
young
people
about
Dallas
in
general
and
I
think
making
a
big
deal
about
it.
If
anything
goes
wrong,
even
slight
issues,
people
are
gonna,
make
they're
gonna
exaggerate
yeah.
A
Yeah,
but
at
the
end,
I
think
it
was
only
this
frontsies
Pula,
so
this
Canadian
guy
I
have
not
really
seen
and
at
the
end
many
many
others
maximalists
have
have
been
preferred,
defended
us
again
with
him.
I
have
not
really
saw
any
support
for
his
side.
Do
you?
Are
you
aware
of
some
other?
You
know.
Maximally
split
have
been
very
negative.
I.
C
Mean
he's
definitely
the
most
vocal
one
I
think
I
mean
personally
I.
Think
there's
been
a
bit
of
a
shift
in
sentiment
over
the
past.
Maybe
month
month
and
a
half
there
have
been
several
events.
I
think
people
are
realizing
that
governance
in
general
is
just
a
big
and
any
approach
to
fix
that
when
it
with
respect
to
decentralized
exchanges
in
kyc,
and
all
that
is,
is
a
good
one.
So
I
think
the
I
think
like,
for
example,
with
that
mr.
C
Hodel
guy
on
Twitter
I've
sensed
a
little
bit
of
a
shift
in
his
and
his
approach
he's
been
a
lot
more
vocally
in
favor
of
bisque
and
what
we're
doing
with
the
Dow.
So
I
don't
know
about
Francis,
particularly
in
particular,
but
I
think
I
think
that
the
sentiment
overall
has
become
more
positive.
Yeah.
A
C
I
even
met
some
people
in
when
I
was
at
in
Boston.
There
was
a
couple
of
people
who
work
with
them,
who
know
him
personally,
who
are
who
said
that
they
were
trying
to
convince
him
about
the
bisque
Dow
and
that
it's
not
really
what
he
thinks
it
is,
and
all
that
so
I
think
he's
it's
it's
something.
He'll
just
have
to
go
slowly
realize
he's
the
only
one.
A
Yeah
that
was
actually
pretty
good,
because
I
mean
it's.
It
was
a
difficult
challenge
to
to
get
this
message
for
this
group
communicated
correctly
and
I
got
the
feedback
actually
from
other
country
from
some
people
that
that
we
did
a
very
well.
You
mainly
did
a
very
good
job
for
communicating
that
it
doesn't
come
over
like
any
IC
or
whatever.
A
But
of
course
you
have
people
are
different
and
some
don't
get
it
and
don't
rate
stuff
and
then
have
to
quickly
their
own
opinion
anyway,
yeah.
So
let's
err
yeah,
that's
good.
Let's
maybe
keep
with
our
goal
to
just
focus
that
we
reach
our
our
users.
I
think
that
we
maybe
need
a
little
bit
more
push.
A
My
goal
would
be
at
least
10%
after
traders,
so
roughly
would
be
between
500,000
users
of
piss
that
they
have
basically
visited
either
the
videos
or
the
talks
to
oppose,
or,
of
course,
we
don't
know
it
the
details,
because
we
don't
do
any
evil
tracking.
But
when
we
see
that
500
people
have
visited
the
videos
we
can
be.
We
probably
not
many
a
visiting
two
times
or
three
times
in
the
same
video
duty.
A
Then,
let's
wrap
up
here,
oh
yeah,
if
you
yeah,
if
anything,
special
and
the
people
just
getting
ping
me
and
so
on,
we
can
go
on
directly
but
would
be
great
there
yeah.
If
anybody
who
works
on
some
errors
put
your
name
on
it.
So
we
get
a
little
bit
of
overview
what's
not
covered
and
to
not,
especially
not
to
miss
something
important
that
we
are
not
two
days
before
the
launch
I,
don't
we
should
have
done
this
and
then
I
have
to
the
later
or
whatever.
B
A
B
B
A
It
would
be
also
good
to
get
some
other
non
developers
like
whom
out
maybe
or
a
lecture
or
some
other
people
who
are
doing
other
stuff,
usually
to
invite
them
to
help
us
testing.
Just
normal
user
testing
doesn't
need
to
be
the
more
complicated
test
just
like
that
to
take
a
little
bit
to
weigh
the
workload
from
your
side
that
you
are
not
so
fully
blocked
at
this
time,
yeah.
B
A
Next
week,
maybe
a
plaintiff
a
little
bit
or
you
or
Devon,
or
both
can
give
a
little
bit
about
the
testing
tool
again,
that
it's
easier
for
people
to
get
started
with
yeah
complicate,
but
just
a
refresher,
yeah
dude.
Even
let's
rev
up
one
half
hour,
wait
too
long,
hey
thanks
everybody
for
watching
and
see
you
next
week,
bye
right,
yeah,.