►
From YouTube: Fil+ July 26, 2022 Notary Governance Call
Description
The July 26th community governance calls to discuss the Filecoin Plus program.
Github:
https://github.com/filecoin-project/notary-governance/issues/567
Slide Deck:
https://docs.google.com/presentation/d/1RNecvaa_O4DO8ES2Pwn54a_0bQv6QDRj47P2abGzn60/edit?pli=1
If you would like to attend these meetings LIVE, the Fil+ Notary Governance calendar is available at: https://calendar.google.com/calendar/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0%40group.calendar.google.com&ctz=America%2FLos_Angeles
Follow Filecoin!
Website: https://bit.ly/3ndAg44
Twitter: https://bit.ly/3ObND0x
Slack: https://bit.ly/3HKfFy7
Blog: https://bit.ly/3HFZFNv
Reddit: https://bit.ly/39N4Jmv
Telegram: https://bit.ly/3bkP8Ly
Subscribe to our newsletter! https://bit.ly/3Oy8J9j
#filecoin #ipfs #libp2p #web3 #nft
A
All
right
well
good
morning,
good
evening,
everyone,
this
is
the
14th
notary
governance
sink
of
2022,
it's
july
26th,
and
we
have
a
very
full
agenda
here.
So
let's
take
a
look
at
what
we're
going
to
be
covering
on
this
call.
We
stick
with
the
same
basic
format.
So,
if
you're
watching
this
for
the
first
time,
we
kind
of
start
with
lows,
intros
make
sure
everyone
on
the
call
is
a
participate.
A
We
are
going
to
cut
down
the
metrics
today
and
just
quickly
give
a
quick
overview
that
we
have
more
time
for
the
community
discussions,
because
we
have
a
very
full
agenda
of
many
points
to
bring
up
today.
So
with
that
again,
we
are
your
friendly
governance
team.
That's
deep,
galen,
myself
and
or
jeff
any
help
you
need,
or
any
kind
of
troubleshooting
or
direction
would
be
the
ones
to
kind
of
fork
you
off,
where
you
need
to
go
we're
in
the
biocoin
slack.
A
If
you
have
questions
as
well
as
the
repo
for
anything
you
may
need,
we
are
piloting
a
new
project
on
this
call.
It
may
or
may
not
work
what
it
is.
It's
a
system
called
otter.
It
sits
in
on
these
calls:
it
listens
to
the
voices
that's
taking
place
and
then
it
provides
a
transcription
service
after
the
call
in
the
form
of
an
srt
file.
We
can
then
have
that
srt
file
translated,
so
that
those
of
you
who
are
mandarin
speaking
or
non-english
speaking,
you
can
then
have
the
translation
service
available.
A
This
is
the
first
time
that
we're
testing
it
in
mass.
So
hopefully
we
worked
the
bugs
out
for
this
call,
but
you
may
notice
an
otter
sink
and
just
letting
you
know
that,
in
addition
to
this
call
being
recorded
for
the
video
on
youtube,
there
will
be
that
transcription.
That
runs
with
it.
If
you're
on
the
call
and
you're
participating
having
more
information
on
your
name
makes
it
really
really
helpful
to
kind
of
route
where
your
questions
are
coming
from
and
where
you
are
as
a
participant
on
this.
A
So
you
can
see
our
name
right
now
and
kevin
foulcoin
foundation
makes
it
really
easy
to
route
it.
If
you
wouldn't
mind
right
clicking
on
your
name
and
just
being
like
you
know,
kevin
notary
or
jim
notary
or
jim
community
participant
that
way,
when
we're
answering
your
questions
in
slack
or
we
go
back
into
github,
it
makes
it
really
easy
to
line
up.
Otherwise,
some
of
your
valuable
feedback
may
get
lost
in
the
call.
A
As
we
start
getting
these
big
discussions
going
if
you're
joining
the
call,
please
make
sure
that
you
follow
this
link,
we'll
post
it
there
in
chat.
This
is
what
this
page
looks
like
the
notaries
that
are
on
this
call.
You
would
have
got
a
dm
from
me
in
the
last
couple
of
days
and
weeks,
just
making
sure
I've
got
your
participation
logged.
A
A
So
please,
I
encourage
all
of
you
not
just
notaries,
to
fill
this
out.
That
way,
we
can
kind
of
have
a
record
and
kind
of
brought
you
to
the
best
places
to
get
you
the
support
you
need.
So
with
that
quick,
look
at
metrics,
we
pulled
this
metric
page
from
this
statistics
that
you'll
see
in
the
link-
and
I
shared
this
slide
deck
in
the
slack
notary
channel.
Excuse
me
the
fill
plus
channel.
A
So
if
you
want
to
follow
along
and
see
these
yourself,
the
quick
thing
to
update
is
you'll
see
some
of
these
times
have
just
skyrocketed,
like
our
average
time
to
datacap.
It's
gone
up,
update
our
average
time
to
ldn
we're
really
diving
into
these
numbers
and
what
they
are
is
outdated
proposals
and
ldn
applications
that
are
super
long
and
they've
just
been
waiting
for
some
kind
of
question
or
allocation
and
when
those
are
80
90
100
days.
A
What
those
do
is
those
really
affect
the
metrics
that
come
on
so
galen
posted
in
the
notaries
channel
a
couple
of
days
ago,
with
nine
applications
we'll
be
following
up
on
that
list,
just
to
kind
of
get
those
numbers
that
are
outliers
really
impacting
this
pipeline,
and
so
to
do
that,
just
like
we
showed
on
last
week.
What
we've
been
doing
is
pulling
some
of
these
really
large
applications
that
we're
sending
specific
pings
so
notaries.
A
So
that's
a
quick
overview
of
the
call
quick
overview
about
who
the
members
of
the
community
team
are
and
a
quick
overview
of
the
metrics.
This
is
the
specific
agenda
that
we're
going
to
walk
through
on
the
call
today
and,
as
you
can
see,
it's
broken
into
six
main
points.
So
the
first
thing
we're
going
to
talk
about
is
just
a
reminder
that
the
august
call
times
are
going
to
be
shifting
as
a
pilot.
We're
going
to
be
talking.
A
A
quick
review
of
the
ldn
out
of
cycle
update
that
we
proposed
last
week
give
you
one
last
chance
to
provide
feedback.
We
got
a
lot
of
great
input
on
that
issue.
Kevin
z
will
be
walking
us
through
an
enterprise
proposal
pilot
that
he's
put
together
we're
going
to
be
talking
about
project
beacon.
I
know
that
we
had
a
lot
of
discussions
in
that
github
issue,
so
this
is
a
chance
to
kind
of
ask
additional
clarifications
or
kind
of
share
any
thoughts.
You
may
have
galen's
going
to
take
this
through
the
ldn
notary
disclosures.
A
We
shared
this
on
the
last
call.
We
have
some
updates
on
these
five
and
then
just
give
you
a
chance
to
weigh
in
on
it.
Then
we
also
have
a
call
back
to
an
issue
that
came
back
in
september
and
that's
the
ldn
process
just
checking
in
it's
been
a
half
year
and
so
galen's
going
to
kind
of
spend
some
time
walking
through
that.
A
Since
it's
such
a
discussion,
heavy
call,
we
kind
of
went
through
the
metrics
a
little
bit
faster,
but
we
do
have
the
links
there.
If
you
want
to
see
them
and
we
might
kind
of
allocate
some
time,
I
would
request
that
if
we
do
have
discussions
that
you
raise
your
hand
in
the
slack,
it
makes
it
really
easy
to
circle
back
any
questions
that
you
want
to
kind
of
come
to
posting
in
chat,
galen,
myself
or
jeff
deep,
we'll
be
kind
of
checking
that
chat
and
making
sure
that
we
can
post
those
questions.
A
So
with
that,
I
will
jump
into
just
the
quick
two
slides
about
the
updates
and
I'll
hand
it
over
to
kevin
z.
So
first
update
the
governance
meeting
time,
starting
in
the
next
two
weeks
in
august,
is
going
to
shift
back.
Not
this
call,
but
the
next
call-
and
so
you
can
see
the
current
times-
is
going
to
shift
to
6
p.m.
California,
time
0,
100
beijing.
A
If
you
are
curious
to
follow
this
calendar,
we
shared
this
link
in
the
notary
channel
here
as
it
loads,
and
what
this
will
do
is
this
is
a
shared
google
calendar.
That
will
then
allow
you
to
add
this
to
your
own
schedule.
That
way,
you
might
not
be
relying
on
me
human.
I
make
typos.
I
think
I
posted
july
25th
versus
the
26th,
so
I
went
with
that
load
too
long,
but
just
as
a
quick
reminder
that
afternoon
call
is
going
to
shift,
and
hopefully
we
see
a
lot
more
friendly
faces
on
that.
A
A
So
this
proposal
was
talking
about
two
things:
one
was
getting
these
two
notaries
on
to
the
ldn,
but
maybe
a
higher
level
root
issue
to
kind
of
have
for
discussion
is
as
a
community
in
phil
plus.
How
are
we
approaching
off-cycle
changes
that
are
outside
of
the
election
process?
Do
we
want
to
constantly
hold
elections
every
two
or
three
months
and
put
notaries
through
that?
Or
do
we
want
to
have
it
be
a
relatively
low
lift
issue?
A
They
can
answer
it
kind
of
get
a
feel
for
their
track
record
on
ldns,
but
again
is
a
refresh.
These
are
applicants.
Excuse
me,
notaries
that
are
in
good
standing
have
no
suspicious
activity;
they
just
wish
to
allocate
on
the
ldn,
v3
and
currently
they're
blocked,
because
they
didn't
go
through
this
very
specific
process.
So
if
you
had
any
thoughts
on
this,
we
talked
about
it
last
week.
This
is
kind
of
the
last
call
of
this
github
issue
and
then
we'll
do
a
final
thread
in
the
slack.
A
B
B
Over
the
past
few
months,
meg
dennis
from
hall
on
was
sort
of
leading
the
charge
on
an
enterprise
program
proposal
and
that
was
put
together
in
june
posted
in
the
github
repo
and
since
then,
I've
taken
over
as
the
as
the
project
lead
to
help
push
this
project
forward
through
the
remaining
phases.
So
what
I
just
wanted
to
cover
today
quickly
over
the
next
few
minutes,
was
a
brief
update
on
kind
of
where
we
were
where
we
are
and
and
go
through
some
more
details
related
to
the
project.
B
B
I'm
gonna
talk
more
about
the
details
of
this
phase
on
the
next
slide,
but
this
is
really
where
we're
going
to
design
the
program
in
detail
and
there's
a
lot
of
opportunity
for
the
for
the
members
of
the
community
to
be
involved
and
to
discuss
some
of
the
key
pieces
of
that
and
then
finally,
the
goal
is
to
complete
the
planning
phase
and
then
by
october,
hopefully
we'll
be
able
to
kick
off
a
proof
of
concept
pilot
over
the
next
six
months.
There
that'll
go
from
october
through
april,
so
next
slide.
B
B
I've
also
positioned
several
proposals
that
are
open
for
discussion
with
the
community,
so
you'll
see
in
the
next
bullet
there
over
the
next
two
weeks.
I'd
love
to
open
up
discussions
on
each
of
these
topics
related
to
designating
a
lead
sp
as
part
of
an
enterprise
program.
What
are
the
data
distribution
rules
to
be
established
up
front?
B
What
are
the
allocation,
the
data
cap
allocation
enhancement,
potential
requirements
and
expectations,
and
then
also
you
know
in
terms
of
kyc
mechanisms
for
enterprise.
So
we
have
separate
discussion
topics
that
are
open
for
everyone
to
go
in
read
through
some
of
the
proposals
and
provide
feedback
and
and
review
for
us
there.
So
I,
the
goal
would
be
to
come
back
in
two
weeks
on
the
next
notary
governance
call
and
potentially
have
a
little
bit
more
time
to
open
up
some
discussions
for
those
things
there.
B
B
B
I've
put
together
a
website
that
that
goes
through
the
eligibility
and
the
and
the
details
for
sps
who
are
interested
in
participating
in
the
pilot.
I
know
there's
a
lot
of
interest
out
there
in
the
community.
I've
heard
personally
and
other
people
have
expressed
to
me,
but
this
is
going
through
sort
of
the
criteria
you're
looking
for,
if
you
want
to
participate
not
only
from
an
sp
perspective
but
from
a
client
perspective
and
then
all
the
additional
details
related
to
timeline
phases
and
those
types
of
things.
B
So
I
would
encourage
everyone
to
please
go
through
review.
Those
details
provide
any
feedback
again
at
this
point.
This
is
just
a
proposal.
This
is
a
broad
sort
of
overview
that
we're
hoping
to
include
as
part
of
this
program
so
then
continuing
on
here
over
the
next
month
in
august,
we're
going
to
be
spending
a
lot
of
time
going
through
and
building
out
and
designing
this.
B
This
enterprise
pilot
in
more
detail
meg,
put
together
a
lot
of
framework
that
we're
going
to
use
and
we're
going
to
use
a
design
thinking,
mvp
methodology
to
go
through
and
review
all
the
different
requirements
that
are
from
from
when
a
client
starts
all
the
way
up
until
a
client,
you
know
receives
data
cap
and
goes
through
the
program
there.
So
there'll
be
a
lot
of
potential
meetings,
I'll
reach
out
we'll
have
discussions
within
the
working
group,
so
so
keep
that
in
mind.
B
Next
slide,
please
so
so
that's
it!
I
just
wanted
to
give
a
quick
overview
of
where
we
are
with
the
planning
phase
I'll
post
this
presentation,
all
of
the
discussion
topics
are
listed
within
the
repo,
so
feel
free
to
go
into
each
of
those
and
read
through
the
details
and
the
general
proposal.
Number
559
is
also
out
there.
B
If
you
need
to
go
back
and
refresh
yourself
on
what
is
included
in
this
enterprise
program
again,
the
plan
will
be
to
come
back
in
two
weeks
and
maybe
have
a
broader,
open
discussion
on
some
of
the
topics.
If
we
want
to
once
we
have
some
feedback
and
some
ideas
on
what
members
of
the
community
are
thinking
and
I'm
also
encouraging
everyone
to
join
the
slack
channel.
B
There's
a
phil
plus
enterprise
working
group,
slack
channel-
that's
open,
feel
free
to
join
that
I'll,
be
posting
more
information
there
as
well
and
offering
potential
meetings
and
and
some
working
group
sessions
on
a
lot
of
the
customer
journey
and
the
tech
requirements
that
will
be
upcoming
over
the
next
month
month
and
a
half
I'll
pause
there.
I
don't
know
if
there's
any
questions
or
thoughts
at
this
time.
B
B
That
will
be
a
struggle
to
get
through
the
current
flow,
but
as
part
of
this
pilot
they
would
be
very
welcome.
So
I
think
the
idea
will
be
to
include
those
those
applications
as
part
of
this-
and
I
I
don't
have
the
detail
on
exactly
those
but
we'll
be
working
through
some
of
those
open
cap
applications
I'll
get
some
details
from
galen
and
others
who
have
more
details
there,
but
just
in
just
more
broadly
to
answer
your
question.
B
You
know
the
idea
is
for
sps
to
really
be
the
lead
vd
in
in
the
lead,
bd
role
here
so
they're
bringing
in
their
own
clients
that
they
might
have
gone
through
discussions
with.
They
have
ideas
around
the
data
around
their
their
requirements
and
they're
going
to
lead
the
the
client
through
this
process.
B
All
right
kevin.
Well,
I
think
that's
it
for
me
today,
like
I
said
everyone,
please
please
go
to
the
discussion
topics.
Please
leave
feedback
join
the
slack
channel,
we'll
continue
moving
forward
and
in
two
weeks,
we'll
potentially
have
a
more
broader
open
discussion
around
some
of
the
proposals
that
are
that
are
out
there
right
now.
A
E
E
I
think
it's
continuing
to
be
a
bit
of
a
hot
topic,
and
so
I
just
wanted
to
do
like
a
quick
recap
of
what
I
think
the
sort
of
the
summary
of
the
conversation
if
you're
not
cut
off
caught
up
and
then
a
couple
of
the
main
like
outstanding
points
for
this
particular
case
so
effectively.
This
started
out
as
an
application
to
store
a
bunch
of
what
was
like
flagged
as
educational
content.
Actually,
I
don't
know
is
eric
on
the
line
he
mentioned
that
he
might
be
able
to
come.
F
E
I'm
here
yeah
cool,
so
eric
I'm
gonna
do
a
quick
intro,
and
then
you
please
correct
anything
that
I'm
saying.
If
you
don't
mind,
even-
and
maybe
the
client
is
here
as
well-
that'd
be
great,
but
basically
started
out
as
an
application
for
uploading
about
11
terabytes
of
unique
educational
content,
which
would
have
ended
up
requiring
a
footprint
of
about
60
peppy
bytes
on
chain,
and
there
was,
like
you
know,
pretty
clear
documentation
up
front
on
where
the
schools
were
that
were
sourcing.
E
E
There
was
some
discussion
on
generally
like
video
surveillance
overall
and
like
where,
like
what
place
that
has
in
the
falcon
plus
program
is
like
encrypted
data.
That
is
not
useful
in
use
cases
beyond
this,
there
was
question
around
like
what
is
the
purpose
of
supporting
private
encrypted
data
on
filecoin
plus
like
in
which,
in
which
cases
should
we
be
doing
it
versus
not,
and
then
towards
the
end,
where
it's
sort
of
headed
right
now
is
like
hey.
E
There's
a
subset
of
notice
that
I've
already
done
that
and
are
happy
to
support
the
application
that
span
a
couple
of
regions,
so
we're
just
double
checking
to
make
sure
we've
got
the
right
set
to
make
sure
we
can
proceed,
and
then
you
know
in
from
from
a
community
standpoint
when
you
can
validate
through
a
notary
with
whether
or
not
the
data
is
useful.
The
only
other
thing
going
on
the
piece
of
data
we
have
is
the
storage
fighters
they're
choosing
to
work
with.
E
A
E
F
So
I'm
going
to
talk
about
sps
first,
because
this
is
the
foundation
of
the
of
safarico
network.
During
the
last
years
in
china,
the
nationals
released
the
national
laws
and
the
regulations,
the
only
for
the
crypto
mining
in
china
and
also
the
the
top
sps
I
mean
for
the
fico
sps
was
arrested
in
china
and
also
a
data
center
was
forced
to
close
somewhere.
So
you
guys
must
know
a
couple
of
days
ago
we're
losing
the
more
than
100
petabytes
robot
power
yep.
F
That's
a
big
data
center
located
in
inner
mongolia
was
shut
advanced
by
the
government
and
also
the
kind
of
power
cut
the
network.
So
you
know
the
reason,
and
also
about
now
about
the
sp
right
now
in
china.
So
I'm
going
to
name
this
to
how
to
survive
so,
some
of
them.
I
think
that
20
of
them
go
abroad
and
also
they're
starting
the
new
life
there,
and
also
you
can
see
some
chinese
investor
in
austin
or
even
in
toronto.
F
F
Fine,
because
they
move,
because
everybody
know
I
mean
especially
for
the
psp.
They
know
you
guys
are
running
the
the
falcon
a
lotus
note
in
in
a
data
center.
So
you,
if
you
move
out
from
the
data
center,
you
can
toward
the
psp
to
find
you
up
and
also
they
use
some
technical
support
to
have
their
ip
address
so
regularly.
So,
in
my
words,
the
chinese,
the
sp
in
china
right
now
they
are,
they
are
leaving
like
like
on
the
reserve
age.
F
You
know,
so
they
move
out
from
the
data
center
and
also
they
hide
their
ips
on
the
internet
and
otherwise
the
psp
will
find
you
out
so
the
community
education
operators
and
also
the
client.
So
last
october,
yes,
last
october,
the
the
data
security
law
of
the
people's
republic
of
china
was
released.
That's
why
you
can
see
a
only
few.
I
mean
the
latest
state-owned
clients
can
join
the
vicon,
so
you
can
see
right
now.
The
people
who
make
the
clients
make
the
applications
in
in
the
fico.
It's
not
the
state-owned.
F
Okay,
so
I'm
not
talking
to
talking
about
the
vicon
economic
model
in
china,
I'm
not
quite
sure,
that's
quite
different
for
for
from
the
u.s
or
from
the
other
side.
So
in
the
last
one
years,
when
the
people
would
like
to
join
the
final
network,
there
will
be
the
ratio.
The
investor
ratio
will
be
like
the
50
for
file
and
the
hardware
for
percent
and
the
lotus
operations
for
twenty
percent,
and
in
this
year's
it
will
change
to
five
hundred
will
be.
F
F
So
I'm
going
to
answer
the
questions
which
you
leave
on
the
github,
so
why
is
the
lead?
Sp
system
is
not
suitable
for
the
project
beacon
because
during
the
the
above
information,
which
I
provide
provided
so
the
no
sp
in
china
would
like
to
take
such
a
risk
to
do
that,
because
the
why
by
the
base?
So
that's
we
are
working
as
a
coordinator
to
between
the
sps
and
the
clients.
F
As
you
guys
can
see,
this
is
not
an
easy
task
and
also
the
top
priority
in
finding
sps.
In
the
project
weekend,
we
are
focusing
on
having
their
enough
fails,
because
the
selling
service
is
no
longer
to
making
any
difference
nowadays.
So,
with
with
this
kind
of
the
goal,
we
are
distributing
this
task
to
more
than
30
investment
organizations.
F
So,
after
like
a
round
of
runs,
communication
or
selections,
12
of
the
investment
organization
were
willing
to
take
the
role
of
sp,
and
these
12
sps
are
responsible
for
the
the
corresponding
capitals
rising
tasks.
If
they
could
not
match,
I
mean
if
they
could
not
approach
with
themselves.
They
would
like
to
require
to
be
the
responsible
to
recruiting
more
small
sps.
I
mean
to
to
finding
the
fails.
F
F
And
the
third
one
is
why
new
sps
with
zero
power
and
no
margin
address.
So
this
is
a
good,
very
good
point.
So,
during
the
preparation
of
the
project
beacon,
some
sps
created
empty
nodes
for
the
I
can
say,
let's
create
the
empty
nodes
to
stake
for
clear
asset
for
allocation
in
the
future.
So,
therefore,
starting
from
the
nodes
with
zero
power
is
definitely
the
best
choice
for
the
investors
who
send
you
the
file.
F
F
So
that's
it
compared
with
the
web
2
storage
provider
like
aws
or
google.
They
need
to
do
one
more
things:
let's
get
the
file.
So
so
did
you
remember
the
what
I
mentioned
with
the
outsourcing
service
provided
for
the
service
provider?
This
is
a
very
a
unique
road
in
in
the
ecosystem
of
china.
Many
storage
providers
having
the
same
outsourcing
team
in
charge
of
their
lotus
operations.
So
compared
with
the
individual
stories
provided
in
us
in
north
america
and
in
europe,
the
the
chinese
farm
market
is
so
different.
C
Yeah
my
question
is
my
question
is
basically:
why
are
you
still
pursuing
to
store
this
data
inside
china
if
it's
not
allowed
anyway?
Why
not
store
it
outside
china?
The
data
is
encrypted.
Nobody
can
read
it
except
your
client,
so
I
don't
understand
why
you're
still
suing
to
to
only
do
this
with
chinese
storage
providers
and
not
select
providers
in
north
america
or
australia
or
singapore
or
other
providers
somewhere
else
in
asia.
F
C
F
What
means
it's
not
means
the
average
storage
provider
can
terminate
their
sector
and
get
the
fell
out,
otherwise
the
falcon
network
will
be
crashed
because
everybody
knows
chinese
sp
is
holding
more
than
50
percent
of
the
power
in
falcon
network.
I
know
that
that's
why
we
know
that
they
are
hiding
themselves.
C
Yeah,
I
know
that
the
situation
is
difficult,
but
my
question
is:
basically:
you
are
not
sp.
You
are
not
allowed
to
run
in
china.
Fine,
I'm
fine
with
that.
If
that's,
if
that's
as
it
is,
but
why
don't
you
store
it
outside
china
if
it's
encrypted
anyway?
Why
don't
you
join
the
fill
plus
program
and
put
it
there?
So
we
can
have
governance
and
we
can
put
it
on
minus
where
it's
secure,
because
if
your
client
wants
to
retrieve
it
and
your
data
center
is
closed,
yeah
there's
no
use
anyway.
F
You
know
finding
these
clients
the
project
beacon
decline.
You
know
they
would
like
to
use
the
fico
network
and
also
they
would
like
to
coordinate
with
others
sp.
So
this
is
a
huge
project
when
protocol
product
labs
knows.
I
started
this
project
in
february
of
this
so
regularly.
We
cannot
stop
it
when
the
client
is
ready
and
also
we
find
the
sp
is
ready.
So
if
we
jump
out,
we
cannot
make
it.
C
I
don't
say
you
need
to
jump
out.
I
say,
find
your
storage
providers
outside
of
china
and
put
in
phil
plus
yeah,
because
if
you're,
if
you're,
if
you're
in
yeah,
I
know
it's
important,
but
if
you're
storing
in
china-
and
it's
not
allowed
to
store
there,
your
data
center
gets
close.
Your
sp
gets
closed.
Your
sp
gets
arrested,
so
there's
no
use
to
do
it
over
there
because
the
data
will
be
inaccessible
anyway.
F
So
the
the
reason
in
china
is
number
one:
the
law
is
not
an
out,
and
the
number
two
is
the
sps
in
china
was
the
setup
they
are
not
all
over.
The
china
and
also
the
client
would
like,
if,
like
they
retrieve
all
the
data,
so
it's
in
the
china
main
end.
So
no
matter
the
website
at
the
internet,
speed
and
also
the
the
shipment
for
the
hard
disk.
It's
quite
easy
for
them
to
go
abroad.
E
Yeah
eric,
I
think
the
question
still
stands
on
like
do
you.
Do
you
think
that
it
is
going
to
be
realistic
for
those
sps
to
actually
be
able
to
store
that
data
while
staying
in
hiding
in
china,
or
do
you
think
eventually
they're
going
to
move
out
anyway,
because
it,
I
think
what
wine
end
is
bringing
up?
E
F
For
me,
it's
hard
questions.
You
know,
I
don't
know
what
happened
for
the
next
or
for
for
the
psp.
By
doing,
but
through
the
sv
which
I
reach
it,
they
try
to
protect
themselves.
There
are
a
lot
of
ways
to
to
to
do
that,
because
no
one
would
like
to
terminate
the
sectors
and
they
would
like
to
keep
contribute
in
the
firecall,
so
they
will
find
them
where
their
way.
E
G
Chinese
storage
use
case
right.
The
the
isn't
strange,
crypto
nonsense,
but
is
an
actual
applicable
use.
So
this
is.
This
is
a
good
version
of
that
right.
The
reason
why
it
doesn't
make
sense
to
like
just
store
it
somewhere
else
if
it's
illegal
within
china
or
illegal
outside
china
is,
if
you're
trying
to
make
the
case
for
a
legitimate
system
within
china,
so
that
the
storage
providers
have
a
stronger
leg
to
stand
on.
G
The
last
thing
you
want
to
do
is
to
break
another
law
right
like
another,
far
more
far
clearer,
like
regulation,
so
we're
in
this
situation
where
and
people
can
jump
in
and
correct
me
if
I'm
wrong
right,
where
there
is
ambiguity
about
whether
distributed
storage
provision
within
china,
it
comes
within
the
regulations
or
not,
but
there's
a
definite
ban
on
moving
this
data
and
not
localizing.
This
data
within
the
country.
Is
that
a
fair
assessment
of
what's
being
said
here.
H
I
think
I
think
so
I
think
this
is
similar
to
what
like
faye
is
bringing
up.
You
know
regarding
flat
enterprise
file
coin
and,
like
other
use
case
examples
of
this,
where,
in
certain
regions
like
australia,
there's
data
that
will
be
encrypted,
that
people
will
argue
is
useful
and
meaningful
and
that
legally
shouldn't
go
out
of
that
country
and
may
be
distributed
around
australia
to
other
interests.
H
I
think
where
some
of
the
concern
is-
and
I
think
that
this
is
the
sort
of
next
evolution
of
the
question,
which
is
what
wine
and
is
also
bringing
up.
Is
that
how
do
we
have
confidence
that
if
we
approve
that,
if
we're
also
saying
that
the
government
is
going
to
crack
down-
and
we
have
ambiguity
about
who
the
storage
providers
are
and
they're
trying
to
hide?
H
How
do
we
have
confidence
that
this
this
project
will
continue
and
they're
not
just
going
to
get
shut
down
or
slash
their
sectors,
or
you
know
so
why?
If,
if
what
we
are
afraid
of,
is
that
the
legal
situation
in
one
region
is
they're
going
to
come
after
and
so
the
solution
for
that
is
well.
Why
not
distribute
internationally?
H
And
then
we
say
this
is
a
circular
argument,
because
we
can't
distribute
internationally
because
that's
also
illegal
and
we're
trying
to
find
a
way
to
distribute
locally
and
gain
confidence.
So
I
think
I
think
that
we're
sort
of
talking
about
you
know
there's
a
problem
down
here.
So
why
not
this
solution?
But
that
solution
violates
this
other
problem,
which
is
what
we're
trying
to
like
get
around
in
the
first
place
and.
C
E
C
C
H
So
maybe
so
right
now,
the
proposal
is
for
60
pips,
but
it's
an
11
data
set.
So
maybe
a
possible
solution
is
similar
to
how
we're
asking
people
to
gain
confidence
slowly
over
time
start
with
a
smaller
proof
of
concept,
with
one
clear
storage
provider
for
that
one
data
set
that
is
11
pibs
and
go
from
there.
I
think,
like.
H
H
D
Yeah
one
one
point
is
that
I
feel
the
pain
from
the
presentation
that
storage
providers
are
having
a
hard
time
and
or
not,
but
I
think
we
gotta
find
out
if
the
program
is
about
helping
storage
providers
or
helping
stakeholders
survive.
I
I
from
my
what
I
understand.
I
don't
think
the
program
is
about
helping
anyone
survive.
I
think
we
are
about
encouraging
and
helping
on
board
useful
storage
and
at
least
that
that
was
what
was
written
in
the
first
proposal
and
I
don't
think
part
of
making
onboarding
useful
storage.
D
H
Want
the
network
to
survive
and
the
network
survives
by
the
stakeholders
continuing
to
come
and
offer
their
services.
The
stakeholders
are
sp's,
offering
their
services,
but
also
clients
taking
up
on
their
services
right,
like
surviving
means.
We
need
the
entire
marketplace
ecosystem
to
be
robust
and
work
for
everyone
who
kind
of
wants
to
participate
in
it.
So
I
think
they're
like
yes,
we
care
about
people
surviving
care
about
the
sp's
business
surviving.
We
care
about
clients,
you
know
being
able
to
safely
store
data.
H
We
care
about
the
integrity
of
that
data,
because
those
are
things
that
impact.
You
know
the
trust
in
the
network,
and
so
if
the
network
becomes
a
place
where
it
is
only
not
useful
data
and
it
doesn't
have
utility.
Why
continue
to
do
that
right?
But
if
it's
encrypted
data,
but
it's
encrypted
and
useful
for
certain
users
like
that's,
still
really
useful,
but
if
it's
just
encrypted,
but
no
one
is
actually
using
it
and
there
is
no
retrieval
and
we
don't
know
that
it's
actually
good
useful
data.
That's
not
helpful.
Yeah.
D
G
Something
that
this
kind
of
like
crypto
ban
mining
situation
could
be
happen
anywhere
else
in
in
all
over
the
world,
like
maybe
in
other
you
know,
countries
in
asia
or
in
europe
as
well,
like
it's
not
highly
likely
to
happen
in
the
united
states,
but
it's
highly
likely
to
happen
to
other
countries
for,
like
you
know
the
general
like
crypto
ban
stuffs
so
like
but
like.
If
these
kind
of
things
happen
like
we
as
a
like
five
coin
network,
we
definitely
want
these
kind
of
you
know.
G
Existing
storage
providers
to
you
know
serve
the
network
right
with
the
destiny.
Like
you
know,
the
broader
vision
of
the
fly
from
like
that
everyone
else
can
store
the
file
to
protect
the
whole
network.
So
I
mean
this
is
not
just
a
question
for
the
like
chinese
region.
It's
for
the
general.
You
know,
question
for
the
whole
whole
network,.
A
F
Yeah,
actually
it's
I'm
going
to
share
more
information
about
this,
so
I
always
alone,
which
was
danny
brian,
mentioned
breaking
law.
Actually,
chinese
government
is
not
allowed
for
mining,
but
not
encouraged.
I
mean
they
also
encourage
the
people
to
making
the
storage.
So
if
you
are
running
a
mining
node
it's
another
out,
but
you
are
running
with
the
storage
provider
as
a
storage
provider.
You
are
not
mentioning
about
any
things
about
the
cryptocurrencies,
it's
okay.
F
So
that's
why
we
pick
up
the
storage
providers
they're
only
using
their
power
to
make
all
the
special
license
to
running
dc
a
data
center
with
the
storage
provider,
I
mean
only
making
the
things
connected
with
the
client.
I
mean
the
because
you
know
the
project
beacon
is
an
education
group.
It's
a
very
huge
education
group.
So,
with
this
kind
of
a
business
they
are
running
too,
they
are
legal
in
china.
That
means
they
are
making
the
backup.
I
mean
a
cub
business
for
very
huge
education
system.
A
H
So
this
is
another
similar
conversation
topic.
It's
come
up
a
few
times.
We
don't
have
a
ton
of
time
to
dive
into
it
here.
Let
me
post
the
link.
It's
gotten
some
discussion
back
and
forth
today.
That
link
is
a
little
bit
long.
What
we
summary
is
there
five
organizations
that
have
applied
to
the
notaries
these
organizations
also
have
ldns.
H
H
You
know
clarity
and
disclosures,
so
I
put
like
a
sample
table
in
and
if
we
could,
I
think
the
next
best
step
here
is
for
those
five
organizations
to
specifically
put
in
that
issue,
571
their
sort
of
disclosure
information
that
will
help
us
then
see
you
know
this
organization
in
d
labs.
This
is
applying
to
be
a
notary.
They
have
also
submitted
an
ldn.
They
have
also,
you
know,
worked
with
these
storage
providers.
So
I
think
that's
a
question
there
we're
asking
those
notaries
to
reply
in
that
issue
directly.
H
Then
sorry,
we're
not
going
to
take
a
lot
of
discussion
topic
on
that
one
we'll
come
back
to
it.
We
haven't
made
any
firm
decisions
on
that,
so
we're
asking
for
more
information
from
those
five
carey.
If
you
could
go
to
the
next
slide,
so
then
there
was
another
request
here.
I
think
kerry
and
I
actually
miscommunicated
earlier
so
project
bearded
from
the
sealed
storage
team.
They
had
sort
of
an
updated
request.
H
So
if
you
remember,
seal
storage
has
three
different
projects:
that
they're
kind
of
running
right
now,
there's
antarctic
bearded
and
by
call
those
ldns
are
in
progress,
they're,
primarily
working
right
now
on
bearded
and
ingesting
that
data,
while
also
ingesting
the
large
data
set
for
antarctic.
They
gave
an
update
two
weeks
ago
about
that
and
how
that
one
sort
of
where
they
are
in
that
process.
H
H
After
doing
the
work
to
start
to
ingest
and
seal
they're,
realizing
that
they
need
more
data,
more
data
cap
because
it's
going
to
be
a
larger
file
so
are
requesting
that
one
of
their
issues
is
increased
by
3.1
and
to
just
say
we
need
some
more
data
cap
for
this
specific
issue.
So
I
think
if
you
have
right.
H
H
We
understand
how
you
know
it
looks
like
there's
some
conversation
in
here
from
faye
and
deep
about
possibly
restructuring
how
graph
split
or
how
the
car
files
are
being
generated
might
be
another
way
to
solve
this.
That
could
also
be
a
long-term
solution
and
a
short-term
solution
for
this
project
might
be
just
increasing
it
by
3.1
pips.
While
we
also
work
with
that,
then
we
have
just
three
minutes
left.
Okay.
I
think
there
was
one
more
slide
that
ended
there.
Okay,
yes,
so
I
know
today
is
july
26th.
H
H
You've
heard
about
some
of
them,
even
today,
with
enterprise
fill
with
some
of
these
changes
on
how
to
support
encrypted
data
with
some
of
the
new
tooling
updates
that
we've
heard
about
so
at
the
next
notary
governance
call
as
promised
not
the
next
one.
Today,
the
next
two
weeks
from
now,
which
will
also
be
the
august,
so
those
will
be
different
times.
We
will
be
giving
that
sort
of
six-week
sprint
update.
What
did
we
hit?
What
did
we
miss
and
what
is
the
priority
for
the
next
six
weeks?
H
So
with
that
we're
pretty
much
right
at
time.
I
know
there's
been
a
lot
of
great
discussions
and
questions
in
the
chat.
Please
go
check
out
the
discussion
topics
check
out
our
slack
channel.
Add
your
questions,
comments
and
concerns
and
the
relevant
issues
thanks.
Everybody
for
another,
great
governance,
call
deep
k-ray
raghav
any
closing
thoughts.
E
A
A
The
topic
of
agenda
for
this
call
is
very
similar
to
others.
We
start
with
metrics.
We
talk
about
some
of
the
issues
that
were
flagged
by
the
community
and
we
hopefully
save
time
at
the
end
for
any
open
issues
that
people
want
to
flag.
For
this
call
the
members
of
your
governance
team
are
here
deep,
galen,
myself
and
jeff.
A
We
will
be
here
to
help
you
steward
any
part
of
the
process
that
you
need
reach
out
to
us
on
slack
and
github,
or
always
slack
us
on
this
call
as
we
go
forward,
but
we
are
your
friendly
protocol
labs,
filecoin
foundation,
community
help
with
that.
You
might
notice
that
there
is
an
addition
on
the
line
that
pops
up
from
otter.
A
What
we
are
testing
is
a
pilot
for
these
calls
to
have
a
transcript
recorded,
so
just
want
to
give
a
courtesy
note
that,
in
addition
to
this
call
being
recorded
and
put
on
youtube,
we
will
be
pulling
some
of
the
transcripts
to
hopefully
translate
that
into
mandarin
and
foreign
language
support.
So
if
you
sit
on
the
call,
that's
why
it's
coming
through
the
second
friendly
request
is
sometimes
it's
helpful
to
come
back
to
these
calls
and
be
like.
Was
this
person
on
the
call?
A
Was
this
person
not
this
plays
in
a
large
part
of
the
attendance
that
we'll
talk
about
as
we
go
through?
So
if
your
name
happens
to
read
like
mine
right
now,
if
you
could
add
anything
to
your
name
that
lets
us
know
where
you're
from
or
how
to
link
you.
So
I
just
changed
mine
on
the
call
by
right,
clicking
it
from
kevin
to
kevin
at
filecoin
foundation.
A
A
This
is
the
way
that
I
was
pulling
those
metrics.
So
if
you
were
a
notary,
please
please
please.
This
will
count
for
your
sla
on
that
application.
Go
to
this
form
and
you
fill
out
hey.
I
came
to
the
call
on
this
day
and
this
time
at
the
end
of
the
calls
I'll
scrub
that
and
I'll
say
which
notaries
were
on
the
call
at
which
time,
if,
for
any
reason,
you
didn't
fill
this
out
in
weeks
past.
A
Just
message
me
in
that
dm
that
we
have
and
I'll
be
sure
to
help
you
get
that
corrected,
but
we're
just
going
to
post
the
link
here
in
slack.
Thank
you
galen
and
that's
just
a
quick
way
that
you
can
mark
down
for
attendance.
So
with
that,
let's
dive
into
the
meat
of
the
call.
The
first
thing
is
metrics,
so
at
a
very
high
level,
we
talk
about
four
key
numbers
that
we're
looking
at
for
the
kind
of
health
and
growth
of
the
program.
A
The
first
one
is
the
average
time
to
data
cap
you'll
see
that
we're
still
hovering
around
that
three
or
four
day
mark
totally
in
line
for
somebody
applying
and
asking
for
that
data.
The
second
number
that
we
look
at
is
the
average
time
to
ldn
data
cap
in
weeks
previous.
This
was
around
the
five
day
mark
two
or
three
weeks
ago.
It
bumped
up
to
seven
and
they
called
that
out
on
the
notary
call.
Now
it's
right
around
that
ten.
A
The
total
amount
of
data
cap
that's
coming
into
the
field
plus
and
the
filecoin
ecosystem
is
still
steadily
growing
week.
Over
week,
we
see
about
0.3
to
0.12
average,
this
week's
no
exception,
so
nothing
to
call
out
as
far
as
sharp
drops
or
sharps
increases
to
the
amount
of
data
that
we're
bringing
onto
the
network
across
that
four
petabyte
scale.
A
With
this,
this
is
just
calling
out
what
numbers
we're
looking
at
the
back
end
nailing
deeper
jeff
and
myself
on
how
we
can
kind
of
look
at
these.
These
come
from
the
statistics
page,
the
interplanetary
dashboard,
if
you're
looking
for
this
slide
deck
that
I'm
talking
about
right
now.
This
is
in
slack
in
the
fill
plus
channels.
So
if
you
want
to
get
any
of
the
links
that
I'm
talking
about,
you
can
see
this
or
any
of
the
other
members
that
we
talk
about
in
the
call.
A
So
with
that,
this
is
the
agenda
that
we're
looking
to
cover
for
today,
six
issues,
two
of
them
really
quick.
Then
we
have
an
update
from
kevin
and
meg
on
the
enterprise
proposal.
Team
kevin's,
put
together
some
slides
to
walk
through
galen
will
walk
us
and
deep
will
walk
us
through
introduction
to
project
beacon,
we'll
talk
about
the
current
status.
There
was
a
lot
of
discussion
over
the
weekend
in
github,
and
there
was
a
lot
of
conversation
about
how
this
plays
out
and
we'll
address
that
on.
The
call
galen
will
walk
us
through
notary
issues.
A
These
are
some
of
the
investigations
that
we're
doing
and
trying
to
keep
the
program
clean
and
then
galen
will
walk
us
through
issue
327
of
the
ldn
process
and
the
bearded
application.
That
comes
so
with
that,
let's
jump
in
and
as
always,
if
you
have
a
question
as
we
go
through,
these
feel
free
to
unmute
your
line.
A
This
call
is
going
to
shift
from
4
pm
2300
to
6
pm
0
100
beijing
time.
The
goal
of
this
is
to
make
it
more
conducive
for
a
majority
of
the
chinese
participants
who
are
dialing
in
and
find
this
at
a
really
inconvenient,
zero
700
time
for
them.
So
right
now
we
have
around
13
14
people
on
the
call
we're
going
to
pilot
this
in
august
and
see
if
we
get
that
participation
number
up
without
losing
you
loyal
callers
at
this
time.
A
So,
just
as
a
heads
up,
you
can
follow
the
link
to
the
google
calendar.
I've
got
that
linkedin
slack.
It
looks
like
galen.
You
were
so
quick.
My
friend
galen
already
put
it
in
chat.
If
you
add
this
calendar,
this
will
pop
up,
and
you
can
see
all
the
links
to
the
notary,
governance,
sync
and
you'll
notice
that
if
we
go
forward
one
month
into
august,
it'll
change
to
that
6
pm
time
frame.
So
nothing
you
have
to
update
in
your
record,
it'll
auto.
Do
that.
A
So
just
as
a
heads
up
as
a
reminder
in
two
weeks,
this
meeting
shifts
a
call
back
to
an
issue
that
we
had
last
week,
and
this
was
how
does
the
community
and
the
phil
plus
program
process
changes
to
some
of
the
applications
and
some
of
the
rules
that
we
have
that
are
soft
and
not
material
in
the
program
change.
So
we
proposed
this
five
six.
Eight.
A
There
was
a
lot
of
discussion,
and
essentially
this
is
notaries
who
did
not
apply
for
reelection
in
the
third
that
are
in
good
standing
that
are
participating,
have
no
fraudulent
activity
or
any
kind
of
outstanding
questions.
Can
they
be
added
to
the
ldn
v3.
So
we
had
a
lot
of
discussion
that
was
captured.
A
lot
of
you
have
voted
this
on
the
issue.
This
was
just
one
final
call
out,
and
I
think
the
flag
that
I
would
make
for
all
of
you
that
are
considering
this.
A
How
are
we
making
these
soft
changes
to
make
sure
that
it
can
grow
and
stable
and
people
that
want
to
participate
are
unblocked
as
quickly
as
possible,
because
the
alternative
to
this
is
having
these
notary
elections
very
regularly
in
order
to
kind
of
update
that
which
feels
like
it's
a
lot
of
lift
on
you
as
notaries
to
put
through
that
election
as
well
as
a
lot
of
lift
on
our
part
to
score
it
and
go
through
it
properly.
So
this
proposal
at
the
root
issue,
it's
just
as
a
community.
A
How
do
we
feel
about
these
small
changes
that
we
make?
So
this
is
your
chance
to
weigh
in
on
that
five
six,
eight!
So
pending
any
discussion
with
this
would
be
most
likely
to
take
it
to
github
or
slack
that
way
we
can
tease
it
out.
I
wanted
to
save
as
much
time
on
this
call
for
galen
and
deep
to
flag.
Oh
excuse
me
for
kevin
to
start
off
with
the
enterprise
proposal,
so
kevin
I'll
turn
it
over
to
you.
My
friend
thank.
B
B
Mcdennis
has
done
a
great
job
of
setting
up
the
foundations
for
this
project
over
the
past
few
months
to
get
us
where
we
are
today,
so
I
I
just
wanted
to
to
spend
the
next
five
to
ten
minutes
just
going
over
where
we
are
and
what's
coming
up
in
the
next
few
months,
some
exciting
stuff.
I
know
everyone's
interested
in
enterprise
and
building
this
out
to
be
a
solution
that
works
for
phil
plus
so
kevin.
If
you
could,
please
go
to
the
next
slide.
B
B
B
The
next
phase
of
it
is
is
now
called
the
planning
phase
which,
on
the
next
slide
I'll,
go
into
a
lot
more
detail,
but
over
the
next
two
to
three
months.
We
really
want
to
set
this
program
up
for
success,
to
design
the
requirements
and
the
needs
of
the
client
experience
of
the
sp
led
pilot
and
there's
a
lot
of
decisions
that
need
to
be
made
and-
and
that's
why
we're
opening
this
up
to
the
community
for
discussions,
starting
today
and
and
through
the
next
few
months.
B
Okay,
now
number
580,
I
put
together
several
new
discussion
topics.
These
are
the
details
that
I
just
wanted
to
quickly
go
through
with
everyone
and
the
timeline
here.
So,
first
of
all,
the
idea
is
we're
looking
to
have
a
set
of
notaries
that
are
involved
in
this
pilot
upcoming
pilot
and
I've.
There's
there's
several
that
have
expressed
interests.
We've
we've
messaged
them
in
github,
we're
putting
together
a
group
that
are
going
to
help
participate
in
in
the
pilot
as
notaries.
B
There's
a
set
of
service
level
expectations
that
we've
put
together
that
they're
committing
to
being
a
part
of
this.
Most
of
it
is
just
you
know,
spending
time
each
week,
looking
at
these
specific
applications
and
and
things
like
that,
there's
also
several
proposals
that
will
be
part
of
this
pilot
that
we
need
to
flush
out
between
now
and
when
the
pilot
starts.
So
there's
the
this
idea
of
designating
a
lead,
sp.
B
There's
a
proposal
for
data
distribution
rules
having
the
client
be
upfront
with
their
data,
how
they
want
their
data
stored,
how
they
want
their
data
retrieved.
You
know
all
the
details
to
be
part
of
a
contract
where
we
can
manage
from
the
beginning,
there's
also
enterprise
data
cap
allocation
enhancements
that
we
want
to
discuss
and
again
these
are
all
open
for
everyone
to
go
into
these
discussion
topics.
Please,
please
provide
any
feedback
questions
that
you
have.
B
I
think
the
idea
right
now
today,
I'm
just
giving
an
overview
of
what's
going
on
in
two
weeks
from
now.
I'd
love
to
come
back
on
the
governance
call
and
have
a
little
bit
broader
discussion
on
some
of
these
proposals.
Once
everyone
had
a
chance
to
review
them,
and-
and
we
can-
we
can-
you
know-
talk
through
this
a
little
bit
more
together
as
a
community.
B
One
of
the
one
of
the
other
big
pieces
of
this
that'll
be
kicking
off
august
1st
kevin,
if
you
could
just
click
on
that
on
the
link
there,
so
we're
asking
sps
that
want
to
be
a
part
of
this
pilot
to
go
through
the
eligibility
and
express
it
of
interest
details
and
so
there's
a
web
page.
I
put
together
that
sort
of
highlight
who
we're
looking
to
be
able
to
include
as
part
of
sps
as
part
of
clients.
B
There's
there's
a
lot
of
details
about
the
timeline,
the
phases
that
we're
looking
to
set
this
up.
As
so
again,
this
is
all
part
of
a
larger
proposal
that
we'd
love
to
just
get
feedback
and
and
buy
in
on.
So
I
ask
everyone
to
go.
Go
through
all
this.
There's
there's
a
lot
out
there
there's
a
lot
of
information
to
go
through
so
so.
If
you
have
any
questions,
please
let
me
know,
but
you
know,
for
sps,
it's
gonna
be
really
important
for
them.
B
I
know:
there's
there's
been
a
lot
of
people
that
have
come
to
me
and
come
to
others
in
the
community
that
are
super
interested
in
kicking
this
off.
So
we
we're
pushing
this
forward.
You
know,
as
best
we
can
making
sure
we
have
the
the
proper
guard
rails
in
place,
then
moving
through
august.
We
want
to
go
through.
B
Our
customer
journey
review,
make
sure
we
have
the
requirements
start
to
set
up
the
tech
and
tooling
that
are
needed
to
enhance
an
enterprise
solution
and
and
the
pilot
so
having
a
kyc
automation
solution
having
a
better
landing
page
for
clients
to
come
to
to
apply
and
provide
their
information
that
you
know
can
be
supported
by
sps.
There
there's
going
to
be
a
chunk
of
this
is
going
to
be
involving
legal
and
setting
up
contracts
templates
that
again,
sps
and
clients
will
need
to
utilize.
B
B
But
the
goal
is
to
get
through
this
and
then
by
october.
If
everything
works
out,
how
we
like
it
we'll
kick
off
the
pilot
with
a
phase
one
which
is
25
sps
and
clients
through
a
six
month
period
and
we'll
sort
of
test,
what
we've
set
up,
we'll
gather
feedback,
we'll
see
how
things
are
going,
we're
using
a
an
mvp
and
sort
of
solution
to
think
through
design.
B
Thinking
as
well,
in
terms
of
you
know,
we
we
we're
going
to
have
a
a
rough
concept
and,
through
iterations,
we'll
be
able
to
learn,
improve,
enhance
this
process
to
make
it
better.
So,
by
the
end
of
the
pilot,
we
can
have
something
that
we're
all
comfortable
with
and
proud
of
to
push
out
and
build
trust
moving
forward
next
slide,
please
so
that's
it
I'll,
post
this
presentation
and
again
there's
several
new
discussion
topics
under
the
efil
plus
working
group
heading
under
the
notary
governance
github.
B
Please
take
some
time
to
review
those
provide
any
feedbacks
or
questions
that
you
have
again.
The
goal
will
be
to
come
back
in
two
weeks.
Time
spend
a
little
bit
more
time.
Have
it
maybe
have
some
time
for
an
open
discussion
on
some
of
those
specific
topics
that
might
be?
You
know,
need
some
more
discussion
openly,
there's
also
a
slack
channel
that
we
have
an
open,
slack
channel
that
feel
free
to
join
I'll,
be
posting
information
there
as
well,
so
I'll
stop
there
I'll
open
it
up.
If
there's
any
any
questions
or
comments.
B
That's
a
good
question.
I
I
think
yeah,
that's
something
we
need
to
talk
through
a
little
bit
more,
obviously
there's
it
will
lean
towards
more
of
the
the
sps
that
can
support
larger
enterprise
level
data
onboarding
right
to
be
a
part
of
this
to
be
eligible,
but
I
think
you
know
we're
open
to
whatever
or
whoever
wants
to
be
a
part
of
this
and
and
and
pilot
this.
I
think,
there's
there's
opportunity
to
test
different
use
cases.
B
H
G
G
C
Sorry
frozen,
that's
always
a
good
look
danny.
The
the
pilot
is
to
sort
out
a
lot
of
the
processes,
so
it's
almost
like
it's
like
flying
the
plane,
while
we're
still
building
it
and
sometimes
to
do
that.
We
go
for
what
is
simple,
especially,
I
think,
kevin's
thinking
about
25
companies
in
the
first
and
then
opening
up
more
broadly
in
a
second
charge.
H
E
E
The
call
today
asked
some
pretty
good
questions
on
like
the
structuring
of
the
video
files
and
put
up
some
relevant
points
and
that
sort
of
kicked
off
like
several
different
threads,
which
is
great
to
see
the
engagement
even
over
a
weekend
and
like
I
think
we
had
a
pretty
productive
sort
of
conversation
back
and
forth
to
try
and
get
the
bottom
of
the
particular
use
case
here.
For
those
of
you
that
aren't
following
the
thread.
E
This
is
initially
pitched
as
like:
educational
content
being
onboarded
about
11
pebby
bytes
of
it
with
five
replicas
intended
to
be
stored,
and
I
think,
through
a
bunch
of
back
and
forth.
What
we've
learned
is
it's
in
addition
to
like
classroom
recordings,
it's
also
according
to
educational
institutions
overall
and
so
there's
some
flagging
of
like
potential
misrepresentation
of
what
the
actual
data
was.
And
then
there
was
some
conversation
back
and
forth
on
the
value
of
that,
and
then
in
line
with
that,
there
was
also
a
conversation
on
like
the
process,
for
this
particular
case.
E
The
notaries
that
were
choosing
to
support
it
and
whether
or
not
like
the
sps
that
had
been
chosen
were
also
reputable
and
like
the
data
set,
could
move
forward
in
this
morning's
governance.
Call
eric
who's
like
the
sort
of
notary
partner
for
this
particular
application,
gave
a
little
bit
of
a
overview
of
like
the
storage
provider
side
of
the
house.
Where
you
talk
through,
why
a
lot
of
the
sp
ids
look
like
they
are
net
new
sps
and
where
that's
coming
from,
and
then
also
talk
through
some
of
the
complexity
around
data
storage.
E
And
why,
like
it,
has
to
stay
in
china
because
wine-
and
it
also
posed
the
question
of
hey
if
it's
encrypted,
can
we
store
it
outside?
And
so
that
was
addressed
as
well?
And
so,
where
we
stand
on
this
right
now
is
basically
there's
a
couple
of
notaries
that
are
still
waiting
to
react
to
the
threat.
As
far
as
we
know
like,
I,
I
think,
jonathan,
you
might
be
one
of
the
people
as
well
between
you
and
mag.
E
That
was
looking
at
signing
an
nda
and
seeing
the
data
underneath
and
so
there's
a
couple
of
a
couple
of
outstanding
opinions
to
come
in
based
on
people
that
have
signed
an
nda
and
are
have
been
privy
to
the
data
itself.
There's
also,
some
clarity
still
required
on
who
the
search
writers
are
that
this
client
is
like
working
with
there's
a
proposal
after
the
meeting
this
morning
from
wine
end
as
well
on
github,
where
he
spent
some
time
talking
with
eric
and
the
client.
E
Also,
as
part
of
the
discussion
on
this
there's
a
lot
of
interesting
ideas
thrown
around
how
we
could
improve
the
process,
some
of
which
I
think,
will
end
up
influencing
the
enterprise
field
plus
effort
with
kz
and
meg.
So
you
two
should
definitely
keep
your
eyes
on
this
one
and
see
how
it
evolves
and
then
jh
from
leland
jonathan
also
had
some
ideas
around
how
we
could
improve
and
introduce
notary,
staking
and
incentives.
By
way
of
this,
and
so
for
that,
we've
kicked
off
like
a
separate
discussion
topic
in
the
notary
governance.
E
E
If,
in
your
capacity,
you
are
willing
to
sign
an
nda
and
that
helps
you
build
confidence
with
a
client
like
that
is
the
work,
the
legwork
of
the
client
to
effectively
even
convince
you
to
give
them
the
opportunity
to
earn
your
trust,
and
so
at
that
point
in
time
the
guy,
like
the
conversation,
was
more
around
it.
It's
an
open
process.
If
you're
willing
to
do
it,
then
great
then
go
for
it
kind
of
a
thing.
E
D
H
Yeah
in
in
february
and
a
lot
there
was
some
question
around
that,
and
some
of
the
conversation
was
around.
If
a
notary
is
not
comfortable
or
willing
to
do
that,
or
feels
that
there
is
risk
to
them
in
one
way
or
another,
then
they
can
have
the
ability
to
make
that
choice
and
that
pl
and
the
foundation
right
now
are
not
mandating.
H
That
is
required
for
a
notary
to
participate
in
the
program
by
doing
ndas
we're
also
not
the
ones
drafting
those
ndas
or
like
providing
legal
counsel
on
like
what
an
nda
they
should
sign,
and
so
it
is
an
ongoing
question
of
like
what.
How
will
that
evolve
in
the
future,
and
that
is
something
that
I
know
the
enterprise
program
has
talked
about
having
contracts,
and
so
in
that
case
they
will
that
enterprise
program
will
need
to
be
piloting.
H
What
some
of
those
contracts
and
stipulations
would
look
like
who's
going
to
write
them
who's
going
to
source
them.
How
much
can
those
contracts
be
standardized
things
like
that,
but
for
right
now,
like
there's,
no
expectation
that
all
notaries
will
always
need
to
sign
ndas
or
have
that
level
of
kind
of
legal
expertise
in
order
to
participate
broadly
in
the
project,
it's
just
something
that
has
come
up
a
few
times
as
a
possibility
for
when
there
is
a
private
client
or
when
there
is
private
data.
H
This
there
was
like
some
discussion
around
is
it
you
know
a
valid
use
case
of
file
coin,
if
it's
private
and
encrypted
education
data,
and
then
the
question
is:
is
it
actually
private
encrypted
education
data
based
on
the
amount
of
data
that
they're
asking
for,
and
there
was
some
back
and
forth
on
kind
of
validating
that
and
the
clients
providing
some
more
details
based
on
number
of
cameras?
I
think
there
were
questions
around.
Is
that
education
data,
or
is
that
security
footage?
And
there
was
a
discussion
around
you
know?
H
What's
the
difference,
this
is
a
different
kind
of
cultural
context.
When
a
lot
of
people
hear
education
data,
they
think
kind
of
one
camera,
one
lecture
which
is
not
necessarily
the
same
thing
and
then
the
conversation
this
morning
really
being
around
if
it's
encrypted,
why
not
export
it
and
distribute
it
to
other
international
sps,
and
that
was
a
question
that
turned
into
a
conversation
about
well
exporting
that
kind
of
sensitive
data
is
also
illegal
according
to
certain
chinese
regulations.
H
So
really
the
the
discussion
as
it
was
kind
of
as
it
has
wrapped
up
from
this
morning
and
is
continuing
to
to
go
on
today,
is
trying
to
see.
Are
there
some
other
existing
notaries
in
other
regions?
That
would
like
to
help
perform
some
more
diligence
on
this,
and
so
there
has
been
a
collapse
of
those.
Some
notaries
have
offered
to
jump
onto
this
specific
project.
D
H
I
can't
remember
the
number,
however
many
20
a
month,
direct
notary
applications
that
go
straight
to
the
notaries,
where
the
notaries
are
performing
that
diligence
in
github.
That
also
don't
require
mbas
and
are
not
being
discussed
here.
So
while
there
are
an
increasing
number
of
these
kinds
of
conversations,
this
project
beacon
has
been
a
like
conversation
for
months,
and
so
this
has
been
a
large
60
pip
conversation
for
months,
which
is
why
it
takes
a
lot
of
attention
and
projects
like
that.
D
Yeah,
I'm
not
saying
that
every
every
request
is
that
is
coming
in
goes
through
this
process.
But
I
I
see
that
it
is
something
that
is
increasing
the
number
of
applications
that
are
being
suggested
to
sign,
nda's
and
and
look
at
the
data
and-
and
I
I'm
seeing
not
every
application,
but
I'm
seeing
that
some
of
those
requests
that
are
new
requests
that
are
coming
in
are
coming
with
suggestions
to
apply
for
for
private
data,
their
cap
for
for
use
with
private
data,
and
they
are
being
suggested
to
sign
in
days.
D
H
G
H
E
E
I
don't
think
that's
a
problem.
I
think
that's
like
us
deciding
to
figure
out
like
the
right
way.
We
need
to
serve
that
number
two.
If
that
means
more
notaries
have
to
be
comfortable.
Signing
nda's
or
more
notaries
are
choosing
to
opt
in
or
opt
out.
Also
not
a
problem
like
the
scale
of
notaries
and
notary
programs
should
continue
to
grow,
and
then.
E
You
don't
talk
about
anything,
so
I
can
give
you
open
trust,
so
you
can
ask
me
whatever
you
want,
and
so
as
we
build
better
proxies
for
that,
the
need
for
that
will
decrease,
but
I
would
flag
that
even
if
the
need
doesn't
decrease,
I
don't
think
that's
a
problem
like
ultimately
like
we.
This
is
like
a
in
a
way.
D
Yeah,
I
I
just
just
think
that
we
got
to
be
aware
of
where
things
are
are
going
to.
We.
We
don't
have
to
stop
that
from
from
from
happening,
but
we
can
plan
ahead
for
for
some
guidance
on
on
on.
What's
that
like
building
some
guidelines
and
or
not-
and
I
guess
a
lot
of
that
will
go
through
the
yeah
yeah
cool
yeah,
but
that
that's
like
a
a
risk
thing
that
I'm.
E
I
don't
think
it's
risk,
I
don't
think
it's
a
risk.
I
do
agree
with
you
that
we
should
have
guidance
but
yeah,
I
would
suggest,
take
it
up
in
in
the
efil
discussions
thing
or
ping
casey
or
mag
directly.
I
know
meg
also
specifically
did
some
thinking
on
this
topic
way
back
in
february,
so
I
would
suggest
let's
continue
the
conversation
there.
E
I
just
want
to
call
it
jonathan's
on
the
call.
I
know
that
he
specifically
had
flagged
a
couple
of
things
in
the
github
issue
as
like
hey,
it
would
be
good
to
talk
about
this
jonathan,
the
client's
not
on
the
call
eric
did
do
some
sort
of
representation
in
the
morning
session
and
that's
recorded,
so
I
suggest
you
definitely
catch
up
with
that.
I
also
posted
some
stuff
in
github
one
and
also
followed
up
in
github,
so
for
beacon.
Specifically,
I
would
say
check
out
the
github
issue
for
the
topics
that
you've
raised.
I
No,
so
I
followed
up
with
vinyl
this
morning.
He
was
pretty
happy.
I
think,
we're
at
the
point
where
I'm
going
to
sign
an
nda
look
at
some
data
and
then
go
from
there.
You
know,
ultimately,
you
know
when
people
put
applications
in
for
data
cap,
they
need
to
be
transparent,
about
the
data
sets
and
also,
and
if
the
data
sets
are
11
petabytes,
you
need
an
exact
breakdown
because
obviously
11
petabytes
is
over
32
36
000
sectors
and
nobody's
going
to
check
36
000
sectors
for
proper
data
right
so
yeah.
I
We
just
need
proper
breakdown
on
that
project
for
the
11
pip.
If
it
goes
down
to
a
lot
smaller
size,
obviously
we
need
to
do
less
check-in,
but
ultimately
you
know
we
still
need
to
know
who
are
the
sps?
Who
is
the
lead?
Sp
who
is
distributing?
Who
is
managing-
and
you
know
retrieving
is-
is
not
fine,
but
long
term.
You
know
we
need
a
white
list
of
you
know
what
what
what
is
going
to
get
through
easily
and
what's
not
going
to
get
through
easily,
because
this.
I
H
I
I
I
However,
you
know
long
term
the
our
our
business
like
every
sp
in
this
whole
community
is
relying
on
more
verified
deals,
not
only
because
we
want
to
make
this
network
as
big
and
as
powerful
as
possible,
but
ultimately
we
we
actually
lose
money
today,
putting
capacity
on
the
network
right.
So
this
is
a
lifeline
for
us
yeah.
So,
yes
step
one
we'll
just
look
at
it
step
two
I'll
see
what
meg
thinks.
That's.
H
I
I
do
believe
notary
should
be
staking
long
term
to
have
skin
in
the
game
and
to
kind
of
check
data
as
well.
That
aligns
notaries
with
the
pla
network,
like
it,
aligns
storage
providers
with
the
network,
but
I'll
carry
that
conversation
on
with
deep
in
the
incentives
channel,
plus
one
big
fan.
Thank
you.
Thank
you.
H
Okay,
ray
cool,
thank
you,
so
notarly
notary
disclosures
issue
571.
This
was
brought
up.
I
don't
think
we're
going
to
have
a
lot
of
time
for
an
open
discussion
on
this
one
here.
What
we
are
asking
for
for
those
five
notaries
that
are
called
out
in
this
issue
that
have
applied
to
the
notaries
have
kind
of
said
how
they
have
some
relationships
and
have
brought
different
partners
to
like
project
gravity
and
refer
different
partners
to
different
parts
of
the
filecoin
network.
H
So
we've
asked
those
organizations
to
put
their
disclosures
all
in
one
place
in
issue.
571
and
we
will
continue
sort
of
reviewing
that
and
working
on
it,
but
we
are
running
low
on
time.
We
have
some
other
topics
to
hit,
so
if
we
could
jump
ahead,
one
more
slide.
Please
great.
I
think
I
saw
a
member
from
the
seal
team
on
the
line,
but
maybe
they
had
to
drop.
H
I
I
think
that
we,
you
know
I
would
like
some
other
people
to
look
at
some
of
the
technical
information
here
and
see
what
that
means.
I
don't
know
that
we
would
be
able
to
solve
things
regarding
this
kind
of
technical
change
if
it
needs
sort
of
a
fit
on
the
time
scale
that
these
groups
are
talking
about.
H
So
really,
I
think
that
the
fundamental
question
here
is
just
are
we
comfortable?
They
initially
asked
for
a
certain
amount
as
they
started
onboarding.
They
realized
that
their
onboarding
rate
and
kind
of
total
overall
size
for
this
project
was
going
to
increase
it's
going
to
increase
by
3.1,
which
is
not
a
huge
order
of
magnitude
by
any
means
to
go
from
basically
almost
7
pips
to
10,
but
it
is
an
increase.
So
I
do
think
that
we
want
to
hear
from
that
team.
D
H
Have
any
on
the
same
applications
open?
They
could
open
another
application
if
they
wanted
that
to
me
feels
like
it's
just
more
overhead,
because
then
we
would
just
create
yet
another
multi-sig
to
give
3.1,
rather
than
just
topping
this
one
up.
So
this
isn't
a
request
to
get
three
pivs
all
at
once.
This
is
them
just
saying:
could
we
increase
what
is
available
to
us
at
the
top
of
the
funnel
and
they
would
keep
getting
that
allocation
calculation,
so
they
could
put
in
another
application?
E
D
H
Right-
and
so
this
would
still
be
requesting,
so
this
would
still
be
going
into
the
application.
This
is
just
changing
when
the
application
said.
We
want
1.9
they're,
changing
that
to
say
from
1.9.
We
want
five,
and
so
that's
just
changing
what
is
available
at
the
top
of
the
funnel
to
them,
and
that
application
has
already.
H
H
This
is
kind
of
like
we
have
seen
this
before,
where
working
with
slingshot
projects,
some
clients
that
were
working
with
slingshot
helping
do
projects
like
slingshot
restore
they
anticipated
that
their
weekly
onboarding
rate
would
be
a
hundred,
and
then
they
realized
that
wasn't
getting
them
enough
data
cap
fast
enough
and
long
enough
and
they
could
onboard
faster.
So
they
asked
to
increase
their
weekly
rate,
and
so
we
just
increased
the
weekly
rate.
It
didn't
mean
that
they
suddenly
got
more
data
cap
without
doing
anything.
D
But
they
I
I
I
get
the
feeling
that
this
should
be.
They
should
be
following
the
the
process
that
we
already
have
for
getting
that
data,
because
that
the
process
already
exists
and
they
are
yeah
essentially
getting
more
data
caps.
So
I
think
the
proper
way
would
be
to
follow
like
the
the
regular
processes
that
we
already
have.
I
don't
know
that's
my
my
take
on
it
at
least
one.
I
I
It's
hard.
We've
had
to
build
software
to
automate
downloading
petabytes
of
data
in
a
very
seamless
way
right.
We're
checking
corrupt
files,
we're
putting
them
in
the
right
places
that
software
took
us
about.
You
know
a
week
two
weeks
to
get
right.
We
then
had
to
build
pipeline
software,
so
we
take
that
downloaded
software
and
feed
it
into
the
lotus
miner,
multiple
lotus
miners
as
quickly
as
possible.
So
we
had
to
build
that.
That
was
another
couple
of
weeks
we
had
to
upgrade
our
pipes
from
like
a
couple
of
gigabytes
to
20
gigabytes.
I
We
had
to
up.
We
had
to
tell
the
isp
to
update
their
upstream
traffic,
so
we
could
get
data
correctly.
I
had
to
employ
a
new
engineer
to
make
all
the
sure
all
the
deals
were
happening
properly.
We
had
to
buy
new
downloading
kit
because
we
needed
you
know
two
petabytes
of
storage
to
manage
all
this
data
coming
in
wow.
You
learn
a
lot
when
you
go
from
terabytes
gigabytes
to
multi-petabytes.
I
So
it's
okay
for
us
to
not
know
all
the
parameters
at
the
start
and
we
and
hold
on
we're
and
probably
still
we're
all
happy
to
share
all
the
things
that
we
had
to
build
to
to
to
get
this
over
the
line
right.
This
is
you
know
my
my
head
of
engineering,
anthony
smith,
has
worked
every
day
for
the
last
four
months
right
just
to
make
this
thing
work
so
for
them
to
for
seal
to
go
yeah
we
didn't
know
this
at
the
beginning
is
perfectly
acceptable.
E
Yeah,
I
think
that
there's
a
couple
things
I
wanted
to
flag
number
one.
I
have
heard
some
concerns
over
like
overall
around
like
projects
that
get
outsized
data
cap
like
this
being
one
of
them
where
it's
like.
Oh
you
know
up
front.
There
was
like
a
request
for
antarctica
for
50
pebb
bites
so
for
this,
for
like
10,
petabytes
or
whatever,
and
then
there's
like
learnings
that
come
around
the
path
around
the
way
and
adjustments
that
need
to
be
made
in
the
process.
E
I
think
that
first
point
I'd
like
to
call
out
is
it's
really
important
for
us
to
be
transparent
as
a
community?
So
I
actually
think
it's
great
that
they're
sharing
this
and
like
updating
this.
I
would,
though,
have
liked
to
see
the
process
itself
be
talked
about
like
there's
a
lot
of
people
that
onboard
this
amount
of
data
very
very
quickly
and
don't
have
these
issues
because
there's
people
that
are
like
are
experienced
and
have
been
able
to
do
this
in
the
past.
E
Folks,
if
you're
watching
this
call,
I
think
it's
great
that
you're
being
transparent
about
this
and
stuff,
but
I
think
you
could
also
be
a
little
proactive
about
like
the
process
and
and
engaging
folks
in
the
ecosystem
about
it,
and
jonathan
same
thing
goes
to
you
like,
if
there's
stuff,
that
you're
doing
that
you're
stuck
on,
I
think
you
should
maybe
use
the
community
a
bit
and
like
outsource,
some
of
the
complexity
to
it
and
see
where
people
are
at.
Personally,
I
work
on
slingshot
stuff.
E
E
Second
thing
I
want
to
call
out
is
this
an
element
around
like
base
of
work,
which
there's
some
sort
of
expectation
in
the
ldn
process
right
like
there's
a
subtle
sort
of
math
here,
that
every
client
is
always
doing
when
they
apply,
and
so
this
is
not
directly
related
to
bearded.
But
a
general
comment
where
it's
everyone
is
a
timeline,
and
everyone
is
sort
of
pricing
in
complexity
into
that
timeline,
and
falcon
plus
itself
introduces
complexity
in
that
timeline
where
it's
like.
Oh,
I
need
to
go.
Get
data
cap.
E
E
At
some
point
in
time,
a
fip
was
passed
right
in
in
february
sorry
integrated
in
february
and
march,
passed
at
the
end
of
the
last
count
of
the
year
to
say:
let's
remove
data
cap
from
clients
that
may
introduce,
like
a
network
risk,
and
part
of
that
is
also
latent
data
cap
sitting
on
at
large
volumes
like
if
you
look
at
data
cap
like
given
to
client
wallets
today
versus
that
stored
in
deals.
It's
about
80,
like
all
of
all
data
cap,
is
actually
used
in
deals
already,
and
that's
pretty
good.
E
There's
a
point
in
time
where
that
number
was
like
30
or
40
percent,
which
is
more
of
a
threat.
But
as
we
move
closer
and
closer
to
80,
that's
great
as
long
as
we
can
get
that
time
to
data
cap
number
down.
But
that
also
means,
when
you
have
substantive,
like
processes
that
have
gone
through,
that
are
just
sitting
laden
on
data
cap.
H
Yeah,
I
think
it's.
These
are
great
points.
I
think
we
would
like
to
hear
from
the
seal
team.
We
have
the
discussion.
We
have
that
issue
there,
where
people
can
go
way
in
and
maybe
we
need
to
open
another
discussion
or
proposal
topic
on
this
and
kind
of
breach,
a
decision
at
the
right
next
notary
governance
call.
I
think
there
was
one
more
slide
in
here
query
and
that
is
to
say
that
today
being
july,
26
believe
it
or
not.
We
have
completed
this
six
week.
This
is
the
end.
H
H
The
plan
at
the
next
notary
governance
call
in
august,
which
will
be
the
second
one
will
be
at
that
later
time
slot,
because
we'll
get
sort
of
a
more
comprehensive
picture
on
what
we
accomplished
in
the
six
week
sprint
and
what
we're
working
on
for
the
next
six
week
sprint.
So
with
that,
we
have
just
about
two
minutes
left,
maybe
not
a
ton
of
time
to
hit
community
discussion
topics.
Lots
of
things
covered
today,
lots
of
great
discussion
issues
across
different
channels.