►
From YouTube: Status Townhall - June 4th, 2018
Description
General
2:43 - Intro
5:32 - Core contributors
9:14 - #Study-fundamentals
11:31 - Marketing update
17:29 - Weekly-tech-talks
18:52 - Design meetup and takeaways
Swarm Updates
25:01 - #Core
Mobile app
28:49 - #energy-effecient
Infra & Tooling
30:07 - Infrastructure automation
32:32 - #167-extended-automated-testing
35:59 - P2P - New cluster
Chat
38:02 - #99-confidence
41:12 - #170-wallet-improvements
43:50 - DApps & Devs
Research swarms
48:33 - #67-nimbus
51:33 - #254-ulc
52:22 - #034-react-native-qt
53:14 - #desktop
Cardona and Q&A
55:54 - Cardona
59:00 - Q&A
Slides can be found here - http://bit.ly/status-th-10
- Bi-Weekly Town Hall livestream
- Q&A Sessions will be held at the end of each livestream if you missed out and would like to ask any questions about the content please leave a comment!
- This week alpha released with optional mainnet, some other great functional swarm updates and other progress happening!
Any other questions please leave a comment or join our chat - https://chat.status.im
C
D
E
Hello,
everyone
and
welcome
to
the
10th
Town
Hall,
as
always
being
broadcast
from
around
the
world.
That's
hosted
from
a
castle
in
Cortona
somewhere
in
Spain,
which
is
pretty
exciting.
We'll
have
some
feedback
on
that
at
the
end
of
today's
Town
Hall,
but
we've
got
a
lot
of
stuff
to
get
through
so
as
always,
we'll
sort
of
start
with
some
general
feedback
from
all
of
the
things
that
status
has
been
involved
in
outside
of
just
developments.
E
We
sent
a
team
down
to
earth
bonus,
Terrace,
which
is
part
of
the
ether
global
hackathon
coordination.
There's
gonna
be
further
events
in
Singapore,
Bangalore,
Berlin
and
San
Francisco
this
year,
so
there's
a
great
medium
pipe
start
about
it.
If
you
want
to
find
out
more
and
we'll
certainly
have
a
team
at
each
one
of
those,
so
there,
let's
know
if
you're
in
the
area
you'd
like
to
participate,
it
should
be
easy
to
organise.
E
Some
feedback
from
the
actual
hackathon
itself
was
that
there
was
a
really
great
project
called
the
token
sewer
which
won
their
thesis.
Being
that's
we're
sort
of
building
a
new
kind
of
empire,
but
empires
like
Rome,
really
function
not
predominantly
on
the
Emperor's,
but
on
their
sewers,
so
they
have
a
way
for
you,
take
all
your
coins
and
then
put
them
into
the
sir.
E
That's
Slash's
them
out
the
other
side
in
some
surprise
boxes
that
you
pay
five
by
four
in
the
net
die,
goes
towards
the
charitable
forces,
so
they
they
they
won
for
building
up
a
whole
think
system.
We've
also
got
a
great
raffle
app.
That
was
both
the
guys
were
particularly
keen
to
start
using
it
in
status.
So
I'm
really
looking
forward
to
the
work.
E
That's
gonna
start
again
this
week
on
101
tensions,
cuz
that
will
enable
that
sort
of
stuff
and
is
particularly
exciting
and
innovative,
at
least
in
my
opinion,
and
then
just
some
general
feedback
on
the
community
in
Latin
America.
You
know
we
we
got
hosted
by
the
Zeppelin
team
who
just
launched
Zeppelin.
Oh
yes,
and
you
know,
managed
to
launch
a
major
product
and
host
this
amazing
events
all
in
one
and
it's
ready.
Latin
America
is
a
very,
very
interesting
place,
particularly
for
blockchain
and
just
decentralized
technologies.
E
In
general,
the
currency
inflation
rates
in
Argentina
sitting
at
40%
Venezuela,
is
about
a
thousand
people.
They
have
sort
of
a
lived
experience
of
what
it's
like
when
centralized
and
trusted
parties
like
governments
and
banks
fail
and
when
doesn't
really
need,
explained
deeply
the
need
for
decentralization
it's
just
about
getting
down
to
business
and
building
the
tools
that
we
need
to
actually
organize
ourselves.
So
that
was
really
inspiring
to
be
a
part
of.
If
you
want
to
find
out
more
there's
a
blog
on
the
status
blog
and
you
can
read
there.
E
C
C
This
last
week,
we
also
added
a
couple
of
extra
pages
to
the
site
about
how
team
members
can
manage
getting
paid
between
Fiat
and
crypto,
how
their
rates
are
established
and
also
how
we
endow
time
off,
because
we
always
said
time
off
is
flexible,
now,
even
more
official.
It
is
also
working
process.
So
whenever
you
look
through
our
pages,
if
there
are
questions
that
remain
and
answer
the
please
make
sure
to
ping
me
or
carry
over
there
was
anyone
in
people
up.
So
we
make
sure
that
we
make
this
better
and
better.
C
C
C
You
can
read
some
examples
if
you
take
the
slug
profiles
of,
for
example,
Igor
Nabil
carry
myself
and
Pedro
I
think
there
is
a
new
field
which
everyone
has
access
to,
which
is
called
my
user
manual,
where
you
can
find
links
to
our
documents
and,
of
course,
you're
very
welcome
to
write
your
own
next
thing.
The
program
which
is
really
big,
we're
thinking
about
what
is
the
best
structure
for
us
to
work
together,
make
sure
that
we're
able
to
be
efficient
while
we're
keeping
as
non-hierarchical
and
flat
as
possible,
which
is
what
we
really
want.
C
E
Thank
you
so
much
stiff
yeah,
the
people
in
people,
ups
rock
so
hard.
Those
those
years
of
manuals,
in
particular
super
useful
I,
encourage
everybody.
That's
on
the
school
in
watching
to
write
their
own
I'm.
Certainly
gonna.
Do
that
because
it's
super
useful
I
feel
like
I
know:
I
got
ego
in
particular
much
well
a
much
better.
Now.
Thank
you
for
that.
E
Some
study
fundamental
highlights
just
quickly
from
a
study
channel
that
we
have,
and
there
was
a
great
live
stream
posted
by
Kim,
actually
which
quoted
citizen
berners-lee,
who
is
speaking
and
he's
really
on
the
warpath
to
find
these
completely
anonymous
ways,
especially
for
people
like
generous
and
human
rights
activists
and
whistleblowers,
to
provide
an
a
public
online
existence
in
a
common
identity
across
websites
that
we
use.
That
can
support
your
online
credibility.
E
So
anonymity
and
credibility
are
sometimes
mutually
exclusive
things,
but
there
are
ways
if
we're
particularly
critical
and
approach,
that's
in
an
innovative
fashion
that
we
can
think
about
bringing
them
together
and
there's
a
lot
of
really
great
identity.
Work
happening
at
status
as
well,
if
you're
interested
in
that
speak
to
Ricardo
or
go
and
look
in
the
identity
branch
of
the
contracts,
repo,
there's
some
really
really
amazing
work
there
and
he
was
blowing
people's
minds
with
it.
Inferno
Cyrus,
which
was
really
great
to
see,
there's
also
a
fantastic
gas
golfing
competition.
E
This
is
where
you
sort
of
write
smart
contracts
and
try
and
optimize
them
for
how
much
gas
they
use
on
the
network
so
that
users
end
up
paying
as
little
fees
as
possible.
It's
really
awesome
see
tools
like
this
coming
out
that
don't
necessarily
just
have
to
do
with
security,
but
also
optimization,
and
it's
another
sign
of
maturity
coming
through
the
ecosystem,
which
is
fantastic
and
then
a
really
great
article
from
Jacque
about
scaling,
Bitcoin
through
lightning
and
the
beginning
of
that
talk.
If
you
sit
down
and
watch
it,
it's
ready.
E
So,
if
you're
interested
in
that
kind
of
stuff
do
feel
free
to
ask
and
there's
another
link
down
there,
where
you
can
follow,
especially
plasma
in
ten
minutes,
which
is
being
worked
on
predominantly
by
the
Mesa
go
team.
So
you
ask
any
questions:
if
you
have
those
in
the
channel
I'm
marketing
up
sites
over
to
Johnny
thanks.
A
Andy,
can
you
hear
me
all
right,
yep
cool,
so
one
of
the
big
things
were
working
on
right
now
is
a
campaign
called
state
of
us
we're
just
you
know
we're
working
closely
with
Chad
and
Rachel
to
effectively
communicate
the
state
of
the
product,
but,
more
importantly,
where
we're
trying
to
communicate
ways
for
everyone
to
get
involved.
So,
like
one
of
the
things
we're
doing,
is
you
know,
we've
got
a
podcast
series
which
Andy
you're
running
new
onboarding
flows
with
new
content
for
any
new
member
to
sign
up
and
we
are
running
up
a
pilot.
A
But,
more
importantly,
this
idea
of
community
involvement,
Kym
and
Alli
are
working
with
an
awesome
illustrator
named
Crystal
to
create
this
how
to
contribute
infographic.
It's
really
cool
just
basically
shows
the
various
ways
any
member
can
get
involved,
whether
it's
through
code
through
content
through
hosting
it
ups.
Things
like
that.
Also
we've
got
a
sixty
second
video,
which
is
in
production
and
we're
crowdsourcing
content
from
the
communities,
so
stay
tuned
for
more
information
on
how
you
can
actually
submit
content
and
get
involved
in
actual
actually
creating
this
video,
so
it'll
be
a
completely
community.
A
Well
not
completely,
but
like
community
driven
piece
of
content
to
folks
who
kind
of
piggyback
up
off
on
this
idea,
we're
gonna
be
running
community
competitions
for
people
to
get
involved
and
also
to
contribute
content
as
well
and
then
Sean.
Now
that
he's,
you
know
now
I
think
three
weeks
full
time,
which
is
great,
he's
rolling
out
his
advocacy
program.
So
there's
gonna
be
some
really
interesting
things
for
the
community
to
get
involved
through
that.
A
So
Ally
also
is
taking
a
deep
dive
back
into
the
positioning
and
branding
one
of
the
things
we
noticed
so
early
on.
We
had
this
idea
of
super
app,
which
was
great,
but
when
we
looked
at
it
again,
we
just
realized
statuses
people
much
more
than
that.
You
know
that
positioning
was
around
the
product
and
what
the
product
can
do
and
its
features.
But
you
know
through
incubate,
embarked
the
community
and
just
you
know
becoming
this
ecosystem
project.
A
We
wanted
to
rethink
that
and
make
sure
our
positioning
was
all-encompassing,
so
we're
taking
a
deep
dive
back
into
that
now
and
another
exciting
piece
of
work
was
the
the
values
swarm
that
kicked
off
last
week.
So,
thanks
to
everyone
involved
in
that
it
was
great
to
get
on
the
phone
with
everyone,
because
you
know
I
think
we
had
different,
maybe
not
different
opinions
or
views,
but
so
many
different
ideas.
So
it
was
just
nice
to
get
on
the
phone
with
everyone
and
really
you
know,
dive
back
into
that.
A
I
have
a
call
with
Steph
after
this
to
figure
out
next
steps
and
really
the
goals
and
deliverables
for
this.
But
one
of
the
really
interesting
things
to
come
out
of
it
was
this
idea
of
creating
like
a
a
rule
book
or
like
a
constitution
almost
for
status.
So
so,
thanks
to
everyone
involved
in
that
and
we'll
be
kicking,
it
we'll
be
continuing
that
work
over
the
course
of
the
next
few
weeks.
A
Content
a
lot
of
content
in
the
works,
which
is
great
so
we've
got
the
Tech
Talks
Kari
has
added
some
more
documentation
to
how
to
sign
up
actually
some
instructions
for
hosting
the
event
the
hosting
the
meet.
So
hopefully
those
talks
get
better
and
better
as
we
go
on
and
you're
working
on
the.
Why
decentralization
series
I'm
really
just
highlighting
you
know
why
decentralization
matters
and
why
we're
doing
the
work?
We're
doing
another
thing
that
we
we're
gonna
be
doing?
Is
team
updates,
so
we'll
be
working
with
people
from
each
team?
A
Marketing
we'll
be
doing
the
same
thing
really
just
to
bring
about
transparency
into
all
the
work
we're
doing,
because
you
know,
if
you
take
a
look
through
slack,
there's
just
so
much
happening,
and
you
know
the
marketing
team
wants
to
effectively
communicate
that
and
just
you
know,
highlight
and
really
show
off
the
work
that
we're
doing,
because
it's
great
we've
kicked
off
on
website
refresh.
Once
again,
you
know
status
has
grown
into
so
much
more
than
just
this
product.
You
know
through
incubate
embark
and
all
the
various
moving
pieces.
A
So
we
wanted
to
kind
of
just
rethink
the
website
and
make
sure
that
information
is
easily
navigable
and
digestible
loads
of
community
events.
The
all
six
got
his
meetup
in
Berlin
and
at
the
end
of
the
month,
F
Berlin
and
F
global.
You
know,
there's
a
series
of
you
know:
hackathons,
which
we're
gonna
be
involved
in
the
status
hackathon
that
will
take
place
end
of
October.
A
You
know
communicate
that
and
create
a
series
of
small
little,
like
short,
bursts
for
for
tutorials
and
information
around
that
we're
kicking
off
an
initiative
with
Jared.
You
know
temporary.
We
named
s
prize,
so
stay
tuned
for
me
for
more
on
that
one
and
then
incubate
ben
karlin
team
they've.
They
set
up
a
introductory
introductory
call
with
our
first
key
Bakey.
Last
week.
It's
really
cool
interesting
project
ahead
of
the
World
Cup,
so
we're
working
with
them
to
come
up
with
their
launch
plans,
then
launch
calm
so
more
to
come
on
that
one
as
well.
A
E
Thank
you
so
much
Johnny,
so
the
regular
weekly
tech
talks
are
back.
Thank
you
particularly
to
Frank,
who
did
an
awesome
talk
on
the
road
to
ulc,
which
is
the
ultra
life
clients.
There's
some
really
interesting
information
in
there
about
our
various
different
attempts
to
try
and
get
like
mode
running
properly
on
you
know,
resource
restricted
devices,
I
strongly
encourage
people
to
go
and
take
a
look
at
that.
E
There
was
some
some
really
some
really
great
information,
that's
not
readily
available
elsewhere,
and
it's
really
great
to
be
able
to
surface
a
lot
of
the
sort
of
deeper
protocol
work.
That's
happening.
You
know
in
sort
of
random,
get
the
channels
and
various
places
around
the
nest
to
a
wide
audience.
So
again,
if
you
have
any
tech
talks,
this
is
particularly
for
our
developers
that
you
feel
could
be
usefully
shared
with
a
wider
audience.
E
I
know
you
got
sick
is
planning
something
for
swarm
which
is
really
exciting
and
if
you're
working
on
something
which
you
think,
could
he
used
to
fully
be
discussed
with
the
wider
audience,
particularly
because
this
is
all
about.
You
know
empowering
people
to
actually
participate
in
these
decentralized
networks.
Then
you
can
play
an
active
role
there
so
sign
up
on
the
link
and
let
us
have
a
little
window
into
your
particular
expertise.
E
D
Yes
yeah,
so
we
basically
wanted
to
to
kick
off,
maybe
just
a
regular
update
from
the
UX
and
the
US
our
team,
beginning
this
time
with
just
letting
you
know
of
about
a
week
and
a
half
ago.
The
design
team
met
up
in
Amsterdam
for
about
four
days,
and
this
is
something
that
we
would
like
to
kind
of
institute
as
a
regular
practice
where
we
maybe
two
or
three
times
a
year.
D
We
get
together
and
we
meet
somewhere
to
just
discuss
things
see
if
we
can
maybe
reorganize
the
way
that
we
work
or
deep
dive
into
particular
topics.
Another
practice
that
we
would
like
to
get
into
with
these
meetups
is,
if
we
go
into
the
next
slide,
is
we
typically
try
and
make
sure
we
set
up
a
user
study
so-
and
this
is
where
we
gather
in
one
of
these
rooms
and
have
people
come
in
and
they
try
out
the
app
or
they
have
a
particular
set
of
tasks
that
they
have
to
do
with
an
app.
D
D
What
needs
to
be
worked
on
if
you
go
on
oh
trying
to
recap
so,
basically,
from
from
this
particular
week
in
these
exercises,
we
had
a
couple
different
takeaways,
one
of
which
was
we've
decided
to
basically
vlog
everything
that
we've
we've
seen
so
far.
So
we
have
a
backlog
sheet
of
62
core
app
issues
that
we've
assigned
unique
IDs
and
then
were
some
of
them.
D
D
D
D
If
you
go
into
the
next
slide,
yehey
has
been
working
on
some
really
awesome,
desktop
work
where
she's
just
looking
marching
towards
a
minimal
Viable,
Product
and
and
basically
you
know,
seeing
how
she
can
play
with
the
information
architecture
and
allowing
people
to
set
up
one-on-one
chat.
So
this
is
really
exciting
to
see
for
the
first
time
and
finally,
on
the
research
activity
side.
D
E
Perfect,
thank
you
so
much
Pat
and
yeah.
It's
it's
always
incredibly
importance
that
we
highlight
just
the
quality
and
scale
of
some
of
the
uxr.
That's
that's
really
going
on,
because
it's
something
that's
not
focused
on
in
the
ecosystem
at
the
moment
and
we've
seen
it
cut
back
on
conferences
after
Eid
Khan
and
in
various
other
places
that
there's
a
desperate
need
for
this
stuff.
E
So
we're
also
Jared
sent
arts
a
big,
VIP
zero's
survey,
which
memy
has
done
some
really
amazing
data
visualization
work
on,
and
I've
also
puts
again
all
of
the
eat,
prized
interviews
and
so
we're
gathering
all
of
these
datasets
from
across
the
community.
Regarding
what
tools
they
need,
what
frustrations
that
have?
What's?
We
can
build
next.
E
That
will
really
have
an
impact
for
everybody
across
the
broader
community
and
will
also
be
open
sourcing
all
of
those
tools,
particularly
around
the
data
visualization,
so
that
anybody
can
sort
of
rerun
uxr
at
scale
in
the
ecosystems
just
because
it's
such
a
desperate
needs.
So
thank
you
to
Patton
Hester
in
particular
for
really
kick-starting
and
the
stuff
in
status.
It's
fantastic
to
see.
We
move
into
swarm
updates
and
the
firsts,
obviously
the
Corps
first
up
and
the
one
that
everybody
in
the
status
channel's
has
been
waiting
for
over
the
last
few
days.
B
F
Yeah
yeah,
so
the
great
news
is
that
we
successfully
released
Point
9.19
on
Friday
and
it's
been
really
really
cool
to
see
the
traction
inside
status
since
that
release
to
the
community
members
who
are
listening.
Thank
you
so
much
for
being
in
the
status
channel
and
in
the
app
in
general
and
participating
us.
It's
been
super
cool
to
see
you
guys
connecting
there.
Of
course,
the
big
news
with
this
release
is
the
fact
that
mean
that
is
included.
It's
an
option
if
you've
had
trouble
finding
it,
that's
because
it's
still
hidden.
F
So
if
you
would
like
to
make
real
transactions
inside
status
using
maenette,
you
can
do
so
by
activating
developer
mode,
which
is
hidden
under
the
advanced
profile
settings.
So
what's
the
big
difference
between
beta
and
these
alpha
releases
that
we've
been
having
in
beta,
the
opposite
is
going
to
become
true.
F
Instead
of
main
that
be
an
opt-in,
that's
hidden
behind
developer
settings,
it's
actually
going
to
be
the
default
for
every
user
and
on
the
flip
side,
if
you
want
to
actually
use
test
networks
for
development
purposes,
you'll
need
to
go
on
to
download
so
because
main
net
is
going
to
be
the
default
Network.
We're
really
prioritizing
right
now,
any
bugs
after
you
with
chat
or
wallet
or
transaction
security,
and
we
have
a
we've
a
beta
milestone
on
github.
F
That's
about
15
issues,
strong
right
now,
and
only
once
we
have
that
down
to
zero
will
we
feel
comfortable,
saying
that
we
have
a
beta
candidate,
so
you
can
click
the
link
on
this
slide.
If
you'd
like
to
follow
along
and
see
the
progress
on
all
that
work,
a
couple
other
questions
that
we've
been
hearing
from
the
community
will
there
be
a
limit
to
iOS
invites
for
beta?
Yes,
there
will
we're
still
distributing
beta
via
test
flight
on
iOS,
and
so
that
means
we
do
have
a
limit.
F
But
if
you
don't
have
an
invite
yet-
and
you
want
to
be
able
to
test
with
us-
you
can
go
to
our
website
status.
Dot
I
am
and
enter
your
email
and
you'll
receive
an
email
with
directions
on
how
to
to
request
an
invite.
Will
we
be
making
updates
it's
frequently
beta,
as
we
have
been
doing
alpha
and
yeah?
Definitely
that's
our
aim.
We
hope
so.
E
Perfect
there's
also
one
thing
I
want
to
say
is
particularly
the
community
members
who
are
watching
and
furiously
messaging
everybody
in
status,
it's
so
fantastic
to
see
and
feel
free
to
go
ahead
and
create
your
own
public
chats
to
discuss.
You
know
like
the
main
specific
topics
of
interest
to
you,
you,
don't
you
don't
need
to
necessarily
you
status
all
the
time.
E
There's
plenty
of
other
topics
out
there
and
you
can
create
your
own
and
you
know,
set
up
your
own
chats
with
people
about
particular
pieces
of
interest
like
open,
bouncies
or
sharding
or
zero-knowledge,
or
something
random
like
pizza,
whatever
you
feel
like,
please
feel
free
to
go
ahead
test
it
out
and
give
us
your
feedback
so
now
into
the
mobile
app
swarms
themselves.
The
first
is
eighty-three
energy-efficient,
and
this
is
ego
ego
online.
B
I
can
take
this
one.
Yes,
amazing,
work
by
the
mobile
app
team
and
the
ATV
swarm
by
Bora
Roman,
John
and
Lucas.
Seen
lots
of
nice
performance
improvements,
this
last
release,
and
now,
when
we
have
relatively
empty
chats,
it's
almost
twice
as
performant
as
it
used
to
be
like
a
month
ago.
Some
like
this,
so
really
good
work.
B
There
there's
still
some
issues
when
we
have
a
lot
of
messes
historical
messages,
so
that's
sort
of
mixed
challenge
in
terms
of
dealing
with
message,
reordering
and
making
sure
it
works,
even
if
you
have
a
thousand
messages
in
a
public
chat
and
so
on.
But
really
people
been
using
that,
especially
on
Android,
this
last
release
versus
maybe
two
releases
ago,
there's
a
big
difference
so
really
cool
to
see,
and
next
up
is
Jacob
who's
going
to
talk
a
bit
about
our
new
cluster.
E
B
You
he
said
I
flicked
on
mute
and
it
crashed
ii.
Do
this
briefly,
so
we
have
a
new
cluster.
The
maintenance
here
is
that
we
have
proper
monitoring,
setup
and
also
work
in
progress,
long
aggregation
and
essentially
making
it
scalable
from
mechanical,
where
stokes
cluster
wasn't
really
scalable
and
it
was
a
it
wasn't
straightforward
for
us
to
move
notes
around
and
these
kinds
of
things
so
Jacob
as
done
really
great
work
here
in
terms
of
setting
up
tooling
and
getting
visibility
into
this
class
as
a
whole.
B
Some
future
improvements
is
rounds
of
having
multiple
data
center
support,
which
helps
us
with
censorship,
resistance,
such
as
eyepiece
being
locked
and
also
doing
some
stuff
form,
log,
decoration
and
so
on.
If
you
good
to
next
slide,
we
have
some
pictures
here.
You
can
see
in
terms
of
how
we
can
debug
the
system.
B
So
here's
some
monitoring
we
can
see.
This
is
wicked,
and
instead
of
doing
a
while
ago,
bits
of
gradually
improved
on
in
terms
of
seeing
whisper
volume
and
the
number
of
envelopes
and
peer
utilization,
and
also
sort
of
understanding
how
discovery
works
and
all
these
things-
and
this
is
great
in
terms
of
giving
us
visibility
and
be
able
to
debug
things
when
they
go
wrong.
So
you
can
find
this
four
core
contributors
at
the
graph,
an
adult
status
that
I
am
and
then
you
can
authenticate
with
github
and
next
slide.
B
We
also
have
more
sort
of
slightly
more
granule
monitoring
abilities,
so
in
terms
of
seeing
if
mail
servers
can
scale,
one
of
hers
of
KPIs
is
having
lots
of
concurrent
connections
and
dealing
with
that
properly,
and
one
block
of
that
is
around
memory
usage.
So
with
this,
we
have
great
insight
into
how
the
nodes
are
performing,
which
is
picked
at
and
other
metrics
and
also
connectivity,
and
so
on
next
slide.
So.
E
Yeah
we
move
on
to
that
I'd.
Also
again,
I
love
visualizations.
It
makes
things
so
much
easier
for
a
broader
range
of
people
to
understand.
So
it's
really
fantastic
to
see
this
stuff
and
if
Jacob
has
made
gone
through
the
call,
it's
really
great
to
have
him
on
team
and
he's
he's
made
a
big
impacts
from
initially
joining.
So
thank
you
to
him
for
all
of
that.
Hard
work
ants
on
Europe.
G
So,
decent
progress
on
automated
testing
site
for
last
weeks.
Basically,
all
extended
tests
now
are
running
against
each
car
and
we
will
decrease
the
execution
time
from
one
plus
hour
to
15
minutes.
Also,
we
increase
the
entrant
test,
reliability.
Basically,
right
now
we
are
maintaining
to
them
in
scope
of
the
same.
We
are
where
the
feature
or
objects
is
produced.
We
share
brings
much
more
availability,
also
another
goods
and
kids
Jenkins
job
for
my
social
ability,
testing
its
PC
for
now,
but
it
can
be
used
by
anyone
announcer.
G
It
serves
our
duty
at
three
tests
which
are
applying
messaging
public
chat
and
one-to-one
chat,
and
you
can
trigger
the
job
is
our
with
an
amount
of
messages
that
you
want
to
send
the
public
chatted
between
two
devices
or
to
receive
in
a
flame.
For
now
it's
dry.
There
is
a
restriction
for
three
hours
from
once.
I
was
laps,
but
we
a
in
contact
with
them,
remove
the
restriction
and
the
limit
is
fifteen
thousand
messages
in
one
to
one
shot
and
as
a
result,
you
will
get
the
graph
next
screen
as
a
graph.
G
Yes,
it's
a
little
bit
squashed
because
we
have
a
small
screen,
but
you
can
see
that
more
than
thousand
messages
has
been
sent
and
received
by
a
user
and
x
is
the
longest
time
to
receive
a
display
message
in
UI
is
four
seconds.
The
main
goal
of
this
test
is
to
create
an
endless
test
which
will
run
from
nightly
tonight.
G
Yes,
so
sushi
goals
is
to
cover
with
internal
tests
interactions
with
stops.
Music
status
tells
dub
great
AB
great
tests
and
yeah
I've
already
thought
about,
and
was
my
social
ability
test
with
like
chart.
So
what
sort
is
test
really?
Reports
can
be
public,
so
we
still
publish
old
reports
on
that
they
are
displaying
text
and
links
and,
yes,
the
limit
for
message:
reliability
tests.
That's
why
it's
not
endless
life
chart
from
now
and
visits
it.
E
H
Cool
yes,
so,
as
you
know,
we
have
this
new
cluster.
However,
it
was
not
released
in
0
919,
yet
we
plan
to
do
it
in
0
9
20,
but
there
are
some
implications,
so
we
are
moving
to
the
new
cluster
because
we
need
proper
logging
monitoring
and
pretty
much
have
a
cluster
that
will
force
clarity
and
extensibility,
and
it
was
no
other
way
to
just
reveal
it
from
scratch
and
prepared
properly.
H
So
the
think
what
we
need
to
do
is
to
update
all
booth
nodes
and
server
nodes
and
so
on
and
so
forth,
but
also
we'd
like
to
separate
alt
caster
from
the
new
one
to
have
like
the
clear
monitoring
and
do
not
have
any
floating
server
nodes
around
that
are
not
supposed
to
be
in
the
new
cluster.
So
the
consequence
of
this
is
that
we
will
have
incompatibility
between
0,
9,
19
and
0.
H
9
20
is
pretty
much
a
very
similar
thing
to
whisper
version,
6
upgrade
where
it
was
not
possible
to
communicate
between
two
different
clients
with
whisper
version,
5
and
whisper
version
6.
So
here,
when
we
do
this
upgrade
of
the
cluster,
it's
again,
it's
not
gonna
be
possible
to
communicate
between
19
and
20,
but
yeah.
We
need
to
do
it
just
once,
hopefully,
and
we'll
have
this
new
cluster
up
and
running
so
yep.
That's
the
goal.
E
Perfect,
thank
you
Adam,
and
it
is
worth
mentioning
that
the
sync
compatibility
is
not
the
same
as
the
last
one.
So
your
accounts
and
all
of
that
information
will
still
be
the
same
as
you
upgrade
from
1920,
but
obviously
you
just
might
be
able
to
send
a
message
to
someone
still
running
19
right.
That's
correct!
Yeah!
That's
correct!
Perfect!
Thank
you
very
much.
So
in
stats
first
one
he
has
confidence
led
by
Pedro,
hey.
I
I
We
also
allow
adding
custom
ml
servers
and
boot
notes,
so
this
will
come
in
handy
if
we
have
like
countries
which
block
our
mail
servers
and
boot
nodes,
people
will
be
able
to
just
scan
a
QR
codes
and
be
able
to
get
up
and
running
again.
We
also
allow
clearing
the
chats
history
and,
for
the
time
being,
we
disable
translations
in
order
to
focus
on
the
critical
path.
F
I
Terms
of
future
goals,
we're
going
to
be
finishing
the
issues
in
the
chat
boards,
especially
making
sure
that
we
find
a
good
solution
for
the
the
mail
servers
blocking
in
Russia
and
also
some
design
issues
doing
some
improvements
in
terms
of
few
X
for
the
chat.
The
lessons
learned
so
far,
it
seems
like
the
99%
cents
received
ratio
as
an
exit
criteria
is
not
really
something
we
can
use,
because
it
just
takes
people
leaving
their
phone
for
24
hours
and
not
opening
status
to
skew
that
metric.
So
it
ends
up
not
being
representative.
E
J
Thanks,
basically,
the
progress
in
wallet
over
the
last
two
weeks
was
exclusively
on
the
back
fixing
front.
We've
detected
and
fixed
the
whole
lot
of
bugs
some
of
them,
which
were
known
from
before,
and
some
of
them
which,
which
we
detected
only
after
we
started
testing
one
and
trying
out
the
a
pin
on
main
it.
So
now
that,
after
after
after
after
those
battles,
basically
wallet
is
much
more
stable
and
unsecured
and
bug
free
the
future
goals.
J
The
immediate
future
goals
are
pretty
much
to
clean
up
the
beta
board
and
implement
the
missing
things
for
beta,
which
are
mainly
the
transaction
gas
settings
for
death
transactions
and
the
chat
info
message
about
the
payment
and
obviously,
there's
always
more
bug,
fixing
and
bug
hunting
and
so
on,
to
make
it
even
more
stable
and
solid
and
Trust.
Well,
the
lessons
learned
so
far
are
first
that
we
must
use
the
app
in
a
realistic
manner
in
order
to
detect
actual
you
know
bugs
from
actual
usage.
J
That
specifically
means
that
we
need
to
test
it
and
try
it
out
on
main
it
as
well
as
it
isn't
estimates,
and
that
we
must
have
as
realistic
data
test
sets
on
test
nets,
as
we
do
on
maintenance
as
much
as
it
is
possible.
For
example,
good
selection
of
test
tokens
and
the
other
lesson
last
nerd
so
far
is
that
we
need
to
apply
the
shoot.
First.
Ask
questions,
questions
later
policy
with
regards
to
bugs.
J
E
Thank
you,
so
Becky
go
ahead,
always
a
little
bit
of
flavor
at
the
end.
That's
some
really
really
exciting
stuff
and
a
huge
kudos
to
you
and
Nastya
for
finding
some
nasty
bugs
that
were
not
at
all
obvious
and
fixing
them
incredibly
quickly.
It
is
there's
some
good
lessons
to
have
picked
up
there
since
the
dieppe.
Some
developers
will
do
a
team
update
here,
rather
than
focusing
on
the
specific
swarms
that
are
working
and
I
think
this
is
Rachel
again
yep.
F
Right
on
and
we
are
kind
of
operating
as
one
big
non-ephemeral
swarm
right
now.
So
over
the
past
two
weeks,
the
the
DAP
and
developer
engineering
resources
have
been
largely
dedicated
to
being
all
hands
on
deck
for
these
critical
beta
issues.
So
I
kind
of
like
their
use
this
time
to
highlight
what
we're
planning
for
the
near
term.
F
We
think
it
would
be
best
if
developers
will
be
able
to
integrate
their
tokens
within
status,
using
whatever
metadata
is
appropriate
to
their
product,
and
so
this
is
going
to
be
a
great
way
for
us
to
just
kind
of
prove
the
concept
of
extensions
and
to
identify
any
problems.
Opportunities
come
up
early
on.
We
also
think
that
this
exemption
will
probably
be
relevant
even
beyond
collectibles,
because
we
can
imagine
a
world
in
which
we're
all
of
assets
are
eventually
represented
by
ERC
7:21
coatings
as
well.
F
The
other
sort
of
tangential
work
stream
that
we
have
is
documentation
work.
We
know
that
developer
tools,
new
builds,
are
worth
nothing
if
we
don't
have
documentation
and
proper
instructions
on
how
to
use
them,
and
so
we're
beginning
that
and
baby
steps
just
by
reviewing
the
existing
wiki
content
and
Andy
I'm,
relying
on
you
for
that
largely
but
we'll
just
review
the
wiki
content
see
what's
still
relevant
what
can
be
updated
and
will
most
likely
end
up
migrating
that
content
over
into
a
static
website.
F
E
When
we
choose
a
certain
technical
solution
to
a
given
problem,
so
Julian
went
ahead.
He
first
wrote
a
manifesto
which
explained
at
a
high
level
conceptual
overview
what
he
wants
to
achieve
with
extensions
and
make
it
possible
for
people
to
actually
built
properly
decentralized
applications
that
are
really
about
the
web
three
and
not
web
2.5,
and
we're
not
using
the
same
old
api's
from
the
same
old
thought
patterns
and
gave
like
a
really
brilliant
conceptual
overview.
E
It's
a
really
fantastic
document
for
the
rest
of
the
team.
It's
easy
to
share
it's
easy
to
tell
people
like
what
the
intention
is
here
and
how
we're
gonna
achieve
its
really
huge
kudos
to
Julian
on
that.
101
extensions
is
where
to
go
to
look
for
some
of
those
Docs,
and
you
can
just
ask
Julian
for
for
a
link
to
the
Google
Docs
that
he
wrote
up
initially
before
writing.
The
idea
I
think
that
it's
a
really
great
template
to
use
when
we
need
to
make
decisions
that
do
have
long-term
implications,
but
require
fixes.
E
K
We
factored
the
gas
price,
computations
improved,
assess,
leveraged
and
number
of
tests
that
are
passing
successfully
and
we
are
exercising
more
and
more
of
the
networking
code
have
been
developed
separately,
our
Bowie
still
to
sync,
with
the
walk
chain
and
being
able
to
execute
the
entire
history
of
the
blockchain
and
until
the
current
point
on
the
other
fronts,
our
library
for
json-rpc
clients
and
servers
is
almost
ready
and
you'll
be
making
a
standalone
release
that
will
be
able
to
that.
The
entire
new
community
will
be
able
to
use.
K
We've
also
released
the
first
version
of
our
new,
a
sync
core.
For
name
I
mean
we
are
now
in
the
process
of
integrating
it
in
our
existing
make
network
libraries
and
measuring
the
performance
improvements.
The
main
goal
here
is
to
increase
the
efficiency
and
the
performance
of
network
encoding.
Me
we've
also
developed
a
test
bed
that
will
be
able
to
tell
the
compatible
compatibility
of
members
with
the
other
item
plans
within
the
context
of
a
private
blockchain,
a
private
network.
K
I
E
Thank
you,
sorry,
yeah.
It's
really
exciting
to
see
that
work
moving
so
fast
on
them
and
Nimbus.
It's
always
fantastic
to
have
more
and
more
clients
operating
across
if
they're
in,
because
that's
also
another
kind
of
decentralization
that
we
care
about
deeply
so
you'll
see.
This
is
the
ultra
life
clients
and
it's
being
led
by
Boris.
E
L
E
L
So,
and
apart
from
that,
we
have
basically
condensed
the
list
of
use
cases
for
the
bat
to
be
released
in
q2
to
just
19
use
cases
19.
This
is.
We
are
going
to
focus
on
reliable
messaging,
basically
using
the
status
desktop
as
a
messaging
gap.
We
also
had
first
design
preview
ready.
This
was
prepared
by
Olga
and
the
brief
stats
for
now.
So
after
we
have
collected
the
use
cases,
they
have
been
transferred
to
the
project
board
by
Nastya
and
each
other.
L
Basically,
we
have
15
issues
to
do
from
in
progress
if
I've
already
done
the
more
attentive
you
might
notice
that
15
plus
5
plus
5
does
not
add
up
to
19,
which
is
obvious
that
some
of
those
issues
in
the
board
being
some
Vox
that
appear
from
time
to
time,
because
as
we
develop
using
status,
react
on
the
desktop
from
time
to
time.
We
have
some
issues
that
have
appeared
due
to
the
new
and
yet
untested
nature
of
the
desktop
fork
of
reactivated
itself.
L
E
Awesome,
thank
you
so
much
it's
really.
This
is
definitely
one
of
the
more
exciting
things.
That's
been
happening
in
status.
Recently.
It's
been
awesome
to
see
guys
squashing,
all
of
those
bugs
and
making
it
easier
to
get
desktop,
actually
running
and
using
react
native
on
the
desktop.
It's
something
that
I
think
will
draw
a
lot
of
wider
interest
from
all
kinds
of
communities
from
people
wanting
to
run
their
own
mail
service
nodes
to
people
who
are
just
fascinated
by
the
fact
that
we're
making
making
react
native
work
on
a
desktop,
which
is
awesome.
E
So
a
last
little
slide
from
me
is
just
that's.
A
number
of
the
team
have
gathered
the
in
cardona
in
Spain
for
a
sort
of
week
get
away
with
the
Givi
team,
the
swarm
city
teams
and
people
from
my
crypto
and
a
few
other
end
and
folks
from
across
the
community.
It's
been
a
really
really
great
time.
It's
fantastic!
Much
like
peppers,
saying
about
the
ux
gathering
in
amsterdam.
E
Yet
second
particular
has
finally
been
granted
his
wish
to
get
more
of
that
core
developers
working
on
some
research
stuff
and
a
lot
of
the
focus
of
this
week
has
been
on
looking
into
swarm
properly
and
trying
to
understand
what
it
might
look
like
to
integrate
different
aspects
of
it
and
how
he
could
usefully
do
that
and
test
things
like
PSS
against
whisper
and
make
sure
that
we
still
have
something
stable.
That
works
without
any
sort
of
compromises.
There's
been
some
really
really
interesting.
E
Research,
particularly
into
sort
of
corrosion
resistance
and
safe
and
decentralized
messaging,
which
is
as
everybody
in
there
is
a
very
difficult
problem.
So
today
is
just
a
hack
day
where
we're
working
on
some
of
the
mail
server
stuff
and
playing
around
with
a
bit
of
PSS,
as
well
as
some
future
sort
of
improvements,
particularly
around
swarm
integrations.
So
that's
a
huge
amount
of
fun
I
strongly
encourage
all
and
every
other
teams
to
get
together
at
some
stage
because
it
really
does
add
a
dimension
for
the
work,
that's
quite
difficult
to
achieve
when
it's
completely
remote.
K
E
L
E
So
the
simple
truth
of
it
is
that's.
The
whisper
documentation
is
a
bit
of
a
shambles.
At
the
moment.
We
have
that
internal
doc
that
Eric
and
Alex
worked
on
about
how
we've
written
our
client-side
like
communication
protocol
in
the
changes
that
we've
made.
That
should
be
open
up,
opened
up
very
very
shortly
and
will
probably
be
the
definitive
source
for
like
how
to
use
this.