►
From YouTube: Status Townhall - May 7th 2018
Description
General
1:24 - Top weekly open bounty contributors
1:58 - New team members
2:38 - People update
5:21 - Study-Fundamentals
7:03 - Marketing update
11:07 - Weekly tech talks
Core Swarms
12:14 - Q2 OKR update
13:55 - Beta swarm
15:26 - #68-core-metrics
16:37 - #167-automated-testing
18:50 - #58-mainnet
Mobile App
20:07 - #83-energy-effecient
22:21 - #92-discovery-v5-research
Desktop App
24:26 - #34-react-native
Chat
25:56 - #87-new-protocol
27:55 - #99-confidence
29:23 - #86-push-notifications
30:49 - #96-tribute-to-talk
Wallet & Account
32:08 - #151-ens-usesrnames
35:14 - #170-wallet-improvements
DApps & Developers
36:38 - #101-extensions
39:52 - #146-status-go-sdk
41:11 - #154-support-web3
Research Swarms
43:37 - #67-nimbus
45:33 - #95-les-service-model
- 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 had some great updates about beta, all of our functional swarms, and more!
Any other questions please leave a comment or join our chat - https://chat.status.im
A
B
And
it's
just
it's
been
a
real
treat
for
the
status
team
to
be
here.
I
think
myself,
Nabil,
Ben,
RJ,
URI,
Eric!
We've
all
really
had
a
great
time,
and
it's
just
reminded
us
exactly
how
great
it
is
to
be
a
part
of
this
community,
and
you
know
again
why
it
is
that
we
get
up
each
morning
and
do
the
work
that
we
do
to
build
the
decentralized
future.
B
So
it's
really
great
to
see
them
continuing
strong
there,
and
the
update
on
this
team
is
that
some
people
will
be
shifting
their
work
to
focus
now
on
desktop
and
there's
a
kickoff
call
schedule
for
that
later
this
week,
but
sure
there'll
be
more
information
sort
of
coming
through
about
that.
Perhaps
in
our
next
few
town
halls.
As
always,
we've
had
some
really
interesting
contributors
join
our
team,
so
it's
the
best
Intel
got
on
the
go
team,
Daniel
Moffat
for
finance
and
operations
with
your
sin,
which
was
really
exciting
and
we
also
still
have
17.
B
So
we
are
actively
hiring,
particularly
in
the
design
area.
So
if
you
know
any
designers
or
other
people
who
might
be
well-suited
to
working
with
stainless,
as
always,
there's
that
referral
program
so
make
sure
that
you
pass
on
their
information
and
that
we
can
continue
to
get
the
best
people
around
the
world
involved
with
with
stones.
D
C
Now,
China
and
staff
have
been
working
on
collecting
all
the
helpful
information
in
one
location
and
compiled
it.
So
on
a
non-party
and
people
hand
brookside,
it
replaces
actually
all
the
previous
Google
Docs
the
site
is
very
helpful
for
reference.
Even
you've
been
contributing
to
status
since
a
while.
So
have
a
look
by
the
way
you
can
click
the
links
here
on
this
site
to
get
to
respect
these
locations.
C
I
recommend
you
it's
the
founder
statements
pie
chart
for
us
to
the
status
wiki
and
have
a
look
at
amazing,
mulching
guide
that
will
provide
you
with
a
deeper
understanding
of
decentralization
and
it's
all.
On
this
Hancock
site,
a
new
section
is
called
keeping
healthy.
It
provides
you
with
hints
on
how
you
can
limit
distractions
by
working
remotely
and
on
how
to
set
up
an
anti-economic
workspace
we'd
like
to
further
improve
their
book.
So
any
recommendation
on
how
to
enhance
it
is
appreciated.
C
You
might
have
noticed
that
at
Poly
was
added
to
slack
with
which
you
can
start
your
own
poles
and
experiment
is
all
going
to
use
poly
to
request
feedback
on
people's
performance
during
trial
periods
and
beyond.
Also
here,
please
let
us
know
if
you
have
any
comments
and
feedback
now
to
improve
response.
Cruciate
now
status
has
been
added
to
Questor
and
job
postings
have
been
integrated
with
twitter
you're.
Very
welcome
to
post
your
comments
about
status
and
last
or
as
specific,
especially
positive
ones,
are
appreciated,
of
course,
currently
up
17
job
openings
for
status.
C
For
that
I
would
like
to
promote
our
referral
program,
for
which
you
will
find
the
details
on
status
wiki.
So,
besides
posting
positive
comments
on
Glassdoor,
please
recommend
status
to
your
friends.
We
need
all
the
support
you
can
get
to
decentralize
all
the
things
and
build
the
best
interface
between
units
in
the
blockchain.
So
thank
you
very
much.
That
was
all
first
as
people
today.
B
So
then,
as
always,
we
just
gonna
go
with
some
study
fundamental
highlights.
So
there's
been
a
book
recently
written
called
radical
markets
that
been
selected.
A
really
interesting
review
of
there's
some
fascinating
ideas
there
from
harbor
to
taxes,
to
a
bunch
of
other
things
that
you
might
not
have
heard
about
before,
and
in
fact
the
PhD
who
wrote
this
book
presented
at
aircon
as
well.
B
So
it's
well
worth
the
time
that
it
would
take
to
read
it
and
then
the
other
two
links
that
I've
included
today
have
to
do
with
the
notion
of
token
curated
registries
or
TC
ours.
That
seems
to
be
all
the
rage
at
the
moment,
so
you
can
go
and
read
the
guy
who's
worked.
Most
of
them
is
a
guy
called
Mike
golden
from
add
chain.
B
Why
we
do
what
we
why
we
do,
what
we
do
so
yeah
dive
into
that
I
strongly
recommend
Simon's
silence,
link
as
well,
especially
if
you're
sort
of
sitting
up
late
at
night
somewhere
in
the
world.
Looking
for
something
interesting
to
read,
that's
well
worth
going
into,
so
we
have
a
marketing
updates
from
Johnny.
Is
he
on
the
call?
No.
E
E
E
Can
you
go
to
the
next
slide?
Andy,
perfect
I
thought
it
was
worth
taking
a
quick
look
at
some
of
our
social
media
metrics.
The
marketing
has
been
working
really
closely
with
our
community
managers
and
a
variety
of
contributors
to
sort
of
refocus
on
social
media
and
we're
starting
to
see
some
great
results.
Major
back
to
back
incubate
and
embark
launches
certainly
helped
drive
some
of
these
numbers.
E
So
if
we
look
at
our
month-over-month
social
metrics
on
twitter,
though,
acquisition
of
new
followers
was
actually
slightly
down
our
engagement
metrics,
which
are
many
ways
much
more
significant
or
all
up
by
double
or
triple
digits,
including
number
of
tweets
likes
clips
and
retweets.
The
largest
notable
increase
was
a
month
over
month,
impressions
which
is
up
205
percent
from
2.7
8
million
to
over
8
million,
which
is
fantastic.
So
thank
you.
Everyone
who
has
been
active
on
Twitter
on
Facebook
reactions,
page
and
post
engagements
are
all
up.
E
F
Right
so
regular
weekly
tech
talks,
we've
seen
some
really
good
talks,
last
few
weeks
from
Andrea
from
Igor,
from
Jared
on
wallet
and
mnemonics
and
key
structure
and
how
status
uses
go
node
and
so
on.
So
we
want
to
keep
it
up
and
every
week
we'll
have
essentially
a
Tech
Talk.
It
can
also
be
a
non
tech
talk
as
well.
F
This
is
a
signup
form
here,
and
the
topic
can
be
anything
from
some
kind
of
report
summary
to
some
user
research,
usually
research
to
some
tutorial
file
to
build
that,
maybe
something
on
smart
contracts
or
anything
you
can
think
of.
And
ideally
these
topics
also
live
streamed
and
published
on
our
YouTube
YouTube
channel.
So
we
assume
that
that
so,
if
you
insist,
don't
hesitate-
or
if
you
want
to
talk
more
about
it
from
ideas,
feel
free
to
reach
out.
G
Hey
very
quick:
okay,
our
update
I
thought
I'd
do
a
very
quick
recap
for
new
people
at
status,
as
well
as
the
community.
What
a
low
chaos
okay
eyes
are.
Basically,
our
North
Star
for
our
objectives
and
key
results
and
the
whole
company
got
together
in
Bangkok
and
core
in
particular,
did
some
like
sticky
voting
and
we
all
voted
on.
G
Our
p0
priority
is
to
make
messaging
reliable
and
we
set
the
key
result
to
have
send
delivered
ratio
greater
than
99%
right
now,
it's
around
ninety
percent,
so
we've
got
some
what
to
do
on
that
and
we
wanted
a
high
reliability
in
confidence
reflected
through
user
surveys
and
some
user
surveys
will
be
going
out
in
the
next
alpha
release.
Our
next
highest
priority
is
to
launch
the
beta
and
for
that
our
key
results
would
have
5,000
daily
active
users
and
highest
seven-day
retention,
and
so
that's
basically
it
quick
reminder.
We
have
our
top
priorities.
G
F
So
what
we're
gonna
do
is
we're
gonna
sort
of
like
one
thing
we
see
with
a
swarm
model,
and
so
on
is
that
we
have
a
lot
of
great
ideas
and
lots
of
interesting
products,
people
working
in
different
directions
on,
but
but
there's
been
a
slight
lack
of
focus
on
the
critical
path,
so
we're
gonna
address
that
and
absolute
biggest
thing.
That's
missing
now,
and
it's
not
good
enough
is
chech
liability
and
we
need
to
put
more
attention
to
some
more
focus,
and
it
will
be
a
call
tomorrow
for
core
to
discuss
this
better.
F
G
G
Reliability
and
we
had
a
great
third
party,
bounty,
contributor,
pak'ma'ra
and
he's
improving
or
she
is
improving
the
often
screen
and
that's
in
PR
and
it's
about
to
be
merged
in
the
the
future
were
hoping
to
fix
up
a
couple
of
the
mix
panel
bugs
discuss
data
sharing
and
see
how
we
can
open
this
data
to
everyone
and
we're
adding
a
metrics
opt-in
reminder.
And
so
we
need
to
finalize
the
the
copy
for
that.
B
H
Yes,
so
it's
about
extended
optimize
the
paestum.
Can
the
core
objective
is
to
reach
80%
of
functional
test
cases,
coverage
miss
optimator
tests
and
progress?
Last
two
weeks:
we've
added
tests
for
account
management,
the
abusive
transactions
chat
management
and,
right
now
we
have
around
60%
coverage.
Also,
we
were
at
this
trailer
reports.
/
nightly
build
and
right
now
not
more
than
10%
of
those
tests
are
failing.
H
Q10
issue
is
a
test
and
a
really
big
great
things
for
if
Kenya,
fighting
visual
validations
for
tomato
tests
right
now,
we
can
compare
user
pictures,
profile,
pictures
and
etcetera,
so
we
can
increase
our
coverage
and
we
have
insisted
so
future
goals
is
to
reach
80%
plus
test
average
width
and
to
introduce
new
nightly,
build
a
support
flow.
So
we
want
tested
manually
and
it
will
be
done
automatically
by
automated
test,
and
we
just
need
to
maintain
them
on
daily
basis.
H
Also,
we
are
going
to
address
start
session
logic
in
case
of
any
infrastructure
issue,
so
we
won't
get.
We
will
get
a
less
than
10%
files
from
issue
due
to
an
issue
this
test
and
the
lessons
learned
so
West
uma
is
where
the
optimistic
goal
day.
It
was
just
me
and
it's
already
in
the
past,
but
this
one
is
still
active.
Also
on
the
next
screen
we
can
see
is
a
an
example
of
the
trail
report.
We
can
see
one
test
by
the
right
side.
H
D
Hey
yep
I'm
here,
okay,
so
our
main
it
update.
So
today
we
have
the
final
readout,
I,
withdrew
and
they're
supposed
to
present
the
final
outcome
up
there.
How
did
so
far
in
the
previous
week
we
have
a
cold
them
and
there
was
no
major
issues
found
so
far.
There's
still
these
two
issues
that
been
found
a
few
weeks
ago.
So
so
that's
good.
D
Yeah,
we
also
identified
some
some
security
improvement
for
managing
chat
history,
as
some
people
may
don't
want
to
store,
and
they
certainly
want
to
clean
it
up.
So
it's
currently
not
possible,
so
that
was
that
was
what
they
found
as
well,
so
so
yeah
yeah,
the
the
the
next
thing
with
this
swarm,
is
to
fix
all
security
issues
that
were
related
to
the
to
the
audit,
and
basically
they're,
like
with
security
label,
involve
status,
reactance,
tatsuko,
repo,
so
so
yeah.
That's
it.
B
I
Yep
here
so
last
week,
we
set
up
the
environment
for
using
Android
profiler
to
find
the
CPU
related
issues,
and
we
also
documented
it.
It
is
a
body
of
knowledge
right
now
for
their
energy
efficiency,
because
it
requires
some
tweaking
here
and
there
possible
to
just
run
the
profiler
of
their
abilities.
Then
we're
working
on
the
one
of
the
things:
what
one
of
the
optimizations
to
do
dublicate
messages
on
the
go
side,
so
we
have
an
initial
version,
already
emerged
to
go
repository
and
there
is
one
update
that
needs
to
be
done.
I
Three
different
problems
right
now
and
while
testing
everything
we
found
out
that
there
is
a
sort
of
a
not
static,
but
then
any
performance
degradation,
the
more
messages
you
receive
in
a
group
the
more
time
it
takes
for
us
to
process
every
message
so
be
honest.
Parents
say
we
found
the
one
of
the
the
major
sort
of
reason
for
that
and
began
is
not
working
to
fix
it.
So
for
the
future,
you
want
to
actually
finish
go
side,
my
favorite
application.
Then
this
reason
why
the
performance
was
degrading.
I
This
time
was
message
grouping
by
David
understand.
So
we
do
to
Matt
a
more
efficient
algorithm
for
that
and
then
we'll
continue
researching
what
the
whole
pot
later.
So,
yes,
that's
previously
backgrounds
model
few
other
problems.
We
are,
if
you
want
by
some
numbers,
so
we're
comparing
to
like
messenger
some
like
Android.
We
are
in
two
hundred
percent
battery
consumption
in
background
and
around
300
in
point
down,
so
we
still
want
to
first
seek
the
foreground.
B
D
D
They
are
not
really
supported
in
the
status
react,
but
they
can
be
and
they
bring
some
useful
information
about
the
discover
status
so
how
many
peers
you
have,
and
so
on
so
for
the
future
goals,
so
improving
monitoring
of
this
of
discovery
version
5,
because
we
right
now
I
struggle
with
making
sure
that
everything
is
fine
when
you
connect
the
to
the
cluster
through
this
protocol
and
also
tested
with
other
networks,
because
that's
pretty
easily
possible,
but
we
haven't
really
looked
into
other
networks.
So
so
that's
that's
it
I
haven't
put
it
yet.
D
B
J
So
react
native
cuties
on
update.
We
achieved
successful
production
built
of
status,
react
desktop
based
on
Kitty
framework,
amicus
bundle
and
Linux
package
of
desktop
F
are
available
for
internal
test
runs
a
javascriptcore
integrated
with
react,
native
desktop
tested
on
Runyan
with
all
status
react
latest
electron
source
Asst
react
native,
desktop
built
on
Windows
start
to
see
our
desktop
built
on
Windows
as
well.
I
believe
I,
finish
Runyan
of
atmosphere
desktop
on
Windows
today,
so
ever
running
on
windows
also
and
future
goals.
B
A
Hi
yes
I'm
here
so
for
the
new
protocol.
Basically
it's
it's
done
since
few
weeks
already,
but
we
kept
the
swarm
open
in
order
to
work
on
benefit,
bug,
fixes
and
group
chats,
but
the
group
shots
are
now
out
of
scope,
and
so
basically
not
the
swarm
is
about
to
close,
and
we
I
think
we
reached
the
success
matrix,
maybe
not
less
than
10
megabytes
a
day
but
still
quite
close
and
way
less
than
it
used
to
be.
So
that's
a
good
thing
and
lessons
learned
so
far.
A
B
Eric
yeah,
in
addition
to
the
battery
consumption,
the
fact
that
we're
sort
of
so
far
down
on
data
is
just
incredible.
It's
one
of
the
things
which
gets
the
greatest
feedback
when
you're
doing
presentations
at
conferences
like
Ed
Khan,
have
moved
from
around
10
gigs
a
day.
It's
roughly
10
megabytes
is
just
an
incredible
performance
increase
and
that
tends
to
impress
people
a
lot
so
really
really
well
done
so
ID
7,
it's
a
great
swarm
and.
A
How
so,
yes,
ok,
so
progress?
For
last
weeks,
we
created
in
the
poetry
server
for
the
next
release.
We
implement
intimately
on
nightly,
builds,
but
actually
not
a
nightly,
but
all
development
and
nightly
builds
right
now
and
current
stats
about
90%
delivery
rate,
and
we
have
the
pull
request,
which
will
help
us
to
distinguish
Knightley's
from
other
builds,
because
right
now,
like
a
local
development,
can
have
some
impact
on
this
numbers,
which
can
be
a
problem.
A
A
K
Yeah
so
last
week
we
last
couple
which
we
started:
the
implementation
of
the
push
notification
server.
This
is
using
the
work
of
another
suam,
which
recently
started,
which
is
the
go
SDK
and
it's
progressing
well.
The
client
development
unfortunately
didn't
starts
due
to
other
swarms
that
our
higher
priority
and
we're
finishing
and
needed
the
help
of
our
closure
resource.
But
hopefully,
during
the
next
couple
weeks,
we'll
have
that
started.
K
The
push
notification
server
itself
is
a
four
week
effort
so
eventually,
hopefully
in
the
next
couple
weeks,
we'll
catch
up
with
those
two
efforts,
the
yeah.
The
lesson
learned
is
just
that
it
was
a
great
coincidence
to
have
the
go.
Sdk
starts
because
it's
greatly
simplified
having
this,
you
know
we're
both
consumers
and
we're
giving
feedback
to
the
go
SDK
swarm,
and
it
also
allowed
us
to
remove
that
offload
a
bit
of
that
work
to
another
swarm,
yeah,
good
cool.
B
L
So
in
the
last
two
weeks
there
was
lots
of
healthy
discussion
in
our
channel,
which
resulted
in
the
design
for
both
the
chat,
requester
and
recipient
screens,
creating,
besides
that,
the
prototypes
that
show
the
flows
forward
of
these
rows
and
also
the
contract
was
simplified
quite
a
lot,
with
a
big
chunk
of
the
logic
being
handled
now.
The
message
signatures
this
translates
into
a
contract
which
is
cheaper
to
use,
while
still
fulfilling
the
requirements
for
this
idea.
L
In
addition
to
all
that,
we
also
got
two
new
participants
in
this
work.
Arrogance
early
and
the
goals
for
the
next
two
weeks
are
to
work
on
the
implementation
of
this
idea,
along
with
creating
boundaries,
so
the
community
may
participate
in
to
building
this
idea
and
that's
it
for
now.
Thank
you.
Yeah.
B
It's
amazing
work.
I
strongly
recommend
anybody
watching
this
call
to
go
and
take
a
look
at
our
contracts,
repo
and
github.
You
can
explore
the
various
different
branches
there.
There's
been.
Some
really
really
amazing
work
by
Richard
and
Ricardo,
and
the
new
signature
scheme
in
distributes
a
talk.
Stuff
is
just
unbelievable.
So
really
really
nice
work.
There
guys
wanted
in
a
can
swarm,
so
151
ENS,
usernames
Ricardo.
Are
you
on
the
call.
M
M
So
there
is
some
some
new
deploy
scripts
on
the
using
embark.
The
test
scripts
are
still
not
good
enough.
They
should
be
simple.
Truth
finish:
the
delay
delay
release
the
release
of
the
names
are
now
implemented.
We
have
this
fixed
time
of
one
year
to
release
and
also
this
release
was
implemented
in
a
way
to
protect
the
user
terms
in
the
contract.
So
whatever
you
deposit
that
locket
SMT
in
the
contract,
then
you
you
know
that
no
one
can
take
that
from
you
whom
I
ask
you
are
wit.
M
M
It
follows
the
move
of
the
domains
and
the
move
of
the
subdomains
so
which
we
have
a
new
contract
that
implements
new
features
that,
in
s
request
the
parts
then
they
you
know,
domain
can
remove
it
and
whoever
wants
to
move
together
can
can
move
moved.
The
subdomains
can
also
move
to
this
new
domain,
but
this
movie
is
not
needed
because
the
user
also
owns
the
subdomain.
M
B
Is
cool?
Thank
you
so
much
Ricardo,
yeah
well
I
was
speaking
at
length
of
Alex
fundus
under
here
dead
khan,
and
he
was
just
mentioning
the
fact
that
you
two
had
had
a
discussion,
and
two
days
later,
you
presented
him
with
a
fully
implemented
version
of
the
contract
and
then
two
days
after
that,
another
contract
that
had
been
optimized
for
gas
and
stephanie
was
just
like
me,
blown
away
by
the
quality
of
the
work.
B
G
I
couldn't
read
it
for
Gore
and,
if
he's
not
so
the
last
two
weeks,
Goran
is
admin
and
the
team
is
at
it
in
ESC,
20
token
transfers
and
transfer
history.
This
was
a
big
blocker
for
beta
for
us,
because
you
couldn't
actually
see,
for
example,
S&T
transfers
in
your
transaction
history
and
there's
been
several
fixed
bugs,
including
some
very
cool
bounties
that
we
weren't
expecting
that
got
picked
up.
Future
girls
were
working
on
a
proof-of-concept
for
sending
tokens
from
chat.
G
That's
one
of
the
features
that
have
been
missing
and
adding
maenette
as
an
option
to
the
alpha
releases
and
lessons
learned
so
far.
We
need
to
address
atheria
user
experience,
issues
to
some
extent.
So
that
means
not
only
do
we
have
to
educate
users
about
how
does
new
status,
but
we
have
to
educate
about
etherium
concepts
and
gas
prices
and
other
things
that
might
not
be
completely
intuitive
for
new
users.
B
N
So
I
shared
two
two
links
in
the
summary
on
the
right-hand
side,
so
you
can
take
a
look
and
eventually
I'll
provide
some
feedback.
So
right
now
we
are
still
on
the
MVP
part
of
this
forum,
so
when
it
has
been
split
into
two
parts
in
the
first
part,
the
one
we
are
currently
implementing
is
focused
on
just
validating
the
concept
and
making
sure
that
we
can
actually
implement
them,
and
we
are
doing
this
first
using
web
technologies
just
to
simplify
maximum.
N
So
one
thing
that
we
learned
doing
this
process
is
I
think
it
makes
a
lot
of
sense
to
to
try
to
sync
and
in
detail
swamp
upfront
and
spend
some
time
trying
to
to
just
understand
what
what
we
want
to
do
and
and
in
detail
with
what
we
plan,
even
if
it's
out
the
scope
of
this
WOM
just
because
it
gives
more
context
and
and
a
clearer
picture
of
what
we
actually
want
to
do.
Thank
you
thanks.
B
Gillian
yeah
I
think
it's
worth
just
re-emphasize
in
that
again,
because
we've
got
some
amazing
documentation,
that's
been
written
before
even
any
code,
and
just
one
of
the
cool
things
about
getting
to
work
at
statuses
that
we
do
have
the
opportunity
to
think
long
term
and
quite
strategically
about
the
things
that
we're
doing,
especially
in
terms
of
how
to
avoid
local,
maxima
and
Julian
is
an
expert
at
that.
And
it's
it's
really.
It's
inspirational
to
see
just
how
much
thought
has
gone
into
you
know,
thinking
about
how
we
can
extend
status.
B
O
I'll
actually
speak
to
this
one,
and
so
the
status-quo,
sdk
swarm
is
also
a
new
swarm.
It
kicked
off
just
after
our
last
townhall,
and
the
objective
of
this
swarm
is
to
create
a
library
that
will
make
it
easy
for
go
developers
to
interact
with
the
status
messaging
system
to
build
their
own
chat
BOTS.
O
So
the
team
has
actually
made
some
really
great
progress
in
the
last
two
weeks
and
as
of
now,
a
go
developer
should
be
able
to
set
up
the
SDK
there
for
interact
with
the
status
node
login
create
an
account
first
for
their
for
their
bot
login
and
also
joining
public
channels
and
interact
in
public
channels
in
the
next
couple
of
weeks.
The
goal
is
to
add
support
for
contacts
and
in
contacts,
and
also
for
one-to-one
and
group
chats
private
chats.
O
As
was
mentioned
in
the
push
notifications
update
from
Pedro.
There
is
a
really
nice
overlap
between
these
two
swarms.
We've
discovered
that
push
notifications
will
be
able
to
rely
on
the
SDK
to
interact
with
the
status
messaging
system,
and
so,
additionally,
we're
going
to
be
building
in
some
specific
support
for
push
notifications
into
the
SDK.
O
I
Yeah,
so
essentially,
what
we
did
in
these
two
weeks
is
that
we
are
developing
with
three
filters
for
our
PC
mode
because
obviously
like
into
our
they
shrink
on
trend
their
API
quite
a
lot
since
we
started
using
them
so
right
now
they
don't
allow
creative
filters
on
their
side,
well
reasonable
solution,
but
therefore
we
have
to
reemployment
them
on
our
own
size.
So
that's
what
we're
doing
now,
then.
I
Yes,
sinkholes,
are
being
in
progress
because
right
now
my
only
support
18
folks
would
call
back
in
backstreet
and
sinkholes
are
supported
and
if
they
need
them,
we
also
had
some
troubles
with
the
cryptic,
tedious
I.
Remember
that
they
were
trying
to
figure
out
which
kind
of
browser
work
we
were
using,
and
then
it
could
be
that
little
history
behind
this
metal
mask
they
for
some
reason
use
the
normal
API
name.
But
what
for
the
parameters?
I
I,
don't
know
why
they
did
that,
but
they
did
they
do,
and
then
there
is
right
now
there
is
some
confusion
and
some
D
apps,
because
there
is
one
method
called
personal
sign
and
in
almost
everywhere
you
get
from
as
its
first
parameter
and
then
what
you
want
to
sign
as
a
second
and
then
in
meta
mask
please
for
some
reason:
flip
them
and
since
Minamata
super
popular
than
a
lot
of
D
F
try
to
figure
out
the
cases
run
in
Merrimack.
We
try
to
flip
the
parameters
down
and
then
yeah.
I
We
had
some
troubles
with
that
as
well.
So
for
for
the
future,
we
want
to
finish
the
web
through
filter
support,
simple
supports,
and
we
also
want
to
add
a
white
piece
of
web
through
method
that
is
available
for
the
web,
like
the
apps,
because
right
now,
for
instance,
the
DF
can
just
disable
all
the
messaging
by
setting
chrome
proof
of
work
for
the
whole
set
us
up.
So
we
sort
of
protect
this
area,
and
you
know,
obviously
we
need
some
kind
of
a
set
of
test
cases,
for
which
kind
of
API
is.
I
A
There,
basically,
our
team
is
too
busy
building
many
of
these
building
blocks
that
are
required
for
antietam
implementation,
libraries
for
big
working
with
big
integers,
with
at
least
a
pretty
cool
working
rivalry,
for
name
for
the
immunization
of
processes
for
hemming
and
tear
on
key
files,
and
so
on
and
we'll
be
moving
on
to
building
all
of
this.
Combining
all
of
these
building
works
together
to
create,
finally,
a
Nimbus,
complete
Nimbus
France
that
we
work
as
a
complete
item
implementation.
A
This
would
be
our
go
for
the
next
two
weeks:
images,
even
initially
it
should
support
running
from
all
the
desktop
operating
systems
like
Linux,
Windows
and
Mac
OS,
and
support
for
running
on
mobile
operating
system
will
come
later.
We
are
also
sending
will
be
announcing
our
first
bounty,
so
if
there
are
any
min
developers
in
the
audience,
I
invite
you
to
take
a
look.
A
The
open
body
website
in
the
next
few
days
for
various
small
tasks
in
enhancing
some
of
this
language
that
we
have
provided
and
as
for
lessons
learned
so
far,
basically
I
guess
we
never
expected
that
the
team
will
be
spending
so
much
time
in
improving
the
name,
language
in
the
ecosystem
and
developing
so
much
basic
libraries.
But
we
are
proud
that
we
take
time
to
establish
very
high
standards
of
quality
quality
in
the
project
and
we
do
not
like
to
take
compromises
so
that
that's
why
we
invest
so
much
time
into
this.
A
Bring
out,
we've
managed
to
deploy
you'll,
see
comparable
server
like
find
compatible
server
on
my
net,
and
we
built
two
versions
of
real
applications,
so
with
ultralight,
client
and
West
Point
to
compare
it
with
in
flora.
They
go
for
next.
Two
weeks
is
to
deploy
two
more
service
and
to
test
real
photo
ID,
find
consensus
and
compare
will
try
I
until
the
infra
version
of
our
application.
It's
all.
B
B
Cool
that's
the
problem.
We
can
always
answer
YouTube
channel
questions
there
in
text.
As
always,
if
you
have
further
questions
you
more
than
welcome
to
join
us
in
check
that
status,
that
I
am
and
ask
us
anything.
We
generally
quite
a
responsive
bunch,
and
just
you
know
from
me
personally,
send
some
love
to
your
sick
is
kind
currently
Onion
Routing
his
way
across
Europe
to
get
to
Slovenia
for
that
swarm
conference.
B
You
know
it
is
worth
just
mentioning
again
how
importance
and
motivational
actually
meaning
the
people
in
person
that
are
working
on
these
protocols
and
tools
can
be.
It's
been
a
fantastic
week
in
Canada,
going
through
ed
Khan
and
ERP
zero
before
its
and
a
web
3
UX
and
conference
after
its
and
it's
just
it's
a
it's
really
great
to
you-
know,
meet
people
in
person,
but
be
it's
also
fantastic
to
see
how
far
ahead
status,
often
years,
particularly
on
our
UX,
some
of
our
design
and
just
the
way
that
this
organization
works
and
thinks.
B
So,
thank
you
to
everybody,
who's
involved.
With
that
thing
all
the
swarms,
it
really
is
inspirational
to
see
the
stuff
just
self-organized
and
produce
the
results
that
it
has
been
producing
so
have
a
fantastic
week
and
I'm
sure
that
we'll
see
you
all
in
slack,
going
riots
and
feel
free
to
ask
any
questions
there
that
you
have
thanks
and
tons.