►
From YouTube: Status Town Hall #40 - Monday August 5, 2019
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
A
B
A
Right
so,
let's
just
get
started:
hi
everyone
welcome
to
this
town
hall,
our
40th
Town
Hall,
your
host
roshaniya.
So
let's
get
started.
First,
we
have
a
quick
announcement
from
people
opps.
We
have
a
new
core
contributor,
Andre
and
joining
us
an
in
developer,
so
make
sure
you
reach
out
and
say
hello
speaking
of
hiring
what
we
are
looking
for:
referrals
or
suggestions
of
anyone.
You
know
for
an
engineering
weed
and
a
small
update
for
the
off
side.
C
So
you
might
have
read
on
discuss
that
we're
changing
our
password
manager,
so
we've
decided
to
get
rid
of
LastPass.
It
wasn't
a
great
user
experience
and
we've
actually
found
an
awesome
open
source
equivalent,
which
is
bit
orden.
A
few
of
you
recommended
it
and
we
checked
it
out,
and
it
looks
really
good
so
I'll
be
reaching
out
to
you
in
the
next
couple
days
about
migrating
passwords.
C
So
have
a
think
already,
if
there's
stuff
that
you
know
you
need
migrated
and
that
maybe
only
you
had
access
to
that
would
be
great
to
have
ready
and
and
we've
got
a
discuss
post
going
and
the
question
that
we
have
right
now
is
whether
to
go
self
hosted
or
not,
and
if
we
do
go
that
route,
we'll
need
to
do
it
sooner
rather
than
later
so
yeah.
Let
us
know
what
you
think
about
that.
Thank
you.
D
D
This
morning,
it
sounds
like
we
had
set
ambitiously
a
target
of
mid-august
to
finalize
all
of
the
the
remaining
work
for
this
particular
scope,
and
it
looks
like
we're
close
but
we'll
probably
probably
end
up
conservatively
having
v1
audit
ready
by
end
of
August
and
I'll
go
into
a
little
bit
more
granular
detail
on
the
the
course
slide
later
about
what
we're
working
on
a
couple.
Other
Jenner
updates
that
I
want
to
share.
D
So
thanks
very
much
to
everyone
who
participated
in
that
and
if
you
have
any
further
thoughts
around
that,
please
please
weigh
in
and
I've
also
recently
created
a
post
about
the
remaining
v1
scope
that
we
cut
just
making
sure
that
we
prioritize
everything
appropriately
for
the
release
cut
itself.
So
there's
a
bunch
of
items
in
there
that
came
out
of
our
scope,
cutting
call
from
three
or
four
weeks
ago
and
I
want
to
make
sure
that
anything
that
needs
to
be
included
in
the
release
is
flagged.
So
have
a
look
at
that
as
well.
E
E
Most
of
the
time
when
people
take
fees
and
cryptosystems,
they
burn
them,
which
means
they
send
them
to
an
address
where
they
can't
be
recovered,
which
then
supposedly
raises
the
value
of
all
the
remaining
tokens
that
are
currently
available.
Barry
did
an
analysis
to
see
whether
or
not
it
be
better
to
recycle
those
fees
into
other
projects
and
then
how
to
evaluate
when
it's
better
to
burn
or
to
send
it
to
a
different
project.
E
So
it's
interesting
article
on
that
we're
currently
working
on
a
teller
network
article
to
transition
from
the
previous
utility
token
economics
articles.
So
after
the
discover
one
we're
going
to
move
to
tell
the
network
which
gives
us
kind
of
transient
transitions
just
nicely
into
the
some
of
the
new
strategy
of
opening
up
and
focusing
more
on
the
status
network
and
what
that
has
to
offer
and
then,
after
that,
we're
also
in
discussions
with
Forbes,
to
create
a
series
on
adopting
traditional
finance
models
for
crypto
currencies.
E
So
what
that
means
is
how
do
we
take
some
of
the
financial
modeling
tools
that
people
use
for
traditional
assets
and
adapt
them
so
they
fit
nicely
within
crypto
currencies
or
are
more
useful
and
something
like
coming
up
with
some
of
the
variables
use
there.
So
that'll
be
like
a
multi
series.
I
got
some
little
blog
series
for
Forbes.
That's
all.
We
have.
A
D
So
I've
merged
core
and
core
UI
into
one
side.
Now,
since
we're
working
together
as
one
team,
so
we've
got
kind
of
two
parallel
paths.
We
had
been
working
on
putting
out
another
beta
release,
version
point,
14,
the
highlights
of
which
are
meant
to
be
pushing
stickers
on
main
that
some
bug
fixes
and
then
just
some
general
preparation
for
4v1,
including
a
notification
to
all
of
our
users,
of
the
changes
that
are
coming
ahead,
so
that
they
can
prepare
themselves
adequately.
D
And,
however,
we
discovered
a
blocker
two
weeks
ago
that
still
has
not
resolved
so
for
Android
for
the
Play
Store.
We
now
need
to
put
out
a
bit
64
version
of
our
app,
and
there
is
a
bug
in
in
this
version
that
Pedro
is
currently
working
to
troubleshoot.
We
won't
be
able
to
make
another
Android
release
until
that
is
fixed.
D
We
might
end
up
as
a
contingency
making
a
re-release
of
version
0.1
3
for
iOS,
just
because
we
have
until
sometime
later
in
August
the
end
of
the
month
to
maintain
our
iOS
distribution
list.
So
if
we
don't
fix
this
bit,
64
issue
in
time
to
uncut
the
full
release
and
then
we're
gonna
go
with
Plan
B,
which
is
just
rerelease
on
iOS
to
maintain
our
distribution.
As
for
v1,
the
team
is
making
really
good
progress
on
on
each
each
of
the
the
big
scopes
of
work.
D
So
the
real
database
removal
accounts
are
nearly
finished
there
to
me.
Tree
and
Eric
have
been
tag-teaming.
That
I
believe
multi
account
account.
Generation
itself
is
now
complete
and
andre
has
moved
on
to
the
options
for
adding
more
accounts,
one
via
the
the
54
path,
which
would
be
just
to
create
a
new
account.
D
So
you
can
have
multiple
and
then
also
the
option
to
create
a
watch
only
accounts,
and
then
we
have
aundrea
and
Adam
who
are
working
on
the
four
remaining
open
issues
under
protocol
separation,
which
are
critical
to
the
b1
scope
on
the
status
go
side
and
I
believe
all
of
those
issues
are
currently
work
in
progress,
so
yeah
I've
included
links
to
the
relevant
project
boards
on
github.
If
people
would
like
more
detail
and
and
that's
our
update.
A
A
F
We
we
basically
yeah
we're
in
this
phase.
That's
where
we're
writing
great,
more
detailed
documentation,
in
fact
about
the
hotel
of
network,
as
well
as
doing
an
internal
audit
as
well
as
as
well
as
some
formal
testing,
so
we
had
sort
of
like
oh
please.
Meanwhile,
we
we
reopened
that
code
freeze
because
Simon
designer
joined
the
team,
and
it
did
a
lot
of
changes
that
look
really
worthwhile.
So
we
implement
the
national
implementing
some
of
those.
Those
changes
today
to
the
US.
F
A
Sorry,
everybody
that
the
slide
didn't
come
through.
Just
a
quick
note.
We
will
share
the
slides
at
the
end
of
the
town
hall,
so
you
can
see
what
you're
talking
about
with
the
relative.
The
relative
links
also
shared.
So
now
we
jump
into
Q&A
and
we
have
just
one
question
that
was
submitted
and
I.
Believe
Johnny
will
take
this
one
and
it
is
to
please
explain
our
v1
marketing
strategies.
A
B
So
the
details
are
being
finalized.
Now
so
there's
you
know
still
some
things
to
sort
out,
but
basically
they
were
taking.
The
launch
of
v1
is
there's
an
opportunity
to
tell
especially
three
stories,
obviously
launching
in
the
product
which
I'll
go
into
detail
on
using
that
as
a
time
to
really
start
communicating,
not
the
shifts,
but
the
idea
that
we're
building
communication
protocols
and
that
extends
into
messaging.
B
We
can
use
it
as
a
time
to
implement
anthem,
amplify
Nimbus
and
then
potentially
some
other
stuff
around
storage
as
well,
and
then
the
other
story
will
tell
is,
is
really
I.
Guess
elevating
the
status
network
and
I
guess
trying
to
distinguish
status,
the
core
application
and
status
that
network
I.
Think
there's
just
a
bit
more
work
do
around
that.
So
people
can
actually
distinguish
between
the
two
and
understand
the
and
we
don't
pigeonhole
ourselves
into
just
becoming
a
mobile
application.
B
And
then,
if
you
know,
if
focusing
on
v1
we're
gonna
break
it
down
into
potentially
four
categories,
which
is
brand,
you
typically
need
brand
coms
to.
You
know
make
sure
we're
continuing
to
tell
the
story
of
our
principles
and
why
we're
building
this-
and
that's
just
you-
know-
lightweight
content.
Community
activations
things
like
that
really
need
to
drive.
The
emotional
connection
to
the
product.
B
Second,
is:
is
the
product
itself
right,
so
we
need
a
lot
of
explainin
air
content,
an
explainer
material
at
a
high
level,
which
is
you
know,
messenger
browser
wallet
and
then,
if
you
think
of
it
in
terms
of
like
a
funnel
content,
marketing
plan
middle
of
funnel
then
is
breaking
down.
Those
features
to
a
bit
further
to
the
you
know
the
benefit
of
them
from
the
privacy
and
security
standpoint
and
then,
if
you
go
further
down
the
funnel
it's
kind
of
like
the
technical
details
around
them,
so
that
is
not
only.
B
B
So
that's
brand
that's
product,
activating
the
community
oxeye
really
bit
on
product
we're
gonna,
be
you
know
you
can
break
that
down
into
message,
brows
and
wallets,
and
each
one
of
those
have
their
own
stories,
but
from
a
message.
Sorry
from
a
browser
perspective
will
be
leaning
into
Dobbs
quite
a
bit.
So
obviously
Annie's
done
a
lot
of
this
really
interesting
work
with
discovery
and
we're
building
out.
B
What's
called
the
DAP
just
app
integration,
Center
right
now
and
there's
an
entire
inbound
and
outbound
campaign
strategy
to
activate
dot
partners
around
the
time
of
our
launch
as
well,
and
then
then,
there's
community
activations,
so
really
really
tapping
into
our
ambassador
group.
We're
trying
to
build
out
the
Ambassador
Program
and
further
right
now
ahead
of
the
launch
we're
trying
to
build
that
local
community.
So,
for
example,
we've
got
meetups
in
Istanbul
before
our
before
our
off-site
to
try
to
like
build
these
local
communities
all
over
the
world.
B
Istanbul
Seoul
Japan,
Latin
America,
you
name
it's
just
tapping
into
the
ambassadors
and
incentivizing
them
to
build
their
local
communities
as
well,
and
then
the
the
final
kind
of
pillar
is
PR.
We're
going
to
lean
pretty
heavily
into
PR,
because
that
amplifies
the
message
that,
at
a
rate
that
our
channels,
just
simply
can't
so
investing
pretty
heavily
in
that
our
launch
partners
just
to
try
and
drive
as
much
possible
awareness
around
the
launch.
I
think
it's
a
really.
Obviously
it's
a
really
important
time
for
the
application.
B
It's
really
a
good
time
to
like
use
that
to
then
amplify
these
stories
around
it.
So,
like
I
was
saying
before
communication
protocols
and
also
the
status
network.
So
that's
a
bit
of
high-level
there's,
also,
some
obviously
very
tactical
things.
We're
working
on
around
you
know
like
safe
ad
networks,
which
we're
exploring
like
code
fund
things
like
brave
browser
all
these
ways
just
so
it
like
get
the
word
out
there,
but
also
staying
true
to
our
principles.
B
So
that's
a
that's
a
very
tricky
thing
that
we're
trying
to
work
on
right
now
we
don't
want
to.
We
don't
want
to
just
tap
into
like
standard
ad
networks,
and
you
know
quote
unquote:
growth,
hacking
methods,
because
a
lot
of
those
just
go
in
direct
opposition
to
our
our
principles,
around
data
privacy
and
data
usage.
So
stay
tuned
on
that
I'm
planning
to
present
all
of
this
in
a
much
more
detailed
plan-
probably
the
next
channel.
So
hopefully
a
lot
of
questions
get
answered.
Then.