►
From YouTube: Status Town Hall - April 23rd, 2018
Description
*-General Updates-*
Carl talks about putting Privacy first in the digital age 1:05
Updates on Status Open Bounty Contributors / New Hires 5:45
Marketing updates 9:44
Bounties updates 13:37
Status Projects / Incubate 15:21
*Swarm Updates*
Meta Swarms 18:02
*Core Swarms*
#34-react-native 23:30
#58-mainnet 25:04
#63-refactor-geth-packages 28:44
#68-core-metrics 30:28
#83-energy-efficient 31:26
#92-discovery-v5-research 34:39
#96-tribute-to-talk 35:31
#151-ens-usernames 36:44
#086-push-notif-v2 40:07
#99-confidence 41:34
#143-seamless-login 43:13
#170-wallet-improvements 44:14
#154-support-web3 46:55
#167-extended-automated-testing 47:52
#94/142 wallet-compatibility 50:36
*Research swarm*
#95-les-service-model 51:58
*Open Bounty swarms*
#121-swarm-compensation 54:45
#122-sob-metrics 56:33
#127-sob-testing 58:21
#140-sob-onboarding 1:00:12
*Q&A 1:02:18*
- 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!
- This week we heard from Carl about his thoughts on Cambridge analytica and it's effect on mainstream media, Status Projects announcement, updates on Status Open Bounty statistics, multiple swarm updates and more!
Any other questions please leave a comment or join our chat - https://chat.status.im
A
Okay,
sweet
all
right:
we
are
making
progress
all
right,
welcome
everyone
to
our
seventh
Town
Hall
and
I'm,
just
getting
the
slides
up
and
running,
and
it's
been
an
exciting
two
weeks
we
made
a
ton
of
progress
and
we'll
be
going
through
that
today,
we've
got
updates
from
every
swarm
as
usual
and
we're
also
going
to
be
getting
add
some
additional
updates
from
from
other
teams
and
as
well
as
a
launch
that
we
had
from
last
week.
So
let
me
just
we'll
just
kick
it
straight
in
I'm,
assuming
the
slides
I'm
not
coming
through.
A
Okay,
yes,
okay,
sweet,
so
anyone
who's
interested
in
following
along
there's
the
Billy
link
to
go
through
the
slides.
But
let's
we'll
kick
things
off
with
Carl
to
give
a
quick.
Some
quick
thoughts
is
one
of
the
co-founders
on
kind
of
the
state
of
the
market,
and
you
know
the
internet
or
the
whole.
So
Carl
you,
you
want
sure.
C
B
And
this
it
had
me
thinking
about
like
social
networks
in
general
and
I,
figured
out
talk
about
this
just
for
a
few
minutes,
specifically
for
new
members
of
the
community,
who
aren't
really
familiar
with
what
say
this
is
or
what
we're
building
and
so
for
those
of
you
who
didn't
see
it.
There
was
media
coverage
in
light
of
this
huge
analytical
scandal,
which
I
think
will
be
the
first
of
many,
and
basically,
this
firm
was
using
data
from
Facebook
to
create
campaigns
that
influence
voter
opinion
and
they're.
B
Doing
this
on
behalf
of
politicians
who
had
hide
this
firm
and
what
followed
was
this
congressional
hearing
with
Mark
Zuckerberg,
where
he
was
questioned
about
Facebook's
business
practices
and
it's
fascinating
to
watch
and
what
I
think
we
can
learn
from
Facebook?
Is
that
if
you
don't
put
privacy
first
and
it's
only
this
afterthought,
you
run
the
risk
of
creating
business
models
that
have
really
perverse
economic
incentives.
B
So
that
is
to
say,
when
you
have
ads
as
a
business
model,
you're
creating
a
system
where
the
more
data
that
you
can
harvest
on
your
users,
the
more
profitable
organization,
becomes
and
like
on
the
surface
like
okay.
Well,
this
sounds
kind
of
trivial
or
subtle,
but
it's
paved
the
way
to
pretty
undesirable
events.
So
now
we
have
a
math
psychological
profiling.
We
have
the
possibility
of
a
small
group
of
bad
actors
to
potentially
sway
the
outcome
of
political
elections,
and
we
have
surveillance
that
level.
B
Is
this
experiment
and
exactly
that,
and
so
my
hope
is
that
we
can
learn
from
the
shortcomings
of
these
web
2
companies
and
create
this
users
as
a
stakeholders
network
that
puts
privacy
first,
and
in
order
to
do
this,
we
need
to
provide
really
secure
defaults
that
respect
the
human
right
to
privacy
and
individual
liberty,
and
we
need
to
do
this
in
a
way
that
is
completely
open-source
and
decentralized.
And
so
one
of
the
the
foundational
principles
here
is
that
everyone
has
fair
access
to
become
a
stakeholder
in
the
network
and
I
think.
B
Consequently,
we
can
break
down
this
level
of
separation
between
the
different
groups
involved.
So,
rather
than
having
someone
who
owns
the
platform,
a
group
of
advertisers
and
users
through
all
want
different
things.
We
can
instead
have
this
single
community
whose
shaping
the
direction
the
software
together
and
it's
like,
ok.
Well,
this
is
new
territory,
it's
gonna
happen
in
iterations,
but
I
think
we
need
to
be
really
mindful
of
where
there
are.
Decisions
now
will
potentially
have
implications
on
privacy
later,
and
this
is
gonna
force
us
to
come
up
with
new
ways
of
doing
things.
B
So,
for
example,
gathering
feedback
to
improve
the
product
it
becomes
non-trivial,
but
it's
important,
and
so
the
ideal
we're
working
towards
is
this
network,
where
everyone
has
complete
self
sovereignty,
the
freedom
to
have
private
conversations
and
free
trade
and
anything
that's
moving
the
needle
and
the
other
direction
it
should
be
challenged.
So
I
think
it's
important
that
we
feel
comfortable
as
an
organization
to
have
these
discussions
openly
and
challenged
decisions,
regardless
of
your
role
in
the
organization.
B
The
hierarchy
is
completely
irrelevant,
and
so
just
to
finish,
like
privacy
is
this
abstract
concept,
and
it's
also
worth
considering
the
first
core
audience
we're
targeting
before
we
scale
will
be
privacy,
conscious
individuals.
So,
if
we're
to
secede,
we
need
to
ensure
the
highest
standard
and
then
more
broadly
and
more
importantly,
like
you
really
don't
have
to
look
far
in
history
or
present-day,
to
see
examples
where
governments
or
certain
institutions
are
trying
to
suppress
certain
ideas
from
being
door.
B
Certain
crews
uncovered
and
it's
people
who
are
living
under
oppressive
governments
and
often
it's
journalists
or
academics.
So
as
soon
as
the
threat,
they
are
precisely
the
types
of
people
that
status
and
etherium
stands
from
power,
and
so,
while
we're
building
this
application
for
everyone,
I'd
like
to
encourage
us
to
try
and
always
keep
this,
this
group
front
of
mine
and
yeah-
that's
that's
it
for
me!
So
please
keep
up
the
amazing
work.
Everyone.
A
Awesome
thanks
a
lot
Carl
it
some
some
some
really
good
ideas
and
important
principles
behind
kind
of
why
status
in
the
first
places
so
we'll
move
on
to
to
as
we
are
regularly
doing,
which
is
looking
at
the
top
of
Bandi
contributors.
So
recently,
we've
got
these
two
Endon
were
and
cleanroom
who
were
our
top
contributors
and
there's
a
really
long
tail
of
people
who
have
also
contributed
and
we'll
go
into
more
detail
about
open
bounty
later
on,
and
we
have
two
new
contributors
have
joined.
A
We
have
Harry
who
joined
today
as
on
the
recruiting
side
and
Yahoo
who's
joined
on
the
DevOps
side,
and
we
have
17
roles
currently
open
and
we're
also
working
on
a
referral
program
for
people
who
are
not
core
contributors
to
try
and
engage
the
entire
community
to
get
involved
as
well,
so
that
that
should
be
coming.
That's
in
the
works,
hopefully
in
the
next
month
or
so
so,
look
out
for
that
and
yeah
we
have
17
rolls
up
and
so
so
check
them
out.
Welcome
both
Harry
and
Yahoo
people
update.
A
D
We
started
by
doing
program,
so
everyone
who
started
from
February
on
yes,
a
body
right
now
and
we're
going
keep
on
helping
the
bandits
with
doing
the
job
we
created
next
channels,
where
people
can
ask
a
question,
so
we
try
to
react
as
quick
as
we
can
and
China
were
joined
at
the
talent
TM
like
a
couple
of
weeks
ago.
Maximum
one
month
is
starting
to
create
a
really
pretty
website
that
is
going
to
contain
all
the
information
at
any
one
part
in
a
status.
We
need
to
have
any
links
to
everything
else.
D
D
Okay,
Ashley,
which
now
are
also
included
in
the
general
company.
Okay,
actually
care
else
in
terms
of
hiring.
As
you
already
said,
we
have
1704
also
help
share
in
there
and
sizes
we
move
on,
and
we
also
updated
the
company
description
and
all
the
job
description
coming
out,
which
is
something
that
again
China
and
I
think
Nabeel
work
done.
I
mean
that
was
it
for
me.
A
A
Se
are
must-reads
for
the
past
two
weeks,
so
check
them
out
and
these
these
will
be
sent
around,
and
if
you
want
to
follow
along
more
closely
there's
the
study
fundamentals
like
channel,
where
you
can,
you
can
jump
in
and
basically
read
and
watching
spend
hours
and
hours
kind
of
diving,
it's
tough.
So
these
are
the
tops
to
read
highlights
for
for
the
past
week,
the
last
two
weeks
I
think
we
have
marketing
now
Johnny.
E
Yes,
so
we
launched
status
incubate
last
Friday,
which
was
great.
We've
got
a
really
good
reception,
Ben's
gonna
be
hosting
a
session
this
week,
Friday
I
believe
so
just
like
walk
through
the
details
of
the
program.
So
anyone
who
wants
to
join
you
can
join
that
I'm
gonna
be
walking
through
a
workbook
where
we
have
all
the
details
laid
out
and
we're
prepping
materials
for
the
nest
for
the
next
status.
Projects
launch
now
so
stay
tuned
for
more
information
on
that,
it's
really
exciting
and
then
working
with
Tim
cannon
team
or
just
prepping.
E
All
the
paper
lunch
calms
working
closely
with
Chad
and
and
the
team
to
just
aligned
the
beta
launch,
with
all
of
our
comms
moving
into
production
on
videos,
tech,
walkthroughs,
branded
content,
a
bunch
of
really
exciting
stuff
they're
working
with
hutch
on
a
new
community
competition
taking
some
learnings
from
last
time
and
kind
of
apply
those
so
stay
tuned
for
more
information
on
that
as
well.
We're
still
kind
of
finalizing
the
details.
E
Kim
is
working
on
new
onboarding
flows
for
beta,
so
we'll
have
two
separate
flows
for
people
who
are
alpha
testers
and
then
anyone
net
new
for
beta
just
so
we're
refreshing,
comms
and
updating
all
the
communications
to
go
out.
We
are
prepping
materials
around
paid
pilot,
so
just
you
know,
prepping
creative
copy
and
gonna.
Just
you
know,
work
to
get
our
CPC
down
as
low
as
possible
ahead
of
production
and
then
some
exciting
is
any
and
team.
We're
planning
a
podcast.
E
E
Tons
of
events
coming
up,
obviously
we'll
be
at
ed,
Const,
arting,
May
3rd
will
be
at
this
warm
orange
summit
in
87,
so
I'll
follow
up
with
the
guys
who
will
be
attending
that
ethereal
will
be
with
the
art
project
team
and
the
true--but
team
here
in
New
York
on
May
11
will
be
at
the
hackathon
in
Buenos
Aires
at
Buenos
Aires
May
25th.
So
that's
really
exciting:
a
few
people
will
be
down
there,
I
think
Eduardo
and
II.
E
You
guys
will
be
and
then
yosik
is
getting
ready
to
plan
or
I
think
he's
sending
out
an
invite
for
anything
and
Clive
developers
workshop
and
to
June
that
will
be
in
Berlin,
so
stay
tuned
for
more
information
on
that
it's
gonna
be
really
great
and
then
status
of
bounty
working
with
martin,
virage
and
Eugenia
on
updated
email
templates
just
to
get
some
more
regular
coms
out
there
and
helping
them
on
the
updated
onboarding
flow.
And
then,
once
again
just
you
know,
content
Jared
I
saw
you
sent
an
email
or
a
note
out.
E
You
know
if
you
want
to
write
a
blog
post
about
anything
you're
working
on,
please
let
us
know
I
can
help
you
shape
the
message,
but
we're
just
looking
to
get
more
and
more
information
out
there,
because
there's
a
lot
of
really
great
stuff
within
within
the
team.
So
please
ping
me
and
then
you
know
there
was
a
session
last
week
with
Andre,
so
we're
trimming
that
down
editing
and
making
sure
it
looks
nice
and
then
we'll
send
it
out.
A
Awesome
thanks
a
lot
Jenny
and
I
lost
update
for
those
that
are
joining
for
the
first
time.
Is
that
if
you
want
to
follow
along
with
everything
that
we're
working
on
in
q2
just
check
out
this
bitly
link
to
look
at
our
you
know:
q2,
okay,
art
so
in
about
one
month,
we'll
do
like
a
media,
okay,
our
chicken,
but
for
now,
if
anyone's
interested,
when's
main
that
what
are
you
guys
working
on?
F
And
after
Oscar
stood
in
for
me
last
week,
we've
had
a
significant
increase
in
the
number
of
bouncies
I.
Just
really
want
to.
Thank
everybody.
That's
been
a
part
of
the
organization
and
part
of
putting
out
bounties
last
week.
If
you
go
to
the
next
slide,
you'll
see
that
we
had
a
record.
We
most
issue,
30
bounties
across
all
of
our
different
repos.
What's
particularly
interesting
is
that
there
are
a
number
of
bounties
in
our
ideas,
repo
itself,
which
is
pretty
cool,
that
we're
able
to
sort
of
bounty
arts.
F
Some
work
around
helping
us
actually
organize
better
to
the
wider
community
in
a
gritty
is
getting
very
meta
and
especial
sort
of
mentioned
goes
to
Nastia
for
issuing
six
bounties
herself
and
oscar
was
sort
of
in
second
place
for
fallen.
As
you
can
see,
we
sort
of
allocated
more
than
five
thousand
dollars
last
week
alone.
F
It's
the
open
source
ecosystem,
so
the
focus
now
for
us
will
be
making
sure
that
we
on
board
a
number
of
other
organizations
and
make
sure
that
those
two
blue
bars
which
shows
state
of
spins
in
dark,
blue
and
overall
spend
on
the
platform.
In
light
blue
begin
to
diverge
a
little
bit
more
than
where
they
are
currently,
but
thank
you
so
much
for
everybody.
That's
been
involved
and
please
carry
on
issuing
bounties,
because
this
is
how
we
build
the
community
horizontally.
F
A
Thanks
Andy
and
we'll
get
some
more
looking
bounty
updates
later
as
well
and
all
right,
so
we
have
a
first
launch
of
what
we
call
status
projects,
which
is
very
much
focused
on
trying
to
build
out
the
ecosystem
around
the
status
application.
So
this
is
around
app
development.
Anything
that
really
helps
people
makes
it
easier
for
people
to
create
fantastic
applications
or
tools,
utilities
inside
of
status,
so
I'll
let
Ben
kick
off
the
first
one
great.
G
Thank
You
Nabil,
hello,
world,
first
and
foremost,
we
are
live
so
status,
incubate
launched
officially
on
the
20th
of
April,
and
the
story
was
actually
picked
up
by
Forbes
and
he
was
followed
by
multiple
news
outlets
after
that.
As
of
this
morning,
that
numbers
gone
up
so
I
made
that
slide
yesterday,
but
this
morning
has
gone
up
to
24
applicants
in
three
and
a
half
days,
which
I
think
is
fantastic
and
we're
really
excited
about
reviewing
them
and
and
really
getting
lower
relevant
ones
into
our
program.
G
I
put
a
question
there
why
status,
incubate
I
think
that
bill
touched
on
it
now
it
is
part
of
the
projects
program
that
status
is
doing,
but
it's
really
a
play
for
a
commitment
to
excel
the
growth
of
the
web
3
ecosystem
and
that's
in
particular.
We
really
want
to
help
early
stage
projects
to
go
from
idea
to
implementation
in
the
fastest
possible
time
and
we're
gonna
do
that
by
leveraging
the
experience
that
status
has
as
an
organization
over
the
last
one
to
two
years.
So
what
are
we
gonna
be
offering
within
the
incubator?
G
G
Now
this
co-working
space
I
guess,
is
the
next
phase
of
what
we're
going
to
be
doing
with
satis
incubate
we're
looking
currently
for
office
space
in
zhuge,
Switzerland
and
Berlin,
but
we
hope
to
expand
that
out
into
multiple
locations
in
Europe
and
Asia
over
the
coming
months.
The
other
aspect
that
we're
working
on
is
really
to
build
out
the
team.
So
we
have
a
position
for
Berlin
at
the
moment
and
you'll
see
more
and
more
positions
being
posted
up
for
status
incubate,
as
the
program
starts
to
get
underway
but
exciting
times
for
us
here.
Awesome.
A
Thanks
a
lot
better,
if
you
have
any
questions,
just
there's
the
there's,
an
incubation
or
or
just
ping
been,
whichever
is
easier
great,
all
right
getting
into
the
development
side
of
things.
We
have
all
our
swarm
updates,
which
we've
been
doing
for
the
past
couple
weeks
and
we've
now
split
up
into
specific
sections.
So
we
have
a
swarm
update
on
how
we
run
swarms.
So
this
is
the
meta
swarm
section
Oscar.
You
want
to
give
a
quick
update
on
sure.
H
So
home
20
is
soon
but
formalizing.
The
process
we
use
around
storms
is
on
I
think
we
have
over
20
films
presenting
today.
That's
really
cool
to
see.
We
now
have
over
80%
of
the
corridors
are
covered
by
teams
that
are
self-organizing
in
swarms.
That's
one
of
the
big
things.
That's
at
the
last
few
weeks
an
address
that
we
now
also
have
a
static
site
sort
of
a
dynamic
index
of
old
ideas
in
the
state
you're
in
so
we
go
to
next
slide.
You
can
see.
H
Sorry,
one
more
I
flipped
around
one
more
so
this
is
essentially
just
like
before
you
had
to
update
the
manual
index
the
readme
file,
but
here
you
can,
instead
of
just
update
like
a
llamo
frontmatter
inside
the
files.
They'll,
hopefully
make
things
a
bit
easier
in
terms
of
working,
and
also
these
with
a
nice
index
that
our
community
used
to
see
what
we
worked
on
and
so
on.
H
If
you
could
go
back
one
slide
once
there
we
go
so
this
briefly
ad
has
been
lots
of
conversations
last
few
weeks
in
terms
of
when
their
swords,
torts
and
so
on.
So
just
like
your
very
ease
of
short
recap
of
some
things,
we've
found
out
to
discover
it,
so
this
one's
can
be
multiple
states
and
initially
they
sort
of
like
it
and
also
draft
process
where
people
chime
in
and
sort
of
give
feedback
on
ideas
and
sort
of
see.
H
If
this
is
a
good
idea
and
like
we
wants
to
work
on
two
so
on
and
a
swim
officially
starts
once
there
is
sort
of
a
pull
request
to
mark
it
as
being
in
progress,
and
this
is
sort
of
approved
by
sort
of
consensus
and
that's
sort
of
when
when
this
one
started
honestly
and
ideally
like
this
one
when
it
started
to
be
well
defined
and
what
that
means
is
the
Fuca
tiers
are
met.
So
this
would
be
some
kind
of
success,
metrics
and
execute
area,
so
success
metrics,
that's
usually
something
like
okay,
ours.
H
It's
some
way
of
measuring.
If
this
swarm
is
successful
in
what
it
would
sets
out
to
do
and
then
makes
it
here,
that's
more
of
a
instead
of
maybe
a
way
of
making
sure
that
products
we
work
on,
don't
go
on
forever,
but
that
is
sort
of
some
clear
stopping
point
for
them.
So
this
could
be
the
same
as
success
metrics,
but
it
could
also
be
that
we're
going
to
by
implementing
this
one
thing
and
then
we'll
we'll
measure
how
it
goes
and
if
it
doesn't
go
well,
then
maybe
we'll
try
a
different
approach.
H
A
different
swarm
and
then
the
second
thing
is
that
there
should
be
sort
of
clear
rolls,
so
this
should
be
at
least
three
contributors.
So
this
sort
of
it's
not
like
just
a
one
person
effort,
but
a
few
people
who
are
trying
to
achieve
some
larger
goal.
However,
it
does
is
sort
of
defined
and
also,
if
you're
used
to
facing
swarms.
It
should
also
be
some
kind
of
product
manager
or
UX
researcher
who
can
sort
of
look
at
things
more
from
this
or
the
user
point
of
view.
H
But
this
also
depends
on
this
form,
so
it
might
be
a
swarm
with
with
just
like
content
writers
or
there
might
be
a
swarm
with
DevOps
of
community
whatever
it
so
depends
on
the
nature
of
the
problem,
and
then
it
should
also
be
some
basic
plan
for
future.
So
the
next
coming
weeks,
or
something
like
that,
like
what
sort
of
work
what's
this
home
trying
to
achieve
and
then
when
a
swarm
ends,
it
ends
either.
H
H
So
this
is
just
some
example
of
how
you
can
use
this
so
so
in
general.
What
sort
of
forms
and
ideas
allow
us
to
do
is
that
we
can
be
more
openness
in
organization
and
involve
the
community
at
large.
So
these
are
some
examples
of
how
you
can
sort
of
update
update.
Your
idea,
like
you,
could
either
say
sort
of
like
Adam,
had
an
example
here
where
there
was
a
bit
of
a
Q&A,
that's
captured
and
that's
super
useful
for
people
who
refer
back
once
you
refer
to
either.
H
H
So
just
some
examples
of
things
you
can
do
to
just
make
it
more
make
your
idea
make
you
so
more
easily
accessible
other
people
as
that's
it
for
me
and
we'll
be
winding
down
this
room
and
it
will
be
sort
of
more
ongoing
support
from
now
on,
and
now
we
have
20
swarms,
there
will
be
something
there
actual
development
work.
Thank
you.
I
She,
okay,
so
update
for
last
week's
status.
React
desktop,
is
integrated
with
react,
native
nest
of
built
with
their
mod
and
it's
possible
to
send
and
receive
messages
in
child
javascript.
Engine
is
integrated
to
book
with
react
native,
desktop
iranian
of
sample
jessica,
parker's,
visible
issues
with
UI.
All
some
adjustments
will
be
required.
I
Changes
for
javascript
are
not
yet
emerged
in
the
master
of
nature.
Desktop
also
work
in
progress
to
extend
a
real
aim
to
support
desktop
platform
via
javascript
or
engine
and
goals
for
next
two
weeks
built
and
run
status,
react
desktop
in
production,
mod
makers
bundle,
distribution
for
status.
We
are
bestop,
really
real,
em
native
module
support
by
rare
native,
desktop
and
javascript,
and
also
Ubuntu
distribution,
build
of
old
status,
electron
or
best
of
wishes
based
on
the
reclamation,
desktop
and
gospel.
I
A
J
Hey,
so
quick
update
about
maintenance
effort,
mostly
about
security
updates,
so
we
finished
like
this.
The
company
finish
this
in
like
50%,
but
this
week
later
actually
later
today,
we
should
have
an
update
again
from
them,
so
should
be
about
7080
percent
and
we
also
extended
the
whole
effort
by
two
weeks.
It's
because
we
upgraded
the
version
to
917
and
they
were
howdy,
think
915.
So
it's
a
couple
of
changes
that
you
want
them.
J
Also
take
a
look,
oh
yeah,
which
we
decided
that
that's
the
way
to
go
so
the
whole
audit
is
extended
by
two
weeks.
It
was
supposed
to
end
today
actually
but
yeah,
it's
extended
by
two
weeks.
What
else
we
tested
main
net
by
the
test
team,
so
I
did
great
work
and
tested
messaging
and
also
sending
transaction,
the
apps
and
so
on
so
forth.
So
it
looks
pretty
good
and
there
are
a
few
I
guess.
J
One
back
right
now
related
to
that
this
on
the
app
that's
sending
two
transactions,
and
we
we
see
just
one,
but
it
looks
like
some
small
startup
fix
minor.
The
song
is
also
available
in
nightly
builds,
so
you
can
test
it
from
there
and
there's.
There
were
also
like
some
JSON
RPC
updates
for
bed
early
app
support,
that's
important
for
for
some
of
the
apps
to
actually
run
in
status.
That
was
also
fixed
for
the
next
two
weeks.
J
We
are
thinking
about
mine
and
it
alpha.
It's
not
decided
when
we
when,
when
this
is
gonna
happen,
it's
gonna
be
just
for
testing
purposes
not
for
normal
use,
but
yeah.
It's
not
decided
yet
when
it's
gonna
happen,
but
we
are
started
talking
about
this
yeah
and
that's
what
I
mentioned.
We
are
gonna
to
work
with
this
travel
to
to
audit
the
changes
between
0,
9,
15
and
0
9
17,
so
yeah
and
yeah.
J
A
K
Adam
moving
like
inks
and
make
amazing
progress
on
me
net
and
really
the
next
step
is
everyone
using
main
net
so
and
it's
been
doing
a
great
job
with
you
know
real
transactions,
real
taps
so
to
help
everyone
get
into
the
spirit
we'd
like
to
give
you
some
three
F
and
SMT.
This
is
for
internal
contributors.
K
J
He
was
main
contributor
and
it
like
the
90%
of
work
and
the
whole
go
team
review
to
all
the
peers
very
quickly,
so
that
was
pretty
pretty
good
stuff.
So
we
basically
removed
count
package,
which
was
like
the
source
of
many
issues
in
the
lake.
It
was
harder
to
just
follow
the
code,
so
that
was
that
was
not
necessary.
J
We
also
removed
unnecessary
interfaces
that
were
also
some
some
stuff
that
that
is
just
not
needed
and
made
reading
the
whole
stuff
horror.
So
so
that
happened
also,
we
got
units
as
Parata
Murano,
so
they
are
running
like
ten
times
faster
or
hora
lots
of
tests.
So
it's
huge
improvement
and
yeah.
This
one
was
completed,
so
it's
it's.
It's
finished
and
I
think
like
with
the
whole
code
base
around
status.
Node
in
status
quo
is
much
cleaner,
now
so
so
yeah,
so
that
was
that
was
pretty
quick
but
noticeable
just
one
lesson.
J
So
we
need
to
maybe
like
put
some
more
attention
to
what's
really
sinking
and
go
a
trim
because
there
are,
they
are
trending,
it
quite
a
lot
as
well,
and
if
we
do
not
hold
it
closely,
we
can
miss
some
nice
features
that
they
are
building
in
your
nice
tools
to
test
stuff.
So
yeah,
that's
what
we
need
to
do,
but
yeah
so.
K
Quick
update
four
core
metrics,
not
a
lot
of
production.
Work
has
happened
in
the
last
two
weeks,
but
we've
had
some
really
interesting
discussions
along
the
lines
of
Carl's
points
at
the
beginning
about
privacy
and
privacy
by
default
and
doing
the
right
thing
by
users
and
by
the
community.
So
we've
got
an
issue
to
improve
our
Austin
messaging
and
we're
also
working
to
open
up
the
data
from
core
metrics
and
share
that.
K
L
L
We
also
migrated
all
the
both
the
day
came
using
your
protocol
that
is
used
to
there
again
can
be
testing
the
application
we
set
up
the
baseline,
where
we
are
comparing
to
telegram
in
terms
of
the
Americans
consumption,
both
with
their
status
clients
and
with
the
status,
go
note
alone,
with
some
kind
of
a
small
native
proper
that
emulates
activity,
and
it
turns
out
that
the
grow
note
behaves
pretty
well.
So
it's
twice,
it
actually
is
quite
less
energy
than
telegram
so,
but
it
it
suggests
simpler
episode
and
then
thought
of
himself.
L
It
actually
is
three
times
it's
like
three
hundred
percent
of
eligible
computer,
so
we
started
using
Android
profile
and
no
piece
tool
to
figure
out
what
exactly
drains
energy
foreground
so
yeah
and
we
right
now
the
night
mates
are
also
tested
for
energy
efficiency.
So
the
goals
for
the
next
two
weeks
is
actually
to
figure
out
how
to
fix
the
issues
in
tennis
so
and
I.
Think
we
learned
that
yeah
in
the
background
mode.
L
I
Also,
we
had
a
more
broad
discussion
with
many
developers
from
go
side,
research,
team
and
clearer
to
him
about
the
protocol
itself
and
I.
Think.
The
lesson
is
that
this
forum
had
made.
We
made
a
lot
of
refactoring
in
the
code
and
that's
the
end,
a
lot
of
documentation
and
it
really
helps
collaboration
and
figure
out
or
we
can
even
improve
further
in
the
future.
H
Adam
Adam
is
on
his
way
from
over,
sell
do
this
quickly
for
him
so
discovery
v5
research,
the
cysts.
So
it's
there's
been
a
bunch
of
the
research
in
terms
of
enabling
this
and
you
know,
discovery
protocol
and
there's
been
a
lot
of
POS
merged
setup,
new
boot
servers
and
tested
on
real
devices,
and
then
for
next
two
weeks
it's
gonna
be
about
changing
some
stuff
in
the
UI
and
also
preparing
it
to
be
released
and
used
in
in
nightly
versions.
A
I
Okay,
so
96
this
forum
is
about
an
SNP
vase
spam
filter.
The
progress
for
the
last
two
weeks
have
been
pretty
good.
We
move
the
idea
from
draft
in
progress
after
having
defined
the
product
description,
matrix
and
exit
criteria.
We
also
initiated
a
UX
discussion
as
well
as
the
work
on
the
smart
contract
is
mostly
complete.
I
The
goals
for
the
next
two
weeks
is
having
the
initial
design
phase
completed.
The
emphasis
will
be
on
we're
framing
a
schematic
flows
on
the
smart
contract
and
we
will
work
on
adding
an
upgrade
ability
mechanism
to
support,
including
new
functionalities,
to
this
ID
and
the
future,
and
also
we're
considering
enable
this
as
a
test
feature
inside.
They
advanced
profile
settings
on
the
status
app
and
observing
how
many
users
activated
and
show
curiosity,
but
that's
not
yet
decided,
and
that's
it
awesome.
A
M
So
the
progress
about
it
was
mostly
discussion,
in
definition
out
one-sided
terms
of
the
contract,
gonna,
be
because
there
is
a
lot
of
questions
like
how
well
who
owns
the
fear
of
the
of
the
username
registration
in
the
case.
I
think
will
be.
Was
the
family
that
the
user
can
withdraw
this
fear
after
one
one
year
so
can
only
register
is
named
it
they
take
back
the
fee
and
the
goals
for
next
week
will
be
to
utilize
the
the
resolver
because
liking
DNS.
M
When
you
buy
a
domain
or
a
sub
domain,
it
doesn't
point
shoe
anywhere
in
in
ENS
I,
also
just
reserved.
You
just
registering
doesn't
point
to
anything.
So
you
need
to
point
the
public
encryption
key
for
sending
public
Church,
the
that
person,
the
others,
not
the
contract,
which
is
a
wallet
offering
the
entity
in
future.
The
ABI
that
will
be
the
ABI
of
the
the
entity
or
whatever
the
contract
is
pointing
to
that
also
can
have
descriptions.
M
M
Of
course,
our
users
would
be
able
to
do
what
they
want,
because
they
can
call
directly
contracts
they
own.
There
is
over.
Also
we
don't
do.
Is
we
don't
have
tests
in
the
poi
scripts
for
the
contracts
yet
so
this
should
should
be
done
the
next
weeks,
and
this
should
also
bring
some
basic
UI
to
directory
interacts
in
the
contracts
and
padam
in
there
singing
of
how
to
call
them
in
the
next
JavaScript
context.
M
This
flow
out
the
the
UX
flows.
We
actually
have
some
song
UX
some
wireframes,
but
but
that's
still
not
enough.
We
need
to
to
have
more
detailed
out
the
process
in
like
if
you
want
to
have
these
in
the
profiling,
because
user
can
set
the
profile
click
in
the
profile
there
is
that
approve
it
pretty
appropriately,
and
so
we
can.
We
want
to
this
registration,
be
there
so
register
user
name,
that
user
click
there
and
do
all
the
process
from
the
profile
pages
as
a
setting.
N
So
this
is
a
swarm
we're
starting
to
today
with
our
first
swarm
meeting.
The
goal
of
this
is
to
improve
the
current
state
of
personal
notifications,
so
that
people
are
able
to
get
more
context,
for
example,
the
the
notifications
regarding
the
message
at
the
actual
sender,
but
still
do
this
in
a
secure
way
so
that
we
don't
give
up
any
of
the
anonymity
in
the
process
we're
going
to
also
start
the
development
of
the
notification
server,
which
is
part
of
the
infrastructure.
For
this,
which
will
be
something
that
can
be
deployed
by
anyone.
N
O
A
O
O
There
was
so
written
some
Accord
on
go
side
for
this,
and
we
still
need
to
implement
changes
in
a
closure
part
of
application
order
to
use
it.
So
also
we
had
some
discussions
related
to
the
way
how
we
show
user
delivery
status
and
actions
which
user
can
make
later
regarding
and
when
he
see.
If
message
was
sent
or
wasn't.
If
a
user
wants
to
send
message
again
and
say
it's
sure
and.
O
K
I
can
I
can
jump
on
so
seamless
login.
The
last
two
weeks
we've
been
working
on
the
idea
and
getting
feedback,
and
we
had
our
kickoff
planning
meeting
for
the
next
two
weeks.
Alexander's
gonna
start
on
the
narration
research,
we're
also
looking
at
how
the
user
experience
will
be
affected.
The
output
of
the
first
iteration
is
just
research
currently
and
with
just
being
really
mindful
to
make
sure
there
are
no
security,
negative
implications
and
then
based
on
that
research
will
define
there,
the
next
iteration
and
hopefully
implement
like
touch
ID
or
biometric
login
updates.
P
Everyone
we
basically
just
kicked
off
this
forum
last
week,
so
this
isn't
going
to
be
a
very
long
update.
The
goal
of
this
forum
is
to
improve
wallet
experience
in
general
to
enable
to
enable
an
equal
UX
for
both
ether
and
various
types
of
tokens
in
both
wallet
and
in
chat
initiated
transactions.
We've
decided
to
actually
start
this
forum
by
by
getting
the
house
in
order
initially.
So
we
are.
P
Probably
the
most
the
most
important
ones
at
the
moment,
are
the
lack
of
transaction
history
for
tokens,
primarily
our
c20
ones,
and
the
fact
that
users
don't
really
get
the
whole
signing
phrase
verification
step.
So
this
is
most
likely
to
be
the
focus
of
who
our
step
steps
in
the
coming
weeks,
but
we
are
also
continuing
two
to
three
in
a
tool
to
go
through
other
bug,
reports
and
and
issues.
P
The
lessons
we
learned
so
far
is
that
users
aren't
really
transaction
transacting
in
the
app
and
that's
what
we
are
primarily
looking
to
fix,
so
nobody
is
sending
or
receiving
obviously,
transactions
to
status.
We
want
to
fix
that,
and
the
other
lesson
we
have
learned
is
that
getting
the
transaction
data
directly
is
quite
tricky,
which
is
why
everyone
else
is
just
pulling
the
data
from
either
scan.
P
I
So
the
goal
of
this
form
is
to
make
sure
that
the
pre
JavaScript
API
works
properly
in
status
and
all
requests
from
that
performance
is
expected.
So
our
plan
is
to
fix
all
on
all
known
issues.
This
is
a
web
free
and
cover
API
by
test,
and
the
progress
is
the
personal
sign
method
is
now
supported
in
status
and
it's
possible
to
sing
sign
messages
and
the
next
step
steps
is
investigate,
Docs,
which
have
web
free,
related
issues
and
also
fix
known
issues
related
to
contracts
so
yeah.
I
Q
I
hope
all
of
you
hear
me
well,
you
know
this
forum
is
about
reaching
our
core
objective
of
80%
of
functional,
automated
coverage
and
so
far
we've
redefined
our
tested,
which
is
which,
where
was
executed
against
each
nightly,
build
by
K
my
tester
using
manually
and
the
suit
is
redefined.
Now
it's
about
60,
unique
cases.
It's
added
to
this
trail
and
a
lot
of
cases
are
squashed
one.
Q
So
after
that
we
are
going
to
implement
new
process
for
nightly
build
testing
so,
instead
of
executing
each
in
a
case,
my
hands
so
will
be
a
resultant
Israel
with
results
of
automated
tests.
So,
instead
of
execute
instead
of
spending
two
three
hours
or
maybe
even
five
per
day,
a
and
two
testers
going
to
spend
two
searching
about
one
hour
to
review
test
results
to
mark
them
all.
Q
So
we
are
introducing
conditional
statuses
like
future
change
it
it's
when
test
fails
and
because
we
have
changed
behaving
product
calls
viola
in
order
to
track
the
issue
as
in
tests
and
all
statuses
on
which
is
passed
back
like
obvious
one.
So
yes,
it's
about
new
process.
It's
about
defiant
test
case
and
also
we
already
have
this
trail
report.
Q
R
Hello,
everyone
yet
so
yeah.
So
in
the
last
weeks,
we've
been
working
on
two
ideas
around
the
compatibility
of
the
mnemonic
wallet
and
the
way
we
generate
accounts
and
keys
and
with
the
idea
94.
Well,
this
one
is
more
about
being
able
to
export
your
status
accounting.
Another
external
wallet
software
and
the
idea
are
142-
is
the
opposite,
so
basically
being
able
to
recover
in
status
and
account
that
has
been
created
in
a
difference,
wallets
software,
and
so
the
code
itself
is
is
implemented
already.
A
C
Yeah
hello,
from
our
side
from
the
earliest
service
model,
we
made
some
progress
in
the
continuation
of
the
USC
development.
This,
the
new
ultralight
client,
which
is
has
pretty
good
ventures
right
now,
up
to
factor
ten
from
le
s,
the
the
consensus
moving
to
trusted
notes.
So
that's
pretty
good
and
the
developments
in
the
state
that
we
are
now
reviewing
it
all
salt
who
is
one
of
the
designers
behind
it,
is
reviewing
it
and
we
are
doing
the
final
polishing
and
for
the
micro
payment
solution
itself
for
the
subs
model
itself.
C
They're,
currently
comparing
different
micro
payment,
finishing
existing
solutions
like
radium,
microwaving,
swap
or
tough
Mukesh,
and
see
how
common
API
to
those
would
look
like,
because
the
idea
of
the
service
model
is
to
those
kind
of
common
avi
with
drivers
using
each
existing
micro
payment
solutions
so
that
clients
could
support
different
ones
and,
and
so
what
different
one
end
to
another
would
stress
all
of
the
beginning
protocol.
What
exchange
which
models
are
supported,
which
one
they
would
choose
or
what
should?
What
which
solution
they
want
to
take?
C
And
then
the
next
step
would
be
auctioning
process
for
the
services,
the
service
provider
in
the
area.
So
provider
has
some
ideas:
I,
for
example,
that
the
service
provider
says
it
has
1000
units
of
bandwidth.
It's
a
very
abstract
size,
and
here
the
already
started
observer
train,
which
is
done
and
the
Train
critic
which
are
not
yet
started
will
come
to
entry
to
say
they
are
monitoring
and
handling
eruption
process.
S
I
S
All
right
so
one
our
one
I
want
to
once
one
conversation
is
about
working
out
of
progress,
a
process
in
which
we
can
incentivize
community
members,
as
well,
as
quote
contributors
to
contribute
to
the
overall
development
of
status,
and
the
idea
was
to
run
experiments
on
what
kind
of
compensation
models
we
need
in
order
to
incentivize
a
broad
range
of
behaviors
these
yeah,
so
that
that's
the
general
idea
purpose
last
weeks
has
been
slow.
Unfortunately,
we
managed
to
define
the
two
compensation
models.
S
S
F
Metrics,
hey
guys,
just
a
quick
one
on
metrics,
so
this
is
one
of
the
things
that
came
out
of
our
okrs
for
a
pin
bounty
that
we
wanted
to
define
a
better
way
to
capture
our
metrics.
So
we
can
gauge
our
progress
and
see
how
quickly
we're
developing
and
how
much
recs
are
contributing
to
the
growth
of
the
ecosystem.
So
I
guess
this
swarm
started
two
weeks
ago
and
it's
around
being
providing
the
capability
to
be
able
to
define
those
metrics
that
we
want
to
capture
and
coming
up
with
automated
ways
to
capturing
it.
F
So
we've
set
up
in
a
base
and
created
queries
to
start
capturing
those
and
I
guess.
The
next
step
is
to
validate
the
results
and
come
up
with
a
little
bit.
I
guess
better!
You
eyes
in
terms
of
visualizing
those
numbers
over
time
and
as
well
as
making
the
data
obviously
available
to
everyone
to
the
community.
So
they
can
I
guess
see
the
progress
as
we
go
along
and
if
you
just
jump
up
to
the
next
slide,
I
thought
it'd
be
good
to
share
where
we
are
at
the
moment.
F
So
this
is
our
some
of
our
metrics
that
we've
captured
to
date,
so
we've
pumped
out
just
over
38
thousand
US
dollars
into
the
ecosystem
in
bounties,
just
on
the
1,400
registered
users
on
up
and
bounty
and
11
active
bounty
hunters
over
the
last
30
days,
and
what
we're
looking
at
is
by
the
end
of
q2
to
essentially
double
each
of
those
numbers,
so
over
70,000
paid
out
over
2,000
registered
users
and
over
20
active
bounty
hunters.
So
that's
what
we're
gonna
be
working
towards.
T
Great
okay
I
have
small
idea
about
inclusion,
because
we've
gotta,
since
that
is
open,
wanted
him
and
the
progress.
In
last
two
weeks,
I
made
one
soap
sharing
knowledge
session,
just
to
spread
our
knowledge
through
testing
him
and
the
in
automation,
terms
and
I
care
about
new
claim
check
can
exceed
two
feet
and
a
bouncy
seat,
and
also
my
the
bounty
was
a
full
description.
T
T
S
Here
we
go
again,
I
close
the
window
now
so
I
hope
the
sound
is
better
all
right,
so
I'm
boarding
is
about
improving
the
onboarding
experience
on
to
a
status
open
bounties,
so
everyone
can
get
to
use
open
bounty
and
not
be
frustrated.
In
the
last
week's,
we
mainly
identified
friction
in
the
existing
onboarding
process
and
started
working
on
a
new
sort
of
on
boarding
flow,
which
we
will
then
go
in
element
for
the
next
two
weeks.
S
We're
planning
to
finalize
that
flow
and
maybe
finish
the
visual
is
that
we'll
see
how
that
pans
out,
but
at
least
start
to
work
on
that
and
in
parallel
to
working
on
the
visual
design,
we
will
also
start
working
on
removing
the
need
to
be
whitelisted,
which
is
a
huge
blocker
for
new
users.
At
this
point,
lessons
learned
so
far.
I
think
that
this
has
been
repeated
many
times,
but
I
think
it's
worth
repeating.
One
more
time.
S
Writing
the
apps
or
applications
that
interact
with
aetherium
is
different,
and
the
latency
that
you
get
when
sending
transactions
and
dealing
with
transaction
tooling,
like
meadow
mask,
can
be
quite
different
to
what
people
are
used
to
when
designing
web
applications.
And
so
we
need
to
be
very
mindful
at
that
and
very
aware
that
we
are
designing
in
a
different
under
different
set
of
constraints
than
usual
product
designers.
You
could
say:
that's
it.
Cool
I.
S
Yeah,
here's
something
nice
to
look
at
this
is
the
revised
flow.
As
you
can
see,
it's
not
final,
but
if
you're
curious
I
want
to
take
a
peek
there's
a
bitly
link
at
the
bottom,
where
we
have
a
bunch
of
like
in
progress
notes,
it's
all
very
messy
like
if
you
don't
understand
it.
That's
probably
fine
but
yeah.
Just
if
you're
curious,
stop
by.
A
Cool
thanks,
I
think:
that's!
That's
all
we've
gone
a
little
bit
over
time,
but
that's
okay.
I
was
really
good
to
get
updates
from
all
the
all
the
different
teams
and
swarms,
and
this
is
just
a
lot
happening
and
I
don't
have
YouTube
open.
So
if
someone
wants
to
relay
any
questions
or
I
might
actually
pull
up
YouTube
it's
on
typing
furiously.
Oh.
S
F
K
That's
what
that's
one
of
the
things
we're
exploring
with
being
super
mindful
mm
touches
to
the
security
model
could
have
implicated
like
deep
implications,
and
so
the
first
iteration
will
just
be
on
on
the
research
and
further
iterations
might
explore
like
different
flows
around
that,
for
example,
a
user
might
be
able
to
set
their
own
log,
our
preferences
and
making
sure
we've
got
the
best
defaults
and
so
on
so
stay
tuned.
For
that.
I
Can
you
hear
me
yeah
yeah
yeah
those
questions
last
week
about
the
hardware
bullets?
So
basically
just
a
quick
update.
There
is
no
swarm
for
this,
but
will
great
one
this
coming
week,
the
current
swarm.
So
the
current
hardware
wallets
code
will
be
created
in
a
sort
of
light
version
of
the
product,
and
we've
now
decided
to
work
on
a
open
hardware
project
which
will
create
a
pro
version
of
the
hardware
wallet,
and
this
will
include
other
features
such
as
a
Bluetooth,
a
screen
and
a
button
in
the
same
sort
of
card
form
factor.
A
Awesome
thanks.
It
updated
alright,
as
I
was
saying,
if
there
are
any
people
who
have
questions
or
anything
just
jump
in
to
riot
and
plenty
of
people
that
can
help
and
world
kind
of
it's
all
interconnected.
So
when
you
hear
about
all
slack,
you
know
jump
in
slack.
It's
all
kind
of
the
entire
conversations
are
mirrored
in
right.
So
you
know
please,
please
come
join
us
if
you
have
any
questions
about
deaf
development,
but
what
we're
doing
and
yep
thanks
everyone
I
hope.
You
have
a
great
couple
weeks.