►
From YouTube: Status Townhall #35 - Monday 27, 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
Okay,
let's
begin
so
welcome
everyone
to
this
Monday
on
our
35th
Town
Hall,
let's
get
started
so
the
first
update
is
actually
from
me
and
it's
about
hour
all
right,
I'll,
say
I'm
sent
on
a
questionnaire
last
week
asking
what
people's
dates
are
for
availability.
We
landed
on
the
dates
of
Monday
September
16th
through
Thursday,
September,
19th
and
the
location
will
be
in
Istanbul.
Turkey
I
will
be
sending
out
more
information
about
the
agendas
and
booking
all
that
information
will
be
coming
up
soon.
A
A
B
So
yeah
I
just
wanted
to
give
a
quick
update
and
recap
of
all
finances,
so
I
think
its
first
sort
of
worth
repeating
the
overall
strategy
with
the
use
of
funds,
as
it
does
create
some
constraints
on
how
we're
thinking
about
budgets.
So,
as
I
stated
a
few
times
before,
like
it's
early,
we
really
need
to
think
long
term
and
hence
why
half
of
the
crowd,
sale,
proceeds
and
ëthe
won't
be
touched
until
status
is
ready
for
more
widespread
use.
B
B
So
the
good
news
is,
if
you've
been
following
the
crypto
markets
at
all
the
past
few
weeks,
you
would
have
has
been
in
some
recovery,
which
is
great
not
only
for
us
but
the
industry
as
a
whole,
and
as
mentioned,
we
already
have
enough
runway
and
Fiat
alone
to
take
the
whole
team
through
to
the
next
year.
So
this
does
hinge
upon
us
sticking
to
the
more
stringent
budgets
we
already
put
in
place,
so
we
can't
deviate
too
far
from
these
at
this
stage,
even
with
the
upturn
in
the
market.
B
That
being
said,
we're
very
cognizant
that
a
lot
of
the
team
took
pay
cuts
in
December
and
it's
something
we're
incredibly
grateful
for,
because
this
help
secure
statuses
feature
and
it's
kept
the
project
alive,
and
so,
when
it's
financially
viable
and
sensible,
we
certainly
still
aim
to
reverse
those
cuts.
We're
weary
of
committing
to
specific
dates
right
now,
given
the
volatility
is
still
there,
but
we're
closely
monitoring
the
situation
and
are
investigating
potential
scenarios.
Should
the
market
continue
to
recover.
B
So
I
expect
that
in
the
coming
months
or
weeks,
if
we're
lucky,
we'll
have
some
further
news
and
updates
there,
and
so
lastly,
I
just
say
that
we
don't
fall
into
any
of
the
same
traps
again
and
focusing
on
providing
financial
security
is
absolutely
paramount.
So,
if
you'd
like
to
chat
with
me
about
it
or
with
Danny,
please
feel
free
to
reach
out
and
yeah.
That's
that's
it
for
me.
Thanks.
Everyone.
C
All
right,
I'll,
quickly,
jump
in
on
the
previous
life
talk
about
kind
of
what
the
thinking
is
around,
what
the
focus
will
be
in
the
second
half
of
the
year,
and
this
is
quite
early
and
so
I
think.
The
main
purpose
is
just
to
share
where
the
the
mindset
is
that,
from
a
kind
of
longevity
standpoint
to
ensure
that
status
can
continue
for
the
long
term.
So
once
the
application
launches
in
hopefully
sometime
few
people
talk
about
that
tiny
bit
later.
The
second
half
of
the
it
will
really
focus
on
creating
value
for
status.
I.
C
Now
value
creation
is
a
little
bit
of
a
nebulous
term
because
it's
summary
revenue,
but
what
does
value
mean?
So
you
can
kind
of
think
of
it
in
two
broad
buckets.
One
is
in
cream
increasing
the
utility
of
SNT
and
that
means
to
implement,
build
and
optimize
all
RS
until
utility
features
in
order
to
have
SMT
be
a
critical
component
in
the
application,
success
and
everything
surrounding
the
status
ecosystem
so
tell
them
that,
for
example.
C
So
that's
what
one
focus
will
be
and
then
second
for
those
for
those
teams
where
it
makes
sense,
it
will
then
be
a
revenue,
focused
value
creation.
So,
for
example,
key
card
actually
can
generate
revenue,
so
those
will
be
the
two
things
that
we'll
focus
on
and
as
I
said
right
now,
this
is
early
and
it's
just
something
for
us
to
to
kind
of
share
and
discuss
and
consult
as
as
a
team
to
say,
okay,
what
does
look
like
four
for
each
area?
Where
does
it
make
sense
to
focus
on
and
sense
utility
versus?
C
Actually,
you
know
here's
an
opportunity
to
generate
revenue
through
what,
through
whatever
means,
so
that
will
be
a
common
theme
going
forward
and
for
us
to
actually
do
that.
We
need
the
application
to
be
to
be
loans
and
for
it
to
be
stable.
So
that's
just
kind
of
a
little
bit
of
a
glimpse
as
to
what
will
be
kind
of
thinking
about
I'm
talking
about
investing
in
going
into
second
half
of
the
year.
C
C
So
I'm
talking
this
to
be
a
code
freeze
at
the
end
of
the
quarter,
which
will
allow
us
to
initiate
and
start
a
security
audit
and
obviously,
as
we
know
from
last
year
for
our
beta
loans,
the
security
audit
is
not
short.
It's
you
know,
it
could
be
anywhere
between,
say
four
and
eight
weeks
and
then,
after
that,
we
need
to
you
know
clean
up
the
bugs
or
security
holes
or
flaws
or
compromises
or
whatever
it
comes
out
of
it.
C
So
we
want
to
be
code
freeze
as
soon
as
it
makes
it
as
soon
as
possible
and
then
sell
this.
You
go
after
that.
The
main
areas
of
importance
are
in
application
performance
as
well
as
in
the
UI
polish.
So
those
are
the
those
are
the
main
areas
that
we
need
to
kind
of
focus
in
on
the
next
month
when
it
comes
to
using
rike.
C
C
And
second-
and
this
is
you
know,
it's
great
to
see
so
much
adoption,
because
this
is
like
the
type
of
thing
that
Network
we're
working
to
improve
is
adding
progress,
so
whether
something
is
being
worked
on
or
it's
on
hold
or
it's
been
completed,
really
helps
to
say,
okay.
Well,
this
has
not
been
done,
even
though
you
know
it
was
meant
to
be.
Even
though
isn't
it
meant
to
be
completed
in
a
week
it's
now
completed,
so
we
could
move
forward
with
whatever
the
dependencies.
C
So
please
make
sure
to
add
that
progress
to
all
the
tasks,
anything
that
is
synchronized
with
github
actually
gets.
You
know
automatically
gets
the
you
know
when
it's
from
when
it
progresses
merger.
An
issue
is
closed
in
github
it
automatically
gets
completed
in
rike.
So
that's
not
an
issue
all
right.
So
now
some
interesting
stats
and
graphs-
it's
a
here
and
lids
coming
through,
but
this
is
where
we
are
at
in
terms
of
our
development
for
v1
I,
try
to
squeeze
as
much
into
the
chart
as
possible.
C
What
what
you're
seeing
is
for
onboarding
and
multi-account,
the
the
the
folders
have
been
open
to.
You
can
see
things
a
bit
more
detail
and
the
rest
have
been
closed
just
because
there
wasn't
enough
space
on
the
screen.
But
what
you
can?
What
you
can
see
is
you
can
kind
of
see,
dark
bars
and
then
you
can
see
basically
larger
bars
below
it.
So
the
dark
bars
were
where
our
progress
was
a
week
ago
and
the
larger
ones
are
where
we
are
now.
C
So,
if
you
click
to
the
next
slide,
you
can
actually
see
basically
our
progress
update
from
last
week
to
today-
and
you
probably
take
this
with
a
grain
of
salt
because
we're
still
getting
a
timelines
finalized.
But
what
we
can
see
is
actually
here's
the
updated
timelines
from
where
we
were
last
week
as
to
where
we
are
now-
and
you
can
see
onboarding,
for
example,
with
you
know,
think
the
timeline
is
moving
forward
by
three
days.
Multi-Count
support
which
has
been
going
through
some
awesome
and
awesome
specification
phase.
C
Actually
has
you
know
he's
27
has
been
moved
forward
by
27
days
and
now
slips
into
July.
So
this
helps
us
say:
okay,
well,
this
work
that
we
thought
was
going
to
be
done
in
q2
is
now
gonna
bleed
into
q3.
Can
we
potentially
paralyze
some
of
the
work
in
get
more
races
on
resources
onto
it,
rather
than
it
being
a
surprise
at
the
end
of
the
quarter
like?
Oh?
No,
why
is
it
taking
so
long?
C
So
this,
even
though
it
seems
like
it's
a
lot
of
work,
it
actually
helps
a
lot
in
identifying
where
who
the
critical
path
is
or
where
the
long
pole
is,
and
we
can
potentially
work
to
improve
that.
So
thank
you
to
everyone.
Who's
been
working
to
get
this
data
kind
of
clean
data
a.m.
equals
data
out
and
we're
able
to
really
help
get
things,
keep
things
on
track
and
identify
like
where
we
can,
where
potential
team
didn't
help
where
potentially
teams
have
excess
can
go
work
on
other
stuff
anyway.
C
So
this
is
the
kind
of
Gantt
chart
view,
as
you
can
see
from
this
slide
by
end
of
July,
we're
looking
to
be
Co
completed.
If
we
can
pull
forward
the
marthy
multi-account
work,
which
right
now
is
so
that
it's
you
know,
there's
the
go:
hey
I
won't
go
into
detail,
but
point
being
we
can
work
to
improve
these
timelines.
We
immediately
understand
exactly
where
we
are
in
terms
of
development,
all
right
next
slide
before
I.
Keep
going
on.
C
This
is
another
cool
indicator
of
how
things
are
going,
so
you
can
say,
there's
a
hundred
and
twenty
seven
tasks
in
total
to
complete
b1.
We
have
completed
49
of
them
and
there
are
eleven
overdue
fourteen
should
be
done
this
week
and
fifteen
backlog
thirty-two
will
be
done
later.
So
this
basically
helps
indicate
progress
and
see
how
we're
doing
it's
kind
of
like
a
burn
down
chart,
but
you
know
focus
on
a
specific
project
and
I.
Think
there's
one
more
slider
is
that
it
yeah.
C
So
the
last
thing
that
the
janitors
are
focusing
on
right
now
is
trying
to
improve
this
one
process
going
into
q3
and
there's
two
areas
that
one
area
of
success
I
think
we
found
and
one
area
we
can
improve.
The
area
of
success
is
being
be,
has
really
kicked
off
a
really
good
specification
phase
for
the
multicam
work,
which
involved
one
week.
You
could
call
them
sprinter,
iterations,
I'm,
basically
trying
to
get
the
design
the
design
and
the
architecture
down
packed
and
that
took
it
took
five
weeks.
C
So
it
wasn't
a
short
amount
of
time,
but
it
made
sure
that
what
we're
building
is
exactly
the
right
thing.
So
amazing
work
by
everyone
involved
in
that
and
I'll
be
following
up
to
try
and
get
that
documented.
So
we
can
add
it
to
this
form,
template
the
areas
that
I
think
we
can
improve
on
in
I
think
it
has
to
do
with
gating
between
these
milestones.
C
So
as
I
said,
multi
counseling
did
it
pretty
well,
but
when
we
go
between
the
research
phase
and
then
we
have
a
gate
to
the
specification
phase
and
then
another
gate
before
implementation
starts,
how
can
we
stream
like
that?
So
how
can
we
streamline
that?
So
it's
not
a
clunky
experience
so
that
it
doesn't
feel
like
people
are
blocked
by
a
process
or
that
process
actually
happened.
C
So
that's
something
that
I
think
we
need
to
work
on
I'll
be
putting
up
a
post
on
discuss
so
that
people
can
share
any
ideas
we
have
just
so
that
we
can
get
better
at
that
part
of
the
swamp
process,
and
that's
it
for
me.
So
just
pay
me
if
you
have
any
questions
on
anything
we've
gone
through
or
you
know
we
can
ask
questions
in
a
tunnel.
Hey.
A
A
D
Hello:
everyone,
quick
update
on
to
book
and
economics
last
week
was
the
week
before
I
forget
times
flying
by
in
ethnic
orb
watching
week
in
New
York,
we've
spent
some
time
me
Jakub,
Johnny
and
berries,
and
some
time
building
the
process
for
embedding
all
of
berries,
observable
HQ,
notebooks
and
a
ghost.
So
that
makes
our
our
blog
posts
interactive.
So
as
you're
as
you're
learning
about
these
different
use
cases
and
how
they
work,
you'll
be
able
to
play
with
all
the
levers
and
knobs
that
change
the
parameters
to
see
how
that
changes.
D
A
E
Hi
everyone,
it's
not
eager,
it's
no
problem.
So,
first
of
all,
they
are
going
to
release
next
mobile
opera
lists
this
week
and
it
has
a
very
exciting
number
13
from
core
improvements
team.
This
release
would
include
reporter
box
features.
So
if
you're,
the
old
user
of
the
up,
you
still
remember
insta-buck
reports
when
you
can
shake
the
device
and
get
the
I
like
some
screen,
where
you
can
report
a
box
to
the
team.
So
now
you
will
be
able
to
send
email
with
attached
logs
and
some
steps
to
reproduce.
E
If
you
describe
them
to
report
some
issues
that
you
experience
to
the
status
team
and
another
feature
is
been
able
to
retrieve
up
to
30
days
of
history
in
public
shots.
So
if
you
are
interested
in
some
all
the
messages-
and
you
just
join
the
chat
now,
you
will
get
possibility
to
see
not
only
the
last
day
or
24
hours
of
the
previous
message
history,
but
you
can
retrieve
day
by
day
and
yeah
travel
in
time
up
to
30
days
in
the
past.
So
what
will
working
on
right
now
in
core
improvements?
E
So
it's
not
yet
introduced,
but
probably
will
be
in
the
next
one:
it's
okay,
maybe
not
in
the
next
one
but
partially.
So
it's
also
moving
protocol
to
status
grows.
It
also
should
give
us
improvements
on
the
performance
side
and
it's
again
it's
still
in
the
deep
same
as
speeding
up
mail
servers
that,
like
has
several
things
to
improve,
and
now
it's
like
about
the
database
will
use
two
for
the
message
history.
So
again,
it's
ready
for
testing
but
again
for
work
is
in
progress.
E
Also
for
our
performance
improvements.
We
already
have
couple
of
PRS
intestines
that
would
bring
us
like,
as
you
see,
25
to
35
fastest
or
top
sorry
25
to
35
percent
hosta
start
up
rather
than
before,
and
this
numbers
depends,
of
course,
on
the
on
your
device
speed.
So
if
you
have
mobile
device,
then
it
will
be
like
thirty
five
percent
of
improvement.
E
If
you
have
have
faster
device
and
its
twenty
five
or
so
percent
of
improvement,
the
next
one
that
again
still
in
progress
but
should
give
us
even
more
improvements
in
the
performance,
is
the
Scotia
script
modules
PL
and
expected
to
improvements.
We
will
get
is
from
60
to
65
percent
of
faster
loading
when
you
start
the
app.
So
when
you
touch
on
the
icon
and
then
when
you
get
the
first
screen,
we
also
would
like
to
thank
use.
The
community
we
have
two
bounties.
Now
one
is
already
merged.
That
is
blank
out
up
preview
screen.
E
So
when
you
switch
you
up
between
others,
you
can
set
the
mood
that
your
preview
screen
will
be
x3
blank.
So,
for
example,
if
you
on
on
the
wall
screen,
nobody
will
see
your
whatever
bullet
balance.
Oh
I,
don't
know
some
secret
chart
that
you
don't
want
to
reveal
and
another
pure
is
a
biometric
authentication
to
login
to
the
app.
So
it's
only
for
logging
in,
but
still
it's
a
huge
sure
thing.
It's
still
at
least
it
today.
E
It's
been
tested
and
I
hope
that
will
be
merge
soon,
so
not
in
the
upcoming
release,
but
probably
one
more
release.
You
will
get
this
touch
ID
to
to
login,
hopefully
also
I
need
to
mention
that
we're
working
on
reproducible,
Android
builds
and,
as
you
see,
we
still
like
ot
use
all
the
space
on
the
slide,
but
it's
not
in
the
soil,
but
I
will
mention
it
anyway.
We
also
have
the
two-pane
UI
for
mobile
app.
That
again
is
still
deep.
It's
for
bigger
screens
and
for
landscape
mode.
F
So
our
team
is
doing
great,
so
custom
tokens
has
been
merged
and
will
be
available
in
the
next
release
and
also
first
part
of
in
ask
users.
Names
is
on
review
on
the
work
student,
progress
and
performance
improvements
in
wallet
has
been
merged
as
well,
and
we
continue
to
work
on
wallet,
improvements
and
the
performance
and
improving
the
transaction
history
and.
A
F
All
scream,
so
we
have
a
new
item
in
manage
assets.
You
can
add
custom
token,
so
you
can
go
to
either
scan
and
find
you're
talking.
You
want
to
add,
and
next
you
can
copy
the
contract
address
and
paste
it
in
status.
If
you
have
balance,
you
can
see
your
balance
and
you
can
use
it
as
the
regular
default
default
tokens
instead,
as
you
can
send
it
in
wallet
and.
F
F
A
G
Yeah
now
it's
me
so
I'm
gonna
walk
you
through
a
few
through
some
updates
that
are
still
in
progress
and
they're
gonna
be
implemented
soon.
So,
first
of
all
is
the
new
onboarding
flow.
We
changed
and
improved
your
onboarding
a
lot
starting
from
the
beginning,
where
we
show
the
value
proposition.
These
are
the
screens
and
the
next
slide.
Please
then
we
changed
the
instead
of
asking
users
for
entering
their
passwords
or
something
else.
We've
decided
to
be
more
interesting
into
in
telling
the
story
of
how
to
set
up
your
account.
G
So
first
we
asked
to
generate
a
key
and
then
to
to
choose
one
of
from
one
of
the
five
available
options
of
a
key
in
name
so
that
just
giving
a
bit
of
a
context
before
we
just
we
were
giving
out
names
to
people
without
them
having
a
choice.
Actually
now
we
have
so
I
have
different
options
to
choose
from
next
slide.
Please
after
you
got
a
name,
you
can
now
choose
where
you
can,
where
you
wish
to
store
your
key
and
since
now
there's
the
key
card.
G
We
have
key
card
as
an
option
and
then
you
include
your
key
and
the
next
slide,
please
speaking
of
the
key
card.
Now
it's
part
of
the
onboarding
also
when
we
created
the
whole
flow
for
setting
it
up
once
you
first
use
it
on
the
next
slide.
Please
and
we
redesigned
the
backing
of
the
receipt
phrase
process
a
little
bit
so
that
it's
gonna
be
much
more
easy
to
back
it
up
and
then
confirm
that
and
stir
instead
of
writing
down
instead
of
typing.
A
F
So
a
frigate
progressed
a
little
a
network,
we're
now
in
this
state
that
it's
it's
pretty
much
finalized
in
a
sense
that
we
most
positive
people
are
not
and
could
go
live.
If
we
we
wanted.
You
know
what
we're
doing
is
really
rng
on
the
different
aspects,
to
really
take
it
to
the
next
level
and,
namely
in
terms
of
scaling,
the
privacy
part
and
also
phyllis
transactions
for
modest.
F
What
I'm
focusing
right
now,
it's
really
on
the
Phyllis
transaction,
so
buyers
can
use
the
used
application
without
having
a
crypto
initially
and
also
we
know
that
will
move
for
the
confidential
transactions
for
for
users
that
might
want
to
do
particular
transactions
that
way
and
for
the
next
slides
for
the
liquid
funding.
We'll
set
it's
very
good
progress,
so
we
created
this
new
application.
It's
a
command
line
tap
with
this
sort
of
like
hold
schooled
menus,
and
you
can
use
this
step
right
now.
It's
it's!
A
H
So
this
this
farm
has
been
in
a
lower
priority
this
week,
but
I've
been
doing
the
research
on
identity
in
public
profile
to
the
delegates,
so
the
delegates
would
be
able
to
list
their
their
profile
in
their
curriculum
to
other
people
too.
To
note
so
the
people
can
know
that
they
are
willing
to
be
delegates
and-
and
this
public
profile
can
be
probably
useful
for
other
applications,
because
I'm
trying
to
build
it
up
up
inside
of
ENS
in
DNS,
usernames
and
and
yeah.
That's,
that's
it!
The
research
for
for
this
week.
I
Everyone
so
this
last
few
weeks
we
have
been
working
on
integrating
non-viable
date
sink
into
the
console
client.
The
rough
set
up
works,
there's
a
few
bugs
that
have
to
be
fixed
in
console
client
before
we
can
be
sure
they're
works
actually
intend,
but
this
is
using
sort
of
whisper
and
our
existing
protocol,
so
it's
actually
integrated
intent,
as
part
of
that
is
all
sort
of
moving
the
protocol
internet.
I
So
you
use
new
to
fan
deceptive
technologies,
and
then
you
have
a
real
lair
for
sending
it
out
into
actual
intent
and
so
on.
So
that's
true
concept,
but
it's
also
ties
into
our
general
effort
on
making
status
more
transport
independent.
So
you
have
data
synchronization,
but
then
you
can
switch
out
that
transport
underneath
so
sweep
up
whisper
for
mix
net
or
PSS,
or
this
type
of
mesh
networking.
I
I
It's
not
too
far
off
from
actually
being
useful,
I.
Think
for
us.
Specifically,
one
thing
is
being
able,
because
we've
had
this
issue
where
we're
abusing
gate
notes
a
lot
of
stuff
or
we
have
problems
with
batteries
and
so
on
so
trying
to
sort
of
take
the
light
client
concept,
but
but
spending
more
effort
on
it
and
also
turning
it
into
sometimes
more,
like
maybe
adaptive
nodes,
which
is
not
the
gateway
and
it's
not
at
all
something
in
between
and
something
that
adapts
your
resources.
So
maybe
you
you
don't
want
to
sing
stuff.
I
While
you
are
in
Fiji,
but
one
of
you
Wi-Fi,
you
want
to
do
it
and
maybe
on
desktop.
You
can
be
a
bit
more
useful
and
so
on
and
it's
kind
of
a
very
general
problem,
and
it
should
really
be
our
core
competency.
Considering
most
people
don't
spend
all
of
time
on
this
and
we
are
so
mobile
at
them.
This
is
really
our
problem,
so
we're
looking
into
working
more
closely
with
with
the
swim
team,
also
making
this
happen
as
I
sort
of
swim
like
client
or
adapter
client,
but
after
node.
I
So
that's
something!
That's
gonna
come
over
the
next
few
months,
most
likely
I
guess
in
conjunction
with
that.
We've
also
been
doing
a
bit
of
preliminary
planning
planning
on
how
to
get
nimbus
into
the
app,
and
this
would
be
one
such
opportunity.
We
would
really
have
self
control
and
can
iterate
quickly
and
sort
of
have
the
whole
adaptive
node.
So
if
there's
a
general
thing
that
exists
in
the
app
and
as
well
as
on
desktop-
and
these
are
the
things
as
some
more
on
that
later
yeah
I-
think
that's
it.
I
J
Everybody,
so
this
is
also
moving
along
nicely.
I,
don't
have
quite
the
screen
share
skills
that
Android
does
to
show
you
where
we
are,
but
you
can
don't
check
outs.
The
first
version
on
da
PPS
we've
been
working
over
the
last
two
weeks
to
implement
the
smart
contract
functionality
and
next
sort
of
you
know
actually
give
users
the
ability
to
vote
with
asnt
that
is
moving
along.
We've
got.
You
know
some
minor
issues,
along
with
some
other
teams
around
caching
content
in
IP
FST's.
J
Certainly
before
the
end
of
q2,
like
Nabil
mentioned,
everything
is
looking
good.
Most
of
the
work
has
been
done.
It's
just
behind
the
scenes
stuff
that
is
still
required
and
should
be
done
this
week
and
then
we've
just
got
sort
of
final
audits
and
some
testing
still
to
do
so.
It's
looking
good
and
there
should
be
a
series
of
blog
posts
coming
out
detailing
exactly
how
the
curve
works
in
tandem
with
other
S&T
use
cases.
That
Cory
was
talking
about
so
yeah
and
everything
is
looking
good
in
the
swarm.
A
K
So
really
intrepid
to
talk.
We
were
in
testing
until
last
week
and
it
came
out
that
the
ipfs
gate
we
were
using
was
not
reliable
enough
for
this
particular
feature
and
since
swarm
has
fixed
the
bug
with
feeds,
we're
going
back
to
that.
So
in
the
next
days,
I
will
push
up
here
too,
to
make
use
of
swarm,
and
since
we
are
not
sure,
with
these
distributed
file
systems,
if
we
can
rely
run
on
percent
on
it,
we
are
going
to
go
back
to
the
initial
contract
solution
that
we
had
as
well.
K
So
basically
we're
going
to
make
a
hybrid
where
for
free
people
can
use
tribute
to
talk,
but
there
will
be
this
slight
chance
that
other
users
won't
see
that
they
are
free
to
talk
set,
so
they
will
not
be
paid
for
talking,
but
if
they
are
willing
to
pay
and
have
unchained
contract,
that
say
they
are
using
tribute
talk.
Then
they
can
have
100%
reliability
on
the
future
and
yeah.
So
that's
pretty
much
it
for
now.
A
Okay,
thanks
and
I
believe
that
was
our
last
update.
So
now
we're
gonna
jump
into
some
Q&A.
All
questions
were
submitted
from
the
status
group
status,
s
town
hall,
questions
so
the
first
one.
This
question
was:
is
status
and
talks
with
any
phone
providers.
Also,
could
you
save
more
on
the
major
partnership,
so
I
guess
answers
questions
status
and
talks
within
phone
for
a
little
bit.
I.
Don't.
L
A
A
C
Okay,
I
can
talk
with
them
to
make
it
so
much
I
mean
as
far
as
I
know,
it's
not
like
a
big
partnership.
Basically,
we
were
looking
to
work
with
them
to
use
dye
in
the
telling
network.
So
it's
not
like
it.
It's
not
a
huge
partnership.
Type
thing
it's
just
because
one
of
the
you
know
big
utilities
of
the
telling
our
cause
is
store
value
and
some
develop
specific
developing
markets.
C
L
So
like
the
telenet
work
is
really
targeting
remittance
and
there's
a
many
transactions
globally.
Internationally
are
essentially
sending
money
back
and
forth
between
families
and
having
their
label
currency.
To
do
that
in
would
be
hugely
beneficial
for
for
people
in
the
in
countries.
Far
away
so
yeah.
A
L
Mean
the
way
the
way
to
get
like
real
privacy
as
far
as
like
transactions
go
and
in
the
wallet
there's
two
things
that
we're
working
on
at
the
moment.
One
is
we're
working
on
this
multi
account
stuff
within
the
wallet,
so
you'll
be
able
to
spin
up
new
addresses
as
much
as
you
like,
as
well
as
custom,
derivations
and
even
import
other
keys.
L
In
addition
to
that,
like
we're,
looking
at
things
like
the
Aztec
protocol-
and
you
know,
mixing
services
that
are
on
chain
to
to
alleviate
that
I,
don't
know
if
tributed
talk
itself
gives
you
a
basic
will
at
privacy,
but
in
like
the
upcoming
versions
of
status.
The
your
public
key
that
you
use
for
chatting
and
the
address
that
you
use
for
transacting
will
be
different
in
the
future.
We
also
have
some
other
plans,
but
stay
tuned
for
that.
H
Regarding
privacy,
the
best
solution
probably
is
to
have
this
separation
of
identities.
Just
what
Jarrod
maintenance
users
have
to
have
a
separate
quality
while
it
in
a
separate
shot
regarding
people
to
talk
I
see
that
this
is
a
concern
in
area
is
also
working
a
lot
to
doesn't
expose
users
in
privacy.
H
That's
why
we
are
trying
to
use
swarm
or
ETFs
to
start
the
payment
information,
but
also
when
we
have
the
separation
of
the
shots
in
the
wallet
we
probably
would
be
able
to
implement
in
a
way
that
users
page
from
wallets
Chu
all--it
and
they
in
a
shot
in
other
identities.
So
it's
it's
not
really
connected
this.
This
contact
list
to
the
payment,
as
you
mention
it,
but
of
course
this
doesn't
solves
the
the
privacy
concern
fully.
H
That's
that
we
only
happens
when,
when
we
have
mixers
implemented
in
users,
can
like
laundry
their
history
to
not
be
able
to
be
traced,
leave
mark.
So
yet
that's
the
plain
Church
to
have
it,
but
we
are
not
starting
with
it.
We
are
just
like
using
to
boo
to
talk
to
look
like
as
a
regular
tea
transfer.
So
you
cannot
tell
that
that
user
paid
a
tribute
out.
H
A
L
That's
it
yeah
I
mean
like
I,
think
Reich
is
in
in
terms
of
how
we're
actually
evolving.
Beyond
the
chaos
I
mean
you
guys
do
make
sense
in
certain
certain
situations,
but
I
think
we're
getting
a
lot
more
visibility
into
our
timelines
with
things
like
Reich
and
we're
certainly
gonna
be
able
to
iterate
on
that
and
learn
from
our
learn
from
our
past
mistakes.
Even
more
so
so.
Yeah.