►
Description
Jarrad Hope presents Status, an open source Ethereum light client for Android & iOS at Devcon2 in Shanghai.
Find out more: https://status.im. We'd love to hear your feedback! Join our Slack community: http://slack.status.im/ or follow our Twitter for updates: https://twitter.com/ethstatus
A
A
But
before
I
do
I
kind
of
want
to
talk
about
my
my
personal
motivations
and
why
I
believe
in
aetherium
see
in
recent
history,
like
you,
can
see
many
cases
of
like
economic
collapse
by
institutional
failures
and
large
populations
of
people
who
have
no
access
to
dependable
legal
technologies.
And
of
course
these
are
complex
problems
but
I
believe
they
stem
from
our
inability
for
us
to
adapt
socially
fast
enough.
A
But
what
if
we
could
create
digital
spaces
and
where
we
can
experiment
with
new
ideas,
new
economic
models,
new
policies
and
new
ways
are
socially
organizing
social
systems
as
operational
closures,
in
which
we
have
unprecedented
access
to
the
entire
economies,
history
down
to
the
very
transaction
level
and
the
social
contracts
that
bind
them.
What?
If
we
can
then
use
this
data
to
discover
something
new
and
then
deploy
it
globally
within
30
seconds
or
less
for
anyone
to
use
voluntarily?
A
That's
the
kind
of
world
that
I
want
to
live
in,
but
none
of
that's
really
possible
until
we
start
getting
aetherium
into
the
hands
of
people
show
of
hands
who
has
a
smartphone
with
them
right
now,
there's
more
than
more
than
that.
Now
keep
keep
your
hand
up.
If
you
don't
have
your
laptop
with
you
right
now,
right
so
smartphones
and
now
the
new
personal
computer
in
2014,
they
Dover
take
overtaking
desktops
in
users
and
now
we're
seeing
that
more
time
is
being
spent
on
them
and
on
desktops
I'll
do
this
information.
A
We
decided
to
bring
a
theorem
to
Android
and
iOS
last
year
with
a
higher
end
goal
of
recreating
the
mist,
dab,
browser
experience
on
mobile
devices,
but
as
we
were,
developing
I
started
looking
at
my
own
behaviors
and
how
I
was
using
my
own
smartphone
and
I
realized.
I
wasn't
really
browsing
the
web,
except
for
when
I
was
at
restaurants
or
I
was
at
home
sitting
down
with
Wi-Fi
and,
to
be
honest,
the
web
is
a
little
tedious.
A
It
turns
out
that
we
are
social
creatures
and
we
love
instant
messaging
and
social
networks.
In
fact,
I
have
compared
to
browsers
instant
messengers
have
three
times
the
amount
of
monthly
active
users
and
a
third
of
all
time
spent
on
smartphones
is
actually
inside
an
instant
messenger.
It
seems
to
me
if
we
want
to
create
the
biggest
surface
area
possible
for
accessibility.
This
is
a
really
good
candidate,
but
then
I
started
wonder
what
would
a
theorem
look
like
as
an
instant
messenger?
A
A
Under
the
hood
status
actually
runs
a
full
implementation
of
Go
ethereum,
with
the
light
client
and
whisperer
protocols
enabled
on
top
of
whisper.
We
build
our
instant
messenger
and
we
actually
do
our
own
key
management
and
transaction
management
to
daps.
It
all
looks
pretty
much
the
same.
They
still
have
access
to
web
3
and
a
local
JSON
RPC
server,
and
we
also
introduce
a
new
kind
of
extensibility
to
adapts,
which
is
more
integrated
with
chat
and
can
render
with
us
with
a
subset
of
react,
native
and
I'll
get
into
those
in
a
moment.
A
So
when
you
first
run
status,
you
meet
your
first
autonomous
entity.
Console
console
is:
is
there
really
to
help
you
with
humble
onboarding,
to
educate
you
on
how
to
use
the
basic
features
of
status?
It
also
is
also
there
to
set
up
your
first
account.
So
here
you
can
see
our
request
message
and
it's
asking
us
to
tap
on
it.
So
let's
do
that
here.
A
Now
a
message
is
sent
and
status
has
generated
a
master
key
based
on
and
given
us
our
passphrase.
Now
we
also
have
the
passphrase
in
multiple
languages,
including
Mandarin,
with
this
master
key,
we
derived
two
child
keys,
our
main
account
and
the
sub-account
root,
with
the
main
account.
We
actually
do
something
a
little
interesting
and
something
you're
not
really
supposed
to
do
with
whisper.
We
actually
inject
the
keeper
directly
into
whisper.
This
gives
us
an
interesting
property,
and
not
only
you
can
transact
with
that
public
key,
but
you
can
also
chat
with
it.
A
This
becomes
your
handle
in
status.
Of
course,
there
is
a
trade
off
with
address
hash
security,
so
we'll
probably
end
up
doing
some
automated
management
with
any
funds
that
are
in
that
into
a
sub
account
in
status.
Daps
are
first-class
citizens.
That
means
they
look
and
feel
just
like
your
friends
at
the
top.
A
Here
we
have
our
default
DAP
wallet
and,
let's
say
a
tap
on
in
and
have
a
look
wallet,
is
an
HTML
and
JavaScript
app
just
like
what
you
would
find
in
mist
or
meta
mask
and
it
pretty
much
all
of
those
would
work.
The
same
within
status,
this
is
actually
rendered
with
a
special
built-in
command
that
turns
the
text,
input
field
into
something
like
an
address
bar
and
it
renders
a
webview
in
the
suggestions
area.
A
A
Chat
DAPs
integrate
with
status
a
little
more
closely
using
a
chat
API.
They
can
create
new
commands
and
new
message
types
here.
We
have
an
example
with
example,
dab
and
here
they've
sent
us
a
request
message
and
just
like
console
did
and
we'll
get
to
that
in
a
moment,
but
in
the
bottom
left
next
to
type.
There
is
a
command.
This
icon,
you'll
notice
that
has
a
little
blue
dot
on
it,
indicating
that
there
is
a
pending
request
somewhere
in
the
chat
history.
A
A
A
A
So
we'll
do
that
now
we're
on
the
second
parameter
from,
and
this
is
using
context
context
self
as
the
default
value,
which
is
us
so
we'll
just
do
that,
and
here
is
the
third
one
amount
the
code
is
emitted
because
they
couldn't
fit
on
the
screen
but
notice
how
this
the
type
is
number.
So
it
changes
the
keyboard
and
in
this
case
the
validator
has
returned
some
custom
user
interface,
which
is
a
slider.
In
this
case
now,
we've
filled
out
all
our
parameters.
We
can
hit
Send
once
this
has
happened.
A
The
message
actually
goes
into
a
staging
area.
The
preview
handler
is
called
and
the
preview
handler
defines
and
what
the
the
chat
message
is
going
to
look
like
now
when
we
press
send
after
the
user
is
reviewed,
it
we're
going
to
call
the
method
of
the
commands
handler
function,
and
this
is
where
the
meter,
the
the
commander,
actually
happens.
In
our
case,
we're
going
to
end
up
calling
web
3
send
transaction.
Let's
see
what
happens.
A
A
Now
I
want
to
talk
about
requests
and
responses.
They
allow
us
to
daisy-chain
commands
and
even
pre-fill
parameters
for
per
hour
to
friends
to
fill
out
commands
as
well.
They
allow
us
to
have
more
rich
in
our
interactions
and
more
meaningful
conversations.
You
can
imagine
in
the
future
we're
going
to
have
multiple
gaps
being
used
in
modular
fashion
and
they
can
be
daisy
chained
together.
In
this
case
example,
that
would
have
ran
a
command
whereís,
which
would
have
made
a
status
request
for
for
our
response,
and
the
target
is
the
first
parameter.
A
A
A
In
status,
gaps
can
be
added
into
group
chats
this
cause
a
mild
dilemma
and
that's
with
daps.
The
codes
are
executed
on
each
participant's
device.
That
means
we
need
to
enable
permissions
for
each
command
for
everyone
to
use
it
within
the
chat
context.
This
is
as
simple
as
going
to
the
DAPs
profile
and
tapping
on
the
commands.
A
A
A
A
A
A
Also
stay
tuned,
we're
working
on
a
github
issue,
bounty
BOTS,
where
you
can
assign
bounties
to
github
issues,
and
then
they
can
be
paid
out
to
contributors
on
successful
pull
requests.
The
current
implementation,
little
naive,
so
yeah,
where
we
give
us
it
like
a
month
or
two
on
that.
One
yeah
and
thank
you
so
much
I
hope
everyone's
using
status
by
DEFCON,
3.