►
From YouTube: Town Hall #65 August 31st 2020
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
B
Thanks
for
the
intro
terry,
hey
everyone
nice
to
be
here
and
for
people,
ops
updates.
We
have
two
anniversaries
today,
congrats
to
jason
for
being
with
the
team
for
more
than
three
years,
a
huge
thank
you
from
status,
jason
dmitry's
first
year
with
status,
big,
thank
you
for
dimitri
as
well
for
being
an
integral
part
of
of
nimbus
team
and
more
brilliant
people
have
joined
status
since
our
last
call.
So
we
have
new
joiners,
ruslan
maho.
B
Ruslan
welcome
to
the
team.
Ruslan
will
be
joining
us
director
of
finance.
His
background
is
in
technology,
entrepreneurship,
banking,
private
equity,
in
terms
of
expertise,
he's
been
working
in
equity,
depth,
capital
he's
been
part
of
startups,
fintech,
property,
tech,
blockchain,
crypto
assets,
you
name
it
peer-to-peer
platforms,
again
mergers
and
acquisitions.
B
Everything
he
could
touch
his
he
put
put
his
hands
on
basically
mark
spann
broke.
Hope
I
pronounce
your
name
correctly.
Mark
big
warm
welcome
to
mark
he's
a
brilliant
engineer.
He
will
be
joining
team
dagger
and
to
a
bit
of
background
on
mark,
he
has
been
an
active
contributor
for
projects
like
a
sustainable
source
which
looks
at
financial
sustainability
for
open
source
projects,
identity
box,
which
is
hardware
for
the
decentralized
web
nem
pc,
which
is
a
secure,
multi-party
computation
for
the
nim
programming,
language
and
cogito.
B
In
the
same
time,
we
have
to
stay
fair
wall
to
a
few
people
that
have
left
the
stamp
and
the
way
status
does
things
so
verbal
kerry,
the
queen
of
people,
operations
and
internal
communications,
she's
moving
up
the
ladder,
but
she's
not
really
saying
goodbye.
She
will
be
in
touch
with
the
team
from
time
to
time
and
helping
status
on
a
part-time
basis
with
people,
operations,
communications
and
so
on
and
doing
her
thing.
B
Basically,
danny
danny
is
a
finance
master,
he's
stepping
away
on
the
31st
of
october
he's
pushing
his
career
forward,
and
this
will
only
happen
after
he's,
he
will
handle
the
ropes
to
rustling
big.
Thank
you
from
the
team
danny
and
appreciate
all
the
work
you
have
done
for
status
and
wish
you
all
the
best
moving
forward
in
terms
of
open
positions.
Now
I
think,
like
the
the
core
team,
I,
the
dapps
team,
is
looking
for
a
senior
react,
developer,
hester
and
a
few
other
people
want
to
revamp
dapps
and
they're.
B
Looking
for
a
new
addition
to
the
team,
we're
still
looking
for
protocol
engineers
were
interested
in
messaging
protocols
for
vac,
ideally
one
junior
and
one
senior
developer,
and
we
also
have
one
more
slot
in
team
dagger,
which
will
work
on
distributed.
Networking
passing
on
the
conversation
to
hester.
I
think.
C
Siri,
thanks
to
you
great,
to
see
new
people,
people
joining
status
as
always
sad
to
see
people
go
as
well,
but
usually
yeah.
It's
it's
with
new
new,
exciting
prospects.
Can
you
skip
to
the
next
site?
Please
thank
you.
So
last
week's
focus
has
been
heavily
on
the
referral
program
and
getting
that
ready
for
release
there's
a
lot
of
dependencies
in
there.
C
We
also
have
the
challenge
of
relying
on
the
play
store
itself
to
fully
test
out
the
the
program,
but
we're
nearly
there
and
we're
looking
to
to
test.
Let's
say
some.
Some
final
run
some
final
tests
on
the
on
the
program
this
this
afternoon
and
tomorrow,
and
then
we
will
be
releasing
that
in
phases
where
we
first
enable
advertisers
to
use
referral
urls
and
soon
thereafter
we
will
look
at
friends
friend
invite
referral
urls,
so
those
are
coming
up.
C
Release
1.8
will
for
sure
include
a
series
of
bug,
fixes
and
improvements,
because
we
don't
want
to
build
up
technical
debt
at
the
same
time,
new
features
whenever
they're
ready.
We
definitely
have
some
features
in
development.
As
I
also
mentioned
last
time,
notifications
on
ios
are
still
being
worked
on,
along
with
in-app
notifications.
C
Some
progress
going
on
there
as
well
group
chat.
Invite
links
are
in
in
final
review.
I
would
say,
as
well
as
adding
local
contact
names,
which
we
know
will
will
make
it
easier
to
remember.
Some
of
those
random
random
animal
names
to
help
identify
people
mentions
is,
is
in
progress,
and
obviously
we
also
want
to
be
able
to
tie
that
to
notifications.
C
C
We
can't
keep
in
focus
is
still
some
of
the
the
features
that
we
have
decided
on
during
the
roadmap
planning
process,
a
workshop
that
we
had
a
while
back
one
of
the
more
exciting
aspects
there-
and
I
believe
dean
is
also
joining
us
to
to
answer
a
town
hall
question
on
this
topic.
One
of
the
things
we're
looking
at
is
how
can
can
walk,
would
be
used
by
dapps,
so
there's
definitely
different
people
core
contributors
from
different
angles.
C
Another
topic:
that's
in
focus
is
organization
channels.
That
is
something
we
were
really
excited
about.
At
the
same
time,
we
we
do
know
a
lot
of
projects
or
organizations
are
quite
happily
using
things
like
discord
and
and
slack
and
are
not
super
likely
to
to
shift
to
to
status
and
and
risk
losing
some
of
their
their
community.
So
we're
looking
at
what
are
ways
that
we
can
facilitate
communities
better
on
status
without,
let's
say
introducing
the
risk
of
of
losing
your
community.
C
So
looking
at
some
other
options,
there
local
contact
names,
I
mentioned
ways
to
to
help
identify
each
other
in
that
same
sort
of
arena.
There's
an
investigation
going
on
and
there's
also
a
post
on,
discuss
that
you
can
follow
around
adding
a
profile
photo.
This
comes
like
as
a
package
deal
with
display
names.
Almost
the
difficulty
with
with
adding
profile
pictures
is
that
sending
photos
over
the
network
is
not
straightforward.
D
C
C
E
E
Read
that
it's
a
great
article,
if
you
try,
if
you
don't
have
a
hard
time,
understanding
what's
actually
happening
on
the
back
end,
when
you
push
send
on
your
mobile
app,
also
phase
two
of
the
nimbus
audit
is
wrapping
up
and
the
issues
are
being
dealt
with.
That's
going
really!
Well,
I
we
have
an
upcoming
article.
E
So
that's
going
really
well
really
happy
about
all
that
for
from
devsecops,
I'm
setting
up
an
instance
of
the
hive
cortex
and
misp,
which
is
a
open
source,
awesome
piece
of
software,
a
couple
pieces
of
software
for
handling
incident
response
within
organizations.
So
when
something
goes
wrong,
you
can
automatically
create
tickets
and
do
all
kinds
of
really
neat
things.
Once
that's
set
up
I'll,
probably
do
a
kind
of
walk-through
tutorial
to
show
how
we're
handling
that
type
of
stuff
on
the
back
end
in
one
of
these
town
halls.
E
E
Waku
only
made
walker
the
default
protocol
for
status
go
that's
awesome,
so
we're
upgrading
all
of
the
back
end
stuff
to
be
more
scalable
for
all
of
you,
so
use
less
bandwidth
on
your
phone
deploy
push
notifications
on
test
fleet,
so
you
can
see
those
coming
soon
in
the
status
app.
We
got
to
test
it
to
make
sure
it's
working
well
resolved
an
extremely
weird
fire
firewall
bug
in
status
fleets.
E
As
for
nimbus
added
floating
ips
to
aws
hosts
to
prevent
ip
changes,
almost
finished,
setting
up
windows,
ci
hosts
for
desktop
builds
so
desktop,
is
getting
closer
and
closer
and
closer
to
getting
to
you
upgrade
mix
packages
and
status,
react
and
multiple
build
tools.
That's
we
have
a
few
upgrades
on
the
right,
not
too
much
really
happy
that
we
switched
to
waku
only
the
more
and
more.
We
do
that
the
less
like
the
the
the
more
we
get
to
kind
of
upgrade
the
back
end
services
and
provide
better
services.
A
F
So
the
keycard
team
has
been
focusing
on
on
payments
for
a
couple
of
months
now,
by
the
way
for
those
who
just
join
keycard
team
is
michele
andrea
and
myself,
we
get
a
lot
of
help
from
a
lot
of
contributors
on
specific
subjects,
so
yeah.
What
I
wanted
to
cover
are
the
the
use
cases.
I
mean
these
big
large
use
cases
that
we're
working
on
for
for
this
month,
what
we've
achieved
and
what's
next
especially
for
status
pay.
F
So
can
you
go
to
the
next
slide,
please
so
yeah
overall,
looking
at
things
from
a
distance,
there
are
two
main
use
cases
we
are
working
on
and
all
our
underlying
work
is
around
those
two.
First,
we
want
to
allow
fast,
cheap
and
secure
payments
in
the
real
world-
meaning
offline,
not
when
you're
in
front
of
your
pc,
for
instance,
when
you're
standing
in
front
of
someone,
and
you
want
to
make
a
payment.
F
The
typical
case
is,
you
want
to
pay
for
stuff
at
a
store
by
tapping
a
card,
for
instance,
and
by
the
way
in
this
specific
use
case,
we
want
to
do
that
in
a
specific
way.
We
want
to
make
becoming
a
vendor
really
permissionless.
Anyone
could
become
this
merchant
and
we
want
the
merchant
to
only
have
to
use
the
status
on
his
mobile.
F
And
we
want
to
build
an
easy
experience
to
retrieve
these
assets
from
the
car
to
any
wallet.
This
is
not
as
trivial
as
it
seems.
You
could
say
hey,
but
what
what
it
is
you're
working
on
here-
it's
pretty
obvious,
but
it's
not
because
we
don't
want
the
assets
to
be
locked
up
on
the
the
cards,
because
these
keycards
they
have
private
keys
right,
holding
some
external
owned
accounts.
We
don't
want
the
assets
to
be
locked
there.
F
We
want
to
keep
some
control
over
the
assets
until
the
cards
are
really
used
so
well.
These
assets
are
actually
on
smart
contracts
and
not
only
on
the
card
on
the
keys
that
are
on
the
cards
themselves
and
the
user
experience
needs
to
be
easy,
and
really
it's
not
obvious,
because
there
are
a
lot
of
things
that
are
needed.
You
need
a
keycard
compatible
free
browser.
You
need
a
wallet
where
to
retrieve
to
you
need
to
bruise
browser,
a
reading
user
interface.
You
need
to
pay
gas
which
is
very
expensive
today.
F
So
a
lot
of
things,
and
if
you
want
the
whole
experience
to
be
easy,
it's
not
trivial.
Can
you
go
to
next
one,
please
so
yeah
some
results
so
for
payments.
We
first
worked
on
building
the
logic
for
all
these
in-person
payments
and
so
that
they
can
happen
with
a
key
card,
and
here
again
first
you
could
ask,
but
what's
the
difficulty
here
I
mean
it
could
be
pretty
straightforward.
After
all,
you've
got
this
status
wallet.
F
I
mean
the
status
app
keycard
is
integrated
within
the
app,
so
you
just
need
to
make
a
payment
with
your
status
wallet
to
some
qr
code
that
the
merchant
is
showing
to
you
and
we're
already
right
there
right.
So
it
was
the
difficulty
I
wanted
to
outline
why
we
had
to
work
on
that.
First,
we
want
point
of
sale
to
be
untrusted
and
we
come
back
to
this
thing.
That
merchants
should
be
able
to
use
their
phone.
F
The
funds
thus
cannot
be
stored
on
the
keys
of
the
car
themselves
and
the
funds
needs
to
be
on
smart
contracts
wallets.
So
we
needed
to
build
an
architecture
where
the
funds
are
on
smart
contract
wallets
and
this
map
these
wallets
need
to
be
associated
in
some
ways.
With
a
card
a
given
wallet
is
associated
with
a
given
card.
F
F
F
It's
communicating
with
the
key
card
through
this
request
screen
that's
been
called
by
the
dap
to
the
phone
and
there's
a
specific
applet.
Also
on
the
keycard
for
for
payments,
that's
called
keycard
cash
and
we've
got
a
smart
contract
wallet
and
we've
got
a
registry,
a
registry
that
that
keeps
the
association
between
wallets
and
the
and
and
cards.
F
F
We've
got
this
architecture
in
place
where
some
smart
contracts
that
we
call
buckets
are
holding
assets
that
each
card
can
redeem
and
the
user
needs
to
have
status
installed.
Browser
redeemed,
app
tapi's
car
to
retrieve
the
assets
on
whichever
wallet
he
wants,
and
this
is
done,
which
is
not,
which
is
a
custom
version
of
the
request
screen
called
the
the
reading
screen.
F
F
F
F
So,
given
this
the
work,
we've
already
done,
what
do
we
miss?
Actually,
we
need
a
higher
throughput
than
l1.
We
need
cheap
gas
costs,
obviously
than
l1,
and
we
need
fast
economic
finality
fast,
economic
finality.
It's
for
the
keycard
case
when
you're
standing
in
line
at
a
shop
and
you're
buying
things
with
your
card.
The
merchants
needs
to
know
that
the
transaction
is
approved
within
a
couple
of
seconds.
So
we,
our
goal,
is
less
than
three
seconds.
You
cannot
wait
more
than
that.
F
Otherwise,
you
can
have
in-person
payments.
So
basically
we
need
status
pay,
which
is
a
scalability
solution,
mostly
on
layer,
2.
and
yeah.
You
can
go
to
next
one.
Please
so
status
pay
a
quick
view
of
the
features
of
this
chain
we
want
to
build.
We
want
it
to
be
evm
compatible
because
we
worked
on
some
smart
contracts
and
we
need
to
pop
them
here
and
we
want
our
adapts
to
run
there
too.
F
F
There
I'll
come
back
on
that,
and
we
want
to
be
able
to
transact
with
any
rc20
on
this
chain
and
we've
dropped
out
the
requirement
of
the
transaction
being
anonymous
from
now
there,
because
it
would
make
things
a
bit
more
complex
and
would
delay
us
having
status
pay
yeah.
Can
you
go
to
the
next
one?
Please?
So?
How
are
we
going
to
do
that?
So
we
work
with
lib
dao,
which
are
experts
at
layer,
2
solutions
and
we
really
evaluated
different
technologies.
F
I'd
be
super
super
synthetic
and
a
bit
simplistic
here,
but
we
stated:
we've
studied
estate
channels,
zero
knowledge,
proof,
follow-ups
and
optimistic
roll-ups
and
basically
we're
going
for
optimistic
roll-ups,
because
we
need
evm
and
now
I
mean
state
channels
cannot
offer
evm
and
zk.
Roll
ups
will
probably
enable
that,
but
it's
not
ready
for
now,
so
we're
just
proceeding
with
the
optimistic
roll-ups
and
in
a
world
what
is
an
optimistic
roll-up?
F
So
it's
a
it's
a
layer
to
chain
with
the
number
of
nodes
that
we
call
the
validators
or
operators
they
are
listening
for
transaction.
They
are
gathering
that
them
in
block
there's
no
proof
of
work
consensus
there
and
these
operators.
I
mean
these
nodes.
They
can
submit
these
blocks
to
layer,
one
by
providing
all
the
transaction
data
and
some
merkle
root
of
the
state
of
the
layer.
F
Two
and
thus
the
cost
of
transaction
is
much
slower
and
the
throughput
much
higher
and
anyone
can
challenge
the
validity
of
the
layer
two
from
layer,
one
because
it
has
access
from
layer,
one
on
all
the
the
transactions
and
state
of
the
the
channel
yeah.
So
that's
optimistic
roll
roll-up.
So
next
yeah,
so
let's
talk
well.
Could
we
use
any
optimistic
roll-up?
So
I
wanted
to
outline
what's
really
really
specific
for
us
here,
because
there
are
different
implementations
of
optimistic
roll-up.
F
F
So
what's
the
plan
more
precisely
so
we
have
we've
worked
with
libdar
a
lot.
They've
been
super
helpful
and
we
wrote
a
system
design
document.
That's
explaining
all
the
problems
we
faced
all
the
rational
and
why
it
led
us
to
the
decision.
I'm
gonna
explain
now,
but
there
are
still
some.
I
mean
these
are
complex
subjects
for
sure
and
optimistic
roll-ups
is
all
over
the
news.
F
I'd
say
I
mean
everyone
wants
to
work
on
optimistic
crawler,
but
still
the
reality
is
that
there's
no
one
solution
on
main
net
now,
maybe
except
synthetics-
I
guess-
but
the
I
mean
it's
not
a
totally
mature.
I
mean
there's
no
proven
solution,
so
we
have
open
questions
first,
one
being:
are
we
going
to
deploy
our
own
roll
up
or
are
we
go?
F
We
want
to
use
optimism
code
and
they
are
in
the
middle
of
a
new
release,
and
so
when
uncertainties
are
when
are
they
gonna
gonna?
When
are
they
going
to
release
it?
Maybe
in
the
coming
days,
but
maybe
in
a
couple
of
weeks
and
and
all
the
decentralization
details
on
there
to
which
consensus
we
use?
What
are
the
incentives
of
the
operators
to
run
a
node
and
to
get
her
reward?
F
F
Main
goal
is
to
have
throughput
and
cheap
transaction
and
to
be
able
to
use
that
for
that,
so
that
you
guys,
I
mean
anyone,
instead
of
working
on
our
status,
app
to
be
able
to
use
this.
So
we
want
to
use
optimism
code
because
their
code
is
the
most
mature
and
we've
got
detailed
comparison
of
all
the
rollup
code
bases
that
are
existing
in
the
detailed
document
that
we
shared
in
the
link
previously.
F
So
we
want
to
run
an
instance.
That's
gonna
be
first
centralized
and
that
needs
to
be
trusted.
It's
gonna
be
super
simple,
it's
gonna
be
one
node
and
there's
gonna
be
just
one
honest
observer,
that's
watching
for
the
data
that
the
node
is
posting
on
l1
and
for
this
simple
version,
nose
taking
or
no
challenges
that
can
be
submitted,
so
we're
going
to
deploy
this
node
we're
going
to
build
the
bridge
for
the
assets
and
deploy
this
one
watchtower.
F
They
are
releasing
new
code,
their
repos
are
moving
every
day
now
but
to
be
followed.
But
this
is
the
matter
of
a
couple
of
weeks
and
then
in
vp1.
If
you
can
go
to
the
next
slide,
we
want
to
enable
keycard
and
trust
testness.
So
this
is
still
going
to
be
centralized.
It's
still
going
to
be
one
one
node
for
now,
but
we're
gonna
implement
all
the
challenges
mechanism
so
that
an
operator
I
mean
meaning
this
node
can
be
challenged
from
l1.
F
Gonna
have
stakes
and
his
stakes
are
gonna
be
used
once
the
the
challenge
has
been
raised
and
we're
gonna
deploy
our
payment
network
contracts
and
add
up
our
debts
to
l2
from
there.
So
the
planning
here
is
I'm
being
very
imprecise,
but
it's
a
couple
of
months.
Another
couple
of
weeks-
and
next
please
yeah
next
slide.
Please
then
next
we're
gonna
need
to
build
the
ui
from
status.
To
use
this
use
status.
F
F
So
we
need
to
find
the
right
consensus
and
we
need
to
build
the
right
economy
around
gas
there
so
that
the
operators
have
incentives
to
join
and
build
blocks
and
and
submit
them,
and
the
other
thing
is
we
want
snt
to
be
used
as
a
staking,
but
if
we
join,
if
we
make
a
joint
effort
with
other
projects,
this
is
not
gonna
work
out.
I
mean
in
this
case
we
need
a
neutral
token
like
if,
for
the
staking
yeah,
that's
an
overview
of
what
we've
done,
what
we're
working
on?
F
What
are
the
open
questions
and
we,
I
wanted
to
highlight
some
short-term
some
of
our
short-term
goals
for
this.
That
was
a
bit
long,
but
we've
not
communicated
a
lot
about
that
in
the
past
week.
So
I
really
wanted
to
share
that
with
you
and
this
gas
price
issue
with
ethereum
is
so
important
right
now
I
wanted
to
pass
the
message
that
this
work
we
are
doing
in
the
keycard
team.
A
G
G
But
luckily
I'm
happy
to
report
that
basically,
the
network
survived
the
nimbus
was
able
to
get
through
these
difficult
times
and
we
delivered
a
lot
of
fixes
in
the
meantime
which
improved
the
stability
nimbus
and
right
now.
If
you
are
fully
synced,
you
should
be
able
to
experience
at
least
95
percent
of
delivered
stations
on
a
regular,
normal,
desktop,
modern,
desktop
machine,
and
I
would
not
specify
what
exactly
is
that,
but
if
you
have
any
performance
that
is
kind
of
worse
than
this,
please
report
it
as
an
issue.
G
Nevertheless,
there
are
some
outstanding
problems
and
this
sensitivity
towards
the
cpu
power
of
your
computer
is
one
of
them.
Some
plans
are
trying
to
use
nimbus
on
raspberry
pi.
It
is
a
goal
for
us
that
this
should
be
perfectly
possible,
but
right
now
it
seems
that
cpu
power
on
these
machines
is
just
not
enough
to
keep
up
with
the
network
and
our
architecture
right
now
is
a
bit
constrained.
G
We
are
running
on
a
single
threat
and
trying
to
handle
all
the
computational
requirements
and
the
communication
requirements
on
a
single
track,
and
this
makes
it
makes
it
a
little
bit
more
challenging
to
operate
smoothly
on
low
power
devices
right
now.
We
are
working
towards
solving
this
issue
and
hopefully
we'll
have
a
solution
soon.
G
We
still
have
this
relatively
major
issue
that
if
you
leave
your
nimbus
note
over
time,
it
will
accumulate
more
and
more
system
resources
like
memory,
and
for
this
reason
we
still
recommend
that
you
do
frequently
starts.
Let's
say
once
per
six
hours
or
four
hours,
and
this
is
another
issue
we'll
be
focusing
on
and
trying
to
come
up
with
a
solution.
G
And
finally,
since
the
network
is,
has
accumulated
quite
a
lot
of
history
now
and
the
required
storage
for
keeping
the
entire
big
chain
in
the
beacon
anyway,
the
entire
beacon
chain
is
quite
large.
Now
and
now
this
is
an
area
we
haven't
been
optimizing
significant
enough,
and
we
should
address
this
with
urgency,
because
it
becomes
unpractical
to
run
nimbus
on
virtual
gps,
for
example,
machines
which
all
capacity
these
are
the
machines
that
we
use
on
aws
to
test
our
fleet
of
nimbus
notes.
G
So
try
this
as
soon
as
it
is
merged
and
you
can
report
all
right.
I
will
just
mention
a
few
stats
from
our
audits
if
you're
more
interested.
Obviously
you
should
follow
the
more
detail.
Rights
of
our
items
that
corey
is
preparing
with
just
some
stats.
There's
been
31
issues,
discovered
reported
so
far,
two
of
them
has
been
classified
as
high
severity
or
more
critical
issues.
There
are
eight
in
the
medium
severity
and
eight
in
the
low
severity.
G
G
A
H
Thanks
terry
quick
one
today,
some
ongoing
work
alec
ran
a
brand
campaign,
just
driving
brand
awareness,
pushing
out
some
of
the
blog
posts
we've
written
to
and
just
trying
to
drive
traffic
to
the
site,
and
here
are
some
of
the
results
overall,
pretty
good.
We're
gonna
be
optimizing
this
over
the
next
few
weeks
and
months
as
we
are
with
our
other
campaign.
So
it's
just
good
to
get
these
pilots
off
the
ground.
So
a
lot
of
partner,
comms
and
partner
outreach
is
going
on
right
now.
H
So,
a
couple
weeks
ago
we
we
hosted
a
an
ama
and
status
with
kyber
network
and
that's
the
first
of
many
and
that's
just
like
the
like.
The
first
activation
we've
run,
we're
doing
it
once
again.
A
lot
of
outreach.
Other
partners
are
going
to
be
rolling
out
a
lot
of
comms
along
the
lines
of
this
ama.
So
look
for
look
for
that
with
some
other
cool
partners,
brazil
and
argentina.
We've
contracted
three
influencers
now
and
we're
finalizing
contracts
for
a
few
others,
but
check
them
out.
H
Alberto
germano
once
again
is
is
quite
technical.
Kryptomanicus
is
a
blockchain-centric
influencer
in
brazil
and
block
latina
and
we're
really
excited
to
get
them
on
board
ahead
of
the
referral
program.
Launch
because
obviously
they'll
be
they'll,
be
key
players
in
that
and
then
also
in
brazil
and
argentina.
H
So
thank
you.
Corey
live
chain
which
is
a
great
one.
The
vancouver
biennale
is
a
cool
one.
It's
with
an
art
group
in
vancouver
and
it's
it's
being
run
by
jessica
angel
who's,
really
a
core.
You
know:
community
member
in
the
nft
and
decentralized
art
community,
so
working
with
her
to
showcase
status
at
the
at
the
event
and
then
also
they're,
building
out
a
sculpture
over
the
course
of
the
next
like
two
years,
which
we
will
incorporate
status
in
in
some
fun
and
exciting
ways.
H
We're
just
going
to
concept
that
with
jessica
block
security
conference,
so
cory
will
present
status
there
and
then
hcpp
the
hackers
congress
at
the
parallel
only
paulus.
It's
the
hackers
hackers
conference
in
prague
and
we're
really
excited
to
be
part
of
that
one,
because
it's
it's
really
like
the
target
audience
for
us
hackers
at
the
space
out
of
hackerspace
who
are
who
are
using
status,
and
it's
cool
so
we'll
announce
this
in
the
coming
weeks.
H
But
status
will
be
the
official
comms
partner
for
the
event
in
which
we'll
set
up
public
channels
for
the
event
and
share
exclusive
content
and
then
host
some
amas
with
some
of
the
top
speakers
in
status.
So
that's
a
really
great
one
for
us
and
it's
you
know
it's
a
really
cool
group
and
a
cool
community
to
be
a
part
of
so
excited.
A
D
What
makes
them
interact,
what
makes
them
share
their
their
experiences
with
their
own
communities
so
that
we
can
create
a
more
meaningful
space
and
and
really
create
those
valuable
experiences
for
for
people
coming
in
exploring
new
ways
of
using
the
status
of
offerings.
I
think
that's
also
very
important.
There's
a
few
people
reaching
out
to
me
over
twitter
and
essentially
asking
about
all
sorts
of
different
things.
One
of
the
the
key
ones
coming
up
is
a
competition
for
some
stickers
for
pride,
organized
by
nifty
pride
foundation.
D
So
that'll
be
very
interesting
to
see
that
community
coming
in
and
hopefully
really
really
benefiting
from
the
chat,
but
also
the
you
know,
the
wallet
features
and
and
the
browser
and
so
on.
So
I'm
looking
forward
to
to
feedback
on
that
and
then
obviously
focusing
on
organic
growth.
Johnny
mentioned
this
earlier,
there's
a
whole
host
of
partnerships
that
we
are
working
on.
It's
very,
very
important
to
support
other
projects
in
the
ecosystem.
D
As
we
know,
the
tide
lifts
all
boats,
so
I
think
it's
it's
imperative
for
us
to
be
there
for
other
projects
and
and
see
how
we
can
increase
the
value
that
they
offer
to
their
communities.
So
there's
a
lot
of
very
interesting
stuff
coming
coming
up,
so
stay
tuned,
there'll
be
loads
of
things
in
the
works
and
the
main
thing
is
around
education.
D
There's
a
lot
of-
and
you
know
we're
still
in
2020-
we're
still
struggling
with
the
fact
that
there
isn't
enough
straightforward
education
or
or
resource
for
people
to
dive
into
what
ethereum
has
to
offer
and
so
we're
spinning
up
a
few
different
courses
or
educational
initiatives
with
some
of
the
partners
that
I
mentioned
earlier.
So
we're
working
we're
going
to
work
on
with
ave
on
a
d5
course
or
rather
how
to
defy
responsibly.
D
I
Okay,
can
you
hear
me?
Yes,
okay,
thanks,
okay,
let
me
give
you
a
brief
update
regarding
the
ambassador
program.
From
now
on,
there
are
56
status
ambassadors
from
25
countries
at
the
moment,
and
there
are
about
40
and
there
were
about
40
ambassadors
in
q2,
so
we've
got
more
than
15
ambassadors
in
q3.
Until
now
and
for
your
information,
ambassador
candidates
are
officially
recognized
as
a
status
ambassador
when
they
complete
their
first
task
and
russian
and
nigerian
ambassadors
actively
participate
in
the
program.
I
I
You
can
find
more
details
on
the
completed
tasks
on
week
on
the
weekend
board
and
I
will
present
some
featured
completed
tasks
on
the
next
slide.
Next
slide,
please
so
big
shout
out
to
all
the
and
all
the
3
35
ambassadors,
so
those
ambassadors
moved
the
status
community
forward
in
q3
until
now,
so
appreciate
all
the
ambassadors
who
expressed
the
words
of
status
worldwide
with
us
again
all
the
completed
tasks
are
priceless
and
meaningful,
but
let
me
present
some
features
completed
tasks
here.
I
One
of
the
monumental
work
from
status
ambassadors
in
q3
was
enrico,
tbenr
and
rico's
technical
contribution
to
status
in
enabling
audio
messages
in
chats
his
amazing
work
was
featured
on
the
blog
post
on
our
status,
our
status
as
well
also
an
italian
ambassador,
marco
100,
translate
our
homepage
into
italian
alone.
So
thanks
to
our
ambassador's
passion
for
the
and
decentralize
society
and
next
next
slide,
please.
A
A
So
question
one
from
celio
is
how
well
does
status
work
in
adverse
serial
environments
saw
someone
mentioned
difficulties
in
belarus.
I
recall
status,
not
working
in
china
last
year.
I
assume
a
state
agency
could
sniff
out
status
users
and
put
them
in
concentration
camps
if
they
really
wanted
to
mysterium
is
opening
up
their
decentralized
vpn
network
to
application
developers,
maybe
something
to
look
at
incorporating
I'm
going
to
pass
that
over
to
corey.
If
you
don't
mind
corey,
would
you
be
able
to
answer
that
question
for
us.
E
But
once
you're
able
to
connect
to
the
status
network.
It's
very
difficult
for
people
to
sniff
out
that
traffic,
as
well
as
who
you're
talking
to
and
what
you're
saying,
based
on
how
we
obfuscate
the
messages
being
passed
around
where
they're
going
and
where
they're
coming
from,
as
well
as
the
contents
of
those
messages.
E
That
being
said
again,
like
we
still
use,
what's
known
as
a
distributed,
distributed,
hash
table
or
academia-like
network
discovery
model.
So
that
means
that
people
can
sniff
out
your
ip
and
then
look
at
that
traffic
or
understand
that
certain
types
of
traffic
are
coming
from
a
certain
type
of
ip.
If
they
have
a
tremendous
amount
of
resources
doing
so,
but
they
won't
know
what
that
traffic
is
and
we're
looking
at
different
ways
to
make
that
better.
E
But
when
you
compare
what
we
do
to
anything
else,
that's
available
of
note.
It's
it's
quite
secure
and
very
difficult
to
see,
what's
being
done
so
like
in
mo
in
the
most
adversarial
setting,
it's
still
really
really
difficult
to
figure
that
out,
but
we're
still
working
on
ways
to
make
it
easier
for
people
to
connect
to
the
network
and
start
sending
messages
back
and
forth.
E
I
can't
like
give
you
strong
guarantees
that
no
one
can
ever
figure
out
anything,
because
we
still
have
more
research
to
do
and
work
to
do
to
figure
out
how
to
make
it
better.
But
in
terms
of
my
understanding
of
the
cryptography
and
how
messages
get
passed
on
the
network
go
read
the
article
that
we
recently
published
that
I
mentioned
in
this
town
hall,
it's
very,
very,
very
difficult
for
even
global
adversaries.
E
A
F
A
E
A
F
Sure
so
it's
definitely
in
the
backlog
of
keycard
items
that
the
the
core
team
is
gonna
end.
All
it's
actually
number
two
because
number
one
in
the
backlog
is
to
to
allow
better
management
of
the
the
keycards
account,
meaning
turn
a
normal
account
to
a
keycard
account
or
being
able
to
just
delete
a
keycard
account.
That's
number
one
and
number
two
is
ios
integration.
F
This
being
said,
it's
not
been
prioritized
as
part
of
the
top
priorities
that
will
help
with
retention.
So
it's
difficult
to
give
a
precise
date
for
that.
What
I
can
say
is
that
we
there's
a
plan
to
speed
these
things
up
and
we've
been
discussing.
If
we
could
get
a
contractor
to
work
on
card
so
can
give
a
precise
date.
We're
gonna
have
ios
integration
for
keycard,
that's
for
sure,
but
when
exactly
difficult
to
say
for
now.
A
Thanks
guy
louie,
and
so
that
is
it
for
the
town
hall
today,
I
just
wanted
to
say
a
massive
thank
you
to
everyone
who
participated
and
gave
updates
today.
It
was
really
really
interesting
and
also
to
thank
you
to
everyone.
That's
been
listening
and
joining
in
in
those
updates
on
behalf
of
everyone
at
status.
We
do
want
to
wish
kerry
all
the
best
in
her
new
role.
It's
going
to
be
really
sad
to
see
you
go
and
I
think
I
sort
of
speak
on
behalf
of
everyone.
Thank
you
for
everything.