►
From YouTube: Status Town Hall - April 9, 2018
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
C
C
C
C
C
D
D
D
D
D
D
Make
fun
thank
so
this
is
the
frame
one
tuning
in
on
YouTube.
We
have
a
channel
which
is
about
studying
fundamentals
of
your
fav,
and
here
are
a
bunch
of
resources
that
have
been
shared
the
last
week
and
also
remind
you
to
check
it
out
if
you
haven't
already
and
want
to
learn
more
about
fundamental
technology
that
we're
building.
On
top
of
you
next
one.
We
have
drawn
me
with
a
marketing
update
thanks.
E
D
Thanks
Johnny,
so
we
have
these
oak
yards
that
we
have
set
for
q2
and
if
it
goes
through
at
length,
we
cancel
and
we
can
sort
of
tracking
okay,
ours
and
also
which
forms
a
target
in
them.
So
encourage
you
to
check
out
four
core
and
statistical
Monte
and
research
for
marketing
and
so
on,
and
you
can
see
the
priorities
are
most
lists
and
also
we'll
see
more
in
the
swarm
updates,
in
terms
of
which
ones
are
targeting
which
soakers
Andy.
Are
you
online?
D
F
Can
you
give
me
hope
so
I
hope
you
can
and
I'm
going
to
speak
about
after
meditation,
it's
a
part
of
continuous
delivery
process,
how
we
are
doing
that
and
status
and
what
I'm
aiming
to
do
next.
So
one
of
our
objective
is
a
continuous
delivery.
You
too,
and
80%
of
automated
test
strategies,
so
I
will
start
from
sharing
actual
state
or
right
now,
almost
all
main
functionality
recover
dysfunctional,
automated
tests,
which
are
ranked
against
each
PR.
It's
about
all
type
of
turn.
All
types
of
transaction
we
are
send
comment
request.
F
F
Can
we
go
to
the
next
screen?
I
can't
yeah
so
says
how
test
results
are
looked
under
er.
You
can
see
that
there
is
a
number
first
number
of
failed
tests
and
also
you
can
see
the
detailed
to
last
steps
and
error
message,
but
the
most
useful
part
of
that
is
device.
1
device
number
links
of
next
screen,
I.
F
Picnic
scream
yes,
so
after
clicking
on
any
device
link,
you
can
see
each
test
step
and
in
the
end,
you
can
see
why
it's
a
test
failed.
So,
for
example,
here
there
is
an
error,
doesn't
support
name
for
all
transactions
in
the
ER
and
that's
it
that's
our
actual
state
of
functional
tests.
For
now
we
have
on
the
functional
tests,
but
we
have
a
lot
of
next
steps
which
I'm
going
to
speak
about
right
now.
F
Yes,
our
next
step
is
to
become
so
right
now
is
that
we
are
part
of
Sydney
process,
but
we
want
to
be
most
significant
part
of
Sydney
process.
First
of
all,
we
would
like
not
to
merge
at
they
are
if
sanity
tests
it
failed.
It's
really
important
because
you
don't
want
any
bugs
in
my
intentionality
to
be
in
develop
branch
in
our
Knightley's
build
and
also
we
don't
want
that
to
be
in
ruins.
So
for
that
we
need
to
seems
to
be
done.
F
Now
it's
only
a
PS
team,
so
in
future
it
will
be
something
like
next
screen
yeah.
Yes,
so
we
will
be
able
to
track
a
CPU
memory.
Peaks
total
download
that
allow
the
data
for
each
test
and
the
most
important
part
that
we
will
be
able
to
see
reach
exactly
state.
What
is
the
exact
state
of
the
app
when
we
have
CPU
spikes?
How
many
course
I
used
in
case
of
CPU
and
which
thread
are
using
the
most
CPU
and
almost
the
same
graphs
will
be
provided
for
memory
for
power
consumption?
F
G
Also
thanks
Anton
sorry
for
the
technical
difficulties
earlier
there
was
some
major
issues
happening
with
zoom,
but
hopefully
everything's
working
back
working
now
and
let's
get
back
to,
we
had
some
open
bounty,
something
we
want
to
talk
about
and
getting
you
know,
increased
adoption
and
I.
Think
Andy
is
currently
in
transit.
So
Martin
are
you
there?
Can
you
give
a
quick
run
through
of
of
this
I'm.
H
Then
please
tell
us-
and
maybe
you
can,
even
when
either
one
solving
it
and
if
that
happens,
please
reach
out
in
the
open
bounty
channel
9
right
and
if
you
have
any
other
ideas,
how
we
can
I
get
more
attractive
to
contribute
via
open
bounty.
Then
please
also
reach
out
through
that
channel,
and
now
we
can
go
through
some
stats
as
well.
H
That
would
be
the
site
exactly
things
nobuhle.
So,
as
you
can
see
the
week
before
this
one
or
the
week
before
last,
we
we
be
like
almost
peaked,
but
last
one
we
haven't
been
so
good,
so
we
will
try
to
one-up
next
week
or
this
week
now
and
yeah.
There
are
some
stats
on
the
side
you
can
review
these
later.
If
you
want
L
won't
go
into
detail
right
now,.
G
A
Yeah
of
last
week's
Beamer
I
worked
on
updating,
react,
native,
desktop
project
who
newer
version
of
react
native,
so
it's
compatible
with
status,
react
of
react
native
and
also
we
have
started
work.
Port
latest
sources
of
react
run
on
react,
native,
desktop
at
firm,
currently
work
in
progress
and
all
democratic
countries.
Working
on
this
also
was
my
investigation
to
integrate
JavaScript
or
yes,
engine
interact
native
desktop.
This
should
eliminate
dependency
on
node.js
engine,
and
this
also
should
increase
compatibility
with
region
react
native
project
because
JavaScript
engine
is
used
there.
A
I
Okay,
cool
yeah,
so
how
did
Secretariat
started
and
we
got
the
record
from
the
first
week,
but
that
was
mostly
looking
for
looking
at
the
network
traffic
and
other
things
like
more
general
documentation.
So
actually
we
had
a.
We
have
a
call
today
later
to
get
more
details,
so
I'm
just
updated
on
channel
but
yeah.
This
is
in
progress
and
we
started
testing
maintenance.
So
basically
I
ran
it
on
real
devices
and
just
worked
fine.
So
we
are
moving
this
to
to
the
testing
team
to
do
more
for
our
tests.
I
There's
one
issue
discovered
that
we
were
using
my
my
servers
for
all
networks:
that's
gonna
to
be
fixed
before
release
dead,
but
yeah.
That's
the
only
blocker
for
now,
and
that
goes
for
the
next
two
weeks
is
just
continue
to
sink,
make
sure
that
my
net
is
working
properly
and
also
finish
automated
status
go
tests.
So
you
want
to
be
sure
that
all
the
messaging
layer
on
the
status
go
is
working
fine
and
check
it
through
Inc,
see
I,
so
so
yeah
yeah.
So
that's
also
like
one
part
of
our
such
go
test.
I
I
I
So
we
basically
wanted
to
simplify
the
dependencies
between
the
packages,
because,
right
now
it
was
leaked
and
rolled
and
their
responsibilities
were
in
different
packages
wanted
to
reduce
that
improved
interfaces,
naming
in
all
things
around.
So
it's
easier
for
external
contributors
to
work
the
codebase
and
that
was
achieved
so
there's
just
little
things
that
were
left
and
we
hopefully
gonna
close
this
successfully
in
in
the
in
the
next
in
this
or
the
next
week.
So
yeah
thanks.
J
Yeah
I'm
actually
standing
in
for
zahary
today
he's
on
vacation,
but
he
was
kind
enough
to
provide
a
slide.
So
I
figured
it's
good
to
go
over
it.
We
had
some
initial
success
like
a
first
milestone.
It
was
pretty
cool.
We've
managed
to
connect
all
the
gifts,
nodes
and
particles
running
out
there
on
the
test
net,
which
is
a
great
step
forwards.
This
means
that
we
have
some
socket
communications
in
place.
We
have
the
discovery
protocol
nailed
so
that
we
can
see
who's
out
there.
J
We
also
have
some
of
the
basic
cryptography
set
up
in
in
Indian
bits
now
so
going
forward
from
here.
We're
gonna
be
focusing
on
the
wire
protocol
itself
in
order
to
be
able
to
start
syncing
the
blockchain.
What's
what's
sort
of
the
next
step,
and
as
I
mentioned
to
me
as
well,
that
that
one
thing
that's
consistently
important
to
think
about.
Is
that
there's
not
just
one
client
out
there?
J
It's
it's
a
collection
of
times,
there's
gas
parity
pie
in
VM
and
so
on,
and
they
all
implement
slightly
different
features
and
those
might
be
slightly
different
features
for
Saint,
but
also
other
parts
of
the
protocols.
It's
always
important
to
keep
this
in
mind
when,
when
developing,
for
at
theorem
and
and
to
have
this
or
feature
fragmentation
in
mind,
that's
it
for
today,
thanks
awesome.
K
K
The
main
achievement
was
to
update
to
v6,
and
then
there
was
they
the
good.
He
made
a
bunch
of
adjustment
based
on
our
feedback
from
new
protocol,
so
yeah
like
it
says
you
need
some
documentation
now
and
then
there's
one
we
because
and
with
the
new
protocol
the
this
one
managed
to
get
about
a
big
reduction
in
in
bandwidth.
So
the
the
matrix
are
almost
which
it's
not
ten
megabytes
today,
but
about
pony
she's,
already
quite
better
than
before.
G
Awesome
yeah:
this
is
a
crazy
improvement,
so
very
happy.
This
is
out
the
door
I
think
it
was.
It
was
pushing
the
most
recent
release
and
hopefully
I
guess
when
the
documentation
is
done.
This
can
be
wrapped
up.
So
thanks
to
everyone
who
worked
on
this
moving
on,
we
have
go
backwards.
So
sixty-eight
matrix,
Chad,
yeah.
L
Hi
so
quick
background
on
call
metrics.
If
you
don't
know
about
it,
it's
a
way
for
us
to
track
some
call
metrics
to
understand
how
the
app
is
doing
to
understand.
For
example,
if
people
are
using
depths
or
sending
transactions
for
the
purposes
of
like
learning
and
actually
improving
the
and
to
do
it
in
in
a
way
that's
like
privacy.
First,
for
example,
we
communicate
upfront
users
about
what
we're
doing.
We
include
like
links
to
the
source
code
and
it's
like
opt-in
and,
of
course,
you
can
opt
out
at
any
time.
L
In
the
last
two
weeks,
we've
upgraded
insta
bug,
there's
a
whole
bunch
of
new
features
there,
including
a
survey
feature
and
we've
drafted
an
messaging
survey
it
that
we're
going
to
use
for
gauging
message,
reliability
and
without
it
our
some
opt-in
and
our
toggle
preferences
and
settings.
We've
got
new
events
added
to
onboarding
screen
and
push
notification,
prompt
and
we've
created
some
dashboards
and
slack
updates.
So
every
day
we'll
get
some
call
metrics
pumped
into
the
sixty-eight
call
metrics
channel.
They
can
give
us
an
idea
of
how
we're
doing
for
the
next
two
weeks.
M
Hey
guys
sue
me
yep,
so
the
main
thing
about
the
onboarding
swim
is
that
we
changed
the
way
we
need
to
read
on
it
and
we
decided
to
sync
up
our
iteration
with
example,
meetings.
So
the
previous
two
weeks,
we
were
free,
pretty
much
figure
around
the
priorities
for
the
first
week
and
then
we
finally
did
it
updated
the
copy,
with
the
marketing
team,
scheduled
some
test
sessions
and
made
first
initial
wireframes
for
improving
the
Welcome
of
home
screen
and
for
the
next
two
weeks.
The
plan
is
much
more
sincere.
M
It's
implement
the
copy
updates
in
the
app
and
the
all
the
rest,
tester,
more
design
related,
which
are
like
drafting
on
the
welcome
screen
and
bring
extra
mock-ups
I
integrate.
The
friend
invitation
today
to
the
onboarding
process,
explore
the
possibility
of
adding
touch
ID
and
creating
some
initial
mock-ups
Netra
baiting
it
into
the
existing
flows
and
improving
the
wallet
set
up
to
encourage
people
to
transfer
their
funds
to
the
cells
wallet,
to
increase
the
daily
active
users
and
the
possibly
be
a
number
of
transactions.
G
K
Yeah,
can
you
hear
me
again
yep
okay,
so
this
one
was
running
for
few
weeks
and
we
finally
got
it
merged
into
develop.
It
was
a
really
big
year
with
Jana
undress
and
it
it
is
basically
the
closure
side
of
low
traffic
swarm,
which
I
used
to
take
advantage
of
all
the
features
of
whisper
v6,
as
well
as
making
some
optimizations
regarding
the
size
of
the
messages
and
the
number
of
messages
that
are
needed
to
have
basic
information
like
scene
messages
and
yeah.
So
now
the
first
iteration
the
MVP
is
done
and
merged.
K
So
it's
in
the
current
Knightley's
and
we
are
currently
in
iteration
1,
which
is
about
reach,
which
is
in
group
chats,
because
that
was
already
in
the
last
release
group
chats
some
features
of
project
where
they
activate
and
for
this
merge
we
reactivate
group
chat
entirely
just
so
that
we
can
focus
on
getting
it
merged.
And
now
we
maybe
today
or
the
next
days
we
will
be
introduced
group
chat
without
the
bags
and
with
all
the
features,
and
then
we
will
have
another
iteration
that
will
be
busy.
B
And
so
basically,
what
we
did
in
what
two
weeks
we
made
it
sort
of
a
proof
of
concept
when
we
use
Android
event
to
post
the
note
when
the
app
goes
to
the
background,
and
it
turns
out
that
it
gives
some
like
improvement
to
energy
efficiency.
But
it
is
not
as
good
as
I
expected
it
to
be,
so
we
will
give
into
it
more,
and
we
also
did
some
work
in
terms
of
polishing
guidelines
and
body
of
knowledge
for
energy
efficiency.
B
B
We
also
will
be
able
to
see
how
much
energy
does
eat
right
now
so,
unfortunately,
or
like
the
new
protocol,
is
a
very
good
thing,
but
since
we
realized
on
the
boss
that
were
sending
messages
to
energy
efficiency
right
now,
we
need
to
support
this
new
Chronicle
to
be
able
to
compare
this
builds
with
lighting
and
then
also
try
to
make
some
kind
of
compression,
because
we
haven't
that.
Our
key
result
is
to
keep
the
background
and
foreground
energy
compression
within
the
boundaries
of
the
similar
I
am
up.
B
C
C
I
Yep,
so
this
was
this:
is
a
research
to
make
sure
or
just
find
out
if
discovery
version,
5
is
usable
and
we
can
use
it
to
switch
from
static
notes
to
the
dynamic
notes
found
using
discovery
protocols.
So
Dimitri
was
working
on
this
recently
huge
huge
effort
to
make
it
work.
So
the
current
state
is
that
we
have
a
core
request:
that's
gonna
be
merged
like
today,
or
tomorrow.
Probably
also
there
was
a
lot
of
improvements
in
network
usage,
because
that
was
the
the
main
that
the
biggest
issue
of
discovery
version
5.
I
So
that
was
also
resolved
and
there
was
there
were
also
extensive
tests
on
the
current
clusters,
which
basically
formed
a
docker
swarm
cluster
and
me
to
run
there
a
lot
of
tests
to
make
sure
that
works.
Fine,
so
so
yeah.
This
looks
quite
solid,
so
you
want
to
merge
pending
peers
and
start
testing
on
real
devices
and
and
see
how
it
can
evolve
later.
I
Yeah
lessons
learned,
discover,
5
version.
5
requires
custom
code
when
in
when
compared
to
the
previous
solution
and
in
killing
consumer
of
traffic,
so
we
were
doing
some
tricks
to
lower
the
number
of
the
number
of
by
it's
going
back
and
forth
so
so
yeah.
It
looks
good
for
now
so
yeah
we'll
proceed
with
the
buddha
steps
in
the
next
two
weeks.
So
so.
D
Yeah,
so
so
this
is
about
sort
of
this.
One
process
that
you
are
seeing
at
the
Town
Hall
and
largely
is
about
sort
of
removing
from
having
issues
where
it's
sort
of
ad
hoc,
how
you
create
ideas
and
they
are
not
updated
and
so
on,
to
what's
being
more
pull
request
based
or
just
like
a
code
base
where
it's
or
you
have
more
discrete
steps
when
a
swarm
starts
and
when
you
update
iterations
and
all
these
kinds
of
things,
that's
been
the
main
thing
we've
done,
and
we've
also
made
their
ideas
repository
more.
D
Who
means
so.
You
can
see
it's
see
which
ideas
are
in
progress.
You
can
see
who
is
committed
to
an
idea,
and
these
kinds
of
things
and
the
sort
of
main
things
we're
trying
to
do
is
one
is
in
terms
of
knowledge
for
link
so
make
sure
that
people's
of
this
general
consensus
of
what
a
swarm
is
and
sort
of
what
it
means
for
a
swarm
to
be
well
defined,
having
roles
and
all
these
things,
and
also
making
sure
that
we
have
swarms
to
cover
all
the
core
OPR.
D
So
we
set
for
ourselves,
and
a
third
goal
is
to
enable
experimentation
for
stays,
open,
bounty,
that's
around
sort
of
step,
taking
steps
towards
creating
a
decentralized
autonomous
organization
and
tying
swarms
and
work
that
we're
doing
to
compensation
as
for
goal
for
next
two
weeks,
it's
but
ensuring
repositories
kept
up
to
date
and
supporting
swim,
leads
and
people
who
created
a
us,
clarify
valid
rules
and
capture
and
spread
knowledge
about
the
life
cycle
of
a
swarm
definition
and
roles
and
so
on.
And
if
you
go
to
the
next
slide,
we
have
some
say.
D
Yes,
you
can
see.
If
you
go
to
that
URL,
you
can
see
that
idea
registry,
where
you
can
see
sort
of
how
each
city
is
doing
if
it's
probably
and
so
on,
and
we
also
have
some
stats.
Things
happen
last
two
weeks
as
we
have
lots
of
ideas
that
are
sort
of
committed,
including
some
historical
ones,
got
eleven
well
defined
swarms
in
progress.
Some
ideas
in
review
right
now
we're
covering
50%
of
core
cures,
and
we
obviously,
when
I
and
that's
sort
of
well
defining
progress
once
it
also
drafts
forms.
D
We
obviously
want
to
push
it
up
higher
and
we
also
have
further
people
who
committed
to
at
least
one
well-defined
in-progress
form.
So
thanks
everyone
who
has
been
helping
out
with
this
and
sort
of
yeah
being
a
part
of
us
adopting
this
thing,
and
if
you
have
any
initial
feedback
on
how
this
concept
is
going
or
thoughts
or
anything,
don't
hesitate
to
to
write
it
in
either
home
channel
or
120
slack
town.
Thank
you.
H
I
hope
you
can
hear
me
yep
cool,
so
just
connecting
to
to
what
Oscar
just
said:
we're
trying
to
move
to
a
model
where
we
have
these
individual
swarms
and
they
could
do
like
delivering
value
to
the
status
app
in
a
stays
community
and
an
important
part
of
that
is
that
these
sort
of
that
work
can
be
incentivized
like
in
decentralized
way
and
all
that
kind
of
stuff.
And
we
have
open
bounty
already.
H
It's
started
last
week
and
over
the
last
weeks
we
defined
the
idea
and
and
worked
out
a
timeline
in
which
it
seems
achievable
and
started
working
on
to
compensation
schemes
that
could
work
for
incentivizing,
entire
swarms
and
so
for
the
next
two
weeks.
We
try
to
kick
off
two
swarms
that
use
these
compensation
schemes
and
we'll
push
that
into
the
community
as
well,
announcing
it
and
then
perhaps
will
try
to
create
a
community
built
swarm
as
well
yeah.
H
H
G
H
G
G
Okay,
ours
is
various
tabs
at
the
bottom
and
you
can
see
what
people
are
working
on
and
yeah.
It's
you
think
it's
really
important
for
people
to
get
context
on
what
everyone
considers
is
the
most
important
thing
so
be
sure
to
check
it
out.
So
on
that
note
now
we
can
move
into
the
Q&A
I
think
we
have
one
question
around
when
we
launch
which
I'm
assuming
means
when
we
launch
our
main
net,
so
we
will
launch
our
main
net
when
the
security
order
is
complete.
G
We
are
two
weeks
into
probably
four
to
six
weeks
of
the
audit,
as
Adam
said
we'll
find
out
more
this
afternoon
with
me:
have
a
call
with
our
third-party
security,
auditing,
firm
who's,
doing
audit
and
then
yeah
we'll
see
how
that
goes.
Last
week
the
update
was
everything's
fine,
but
they
are
about
15%
of
the
way
through
well.
The
next
question
is
about
the
harder
wallet
so
that
the
current
situation
with
the
harder
wallet
is.
G
We
are
code
complete
on
what
should
be
in
the
Java
card,
but
and
we're
looking
for
a
manufacturing
partner
to
work
with
us
to
actually
build
the
cards.
So
that's
a
hurdle
that
we
are.
We
are
covering
it's
not
our
top
priority,
but
it's
definitely
something
we're
still
working
on
at
the
same
time
that
we're
very
wary
that
we
want
to
go
with
the
trust
and
firm
because
you
obviously
this
is
something
it's
incredibly
sensitive.
G
D
G
That
is
something
that
is
currently
planned,
and
then
there
were
also
that
there's
thoughts
around
SNT
utility
and
how
you
can
manage
that
group
chat
so
that
you
can
ensure
that
quality
is
high
enough,
that
potentially
there's
a
threshold
for
joining
or
something
like
that.
So
public
chats
is
something
that
the
team
is
looking
into.
G
I,
don't
think
it
is
an
okay
are
in
queue
to
as
far
as
I
know,
for
the
core
team,
but
is
something
that
has
been
dabbled
I
think
there
was
a
couple
of
early
swarms
that
were
ended
up
getting
merged
and
then
disbanded
on
this
topic
last
quarter.
But
yes,
it
is
something
that
it
likely
won't
get
built
in
q2,
but
probably
in
q3.
G
G
Nope,
okay,
all
right
otherwise
yeah
you
can
come
find
us
on
riot
everyone's
there
yeah
all
right
thanks
everyone
hold
on
Chloe
yeah,
one
more
question:
yeah:
oh
yeah
I
got
it
when
when
will
there
be
push
notifications
or
flagging
boxing
for
public
chats?
And
so
this
is
an
interesting
one,
because
the
way
in
which
public
chats
are
currently
implemented
is
that
you're
kind
of
listening
in
on
the
channel
I,
probably
I'm,
gonna
botch
the
explanation.
G
D
Can
jump
in
so
it's
we.
We
have
a
drafts
forum
for
extending
push
litigations
to
deal
with
these
kinds
of
scenarios
right
now.
It's
not
a
top
priority,
but
depending
on
user
feedback,
we
might
make
it
move
it
up
a
it's,
not
something.
That's
part
of
the
QT
opra
q2o
cures,
so
I
think
it's
something
that's
more
likely
for
Q
free!
D
E
D
Yeah,
currently,
no,
not
really
it's
it's
only
one
on
one
chapter.
Currently,
if
you
want
to
read
more
about
this,
that
you
can
have
a
look
at
that
to
say,
if
you
go
to
the
IDS
repository
and
search
for
push
notifications,
there
is
a
drafted
at
Pedro,
brought
up
with
some
thoughts
on
how
we
can
extend
our
current
implementation.