►
From YouTube: Status Townhall #29 - Monday March 4, 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
Sorry,
yes,
JB
and
Carrie
put
out
the
engagement
survey
last
week,
I
think
of
one
and
thanks
for
them
for
doing
that.
You
know
they're,
quite
a
lot
of
good
feedback
that
came
through
some
of
the
seem
more
pressing
than
others,
but
there
were
some
three
dominant
themes,
which
is
basically
the
financial
uncertainty
strategy
and
direction
and
communication.
B
I
just
want
to
say
in
case
this
goes
on
for
long
and
I
started
rowing
on
I
just
wanted
to
say
thank
you
for
working
on
status
and
for
your
patience,
your
security
and
safety,
and
the
future
of
the
organization
has
been
my
number
one.
Priority
and
I
was
actually
looking
to
address
the
strategy
in
finance
and
a
much
more
elegant
presentation,
but
the
conversation
has
been
accelerated.
So
oh
yeah.
B
So
yeah
financial
uncertainty-
this
is
all
the
interpretation
of
everyone's
results,
so
people
want
more
communication
on,
or
attention
to
a
financial
situation.
There's
been
worries
about
longevity
of
the
project.
We
there
was
a
desire
to
include
more
finance
or
financial
updates
in
the
weekly
newsletter.
There
was
some
misinformation
that
actually
went
out,
that's
being
corrected
in
the
in
the
next
newsletter
that
comes
out
I
believe
we
need
to
be
explicit
about
runway
and
job
security.
People
also
like
to
have
more
guidance
in
what
expenses
can
or
cannot
be
claimed.
B
B
B
B
We've
also
sold
more
F,
which
is
great
because
with
the
size
of
status
as
it
is
today,
when
our
funds
alone,
we
can
now
go
beyond
November.
So
this
means
that
the
research
of
security
as
it
currently
stands,
close
of
courses
we
can
to
get
towards
the
end
of
the
year.
So
you
know,
look
you
relax
and
hopefully
enjoy
our
work
a
little
more
and
don't
feel
like
you
need
to
stress
yourself
or
outs
or
anything
like
that.
So
I
hope.
That's
really
good
news.
B
And
our
earth
reserves
currently
sit
at
173
kef,
but
it's
important
to
realize
that
there
is
actually
a
grander
strategy
around
the
allocation
of
those
s
at
the
time
that
we
did
the
raise.
For
example,
the
100k
of
that
F
is
actually
dedicated
for
user
growth
and
business
operations
after
the
development
and
deployment
of
the
application.
B
B
Facebook
they're
all
getting
interested
in
spot
chain
technology,
this
time
to
create
wallets
and
their
sign.
I
work
on
earth,
which
is
actually
great
for
us,
because
it'll
increase
the
value
of
s
and
therefore
rise
us
as
well.
If
we
deplete
our
resources
too
quickly,
then
we
can't
play
a
long-term
game
and
we
can't
actually
compete
against
them.
B
No
I
mean
and
I,
don't
know
if
you've
seen
three
ma.
If
you
haven't
heard
of
them,
I'm
not
surprise,
it
is
a
secure,
instant
messenger,
but
they've
only
managed
to
get
like
a
million
installs
I
think
not
even
monthly
active
users.
So
with
that,
like
I've
discussed
the
VPI,
the
cost
per
install
business
model
in
software
distribution.
Basically,
you
can
imagine,
like
a
user
somewhere
between
five
to
ten
dollars
to
get
the
acquisition
of
a
retained
user
and
you
do
the
math
like
100
KS,
especially
it's
today's
rate.
B
Isn't
that
a
lot
of
that
many
uses
on
the
grand
scheme
of
things
and
certainly
not
as
much
as
what
we
intended
to
create
when
F
is
an
all-time
high,
so
stay
tuned?
There
is
not
much
more
comprehensive
breakdown
over
the
finance
and
how
it
pertains
to
the
overall
strong
term
strategy.
Just
give
me
some
more
time
on
that.
One.
B
Another
way
to
think
of
it
about
this
as
a
heuristic.
Basically,
F
is
at
half
price,
the
initial
raise
and
our
initial
plan.
So
basically,
everything
is
kind
of
quote
unquote
twice
expensive
I
mean,
of
course,
that's
not
like
actually
the
case
in
many
ways,
but
it
kind
of
is
as
well
so
if,
if
this
gets
like,
if
it
gives
the
final
service
to
in
depths
it's
kind
of
like
basically
the
situation.
B
So
the
other
thing
is
returning
to
salaries,
went
that
gonna
happen.
I
mean.
Basically,
the
current
idea
is
that
if
we
can
get
a
sustained
10
percent
margin
or
above
the
fu
USD
price
at
a
trace,
then
it
makes
no
sense
to
to
bring
everybody
back
up.
I
mean
the
reality.
Is
the
previous
salaries
were
fitting
for
an
organization
of
our
previous
wealth,
but
it
was
slightly
overpriced
for
a
start-up
and
our
current
wealth.
B
However,
we
I
mean,
like
later
on.
We
can
make
this
a
collective
decision
if
we
want
to
decide
to
reduce
our
runway
or
if
we
want
to
choose,
who
stays
or
goes,
I
wouldn't
recommend
it,
but
I'd
like
to
present
the
overall
strategy.
First
again,
that's
not
going
to
be
today
but
that'll,
be
sometime
in
the
very
near
future.
B
So
another
very
cool
is
the
strategy
and
direction.
You
know
there's
this
idea
of
being
feared
for
fired,
fear
or
being
fired
without
notice,
and
it's
causing
stress
of
course.
So
how
can
we
just
reassure
people
that
they're
doing
a
good
job
I?
Think,
quite
frankly,
everyone's
been
doing
a
fantastic
job.
I
couldn't
be
more
proud
to
be
working
with
everybody.
It's
been
really
awesome,
and
hopefully
now
that
you've
seen
we
have
more
Fiats,
at
least
until
November.
B
B
Now,
there's
also
been
some
disagreements
over
the
technical
direction.
We
need
to
make
clear
communication
reiteration,
what's
important,
basically
still
we're
still
in
q1,
and
the
q1
goals
are
to
deliver
the
white
paper.
Promises
they're,
not
done
yet.
So,
let's
keep
the
focus
on
that.
There's
also
been
this
sort
of
idea
of
the
technology
versus
the
user.
B
So
we
need
to
understand
the
technology
really
really
well
in
order
to
deliver
the
best
user
experience
say,
for
example,
like
message,
reliability
has
been
in
one
that's
quite
difficult
to
do,
but
even
in
our
current
setup,
that's
also
very
challenging
to
solve,
because
the
fundamental
conceptions
around
developing
that
protocol
needs
to
be
your
address.
So
there's
a
lot
of
foundational
work
that
needs
to
be
done.
That
then
materializes
to
the
users
point
of
view
and
we're
going
to
be
addressing
this
like
a
lot
of
what
q2
is
going
to
be
about
is
optimizing.
B
There
was
also
this
idea
that
we're
trying
to
support
too
many
platforms-
yeah,
it's
true
like
I,
mean
status,
is
always
going
to
be
an
Android
and
iOS
application.
It's
a
it's
a
little
unclear
how
successful
we'll
be
on
iOS,
really
at
the
went
at
the
wins
of
Apple,
but
on
Android.
That's
definitely
should
be
the
focus
now
there
was.
The
problem
is:
there's
a
good.
B
There
was
a
bit
of
a
historical
development
glitch
when
it
came
to
desktop,
but
the
idea
actually
was
to
use
the
same
code
base,
at
least
in
status,
react
to
deliver
for
all
of
these
platforms.
It
diverts
slightly,
but
we
have
been
fixing
that
recently,
so,
hopefully
supporting
all
of
these
platforms
isn't
the
mountain
of
a
task
that
it
sounds
like.
If
people
disagree,
we
can
definitely
have
a
discussion
about
it.
B
As
for
the
value
of
adding
features,
why
do
we
do
that?
It's
is
it
distracting
from
core
performance,
I,
don't
think
so.
I
mean
we
have
a
team
dedicated
for
core
performance,
they're
called
status
core
led
by
igor.
It's
got
some
fantastic
people
in
there
and
they're
doing
amazing
work
they're
just
mowing
down
their
backlog,
but
the
other
side
of
that
is
like
we
are
delivering
the
white
promises
and
that's
really
the
only
features
that
we're
developing
right
now
and
that
ties
directly
back
to
the
business
model.
B
That
is
growing
the
S&C
economy,
and
should
we
prioritize
bug
fixing
versus
new
feature
development,
I
mean
we
get
the
webhead
promises
done,
because
that's
really
important
to
get
that
off
our
back
and
it's
not
what
we're
trying
to
achieve
in
out
on
that
will
make
them
quickly.
It's
just
a
matter
of
getting
them
done,
because
that's
what
we
promised
right.
B
B
Believe
me,
you
didn't
want
it,
you
don't
want
to
do
it
like
I
mean
I
didn't
want
to
do
it.
It
was
incredibly
difficult
and
thankfully
that's
not
looking
like
it's
has
to
happen
for
the
face
foreseeable
future,
and
if
we
didn't
do
it
fast,
we'd
have
lost
a
lot
more
people
and
that's
actually
been
a
bit
of
a
problem
with
the
sort
of
democratic
approach.
Right.
It
is
a
bit.
B
B
B
We
have
the
liquid
or
topic
democracy
that
can
like,
hopefully,
feed
into
the
meritocracy
in
terms
of
having
the
users
to
choose
who's
in
or
out
of
it,
and
we
have
the
DAO,
so
we
can
start
be
centralizing
how
things
get
funded
and
what
gets
funded
and
who
somewhat
so
a
lot
of
these
ideas
that
they've
been
with
status
since
the
beginning,
and
they
will
continue
to
do
so.
It's
just
unfortunate
times
call
for
drastic
measures.
I
hope,
that's
understandable,.
B
B
It
feels
like
we
haven't
done
enough
good
enough
job
of
articulating
what
for
whom
and
why
we
build.
We
started
talking
about
that
frog,
I
kind
of
agree,
but
I
mean
everything
that
we're
doing
currently
is
encapsulated
within
those
within
the
Swans
repo.
So
if
you
go
to
the
readme,
you
scroll
down
you'll
see
the
act
of
swarms.
That's
currently
what's
being
worked
on,
of
course,
that
doesn't
address
the
sort
of
longer-term
vision,
but
again,
like
I
mentioned
I'll
get
I'll
get
to
that,
hopefully,
for
the
next
town,
Pole
yeah.
B
That's
exactly
what
I
said:
it's
literally
what
I
plan
to
do
for
this
town
hole
but
stuff
like
this
came
ups
and
it's
I've
been
working
with
lot
of
the
swarms
and
although
that's
higher
priority,
because
that's
actually
where
things
are
getting
done,
but
I
will
I,
do
hear
about
this
and
I'll
sure
be
sure
to
deliver.
So
it
makes
almost
sense
stay
tuned.
B
There's
the
question
of
like
why
some
teams
like
embark
and
Nimbus
in
Gitta,
for
example,
I
mean
this
really
boils
down
to
the
same
problem
we've
had
for
for
over
a
year
now
or
since
the
beginning,
and
that's
just
message:
reliability,
except
for
the
last
few
weeks.
It
has
a
significant
impact
on
the
organization
and
our
users,
I
think
like
the
last
week
was
so
there's
there's
been
a
lot
of
complaints
on
that
and
it
hasn't
really
been
that
reliable
I
know
I'm
still
losing
messages.
B
This
is
status
quo
and
status,
protocols,
responsibility
and
we
do
need
to
give
them
as
much
support
as
we
can
so
like
if
you're
seeing
messages
or
you
feel
anything
wrong,
you
know
send
your
logs
in
to
Joanna
or
ego
or
whoever
and
you
know,
send
screenshots
and
report
in
hashtag
status
core
just
so
that
there's
a
lot
more
visibility
on
the
issue
has
also
been
like.
The
wish
for
more
connectivity
in
in
like
the
meat
space
in
real
world,
that's
a
little
harder
to
answer
at
the
moment.
I
think
I
got
self
funded
option.
B
B
Yeah,
there's
also
this
desire
for
more
product
updates
for
the
community
and
dev
related
contents.
Basically,
you
know
Johnny's
been
working
really
really
hard.
He's
got
a
content
pipeline,
he's
mashing
it
out,
but
he's
like
he's
only
one
man,
you
know
hot
results
and
the
status
fear
ambassadors
are
all
doing
their
part
and
they're
doing
amazing
job.
The
sort
of
technical
stuff
I
mean
that
comes
from
core
contributors
developers
if
they
have
time
to
write,
but
everyone's
pretty
pretty
resource
strapped
at
the
moment,
so
it
is
definitely
very
challenging,
but
it's
also
very
appreciative.
B
I
think
what
I'd
like
to
see
is
like
maybe
some
more
stuff
in
terms
of
extensions
and
developing
that
out,
because
it
serves
as
a
great
entry
point
to
the
contribution
later
on.
But
that's
just
my
opinion,
I
think
just
raising
this
that
this
is
a
discussion
we
should
have,
and
hopefully
we
can
find
some
solutions
to
it.
A
B
C
D
C
A
fifth
of
the
monthly
core
contributor
compensation
is
paid
out
in
theatres
and
status
network
tokens.
This
means
80%
is
still
being
paid
in
fear.
Many
core
contributors
have
commented
that
they
would
like
to
switch
to
receiving
cryptocurrencies.
If
these
were
more
stable
versus
native
currency,
their
native
currency
well
dies
providing
this
property
as
dies,
decentralized,
stable
context,
the
US
dollar,
it
is
fully
collateralized
by
ether,
so
receiving
your
salary
and
I
will
protect
you
from
the
crypto
fluctuations
versus
the
US
dollar.
In.
E
C
To
receive
die
core
contributors,
please
go
to
bamboo,
HR
and
log.
In
there
you
can
choose
the
percentage
of
your
monthly
salary
and
expense
reimbursement
which
you
would
like
to
receive,
instead
as
Network
tokens,
either
or
to
stable
condi.
By
the
way,
when
you
choose
to
receive
your
compensation
in
crypto,
you
will
get
the
bed
rate
of
the
five-day
average,
leading
to
your
compensation
due
date
or
the
current
rate
at
the
time
of
the
payment.
This
means
in
a
bear
market.
C
You
don't
have
to
worry
to
lose
because
of
the
timing
of
the
payment,
as
you
will
get
more
crypto
and
in
a
bull
market.
Hopefully
soon
you
will
enjoy
the
lower
every
trade,
giving
you
an
additional
compensation
boost,
measured
in
fear
so
head
to
member
HR
and
opt
in
to
receiving
crypto.
Now,
please
do
that
by
the
twentieth
of
each
month,
so
we
can
take
a
snapshot
and
make
sure
that
everybody
who
opted
in
receives
crypto.
Thank
you
very
much.
F
D
G
F
So
development
of
the
feature
is
finished
and
tested
on
Rob
stone,
so
we're
just
in
the
process
of
commissioning
those
stickers.
We've
done
some
further
character:
development
with
the
illustrator
that
we
hired
and,
of
course
we
have
phase
2
of
our
sticker
head
suger
contest
beginning
today,
I
believe
and
Corey
is
still
managing
contract
security
issues.
In
the
background,
so
yeah
sticker
markets
forum
is
in
great
shape
and
hopefully
we'll
easily
hit
those
CTA
of
end
of
the
month
to
ship
that
fenced
in
her
name
ease
Network,
incentivization.
D
So
basically,
we
like
I
like
the
old
arrow
here,
so
we
moved
a
little
bit
to
the
specification
phase
and
yep
and
also
we
will
start
doing
like
proof-of-concept
price
of
like
maybe
this
week
or
somewhere
next
week,
and
also
we
did
some
your
exploration
in
terms
of
how
the
user
will
see
this.
The
one
who
uses
test
address
app
itself
and
I
guess
I'm.
Three
is
ready
to
give
some
presentation
on
that
right
now.
E
Hey
yep
sure,
so
there's
been
two
sort
of
ways
we
decided
to
explore:
the
UX
of
network
incentivization
and
the
first
one
is
called
per
contacts.
Settings
yeah.
It's
based
on
the
idea
to
extrapolate
the
gas-like
pattern
to
communication
status
so
that
you
would
choose
to
pay
a
fee
for
each
contact
you're
currently
talking
to
so
that,
if
you
want
to
make
sure
that
your
message
is
to
Alexander
Wang
in
this
example
would
get
delivered
faster.
You
choose
a
higher
rate
and
you
paper
for
for
each
message.
E
Just
like
you
do
and
then
the
transaction
on
the
blockchain
and
firstly,
we
thought
that
this
is
a
great
idea,
because
this
is
a
relatively
familiar
pattern,
at
least
within
the
cryptic
community.
But
then
we
realized
after
doing
this
UX
exploration,
that
this
a
bit
different
from
the
transaction
because
transaction
just
it
happens
tuned
and
it's
done,
but
so
you
have
to
specify
the
fee
only
once.
E
But
here,
if
you
want
to
manage
those,
it
would
become
quite
complex
so
that
if
you
wanna,
for
example,
change
the
message
delivery
fee
for
a
certain
we
see
pen,
we
have
to
find
a
recipient.
In
your
chat,
history,
you
have
to
change
that
and
that
becomes
quite
hard
to
manage.
Basically,
and
we
decided
to
explore
a
more
traditional
and
conventional
way
of
networking
systemization
and
it's
the
next
slide.
It's
a
basically
subscription
model,
which
is
also
pretty
familiar
to
everybody,
even
more
than
a
guess
like
pattern
and
XY
please.
E
This
is
how
it
looks
like
so
we
been
thinking
about
the
entry
point,
which
is
the
profile
screen
and
we
could
add
an
item
over
there,
which
is
called
status
Network
on
the
first
mock-up.
The
second
mock-up
is
the
intro
like
a
promo
screen.
That
explains
what
is
it
all
about,
and
the
third
mock-up
is
the
screen
where
we
explain
in
more
detail.
E
This
is
a
completely
arbitrary
number
by
the
way
you
you
you'll,
pay
a
certain
amount
per
month
and
that
will
help
you
to
incentivize
all
the
messages
years
and
everybody,
and
by
doing
that,
you're
gonna
provide
an
incentive
for
third
party
known
runners
and
by
the
way,
this,
those
these
sorry
UI
explorations
are
only
about
the
user
facing
side.
This
is
not
about
the
node
runners
and
for
now,
and
the
next
slide
please
so
just
to
show
like
this
is
how
the
subscription
screen
could
look
like.
E
Once
you
choose
to
activate
your
subscription
you're
gonna
ask
your
active
subscription.
We
can
show
some
stats
so
that
you
you,
you
would
know
what
are
you
paying
for?
You
can
change
the
Woollett
or
the
subscription
plan
at
any
time
and,
like
I
said
just
now,
this
is
only
for
the
user
facing
part.
The
node
runners
part
for
now.
At
least
we
decided
that
it's
gonna
be
a
tech,
space
command
command
line
interface,
but
eventually
it's
gonna
be
part
of
the
desktop
plan.
E
What's
it
once
it
was
because
on
your
desktop,
you
can
have
much
more
resources
and
to
run
your
own
own
and
will
create
a
nicely
looking
UI
so
that
you're
gonna
be
you're.
Gonna,
see
how
much
when
you
get
from
the
users,
how
much
people
use
the
notes
you're
running
and
for
UX
explorations
and
please
stay
tuned.
It's
a
really
interesting
subject,
and
it
could
be
much
more
cool
stuff
happening.
H
Parallel
to
that,
Maciej
has
done
some
really
really
cool
designs
and,
given
that
conversations
on
the
navigation
buy
in
status
as
a
whole
have
kind
of
progressed,
and
the
amazing
Rachel
has
plotted
out
a
road
map
for
the
whole
browser
improvements.
We're
able
to
do
a
design
review
tomorrow,
hopefully,
which
means
that
we
can
also
put
up
some
fancy.
H
Easel,
perhaps
engage
another
community
organization
to
build
the
actual
store
for
us,
which
will
be
a
sort
of
suggested
home
button
for
our
new
browser
when
that's
ready,
so
that
I
could
maybe
be
a
little
bit
further
on,
but
I'm
a
fan
of
you
know
amber
estimating
how
far
we
are.
So
it's
going
well
and
we
should
hopefully
at
least
have
a
contracts,
that's
order
to
play
around
with
and
do
some
UX
explorations
in
the
next
few
weeks.
In
addition
to
building
front
end.
F
D
I'll
take
a
bit
more
time
today,
but
yeah.
We
are
this
type
of
swarm
right
now,
that's
usually
hears
from
people
when
something
doesn't
work.
We
don't
usually
hear
when
something
does
work,
so
I
decided
to
a
bit
flip
this
bias
and
also
a
bit
more
about
what
we
did
and
how
and
I
want
to
talk
about
like
three
things.
First
is
like
we
did.
D
0
sin
0,
it's
a
new
like
release
like
release
number
scheme,
but
that's
a
new
release
and
it's
actually
was
just
17
days
since
the
previous
one,
which
pretty
fast
and
it's
already
had
like
in
total,
like
1
164,
commits
of
course
it's
the
whole
team,
like
not
just
core
improvements,
but
yeah,
it's
still
pretty
impressive.
That's
it!
It's
a
big
release.
Just
to
give
you
a
comparison
like
the
previous
one
had
like
250
commits,
but
it
was
like
preparing
from
November
to
like
February.
D
D
Obviously
that
no
one
port
on
the
weekend
on
this,
so
this
script
was
removing
actually
the
real
peers
as
well,
not
only
they're,
the
ones
who
get
stuck
and
then
just
after
that
on
Monday,
we
found
we
just
added
like
tweak
the
code
to
actually
mitigate
this
issue
on
the
Status
goal
level,
and
we
deployed
it
again.
So
thats
actually
is
supposed
to
have
fixed
most
of
the
issue
that
we
were
server
set.
D
But
then
it
turns
out
that
we
also
had
a
like
a
client-side,
but
on
the
same,
that
looks
exactly
the
same
as
a
server-side
bug,
but
it's
just
a
we're
showing
the
like
item
like
the
air
dialect
in
the
wrong
place.
Essentially,
so
we
also
had
to
fix
that
and
we
fix
that
and
release
like
zero
point:
zero.
Ten,
zero!
That's
like
fixes
this
issue,
and
even
after
the
release
we
found
out
that
it's
also
one
small
H
keys.
D
D
So
people
just
pop
up
on
the
channel-
and
sometimes
we
have
to
like,
ask
the
same
question
which
bill
do
you
have
and
which
do
you
have
like
BFS
over
off
and
things
like
that,
and
hopefully
that
will
fix
this
issue,
because
you
will
be
able
to
just
share
your
logs
and
technical
information.
Maybe
a
screenshot
with
us
like
with
a
simple
Nick
or
something.
So
it's
currently
more
or
less
in
progress,
but
hopefully
like
in
the
next
few
releases.
D
F
I
Yeah,
very,
very
quick,
very
brief.
We
noticed
that
in
in
several
conversations
that
came
up
that
is
difficult
to
see
where
design
is
at
when
working
on
a
initiatives
specific
projects.
So
this
is
to
share
a
little
bit
about
the
process
and
how
to
process
my
different
foresters
and
features
or
a
design
ax
or
whatever
you
would
want
to
call
it.
We
do
have
a
process
that
we're
trying
to
follow
sometimes
more
or
less.
There
extends,
depending
on
the
type
of
design
asks.
I
So
that
makes
it
a
little
bit
confusing
like
where
we
are
at
any
given
moment,
because
it
differs
for
each
project
that
we
work
on
for
most,
you
can
see
we
would
go
through
a
funnel
of
say,
have
a
tech
review
where
the
designer
will
reach
out
to
the
developer,
either
separately
or
during
a
call
to
understand
like
it's
like
the
design
that
I
have
prepared
now.
Will
that
actually
work?
Is
it
feasible?
We
will
have
a
design
review
with
janitors.
I
Usually
that
consists
of
myself
of
nabiollah,
Rachel
and
anyone
else
relevant
to
the
project
to
understand
and
do
a
sanity
check
on
the
designs.
Usually,
we
will
have
some
sort
of
design
to
death
handoff,
which
basically
is
usually
a
call
say
these
are
the
designs
I
have
discussing
any
details,
any
questions
left
in
order
to
implement
and
what
we,
what
we're
trying
to
get
impress,
does
a
lot
more,
which
has
been
happening.
I
A
lot
recently
is
that
the
design
implementation
comes
back
to
design
by
a
developer,
eater
tagging
or
pinging,
or
asking
the
designer
to
review
side
by
side.
This
is
your
specification.
This
is
what
it
looks
like
now.
It's
this.
According
to
the
specification,
so
for
most
projects
we
will
go
through
those
phases.
I
There
are
exceptions,
so
thinking
of
copy
changes
or
thinking
of
an
existing
component
that
undergoes
slight
slight
adjustment
or
is
applied
somewhere
else
in
isolation.
In
that
sense,
we
might
skip
some
of
these
phases,
which
I
understand,
make
it
a
little
bit
confusing.
It's
just
there's
no
know
one
single
process,
and
neither
what
we
want
that,
like
not
lock
people
in
okay
go
to
the
next
slide.
Please
right
so
also.
I
Understanding
where
design
is,
that
also
means
that
sometimes
it's
not
really
visible.
What
designs
are
already
out
there
there's
definitely
a
lot
of
work
in
the
pipeline
that
has
not
been
implemented
yet,
but
is
out
there
and
I
would
invite
you
to
go
and
check
out
designs
on
the
figma,
so
you
can
get
a
full
understanding
of
what's
there
with
regards
to
white
paper
promises
also
in
this
deck,
you'll
find
the
links
to
a
prototype
that
kind
of
binds
them
together.
I
So
these
are
basically
the
design
efforts
for
the
work
of
upcoming
upcoming
months
that
are
waiting
to
be
implemented,
then
finally
anos
life
or
death,
but
discussing
with
the
team
this
morning,
we
really
really
are
extremely
grateful
for
the
work
that's
going
on
in
in
terms
of
components.
We've
had
several
conversations
around
that
and
it's
been
a
major
relief
for
the
designers
and
speaking
on
their
behalf
now
to
see
some
of
the
components
like
the
bottom
drawer
and
the
navigation
that
Romans
were
working
on
and
to
see
like
the
horizontal
scroll
that
Andre
is
doing.
I
F
F
F
A
A
A
F
A
A
G
A
A
B
Again,
yeah
like
timelines
aside,
let's
not
focus
on
that
too
much.
Basically,
once
the
current
swarms
are
done,
that's
kind
of
like
a
q1.
What
stuff
the
next
of
a
series
of
swarms
I
get
to
be
decided,
but
they're
going
to
be
focusing
on
things
like
onboarding.
So
when
the
SMT
white
paper
swarms
are
done,
status
is
basically
going
to
look
like
it
is
today,
but
with
some
SMT
utilities.
B
B
Having
said
that,
I
also
want
to
re-emphasize
that
we're
probably
still
gonna
have
some
messaging
problems
because
we
need
to.
We
need
to
depart
from
whisper
and
developer
and
protocol
and
that's
going
to
be
a
very
long
term.
Prog
process.
Having
that
said,
the
status
protocol
swarm
is
looking
at
a
data
synchronization
layer.
So
hopefully
we
can
get
a
message.
Reliability
up
wake
up;
it's
just
that
it's
going
to
still
be
quite
bandwidth,
consuming
so
yeah,
I'm,
wholly
positive
I
think
everybody
is
working
really
hard
and
it
should
look
like
something.
Oh.