►
From YouTube: Status Townhall #26 - January 21, 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
B
B
Cool
yeah,
so
it's
basically
we're
working
towards
getting
to
this
doubt
so
I
sent
out
an
email
this
week.
Oh
sorry,
last
week
asking
a
couple
of
questions
seeing
like
if
you'd
be
willing
to
accept
what
were
your
token
preferences
and
if
there's
any
sort
of
potential
issues
in
adopting
crypto
as
a
primary
form
of
pay.
B
There's
a
couple
of
comments,
basically
saying
that
they
would
like
to
like
trial
like
splitting
their
fiat
versus
crypto.
Just
so
I
just
want
to
remind
you
that
you
can
actually
already
do
that.
We
just
need
to
log
in
to
bamboo
and
set
that
up
for
yourself
reach
out
to
people
ops
if
you'd
like
to
make
any
of
that
happen.
And
yes,
basically,
in
addition
to
that,
the
I
put
in
the
defaults
of
token
preferences.
B
A
few
people
change
them,
but
it
was
kind
of
interesting
to
see
that
those
basically
a
50/50
split
between
F
and
I,
as
their
first
preference
with
this
second
third
being
a
predominately
favoring
SNT,
which,
which
is
good
to
see,
be
great,
to
see
this
first
but
I
understand
why
but
yeah
that's
pretty
much
it
from
me
and
I'll
be
following
up
with
it.
A
lot
of
your
comments,
Thanks
cool.
A
A
Some
teams
have
done
a
really
good
job
of
adopting
some
of
the
various
features
and
one
that's
really
awesome
is
epics,
and
you
can
see
here.
This
is
the
core
team
using
epics
to
track
a
variety
of
different
issues,
and
it
gives
a
really
good
snapshot
of
like
how
much
how
much
is
progressed.
How
much
is
in
progress
and
how
much
is
left
to
do
ignore
the
estimates
on
the
far
right.
A
You
need
to
feed
it
a
lot
of
data
to
start
getting
accurate
estimates,
but
essentially
for
any
teams
that
are
using
pivotal
tracker,
which
is
pretty
much
all
swarms,
try
to
cluster
them
into
epics
and
then
you'll
be
able
to
get
these
sweet
graphs
and
then
every
Town
Hall.
You
simply
can
just
show
this,
and
it
just
generally
helps
with
getting
everyone
on
board
on
what
the
top
priorities
are
and
how
much
progress
isn't
made
so
friendly
reminder
all
right,
jumping
into
specific
swarms,
egor.
C
Progression,
but
the
first
thing
is
that
we
will
probably
extend
the
research
for
at
least
two
weeks,
maybe
more
because
yeah,
basically
because
there
will
be
meetup
in
Brussels
about
the
new
protocol,
and
we
also
want
make
sure
that
our
decision
is
not
at
least
not
incompatible
with
develop
content
switch
into
the
new
protocol
since
it's
very
tightly
coupled
with
it
to
some
extent.
So
what
was
done
in
these
two
weeks?
C
Yeah,
basically
Andrea-
was
working
on
it
and
we
did
a
conversion
of
possible
incentivization
structure
for
our
current
setup,
like
mail
servers,
whisper,
flood
of
messages,
and
things
like
that,
like
we
have
right
now
and
we
also
chose
one
protocol,
that's
very
different
from
that
to
make
a
more
generic
idea
about
what
would
be
the
pitfalls
if
our
protocol
will
change
and
it
will
probably
change
in
the
future.
So
that's
the
the
biggest
point
so,
unfortunately,
right
now,
it's
like
it's
a
little
bit
yeah.
C
It's
mostly
Andres
doing
this
work
and
and
mostly
Oscar
giving
feedback,
but
starting
from
the
next
two
weeks.
We
also
trying
to
start
some
design
research
on
recurring
payments,
and
things
like
that.
So
we
will
try
to
make
it
more
a
parallel
solution
to
offer
a
little
bit
faster.
That's
all
for
me,
cool.
A
D
So
we've
made
the
progress
with
the
design
of
tribute
to
talk
and
no
Vitellius
made
good
progress
with
the
screens
for
Tara
to
talk
regarding
the
blocking
feature
we've
decided
to
delay
it
so
that
we
implement
the
contact
lists
to
in
to
allow
people
to
unblock
before
we
release
the
feature,
because,
what's
ready
now
only
allows
to
block
but
not
unblock
so
our
yeah.
So
right
now
we're
working
on
tribute,
talk
and
block
user
feature
and
we've
also
started
discussions
with
design
for
the
ENS
user
names
in
chat.
B
B
Outside
of
that,
we've
got
a
few
open
browser
issues
still,
but
we're
probably
actually
going
to
continue
to
prioritize
polishing
the
khyber
extension,
especially
because
we're
going
to
be
sponsoring
extension
bounty
at
Denver,
but
we
also
really
want
to
make
sure
that
that's
a
really
good
improve
of
concept.
For
extension,
that's
close,
there's
just
a
few
minor
issues
that
are
open.
E
We
focused
on
trying
to
come
up
with
the
simplest
solution
and
essentially
the
idea
is
to
just
ship
and
implement
as
soon
as
possible,
so
that
we
can
get
a
feedback
from
people
just
testing
whatever
we
did
so
on
top
of
that,
so
I
pushed
a
bit
on
the
UI
front
and
implemented
some
proof
of
concept
of
the
the
mock-ups
that
we
are
and
so
that
there
is
a
share,
the
video.
If
someone
can
trigger
it.
That
would
be
interesting
in
fullscreen.
Eventually,
if
that's
okay,
we
just
rather.
A
A
F
E
E
So
what
we
plan
to
do
next
week
is
kind
of
finish
with
we're
right
now,
mostly,
what
we
miss
is
the
the
purchase
walkthrough
so
that
you
we
need,
like
the
world
logic,
to
decide
to
buy
a
bag
or
to
pay
a
pack,
because
there
are
some
free
packs.
So
we
will
implement
this
and
also
like
the
the
one
was
the
biggest
thing
that
we
are
missing.
E
Right
now
is
interacting
with
the
real
contract,
because,
right
now
everything
is
kind
of
fixed,
but
there
are
interaction
with
some
kind
of
contract,
but
it's
not
a
real
contract
were
deployed.
The
way
that
this
is
what
we
will
push
this
week
and
yeah.
Eventually,
hopefully,
we
will
get
some
feedback
and
and
try
to
to
understand
if
we
want
to
add
more
features
or
if
we
are
fine
with
the
current
state
of
things.
E
B
So,
after
a
conversation
with
designers,
we
have
a
softs
thank
for
that
15th
of
February,
because
this
is
a
p1
and
not
a
zero
swarm.
So
we'll
have
initial
designs
the
BAPS
for
next
month,
and
if
you
would
like
to
follow
along
with
the
latest
research,
but
it's
ongoing
at
the
moment.
It's
mostly
just
me,
but
there's
a
pretty
cool,
observable
things
on
this
slide.
B
That's
will
be
going
along
in
tandem
with
this
is,
hopefully
a
UX
survey
with
tester
to
try
and
understand
what
people
might
be
willing
to
stake
in
ad
app
store
and
what
they
would
be
expected
out
of
it
and
just
get
a
better
sense
of
what
you
know.
Our
sort
of
basic
user
expectations
would
be
so
that
we
can
feed
some
better
data
into
trying
to
understand
what
the
optimal
curve
to
use
is.
A
Sweet
thanks
Andy,
so
it's
going
over
some
of
the
other
priorities
that
we're
working
on
so
there's
the
the
Dow
that
you
were
is
driving
there's
also
the
talent
Network.
There's
no
updates
this
time,
but
I
think
there'll
be
more
detail
update
next
time
on
both
of
those
two
things:
okay,
Yuri,
you
want!
You
want
to
give
an
update,
then.
G
G
So
essentially,
we
have
a
very
basic,
very
basic,
you
wire,
that
can
you
come
to
the
basic
arbitration
and
dispute
mechanism
and
we
learn
Eliza,
more
in-depth,
more
advanced
for
a
more
advanced
reputation
system
and
also
also
this
situation
that
all
kind
of
wire
catch,
the
Krypton,
the
first
crypto.
If
it
is
not
Scripture
in
the
first
place,
and
we
were
going
to
leverage
the
the
existing
Catherine
layer-
that's
that
started
as
the
walk.
G
We
also
we're
so
experimenting
developing
a
mobile
tap
like
so
that
could
be
sold
in
the
App
Store,
potentially
and-
and
so
this
week.
We're
gonna
continue
to
develop
that
reputation
mechanism
and
continue
to
fix
some
bugs.
So
we
can
go
towards
the
the
second
stage
of
the
toffee,
the
MVP
for
the
for
the
doll
and
we.
So
we
didn't
really
why,
for
the
sandbox
and
I
very
did
a
really
really
great
job
on
that,
and
so
it
does.
B
C
C
We
also
started
work
on
their
message:
compressibility
and
upgradability.
Essentially,
this
is
this
issue
that
we
had
when
a
new
version
didn't
really
play.
Well,
with
replies
from
the
old
version
and
things
like
that,
so
just
how
can
we
make
it?
So
it's
not
like
that
anymore
and
actually
a
side
effect
of
this
one.
It
will
hopefully
be
a
second
clients
in
go
for
the
status
protocol.
C
There's
also
will
hopefully
have
help
testing
status.
Go
releases
like
to
be
able
to
manually
test
items,
go
releases
because
right
now,
it's
a
pretty
long
process.
When
audition
you
release
and
then
you
have
to
test
it
on
a
status
react
side.
So
I
guess
you
guys
have
a
lot
of
that.
What
to
say
about
this
process,
which
is
very
simple,
to
also
hope
to
fix
that
as
well.
So
yeah,
that's
all
for
me.
F
So
you
know,
please
have
a
look
at
that.
If
you
wanna
see
the
current
state
of
that
is
probably
going
to
improve
it,
a
bit
sort
of
make
some
assumptions
more
clear.
F
A
B
B
A
H
A
H
Good,
thank
you,
okay.
So
this
is
a
about
10
minutes,
update
about
where
we're
at
and
what
the
next
steps
are
for.
A
keycard
I'd
like
to
first
start
by
explaining
what
we
are
trying
to
build,
because
actually
we
are
doing
something
much
broader
than
building
just
one
single
hard
wallet
that
looks
like
a
card
and
is
integrated
with
status.
We
really
are
creating
an
open
ecosystem
for
smart
cards
are
in
the
crypto
space.
H
Can
you
go
to
the
next
slide?
Please,
and
so
what
does?
This
ecosystem
looks
like
even
surely
different
things
on
the
left
here.
You
have
some
example
of
third-party
projects
that
want
to
integrate
with
smart
cards.
These
are
mostly
mobile
applications
and
mostly
wallet
actually,
but
they
can
also
be
some
dedicated
hardware
projects,
one
example
being
a
grid
plus,
which
is
some
sort
of
home
connected
our
wallet
to
pay
your
utility
bills,
or
this
can
also
be
some
point
of
sales.
H
These
are
the
clients
and
on
the
right
side,
you
have
some
smart
cards.
So,
of
course,
key
card
itself,
the
one
on
the
top,
but
also
smart
cards
from
other
projects
and,
importantly
in
the
middle.
The
blue
to
this
ecosystem
is
our
open
set
of
protocols
and
tools
that
we
call
key
card
API,
and
it's
here
to
provide
interoperability
between
the
different
projects
so
that,
for
instance,
you
could
use
your
status
key
card
with
another
wallet
app
or
then
status
or
with
the
point-of-sale
x/y.
H
Overall,
we
are
trying
to
create
a
defect
to
standard
and
toolbox
for
all.
Contactless
are
where
it
likes
scenarios.
So
this
is
working
over
NFC,
of
course,
but
not
only
since
we
we've
seen
there's
some
need
to
standardize
how
hard
were.
Let's
talk
to
mobile
over
Bluetooth,
we
heard
that,
for
instance,
at
some
other
magicians
meetings,
for
instance,
and
can
you
go
to
next?
Do
the
next
one?
Please,
and
what
you
see
here
on
the
bottom
right
is
the
Nano
Ledger
x.
H
That's
integrity
that
have
integrated
the
key
code
to
be
able
to
use
the
nano
X
with
a
codification.
So
this
adds
value
to
do
a
whole
ecosystem.
So
this
is
really
what
we're
trying
to
build,
and
it's
going
to
take
us
some
time,
but
that's
reader.
The
vision
we
have
here.
Can
you
go
to
next
one,
please.
So
what
is
key
card
about
in
terms
of
use
cases?
H
What
we've
been
enabling
up
to
now?
Hardware
scenarios
to
bring
users
control
over
their
keys?
It's
been,
and
it
will
continue
to
be
the
it
will
continue
to
be
for
some
time
actually
our
main
focus,
but
there
are
two
other
use
cases
that
key
cada
can
enable
a
payment.
Fines,
10
so
use
your
account
to
pay
for
some
groceries
in
a
shop
for
your
transport
ticket
in
a
bus,
and
another
use
case
is
a
prepare.
H
The
crypto
cards
so
buy
in
a
shop,
some
Crito
crypto
by
buying
a
card
with
yet
and
what's
in
it
for
status.
Of
course.
First
we
are
empowering
empowering
sorry
the
ecosystem.
We
are
bringing
tools
for
any
projects
to
build
these
use
cases
for
themselves.
We
also,
of
course,
driving
studies
adoption,
because
we
are
making
a
better
user
experience
for
those.
H
We
use
status
application
and
we
are
doing
a
third-party
projects
and
the
progress
to
build
the
for
statistical
system
directing
this
ecosystem
will
also
help
us
to
build
new
partnerships
for
for
sure
and,
interestingly,
it
will
create
revenues
because
t
code
is
going
to
be
sold
and
it
will
drive
those
revenues
that
will
cover
the
development
cost,
which
is
interesting.
Obviously,
can
you
go
to
next?
Please?
So
what
are
we
building
exactly
we're?
Not
building
one
thing:
we
have
been
in
four
different
things
that
are
distinct
projects.
H
H
H
We
love
first
complete
samples,
meaning
the
card
packaging,
the
booth,
let
the
booklet
getting
out
of
the
real
factory
that
we
manufacture
them
by
end
of
January
and
the
first
real
production
of
a
lot
of
2000
products
will
happen
in
the
last
days
of
February,
so
we'll
have
them
ready
to
be
dispatched
by
first
week
of
March.
That's
for
the
card
for
a
patent
API.
We
worked
on
the
key
card,
API
v2
that
covers
hardware.
That
scenario
it.
H
This
is
ready
and
we
are
currently
in
research
phase
for
v3
of
the
API
I'll
come
back
to
that
and
that's
what
the
status
app
it
will
be
in
the
beta
release
in
March.
Come
back
to
that
also,
can
you
go
to
next
one,
please
so
some
more
updates
about
the
projects.
If
we
go
more
in
detail.
As
for
the
card
itself,
this
is
the
concurrent
design,
so
it's
a
flat
design
to
be
shipped
within
a
letter.
It's
using
status
blue.
H
We
have
a
new
logo,
we've
got
a
booklet,
we
have
the
user
setup
this
key
card,
and
this
is
what
we'd
get
an
end
of
the
month
in
samples.
Can
you
go
to
next?
One
please
Ned
and
Johnny
are
exploring
new
branding.
Language
is
for
Takada,
so
this
is
really
uncool
now,
what's
the
what's
displayed
here
is
purely
exploratory,
but
we
want
to
use
this
new
branding
language
for
the
upcoming
website
and
possibly
for
the
production.
H
Can
you
go
to
next
one,
please
yeah?
As
for
the
card,
so
we
we've
got
a
good
partner
with
self.
That's
our
Factory,
it's
a
factory
in
France.
We
have
committee
to
manufacturer,
10000
key
cards
with
them.
The
first
lot
of
2000
by
end
of
February,
as
I
said,
the
photo
all
the
logistic
part,
meaning
getting
I
mean
taking
care
of
the
stock,
the
fulfillment
and
the
shipment.
H
We've
got
a
pretty
good
deal
with
them,
so
we'll
start
with
them,
but
I'm
assessing
more
competitors
to
make
sure
we
have
best
distribution
price
for
the
future
and
lasting.
A
quick
remark
is
that
status
has
now
officially
a
registered
number
to
deploy
smart
cards
a
pet.
So
it's
something
that's
required
by
ONC
and
the
ISO
rules
next,
one
please
so.
As
for
the
API
in
a
pet,
as
previously
previously
said,
Adam,
we
worked
in
the
past
months
from
Kiko
v2,
it's
ready
now.
H
This
is
what
we'll
use
for
the
lounge
and
it's
about
our
weighted
scenarios.
Why?
It's
not
a
v1,
because
we
fixed
many
things
and
we've
improved
with
the
framework
I'm
by
adding
count,
duplication
which
can
be
a
possibility
native
to
writing
ham
mnemonic.
It
means
that
the
second
key
card
can
backup
your
secrets.
H
It's
safer
than
a
piece
of
paper.
Without
your
twelve
words
were
written
on
it.
We've
added
tap
to
download
an
application
for
the
setup
and
tap
to
launch
this
application.
We've
got
now
Android
and
desktop
SDK
and
we've
got
much
better
documentation.
So
this
is
ready
and
we
are
in
research
phase
for
v3
of
this
API.
H
We
are
adding
mostly
the
old
point
of
sale,
use
cases
and
also
signature
applet,
because
we
want
to
be
able
to
uniquely
identify
each
card
and
it's
a
pretty
simple
application,
but
we
needed
to
enable
crypto
cards
use
cases,
meaning
you
buy
one
card
in
the
shop
with
a
whenever
you
need
for
flat.
So
that's
going
to
be
a
good
post
in
discuss
about
the
point-of-sale
use
cases
that
I'll
pass
the
later
today
so
watch
out,
and
your
feedbacks
are
most
welcome
next,
please.
As
for
the
application
status
up,
there's.
H
Obviously
a
lot
of
work
going
on
here.
What's
done
is
the
specification
or
the
UI
or
the
screens
or
the
cistern.
Of
course,
all
the
card
upgrade
meaning
uploading,
the
the
firmware
or
the
creation
of
accounts,
the
settings
this
is
done.
The
logging
with
the
key
card
is
Blagh,
because
we
have
a
dependency
on
weather.
Can
we
see
the
coping
I'll
come
back
to
that
and
what
we
still
have
to
do
is
signing
of
transactions
importing
account
and
migrating
emigrating.
An
existing
account
a
true
keycard
yeah.
H
We
merged
a
couple
of
peers
that
decouple
the
key
internally
does
not
appear
pure.
That's
open,
create
the
two
different
keys,
the
white
one
and
a
chat
one
and
Android
opening
last
one
to
log
in
with
the
key
code
and
inject
the
whisper
key
on
the
user
experience
front
and
Jerry
and
Esther
add
to
define
a
simple
way
to
define.
H
You
can
see
my
wallet
address,
we've
chosen
a
pretty
simple
path,
which
is
to
allow
that
my
contacts
and
my
contacts
only
can
see
my
my
wallet
address,
and
there
are
now
discussion
with
Esther,
Rachael
and
Angela,
mostly
on
what
strategy
we
should
take
to
migrate.
All
the
counts
to
two
new
accounts,
so
there'll
be
some
decision
to
take
on
this
has
as
a
team,
I
guess
in
the
coming
days.
H
Next
one
please,
as
for
marketing
me,
the
effort
is
mostly
driven
by
Johnny
and
Ned
for
the
branding
part
we're
going
to
face
this
first
phase,
which
is
to
be
fully
ready,
fully
ready
by
F
Denver
on
13
of
February.
The
goal
is
to
communicate,
but
the
hard
way
that
we
brand
to
key
card
to
create
awareness
and
engage
and
build
and
help
to
build
the
with
key
cost
for
other
projects
and
get
signups.
So
to
do
so,
we
are
working
on
a
new
website.
H
H
This
should
be
live
very
soon
since
McKinley
at
some
frustration
ready
last
week.
So
this
is
phase
one.
If
you
go
to
next
slide
phase
two
is
to
be
ready,
beginning
of
March
first
week
of
March
and
is
about
distribution.
The
word
is
ready
to
make
key
card
available
worldwide
for
any
developer.
That
wants
to
develop
with
it.
H
So
for
this
we
are
on
top
of
phase
one
setting
up
our
own
shop
so
with
its
content
and
setting
up
the
payment
channels,
including
crypto
payments
on
this
shop,
and
we
set
up
the
supply
chain
with
the
factory
and
that's
for
the
price.
We
got
several
discussion
about
that
starting
in
December,
and
the
consensus
seems
to
be
that
we
position
it
at
twenty
nine
dollars
or
Euros
and
we'll
have
some
rebates
at
lunch
to
facilitate
the
start
of
the
the
project.
Next
one
please.
H
H
To
finish
on
a
simple
message,
so
somehow
some
of
you
are
directly
working
on
key
card,
some
are
not
but
I
thing
for
sure.
We
can
all
do
something
to
add
with
the
project
it's
to
develop
the
awareness
and
help
engage
other
projects
to
build
whisky
card.
I.
Think
that's
really
the
key
thing
now
and
whether
you
participate
to
some
blockchain
conference
or
working
with
some
other
blocking
projects,
or
even
other
your
Twitter
account
of
your
own.
H
H
A
H
Opening
on
the
key
card,
the
channel,
so
there
were
a
lot
of
discussion
about
that
last
week,
but
I
guess
it's
a
since
I
had
the
same
question
from
us
Carl
one
hour
ago,
I
think
I'll
set
up
a
dedicated
channel
for
this
and
I
will
post
the
document
from
Esther.
That's
that
summarizes
or
the
discussion
we
had
last
week
about
it.
F
A
quick
one
I
just
want
to
plug
the
coded
meeting
on
Monday,
so
some
feedback
on
some
people.
If
there
is
anything
a
problem
or
something
you
might
announce
other
people
that
requires
sort
of
coordination
across
swarms,
it's
a
great
opportunity.
So
please
just
go
to
the
github
repo
and
add
stuff
you
want
up,
but
yeah.
A
H
Yeah
so
well,
it's
really
a
trade-off.
I
mean
we
want
to
create
adoption,
so
we
want
to
be
as
low
as
possible
and
well,
we
have
to
be
I,
mean
the
price
contact
to
make
sense
with
the
rest
of
the
market
and
also
we
want
to
generate
some
margin
to
cover
our
costs.
I
actually
shared
in
the
discus
past
in
December
least
of
all
AdWords
on
the
market
and
29
was
a
good
trade-off
because
it's
it's
cheaper
than
all
other
AdWords
with
the
same
type
of
function.
H
So
it's
a
good
price
point
to
trigger
adoption
and,
at
the
same
time,
it's
high
enough
for
us
to
sell
directly
but
also
high
enough,
so
that
in
the
future,
maybe
in
a
couple
of
months,
we'd
want
to
sell
that
through
some
distributors.
So
it's
really
a
question
of
trade-offs.
I
share
again
the
document
with
all
the
rationale,
but
the
29,
your
price
point
I.
F
Have
a
quick
question
on
how
you
met
and
let's
say
like
right
now:
a
lot
of
people
might
have
a
hardware
wallet
like
that's
your
chest
or
whatever.
How
do
you
imagine
people
going
from
that
to
the
using
key
code
more
roughly
how
it
will
what
work
with
the
key
code
API
or
if
it
will
require
people
to
transfer
funds
or
some
roughly
like
that.
F
H
F
F
If
I
have,
if
I
have
a
hot
wallet-
and
they
said
they
created
like
a
five
where
update
that
allows
us
to
use
the
key
card
API,
is
this
some
sort
of
mechanism
whereby
I
could
use
the
key
card
without
sort
of
moving
funds
or
a
movie
like
importing
in
Monaco?
Something
at
this
sorry,
it's
a
broad
question
I'm
just
trying
to
understand
their
I.
H
D
A
D
H
Idea
would
be
to
really
to
present
a
flat
price
to
the
user,
because
the
user
will
spend
some
fiat
at
the
store
so
and
convert
that
to
a
crypto
that
we
have
to
choose
either
die
or
s
NTS
or
either,
but
yeah.
Really.
The
goal
is
to
be
this
gateway
between
the
Fiat
and
one
crypto
we
choose.
So
basically
message
would
be.
D
H
D
H
H
Does
it
have
to
be
one
crypto
I
mean
it's
well,
we
have
to
start
off
with
one
crypto,
because
the
message
needs
to
be
clear
for
the
user.
Well,
we
can
say
back
10
euros
worth
of
crypto,
but
maybe
that
would
be
too
vague.
You
know
if
you
were
gonna
spend
your
10
euros.
You
want
to
know
what
you
get
if
you
just
say,
get
some
crypto,
the
one
you
may
be,
the
one
you
choose
on
a
within
the
app.
H
D
C
B
The
first
use
right
now
and
one
of
the
things
we
want
to
do
instead
is
to
have
people
register
the
username
or
whatever
so
I
think
Lee.
They
should
need
some
SMT
and
then
maybe
we
want
to
encourage
them
to
try
out
some
of
the
service
or
simply
have
something
to
do
with
that
crypt,
and
maybe
we
want
to
die
so
that
they
also
don't
feel
cheated.
So
I
don't
know
if
it
necessarily
has
to
be
one.
F
What
one
idea
framing
that
would
be,
you
say
you
get
10
euros
worth
of
F
and
then
you
have
textual.
You
take
a
bit
of
profit
in
the
spread
price
and
then
you
give
hundred
S&T
for
for
free.
But
really
the
total
value
is
the
same,
but
you
just
you
make
it
some
some
amount
of
F
and
then
you
just
give
some
S&T
or
whatever
free.
A
Great
ideas,
I
think
it
will
be
really
useful
if
there
was
a
yeah.
If
you
want
it,
when
you
publish
your
discuss
post
key,
if
you
could
put
a
channel
per
people
to
kind
of
give
suggestions,
feedback
I
think
is
a
very
exciting
project
and
a
lot
of
people
you
know
either
want
to
get
involved
there.
You
know,
have
some
ideas
to
make
it
even
more
successful.
Yeah.
H
D
H
I
mean
absolutely,
and
actually
when
I
was
talking
about
the
discussed
post
I'd
send
this
afternoon.
It's
about
yeah,
point-of-sale
use
cases
and
that's
an
abuse
Wanya
using
the
status
application
as
a
point
of
sale.
But
I
really
really
would
like
your
everyone's
input
about
some
concrete
real-life
setting
scenarios
in
this.
In
this
use
case,
but
for
sure
I
mean
we
have
the
opportunity
to
turn
everyone's
phone.
We
studies
up
into
a
point
of
sale,
which
is
where.
A
Both
for
accepting
payments
as
well
as
telling
Network,
so
you
can
see
from
the
sellers
side
there's
a
lot
of
overlap
there.
Well,
there
will
be
overlap
on
that
on
when
you
start
getting
to
a
point
of
sale
system
with
what
they're
telling
network
is
doing
as
well.
Just
I'm
going
to
keep
in
mind
not
to
distract
yeah.