►
From YouTube: Status Townhall - July 2nd, 2018
Description
General
0:40 - Intro
1:18 - Ascending into the Blockchain
5:09 - Layer 0 - Culture & Network Thinking
7:12 - Layer 1 - Communication
7:50 - Layer 2 - Identity & Voting
8:10 - Layer 3 - Proposals & Funding
11:13 - Layer 4 - Soft Governance
12:58 - Layer 5 - Profit from Knowledge
14:07 - Layer 6 - Dashboards
Non-Tech Updates
16:10 - Core-contributors
16:50 - Q3 OKR's Voting
19:34 - People Ops
22:35 - Marketing update
32:37 - Hack Week
34:55 - Status Incubate update
UX/UXR
38:44 - Design System
Core Swarms
40:53 - Core Goal: Beta Launched
42:00 - Core Goal: 1.0
43:14 - #83-energy-efficient
Infra & Tooling
45:09 - Infrastructure automation
46:47 - #280-disc-mail-servers
47:34 - P2P Initiatives
Chat
49:45 - #99-confidence
Wallet & Account
52:15 - #151-ens-usernames
53:20 - #170-wallet-improvements
DApps & Developers
54:32 - DApps & Developers
Research Update
56:47 - ECDC
Desktop
58:36 - Desktop update
Embark
1:00:10 - Embark
Q&A
1:02:45 - Q&A
Slides can be found here - bit.ly/status-th12
- 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!
- In this Townhall Jarrad covers over some of his thoughts on Status becoming a DAO, updates to UX - tooling and beta, and desktop progress.
Any other questions please leave a comment or join our chat - https://chat.status.im
A
B
C
D
Have
first
up
happy
beta?
Congratulations!
Everyone!
Thank
you!
So
much
for
putting
in
so
much
work.
The
release
is
absolutely
amazing
and
it's
so
good
that
we
feel
comfortable
being
on
main
from
here
like.
Hopefully,
we
can
start
adding
more
functionality
and
getting
some
performance
up
and
really
looking
forward
to
the
sort
of
exciting
progress
that
will
be
coming
up
in
the
next
few
months
and
years.
D
D
The
question
is
like
why.
Why
would
we
do
this?
In
fact,
I
think
status
probably
has
one
of
the
the
best
sort
of
use
cases
for
doing
this,
set
the
moments,
and
it's
largely
due
to
Brazilians
doing
a
decentralized
communication
platform
that
also
allows
you
to
send
value
in
a
completely
translucent
and
civilus
way
is
probably
going
to
annoy
some
people
further
down
the
line.
Oh,
if
someone
can
Amazon
again
and.
D
Yes,
so
so,
basically,
if
we
can
move
everything
into
the
blockchain,
then
we're
a
lot
more
resilience
and
the
organization
continue
to
perpetuate
itself,
regardless
of
our
involvement.
You
can
even
imagine
it
one
day,
maybe
in
ten
or
twenty
years
time,
where
it's
been
entirely
driven
by
the
community
and
people
who
are
actually
using
this
software
allows
us
to
do
things
like
permissionless
participation,
so
anyone
can
access
get
into
it.
We
can
do
organisational
oversight,
so
there's
lot
more.
Transparency
involved
and
just
like
I
said,
market
directed.
D
So
you
know
it's
been
two
years
now,
I
think
we
haven't
really
seen
large
instantiations
of
doubt
like
structures
anymore
because
of
this
events,
but
now
we
have
a
lot
more
mature
tooling.
We
have
a
lot
of
knowledge.
We've
learnt
a
lot
from
that
events
and
we
can
do
it
in
a
much
more
sort
of
modular
and
sort
of
a
controlled
way
and
I
mean
we
can
control
the
capital
flow
when
the
Dow.
Basically
there
was
capital
flowing
everywhere.
I
mean
we'll
just
take
some
baby
steps
with
this
sort
of
thing.
D
So
basically,
this
I
think
was
probably
roughly
seven
or
so
layers
to
implementing
this,
and
this
is
starts
off
all
with
culture.
But
then
we'd
like
to
look
at
communication.
We
can
identify
proposals,
this
idea
of
soft
governance
profiting
from
knowledge
and
ultimately,
just
dashboards
and
views
them.
This
is
a
sort
of
network
data
structure
that
we
create
so
starting
on
the
the
bottom
layer.
D
This
kind
of
relies
on
subscribing
to
this
sort
of
dissented
theory
of
governance,
where
you
view
individual
actors
as
having
sets
of
sets
of
own
beliefs
and
the
practice
of
States
as
a
cultural
practice,
and
this
is
basically
different
actors
forming
a
narrative
and
establishing
traditions
and
customs,
and
this
kind
of
thing
so
getting
culture
from
the
very
beginning.
Rights
is
a
huge.
Well.
D
You
know
transparency,
facilitating
deeper
personal
connections,
keeping
people
self
directive
being
active
in
inclusivity,
trying
to
grow
their
network
and
bring
people
in
is
really
important
and
on
the
next
slide,
I
would
like
to
talk
about
sort
of
pipes,
and
so
I
think,
what's
really
important
to
kind
of
grapple
here
is
this
idea
of
network
thinking
basically
community
is
is
in
our
case
is
synonymous
with
organization.
It's
not
really
a
separate
thing.
There
is
no
external
versus
internal
in.
D
We
should
be
bringing
more
people
into
the
network
to
see
a
grow.
This
graph
that
you
see
here
is
a
weighted
graph
in
terms
of
public
communication
within
the
slack
Channel,
and
you
can
kind
of
view
our
community
as
all
the
core
contributors
at
the
moments,
and
there
isn't
too
many
people
outside
of
that.
Unfortunately,
so
this
is
something
that
we
really
need
to
start
working
on,
but
this
is
also
a
preview
into
what
the
user
interface
may
look
like
for
managing
the
status
down
in
the
future.
D
The
next
layer
is
communication,
and
this
is
pretty
much
what
the
last
year
year
or
two
years
have
been
all
about,
basically
to
continue
to
function
at
minimum.
We
need
to
be
able
to
communicate
just
coordinate,
and
we
have
to
do
so
with
the
assumption
of
a
hostile
environment,
which
is
why
we're
doing
it
in
the
trustless
that
peer-to-peer
way
you
know,
chat
with
our
mobile
and
desktop.
It's
really
important,
but
we
also
think
you
think
about
blogging
and
forums
as
alternatives
as
well.
D
On
top
of
this,
we
also
need
to
create
like
identity
invoicing.
Basically,
you
can't
really
do
really
good
voting
without
having
some
kind
of
proof
of
individuality
and
there's
a
couple
of
different
ways.
We
can
go
about
that
a
lot
of
its
basically
research
topics,
but
I
won't
go
into
it
now,
just
for
time
sake,
layer,
three.
This
is
probably
the
the
most
sort
of
dramatic
thing
that
we're
doing,
and
it's
largely
inspired
by
givethe
idea
of
liquid
pledging.
D
It
also
allows
people
to
create
there
are
only
good
pledges
anytime
and
get
a
fulfill
them,
and-
and
we
can
imagine
that
there
is
an
entirely
different
funding
hierarchy
for
status
speeches-
that's
not
even
done
by
our
our
core
contributor
team.
You
can
imagine.
This
also
creates
an
org
chart,
but
it's
kind
of
like
a
buffet
of
different
functions
and
tasks
that
you
could
essentially
get
paid
or
rewarded
for
fulfilling.
D
So
yeah
this
is
the
like.
I
said
liquid.
Pledging
is
kind
of
like
a
wallet.
You
have
some
funders
who
can
pledge
funds
into
it
to
show
their
intense,
so
you
could
imagine
like
someone
proposing
activity
and
some
people
with
capital
can
can
basically
go
okay,
yeah.
This
is
a
good
idea.
They
can
put
funds
in
there
and
then
they
can
veto
rights
any
requests
on
their
own
personal
funds.
D
Anyone
can
request,
of
course,
at
any
time,
and
they
can
be
auto-filled
if
they're
not
vetoed
are
for
a
certain
period
of
time
and
funds
can
actually
be
delegated
to
different
people
in
in
this
as
well
to
then
pass
on
those
delegations.
So
you
can
create
delegation
chains
of
funds
and
basically
do
a
sort
of
direct
democracy
like
thing,
but
with
actual
value,
in
our
case,
we'll
probably
attach
a
liquid
pledge
to
a
particular
chat
topic.
D
With
voting
again
like
with
these
liquid
pledges
that
have
chats,
we
can
also
add
attach
a
voting
mechanism
to
that.
So
we
can
actually
change
the
logic
in
terms
of
how
people
request
funds
and
who
they
get
to.
So
you
can
imagine
offloading
this
to
the
community
as
opposed
to
eating
and
like
a
delegate
person,
so
in
say,
for
example,
maybe
not
so
this
iteration
of
okay,
ours,
but
the
next
iteration
of
our
chaos.
D
Now,
which
is
this
one?
So
sleep
are.
These
are
mostly
just
primitives.
They
don't
really
do
too
much
on
their
own
and
this
and
it
basically
modular
and
their
finite,
so
we
can
basically
cancel
them
at
any
time.
We
don't
have
to
worry
about
sort
of
runaway
funds
like
we're
not
going
to
be
committing
capital
into
this
in
large
quantities
to
start
with,
and
it
will
be
entirely
politic
and
voluntary
to
participate
and
testing
these
ideas.
D
But
what
this
sort
of
Dow
will
be
mostly
doing
at
least
my
initial
ideas
on
this
is
doing
a
sort
of
government
like
procurement
process,
so
you
can
mention
like
we.
We
initially
put
a
liquid
pledge
out
there
for
our
final
request
for
information,
and
then
we
basically
pay
people
to
provide
more
information.
Then
we
can
do
a
request
for
proposals.
D
After
that
we
can
publish
this
information
and
let
our
people
pay
people
to
provide
us
proposals,
and
then
we
can
do
an
RFT,
so
people
can
actually
start
providing
solutions
based
on
those
kinds
of
proposals.
Of
course,
the
the
information
in
proposals
is
just
guidelines.
I
mean
the
attenders
solutions
could
be.
It
could
be
anything
as
long,
but
it's
just
a
different
way
of
getting
informations.
So
you
can
imagine
this
being
really
useful
for
okay
ask.
Well
maybe
we
have
like
a
multi-step
request
for
information
process.
D
First
were
like
getting
ideas
of
things.
We
should
focus
on
from
the
community
and
they
can
get
paid
for
that
and
then
maybe
we
we've
trying
to
filter
that
down
into
into
actual
quantitative
objectives
and
the
people
who
facilitate
that
or
incentivize
to
do
so,
because
we'll
also
pay
them
to
do
that
so
yeah
another
layer
is
doing
a
prediction
market
or
profit
from
knowledge.
So
you
could
imagine
we
could
use
something
like
or
go
or
gnosis
on.
On
top
of
this
to
basically
allow
competition
over.
D
Request
fulfillments,
so
you
could
imagine
that
testers
who
are
paid
to
test
against
a
particular
swarm
feature,
and
they
see
it's
not
going
so
well.
Maybe
they
can
actually
been
against
the
developers
in
terms
of
their
ability
to
get
their
funding
requests
made
and
they'll
have
to
adjust
it
to
a
more
sensible
level
and
vice
versa,
so
the
developers
could
potentially
bet
against
testers,
but
even
more
broadly,
you
can
even
imagine
traders
getting
involved
and
being
able
to
become
basically
play
against
our
execution
performance
organization-wide.
D
So
for
anybody
wanting
the
overview
of
the
organization
could
look
at
these
different
modules
and
just
see
how
well
that's
performing
based
on
the
games
are
being
played,
which
would
be
really
interesting
and
the
the
final
layer
is
basically
dashboards,
and
how
do
we
actually
present
all
this
information
that
to
the
to
the
user
or
to
anyone,
who's
still
apply?
Have
oversight
of
the
organization?
D
It'll,
probably
adapt
insights
that
itself
I.
Imagine
there'll,
be
a
large
network
visualization
components
this,
because
it's
really
useful
for
finding
communication
lines
between
people.
Finding
well
areas
of
activity,
you'll
be
able
to
identify
funding
dependencies
and
you'll.
Also.
Will
also
make
it
so
you
can
color
these
things,
so
we
can
actually
create
quote-unquote
teams
through
essentially
a
cosmetic
grouping
of
nodes,
but
that
wouldn't
actually
have
any
functional
value.
It's
just
good
with
reasonability.
D
You
can
imagine
that
we
have
like
a
specific
system,
maybe,
like
all
of
these
things
are
tags
and
if
you're
an
interesting
people
lot
so
you're
on
the
communication,
stuff
you'll
be
able
to
filter
out
those
things
and
then
even
maybe
like
a
minimum
maximum
earning
potential
that
you
could
filter
out.
So
you
could.
You
could
literally
change
this
network
topology
to
and
view
to
what's
relevant
to
you
and
get
a
very
quick
oversight
over
everything
happening
and
here's
it.
For
me
also.
B
D
B
B
We
also
have,
as
usual,
is
still
around
20
open
rules
and
yet
particularly
on
the
design
agency,
we're
still
hiring
I,
think
five
there
and
on
incubate
we're
now
we'll
have
an
update
later,
but
anyway,
so
check
out
the
referral
program
still
they're,
following
up
from
kind
of
Jared's
comments
earlier
about
creating
a
voting
mechanism
in
the
doubt.
So
as
part
of
our
two
three
okay
ours,
we
have
I
would
say
one
of
the
first
in
associations
of
being
able
to
use
as
NT
as
a
utility
inside
the
application.
B
This
is
on
the
right.
You
can
see
kind
of
like
our
boasting
DAP.
The
URL
is
still
being
where
there's
still
a
couple
of
iterations
left,
so
hopefully,
by
tomorrow,
we'll
have
a
URL
we
can
share
with
everyone.
That's
going
to
be
on
main
net.
Basically,
how
it
works
is,
if
you're
holding
SNT
in
the
in
your
status
wallet,
you
can
vote
so
you
can
add
a
proposal.
Whatever
your
idea
is
alright
for
any
new
features
that
you
think
would
be
useful.
B
Anyone
else
can
then
go
in
look
at
those
ideas
and
then
vote
using
Narus
NT.
So
you
take
a
copy
of
the
amount
of
S&T
you
have
so,
let's
say,
for
example,
I
have
a
hundred
SNT
in
my
wallet
I.
Can
it
take,
makes
a
copy
of
that
hundred
and
I
can
use
that
too
vote
for
whichever
feature
that
I
want
to
to
be
built
into
three.
We
use
quadratic
voting,
so
you
can
see
you
know
if
I
have
a
hundred
SMT
I
get
ten
votes
and
so
on
and
so
forth.
B
This
will
be
open
for
the
next
week
and
we'll
kind
of
try
and
get
as
many
people
to
engage
to
add
features
to
vote
and
then
next
Monday
we
can
figure
out
what
this
looks
like
and
integrate
that
into.
As
kind
of
the
key
part
or
the
core
part
of
our
team,
okay,
ours
so
yeah-
this
is
this-
is
very
exciting
great
work
to
to
Barry
and
Richard,
who
have
been
hammering
on
this
for
the
past
week,
and
you
know
I
was
playing
around
with
it
even
this
morning
and
it's
pretty
much
ready
to
go.
B
You
can
put
it
on
maintenance
to
a
couple
of
things.
The
one
thing
I'd
kind
of
point
out
to
all
the
teams
is
that,
based
on,
we
have
a
feature
request
section.
That's
in
me
need
help
inside
the
app
and
right
now,
like
our
number
one,
most
popular
feature
is
being
able
to
send
images
and
number
two
is
logging
in
with
touch
ID
or
face
ID.
E
Hi,
this
is
Kerry,
giving
you
a
people
up,
updates.
We've
heard
a
lot
about
it
already
on
this
call,
and
it's
okay
our
time.
So
what
we
wanted
to
do
with
this
section
is
really
just
to
give
you
a
sneak
preview
of
the
kind
of
things
that
we're
focusing
on
in
the
next
quarter.
In
q2,
we
really
were
looking
at
the
basic
so
being
responsive,
creating
documentation,
those
kind
of
foundational
things
and
beyond
that
we
there
are
so
many
more
things
that
we
need
to
get
right.
E
We
want
to
just
make
sure
that
we
create
as
smooth
and
experience
as
possible
for
all
of
the
team
members
working
here.
We
also
have
some
big
questions
that
we
want
to
answer.
We
know
that
we're
aiming
to
be
a
decentralized
autonomous
organization.
How
do
we
do
that,
whilst
also
supporting
the
people
that
work
within
it,
so
project
flattened,
is
looking
at?
The
idea
of
people
leaves
like
what
would
be
alternative
so
that
how
can
we
support
people
without
relying
on
traditional
people
management?
The
second
is
compensation
structure.
E
So
how
do
we
create
a
fair,
transparent,
equitable
way
of
paying
people
and
determining
pay
rises?
We
want
to
really
improve
our
onboarding
so
that
it's
not
just
kind
of
like
a
functional
information
sharing
experience,
but
for
new
joiners,
really
a
chance
for
us
to
impart
the
culture
and
add
delight
performance
management
is
some
kind
of
dry,
but
for
us
is
really
important,
and
it's
about
increasing
the
flow
of
feedback
amongst
peers.
E
More
guidelines,
I
think
documentation
and
sounds
boring,
but
we
found
it's
really
helpful
to
answer
commonly
asked
questions
and
we're
adding
to
that
all
the
time.
So,
if
you
see
anything
that
we
haven't
documented,
that
you
think
is
really
poor
and
let
us
know
and
we'll
link
to
that
in
our
people
up
site.
E
I
know
this
has
been
said
already,
but
I
just
want
to
say
it
again.
We
are
so
lucky
to
have
such
fantastic
people
here
in
the
organization
and
the
wider
community
as
one
so
I'm.
Just
really
a
shout
out,
I
know
that
you
all
have
put
so
much
energy,
enthusiasm
and
passion
into
the
beta
launch,
and
it
was
just
really
awesome
to
see
all
around
and,
lastly,
a
really
boring
one.
E
But
this
is
the
expenses
and
if
you
wouldn't
mind,
if
possible,
please
can
you
group
your
expenses
up
to
de
minimis
of
50
US
dollars
before
submitting
that
really
helps
finance
because
they
have
to
process
each
transaction
individually
if
it's
not
possible
for
cash
flow
reasons,
no
big
deal
but
I'm,
just
something
that
would
really
help
our
finance
team
out.
So
if
you
can
do
that,
that
would
be
great.
Thank
you.
Awesome.
B
C
Just
really
quickly
high-level
going
through
some
of
the
ongoing
things
we
have
our
Tech
Talks
in
progress
team
updates.
We
have
four
series
going
on
right
now
that
are
in
creation,
whisper,
UX
design
and
research
and
people
ops
and
then,
of
course,
our
usual
call
for
content,
because
we
really
want
to
make
sure
that
we
are
capturing
the
content
that
really
will
resonate
within
the
community
from
our
devs
and
from
community
members.
So
it's
our
usual
call
for
content.
C
Please
bubble
up
anything
that,
from
the
tech
side,
might
be
noteworthy
state
of
us
campaign
again
that
is
launching
this
month
with
a
lot
of
fun.
Think
on
community
competitions,
infographics
our
podcast
is
gonna
launch.
We
have
some
great
guests.
We
have
Jared
and
Carl
as
the
first
one
for
the
kickoff
we're
going
to
be
talking
to
Hester
and
Patrick
on
the
UX
research
side,
and
then
we
also
have
a
Glenn.
While
author
of
radical
markets,
all
interviewed
by
our
own
crypto
under
Andy,
Ted,
hope
Sean
I,
let
you
take
advocacy
cool.
F
So
we're
just
working
through
that.
Aside
from
that,
we've
got
yeah.
Kim
just
said
the
community
competition
which
is
tied
to
the
state
of
us
the
campaign,
and
you
know
that
one
should
be
kicking
off
in
the
next
24
hours.
Oh,
please
so
keep
your
eye
out
for
that.
It's
really
exciting
and
then
local
channel
launches
so
going
further.
F
Where
we're
looking
to
try
and
launch
a
Spanish
speaking
channel
off
the
back
of
f
Boris
Aires
and
all
the
interest
that
we've
seen
from
the
community,
the
spanish-speaking
community,
we're
building
out
a
plan
of
how
we
can
launch
dedicated
spanish-speaking
channels
and
Eduardo's
doing
a
great
job
on
that
that
should
be
coming
in
the
next
week
or
so.
And
then
the
last
piece
is
the
the
content
creator
series,
so
we're
actually,
as
part
of
the
beta
we're
actually
working
with
I'm,
actually
proud
to
say.
F
We
work
with
creators,
content
creators
across
multiple
languages
to
actually
unpack
the
beta,
further
and
kind
of
tell
an
interesting
narrative
whether
it's
on
you
know
the
road
to
beta,
or
you
know,
even
just
just
for
for
some
of
the
markets,
that
we
don't
produce
a
lot
of
content
for
non-english
speaking
markets
being
able
to
go
into
more
depth.
On
kind
of
you
know
what
what
is
the
latest?
The
latest
update
yeah.
C
F
Cool
I'll
keep
going
then
so.
Yes,
this
is
just
something
that
we
want
to
try
and
do
more
often
now
as
part
of
this
process.
So
looking
back
at
the
content
over
the
past
fortnight
and
comparing
it
to
the
previous
fortnight,
so
we
have
a
gauge
of
how
our
content
has
performed.
So
you
know
with
the
last
fortnight,
we
obviously
saw
a
lot
of
momentum
behind
the
behind
the
beta.
F
But
what
was
actually
really
interesting
was
is
that
the
total
impressions
for
fortnight
decreased
by
15%,
but
what
we
did
see
was
we
saw
a
pretty
substantial
increase
in
overall
engagements
and
our
actual
total
following
grew
by
doubled.
Actually
what
the
growth
was
of
the
previous
of
the
previous
reporting
period,
so
in
terms
of
looking
at
looking
into
a
deeper
in
terms
of
the
balance
between
impressions
versus
engagements,
that
kind
of
comes
down
to
Kim
might
go
to
the
next
slide
kind
of
comes
down
to
a
focus
on.
F
You
know
trying
to
be
I
guess
with
the
beta
trying
to
be
a
bit
more
focused
on
the
grassroots
and
the
community,
and
you
know
really
test
it
out
and
and
and
not
go
big
with
a
PR
kind
of
announced
in
the
previous
reporting
period.
You
know
we
had
the
announces
around
our
us
joining
the
ECF
and
obviously
crypto
strikers,
which
got
a
bit
of
a
bit
of
press.
F
So
what
we
did
see
with
that
was
was
an
increase
in
in
overall
impressions,
but
when
you
move
below
that,
in
terms
of,
if
you
consider
impressions
to
be
a
vanity
metric,
if
you
move
below
that,
you
actually
look
at
engagements.
What
we
actually
saw
was
we
saw
a
pretty
substantial
volume
of
actually
people
talking
about
status
and,
while
the
total
mentions
increased
by
a
hundred
and
twenty
one
percent
based
on
the
previous
fortnight's,
we
actually
saw
the
volume
of
mentions
on
Twitter
increased
by
two
hundred
and
thirty
five
percent
based
on
the
previous
fortnight.
F
C
So,
for
a
top
performing
content
we
have
been
doing
is
bucketing
our
content
into
three
content
pillars.
The
first
one
is
really
for
sort
of
the
non
techie
audience.
It
requires
little
to
no
understanding
of
aetherium.
This
would
be
sort
of
release,
notes
and
general
updates
bucket
two
requires
that
minimal
understanding
of
aetherium
and
then
bucket
three
requires
experience
as
develop
as
a
developer,
so
much
more
highly
technical
content.
So
our
top
performing
content.
We
had
obviously
the
beta
release
announcement
on
Twitter,
with
156
thousand
plus
impressions
and
1700
total
engagements.
C
That
was
not
surprising,
I
think
we
were
expecting
the
beta
release
sweet
to
to
get
to
perform
that
well.
The
second
top-performing
was
the
release
of
our
UI
video
for
beta,
which
again
I
think
was
not
a
surprise
that
I
think
was
well
received
by
the
community.
We
have
I
think
almost
1200
likes
on
YouTube
in
the
first
or
views
on
the
first
five
days,
which
is
which
is
not
bad
and
then
in
content.
C
Pillar
to
the
top
performing
content
was
a
piece
we
did
on
custom
boot
notes,
which
I
believe
was
part
of
not
the
beta
release,
but
the
release
prior,
the
O
920,
and
so
that
did
fairly
well
also
with
the
decent
number
of
impressions
and
then
content
pillar
three
are
much
more
technical
audience.
The
top
performing
piece
was
the
embark
Tech
Talk,
which
also
a
decent
amount
of
impressions
and
engagement.
There
next
slide.
C
So
this
is
just
a
quick
look
at
our
email
performance,
and
this
is
again.
This
is
from
last
week
so
just
concentrating
on
the
week
of
the
beta
launch
versus
the
week
prior
and
because
I
think
typically
we're
not
too
heavy
on
the
email
marketing
side
unless
it's
some
sort
of
announcement
or
release
and
we
go
dude
standard
marketing
emails.
C
And
so
just
looking
at
the
beta
release
week,
you
can
see
the
email
performance
we
sent
about
ninety-five
thousand
emails
out
and
so
far
we
have
an
open
rate
of
46
percent,
which
is
pretty
good
overall
and
then
also.
You
can
also
see
the
contacts
by
source
with
the
lifecycle
stage.
This
gets
a
little
tricky
because
it
kind
of
reports
on
what
the
original
contact
was.
C
This
is
our
site
traffic,
and
so
we
had
in
just
the
last
week
we
had
an
increase
45%
in
our
site
traffic
sessions
and
which
was
really
nice
to
see
and
again
I.
Don't
think
it
was
too
terribly
surprising
for
bata,
that's
the
number
of
visitors
to
the
status
site
during
last
week
as
compared
to
the
week.
C
Prior
and
again,
it
was
driven
by
the
beta
launch
and
the
majority
of
the
time
spent
on
the
site
was
on
the
beta
signup
beta
email,
confirmation,
and
so
that
was
again
really
nice
to
see
and
and
one
thing
worth,
I
think
just
throwing
out.
There
is
that
during
our
beta
release,
which
I
think
went
pretty
smoothly
by
everyone,
standards
slack
went
down
and
then
what
was
really
nice
was
that
everybody
instinctively
jumped
over
and
started
communicating
using
the
app.
C
So
we
didn't
even
really
skip
a
beat
with
sort
of
community
coordinating
all
the
communications
and
and
things
around
beta,
which
was
really
nice.
It
was
like,
okay,
slack
us
down
all
right,
let's
jump
into
the
status
app
and
then,
let's
start
communicating
that
way.
So
that
was
actually
a
really
nice
use
case
that
we
lived
our
first
hand
during
the
beta
release.
G
But
it
can
be
an
amazing
opportunity
to
take
a
step
back
and
just
work
on
whatever
we
want.
Hack
weeks
are
useless
and
different
companies
to
drive
new
ideas
have
cross-pollination
between,
like
teams
and
people,
as
well
as
like
exploring
new
opportunities
and
some
hack
weeks,
I've
seen
people
spending
time
like
learning
the
piano
or
doing
art
installations,
but
other
times
people
are
like
scratching
an
itch
so
I
know.
There's
a
lot
of
projects.
G
We've
been
work
with
wanted
to
take
on
over
the
last
few
months,
but
just
haven't
had
the
time,
because
we're
working
on
beta
hack
week
could
be
an
amazing
time
to
like
put
forward
some
ideas
like
recruiter
team
works
best
when
you
haven't
like
work
with
these
people
before,
and
these
ideas
can
come
from
from
anywhere.
So
hopefully,
we'll
see
a
lot
of
submissions
from
the
community,
we'll
see
like
open
bounty
contributors
joining
in
we'll
see,
there's
regular
users
with
like
a
wonderful
idea.
We
might
see
like
blockchain
reinvented.
G
We
might
see
some
new
things
for
S&T
that
we
haven't
thought
of
before.
So
next
steps
is
to
jump
onto
our
forum.
It
discussed
at
status,
diam,
there's
a
thread.
There
suggest
an
idea
find
projects
to
work
on
and
kind
of,
try
to
drive
that
collaboration.
Usually
it
works
by
leading
up
to
it.
Ideas
to
propose
teams
are
formed.
The
first
four
days
of
the
hack
week.
Everyone
gets
hacking
and,
on
the
last
day,
there's
a
type
of
async
presentation
where
we
vote
on
it,
and
so
people
can
either
like
upload
videos
or
slide
decks.
G
Something
like
that
and
we
can
all
like
look
at
a
sink
and
and
vote
and
coming
from
hack
week.
We
might
choose
to
implement
some
ideas
because
they
really
awesome
or
put
some
on
the
roadmap
or
otherwise.
This
is
the
great
opportunity
for
us
to
have
some
fun,
so
yeah
hope
to
see
on
the
forum
awesome.
B
H
Other
things
no
bill,
so
I
guess
I've
got
a
few
updates.
The
first
one
is
with
crypto
strikers,
so
I
guess
most
of
you
would
have
heard.
We've
been
incubating
them
for
over
a
month
now
and
I
just
wanted
to
use
this
opportunity
to
thank
the
people
involved.
There
was
Richard
Johnny,
Hart,
Jason,
Andre,
Julian,
Rachel
and
others
that
really
contributed
to
the
incubation
period
for
crypto
strikers
and
we've
seen
some
great
results
in
terms
of
their
future.
H
We're
going
to
be
continuing
to
support
them
until
the
end
of
World
Cup
and
then
we'll
figure
out
a
road
map
that
sort
of
makes
sense
for
both
of
us,
but,
but
so
far,
has
been
really
great
in
terms
of
the
the
approach
for
incubator
we've
pivoted
from
what
we
originally
thought
we
were
going
to
do.
We
now
are
going
forward
with
a
fully
decentralized
program
and
there's
a
few
reasons.
H
Behind
that
reason,
number
one
would
be
to
ensure
that
what
we're
doing
with
the
incubator
is
in
line
with
our
core
principles
of
decentralization
and
what
that
means
is
that
we
would
no
longer
need
to
pursue
physical
space
and
we'll
start
to
have
a
program,
that's
purely
decentralized
and
purely
remote.
So
there's
pros
and
cons
for
both
I
think
the
pros
outweigh
the
cons.
H
In
this
case,
we
will
be
able
to
accept
people
from
all
over
the
world,
we'll
be
able
to
leverage
off
the
fact
that
we
are
decentralized
organization,
they're
really
good
at
it,
and
so
we
can.
We
can
basically
use
the
existing
model
that
we
have
and
and
incubate
up-and-coming
projects
in
terms
of
the
actual
formal
program
that
will
start,
hopefully
in
October,
2018
and
it'll,
be
a
three-month
program
with
batches
of
about
four
to
five
projects.
H
H
The
next
intake,
however,
between
this
fully
decentralized
program
and
crypto
strikers,
is
sort
of
in
between
intake
of
two
projects.
Unfortunately,
I
can't
announce
what
the
projects
are,
but
they
will
be
public,
hopefully,
in
the
next
couple
of
weeks,
they're
really
really
exciting:
two
very
different
projects
in
two
different
parts
of
the
world,
so
one
thing
that
I
would
ask
for,
though,
is
if
anybody's
interested
in
helping
them.
Please
send
me
a
message.
Volunteers
are
definitely
welcome
and
you
know
the
whole.
H
These
new
projects
are
a
very
early
stage
and
require
health
from
from
all
of
us.
Lastly,
manpower.
We
are
hiring
for
this
incubator
program
in
order
to
ensure
that
we
can
launch
a
program
by
October
and
ensure
that
we
have
a
really
really
solid
decentralized
program.
We
need
to
hire
four
main
positions,
the
first
one
being
the
program
manager,
which
will
facilitate
the
entire
program
for
the
three
months
and
help
with
the
coursework.
H
The
second
is
a
dedicated
marketing
manager
for
status
incubate,
and
this
person
will
also
help
to
set
up
the
marketing
strategies
for
the
individual
projects
that
are
within
the
incubator.
Similarly,
the
design,
the
designer
or
the
UX
contact
would
also
work
with
the
incubator
specifically
and
the
last
one
is
a
research
analyst
where
this
person
will
be
in
charge
of
basically
looking
at
applications,
analyzing
their
gear
hubs
and
also
sourcing
proactively
projects
to
be
included
within
the
incubator.
H
B
I
Sure,
since
the
beta
has
launched,
we
were
currently
working
on
improving
and
just
amazing
the
the
UI
of
the
app
you
can
jump
onto
the
next
slide.
Please
it's
just
a
brief
walkthrough
of
what's
going
on
in
terms
of
the
design
system,
so
we
working
on
you
can
you
can
go
through
the
slides.
You
can
wait
for
five
seconds
and
go
through
them
so
yeah.
This
is
the
color
palette
type,
it's
quite
a
few
of
them
quite
and
color
palette,
psychography,
we're
working
on
refining
our
icon
set
and
making
it
more
yeah,
look
alike,
there's.
I
Finally,
a
link
with
some
basic
brand
s,
that's
available
for
download.
This
is
also
going
to
be
it's
working,
progress
and
going
to
be
improved
and
we're
also
working
on
specifying
and
documents
and
the
components
of
the
app
so
that
they
would
be
less
coupled
together
for
a
solid
structure
and
make
it
easier
to
outsource
some
of
the
design
work.
So
here
are
the
toolbars
and
some
badges
with
the
documentation
of
the
priorities
and
all
the
thrift
stuff
next
slide
the
transaction
messages
next
one
the
commands
and
the
text
input.
I
So
all
of
those
little
parts
now
form
a
unified
system
which
would
approve
the
UI
quality
and
the
basic
flows,
and
also
like
yeah,
a
brief
walkthrough
of
the
currently
the
stuff
that
is
currently
in
progress.
But
the
seamless
login
with
the
face
I
did
touch
ID,
which
was
highly
requested
by
the
community.
We
were
also
working
on
well
improvements
and
chat,
commands
and
yeah,
and
finally,
adding
animations
and
gestures
pretty
much
sooner
and
working
at
a
new
dock
site,
yeah,
that's
pretty
much
it
for
the
design
and
the
UI
UX
or.
Thank
you
awesome.
I
B
G
It's
me
so
a
quick
update
on
core
we've
had
a
big
goal
to
launch
the
beta
and
we've
covered
it
so
far,
but
the
beta
was
released
and
we
saw
a
pretty
nice
spike
in
downloads,
messaging
users
and
transacting
users,
which
is
a
really
good
sign,
and
this
is
a
reminder
for
everyone
that
the
beta
is
main
net
by
default.
We're
gonna
keep
going
with
ongoing
releases.
G
We
aim
for
weekly
release,
cadence
and
so
we're
gonna
aim
to
cut
oh
922
this
way
and
release
next
week
and
what
we're
aiming
for
if
the
beta
is
to
inform
our
Wanda
launch
we're
really
looking
out
for
community
feedback
and
bugs
and
crashes
and
issues,
because
we
want
the
$1
launch
to
be
as
solid
as
possible,
so
we're
really
hardening
that
at
the
moment.
So
please,
like
definitely
drop
a
note
in
with
insta
bugs
shake
your
phone
go
to.
G
G
We
definitely
want
the
community
to
be
part
of
this,
so
vote
discuss,
chat
and
status
and
a
big
thank
you
to
everyone.
That's
been
doing
that
so
far.
We
read
all
of
your
messages
in
like
the
status
and
aetherium
and
other
channels,
and
we
read
every
inch
the
bug
report
like
yeah.
If
we
don't
get
back
to
you,
we
do
have
a
lot,
but
all
of
it
is
read
and
appreciate
it
yeah,
that's
the
that's
the
goal
for
one
another.
Thanks.
J
H
J
We
released
the
beta,
it
was
a
pretty
good
job
and
pretty
good
launch,
and
unfortunately
there
is
one
thing
that
we
actually
that
sleep
through
in
beta
and
that's
battery
performance
regression.
So
it's
actually
behaves
worse
than
on
Android
devices
than
their
previous
releases.
We
did
and
we
are
currently
investigation
and
fixing
this,
but
the
most
likely
root
cause
of
that
was
the
react
native
upgrade
2-0
54
55
4,
and
it's
Android
only
and
it
requires
you
to
type
a
relatively
long
messages,
and
that
was
the
point
why
it
missed
from
our
test
cases.
J
So
what
we
do
next,
we
already
switch
to
the
fork
of
react
native
to
be
able
to
fix
box
there
as
soon
as
possible,
because
they're
not
super
responsive
there.
We
will
have
to
downgrade
react
native
for
at
least
some
time
while
we
are
in
litigation
increasing
the
actual
root
cause
inside
it,
and
here
we
are
planning
to
actually
submit
EPR
to
really
positive,
and
we,
of
course
to
fix
our
performance
test
cases,
that's
pretty
much
all
from
my
side.
So
if
there
any
questions
just
being
a
songwriter
awesome.
K
Limitation,
so
the
onboarding
is
much
smoother
in
other
bigger
things.
We
now
have
proper
alerting
for
the
stickers
I
infrastructure,
which
includes
both
health
checks
and
metric
based,
alarms,
various
thresholds,
and
these
are
sent
up
by
email
and
a
$2
general
suck
other
than
that.
There's
been
a
lot
of
smaller
preparation
work
for
including
that
there's
a
handler
which
essentially
is
for
linking
status
up
related
things
like
channels
and
users
and.
K
K
Yeah,
so
we
have
to
start
working
on
the
swarm
and
the
main
goal
is
to
make
my
servers
discoverable.
So
currently
they
are
hard-coded
in
the
app.
So
that's
the
one
more
thing
that
we
need
to
finish
to
make
sure
that
the
whole
set
up
is
decentralized
in
at
least
in
on
the
level
that
you
want
it
to
be
centralized
right
now
we
all
work
on
this
more
in
the.
B
K
B
K
A
K
There
are
more
like
more
general
things
that
are
not
they're
smaller
and
not
really
wrapped
into
this
form.
So
the
first
thing
is
implemented
mr.
representation,
so
that
was
a
huge
effort
from
Andrea.
He
made
a
full
request
and
that
was
already
meritorious.
It's
almost
gonna
be
the
first
like
today
or
tomorrow.
I
guess
it's
already
much
so
pretty
much,
that's
a
huge
thing
or
improve
comments,
so
especially
for
public
chats,
where
we
right
now,
some
lonely
pretty
little
messages.
K
K
So
that's
an
effort
to
pretty
much
cement
and
better
pure
discover
protocol
that
it's
useless
traffic,
increased
speed
and
ability.
So
we
would
like
to
maybe
couple
this
with
Discoverer
version,
5
prodigal.
Let
me
use
Miriam
but
yeah
right
now.
It's
in
the
research
area
and
I
di
Custer
health
on
p2p
level.
You
know
in
progress.
We
have
one
nice
full
3d
visualization
and
provides
amazing
information
for
now.
Hopefully
we
can.
We
can
build
more
on
top
of
this,
to
get
more
insight
into.
K
What's
going
on
in
our
cluster,
make
sure
that
there-
and
there
is
healthy,
pretty
much
and
also
to
research
how
it
behaves
when
we
do
some
changes.
So
this
is
the
name
progress
we
started
working
on
this
a
few
weeks
ago,
but
that's
not
really
a
product
right
now,
so
that
for
this
two
things
first
are
the
top
30
so
check
out.
That
could
be.
It
awesome.
L
So
last
couple
of
weeks,
we've
focused
on
the
beta
release.
We
added
localized
default.
Chats
we
developed
the
fix
for
Korean
chat.
Chinese
Japanese
is
character
inputs,
which
was
another
regression
after
the
react
native
updates
kudos
to
Eber
for
helping
with
that-
and
we
did
a
bunch
of
other
fixes
and
improvements,
we're
going
to
be
aborting
the
swarm,
even
though
it
was
successful,
mainly
because
we
are
lacking
the
the
metrics
to
support
any
decision,
and
this
is
something
we
need
to
fix
to
have
the
the
insta-buck.
B
A
A
A
Everyone,
first
of
all,
I'd
like
to
I'd
like
to
welcome
young
Filipino
bean
who
joined
this
team's
life
swarm
so
yeah
we
have
written
for
reinforcements,
that's
great,
so
the
programs
over
the
last
two
weeks
was
mostly
around
bug,
fixing
and
mostly
around
the
beta
release.
So
that's
something
we
are
not
planning
to
stop
now
that
the
beta
is
out.
A
So
obviously
we're
still
bug,
fixing
and
factoring,
and
one
of
the
larger
items
on
that
front
is
the
command
API
so
shortly
put
we're
getting
rid
of
the
existing
command
API
and
we'll
replace
it
with
something
a
lot
more,
a
lot
simpler
and
a
lot
more
manageable
and
generally,
the
goal
in
the
immediate
future
is
to
provide
the
stable
and
consistent
and
bug
free
wallet
experience.
So
that's
that's
more
or
less
it
polish
and
the
bug
fixing
yay,
awesome,
yep.
M
Hey
and
so
because
QT
just
ended,
I'd
like
to
share
couple
numbers
on
dab
usage
and
transactions
quickly
over
the
last
seven
days
about
35%
of
users,
open,
adapt
and
11%
of
those
users
may
transactions
within
a
def
and
because
these
metrics
come
only
from
users
who
have
explicitly
option
to
tracking.
We
can
assume
that
the
actual
numbers
are
actually
much
closer
to
our
goals
of
60%
of
users,
opening
adapt
and
20%
transacting
overall.
So
that's
great
I'm.
M
Also,
some
great
progress
by
the
DAP
team
in
the
last
two
weeks,
unfortunately,
also
mostly
on
fixes
and
blockers
headline
news-
is
that
Collectibles
did
not
make
the
bad
cut
because
it
the
last
minute
we
have
some
security
concerns
about
the
remote
SVG
images
that
we
used
to
display
them
and
those
risks
are
ultimately
going
to
require
a
longer
chain
solution.
So
we
plan
on
adding
some
form
of
security
audit
to
RP
our
checklist
and
releasing
collectibles
in
the
next
release.
M
Other
major
fixes
from
the
past
two
weeks
browser
history
is
back
so
for
adapts
for
navigation
states
change.
You
can
once
again
navigate
back
and
forth.
Certain
links
in
depth
didn't
work
because
they
were
targeting
new
tabs.
That
was
a
big
blocker,
so
we're
happy
to
have
a
fix
in
for
that
DAP
transactions
where
sometimes
failing,
because
estimated
gas
costs
were
too
low.
So
we
added
a
multiplier
that
should
prevent
those
errors
in
the
future
and
I'm
the
developer
side.
M
There
were
a
few
blockers
to
running
status
locally,
so
alex
has
made
some
updates
to
how
we
include
certain
dependencies
and
also
to
the
version
of
NPM
installed
with
our
setup
scripts.
Hopefully
that
will
unblock
you
developers
from
building
status
and
then,
lastly,
some
progress
on
extensions
and
on
the
developer
dock
site.
Julien
feels
good
saying
that
the
extensions
MEP
is
now
production,
ready,
he's
added
error,
handling
and
worked
on
infrastructure
and
tooling
for
continuous
integration,
documentation
on
the
topic
of
documentation,
and
he
has
both
a
really
beautiful
starter
site
for
the
future.
M
Talks
about
status,
I
am
using
doc
II
Soros
and
we're
actually
going
to
kick
off
a
documentation
swarm
to
get
some
more
momentum
behind
that
project
tomorrow
over
the
next
two
weeks.
He
also
plans
more
in
tribute
to
the
browser
and
to
the
dab
screen
and
we'll
be
making
more
concrete
headway
on
extensions
and
Chuck
bans.
That's
it.
B
N
N
Development,
we
have
members
from
all
the
major
Clinton
relations
come
together
and
discuss
basically
protocol
and
client
related
matters,
and
you
know,
party
guests,
currently
harmony
drop,
so
diamond,
couldn't
make
it
unfortunately,
but
he's
not
a
globs.
Were
there
and,
like
I,
said
this
or
this
kind
of
consensus
that
deals
with
practical
matters.
N
We
had
presentations
ranging
from
performance
to
shouting
simulations
to
what
to
be
the
new
beacon
changes.
Inb4
were
parts
and
snarks
all
kinds
of
stuff,
very
interesting
things
we'll
be
publishing
those
videos
as
soon
as
they've
been
edited
other
than
that
great.
Yet,
with
the
themes
what
to
do
for
the
next
quarter
and
yeah?
That's.
B
O
O
Okay,
so
during
the
past
two
weeks
ago
we
started
doing
the
grunt
task
of
development
desktop
merges
so
far,
it's
been
done
in
one
direction,
so
recent
developers
have
emerged
to
desktop
and
for
the
next
two
weeks
we're
looking
forward
to
doing
them.
Verse,
Brown
branch
merge
so
that
that
stuff
will
be
murchison
to
develop
and
finally
will
have
a
single
codebase.
Both
desktop
and
mobile.
We've
also
been
doing
some
UI
changes
across
across
the
code
and
some
bug
fixing
I
just
like
to
highlight
two
things.
Like
the
profile
end
of
updates.
O
There
were
some
recent
progress
and
updated
chat
designs.
We
have
lots
of
stuff
various
in
progress
and
we're
looking
forward
to
finally
nail
down
some
of
the
UI
stuff
that
is
still
preventing
those
beers
from
getting
merged
and
closed
down.
All
of
their
many
p0
issues.
I've
also
been
put
in
the
next
slide
like
this
sort
of
on
a
humorous
side
yeah.
So
this
is
the
current
progress
we've
had
so
far,
yeah,
it's
getting
better
I'd
say
not.
Everything
is
mushed
yet,
but
hopefully
we'll
get
there.
So
it's
been
austere.
J
B
P
Yeah,
we
plan
to
did
releases
once
a
month
more
or
less
so,
but
yeah
we'll
try
at
least
every
two
weeks
it's
on
hold,
if,
if
possible,
so
this
model
released
in
part
3.1,
which
we
called
names,
Planet
Express
I,
was
quite
a
big
release.
There's
a
lot
of
new
features.
Just
some
of
this
new
features
include,
for
instance,
a
light
client
wallet,
so
the
world
Birkin
specified
is
own
accounts
and
things
like
balances.
P
There
are
things
like
a
transaction
to
logger
contract
profiler,
as
well
as
the
equating
much
photographs
which
should
make
the
developers
lives
much
easier.
We
also
added
initial
support
for
ens,
an
initial
meaning
we
added
on
on
the
topside
and
we
plan
on
having
full
support
and
joint,
but
for
the
next
release
we
also
improved
the
performance
overall,
very
much
from
starting
a
bar
to
building
the
tab
to
the
tasks
themselves,
and
we
still
have
some
improvements
to
do
actually,
but
we
believe
right
now.
P
It's
the
fastest
smart
contract
testing
framework
out
there
and
for
the
next
two
weeks
we
we
are.
We
are
retaking
the
important
part
line
and
meaning
are
we
make
use
of
web
pack
and
how
we
can
better
support
different
workflow,
so
that
developers
can
can
fine-tune
audio
mana
builder
dirt
app.
So,
for
example,
for
production
they
can.
They
can
create
much
smaller
JavaScript,
while
maintaining
for
the
world
put
things
like
source
maps
that
they
might
need
for
for
debugging,
and
we
also
burning
a
lot
of
effort
in
creating
more
tutorials
and
improving
the
commutation.
P
G
G
Q
That's
a
really
good
question:
I'm,
not
sure
it's
a
function
of
how
large
an
active
it
has
to
be
it's
rather
its
brother,
more
than
any
functions
that
are
laid
out
or
any
structure
that
ends
up
being
created
by
by
also
or
and
all
the
community
gets
the
building
continues
situated.
So
I
guess
it's
kind
of
like
a
blockchain.
G
We
have
another
question:
this
is
for
you
in
the
bill
on
okay,
ours,
do
you
spend
SN
T
to
vote
or
are
the
oats
weighted
based
on
how
much
S&T
a
user
has
and
actually
Jared
type
to
reply?
I'll
just
read
this,
so
maybe
we
can
add
to
it.
You
don't
spin
S&T
polls
take
a
snapshot
of
S&T
balances
at
poll
creation
block
time
and
make
a
clone
of
voting
token
yep.
B
And
basically,
exactly
right,
so
if
you
have
a
hundred
SNT
in
your
status
wallet
you
don't
you
don't
actually
spend
that
hundred.
You
have
a
hundred
SN
team
to
use
to
vote
and
the
number
of
votes
you
have
is
so
if
you
have
a
hundred-
and
you
like,
you,
cannot
in
that
UI,
you
can
actually
see
it.
So,
as
you
slide
it
along
the
little
slider
in
the
diagram,
you
can
actually
see
how
many
votes
you're
putting
in
with
you
Madison
T,
but
that's
just
for
promoting.
That's
not
actually
spending
it.
B
J
P
B
B
D
Yes,
adapt,
so
it
should
work
through
through
meta
masks.
That's
definitely
a
valid
point,
but
yeah
it's
it's!
The
the
address,
that's
holding
the
SMT
at
the
time
of
the
particular
polls
creation
is
where
the
balanced
snapshot
comes
from.
So
if
you
wanted
to
use
it
in
your
inter
status
wallet,
then
you
should
transfer
the
SMT
into
that
wallet
prior
to
the
poll
creation,
so
we
should
probably
actually
have
like.
Maybe
you
know
a
couple
of
days
or
a
week
before
we
start
creating
mini
polls
so
and
communicate
that
people
who
should
be
getting
ready.