►
From YouTube: Filecoin Plus - September 05 Notary Governance Calls
Description
The seventeenth set of Notary Governance calls of 2023 September 05 to discuss the Filecoin Plus program.
Slides and Links: https://docs.google.com/presentation/d/1tDh_4nc_Y8KXyo5nqwCeH-XHKH_JjtTbccew-wGR3U8/edit#slide=id.g1184233f2bd_0_34
Agenda
Notary
Upcoming LIVE events and conferences
Dispute Resolution Tracker
Working Group Updates - None
Trustless Notary Presentation - dataswap
Proposals
974 - DataCap removal bot
976 - AC bot
Community Issues
All LDN application presentations are a-sync will be discussed in #fil-plus-application-review SLACK
If you would like to attend these meetings LIVE, the Fil+ Notary Governance calendar is available at: https://calendar.google.com/calendar/u/0/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
Foreign
hellos
everybody
Welcome
to
the
first
call
of
September
5th.
Let's
take
a
look
at
what
we
have
on
the
agenda
coming
up
for
notary
issues,
we're
going
to
talk
about
upcoming
events
that
are
taking
place
around
the
world.
We've
invited
Meredith
from
the
foundation
and
she's
going
to
kind
of
give
some
summaries
of
what
those
issues
are.
A
What
the
main
talking
points
are
at
those
events,
and
if
you
have
any
questions,
she
leads
our
event
team
and
can
be
happy
to
answer
anything
or
at
least
take
that
down
and
make
sure
we
get
you
round
to
the
right
person.
Rg
will
be
on
the
call.
He'll
walk
us
through
updates
on
the
dispute
resolution,
trackers
pretty
much
how
that
process
is
coming,
what
we've
seen
new
and
what
we
should
expect
to
see
coming
forward
in
the
future.
A
There
will
be
no
trust
and
transparency
working
group
updates
on
this
call,
but
we
have
a
request
and
we're
going
to
be
joined
by
Wayne
from
data
Swap
and
they'll
be
walking
us
through
their
presentation
on
trustless
notary
design
and
what
that
looks
like
afterwards.
We
have
two
new
proposals
that
have
come
in
since
the
last
fall
and
Simon
and
Phil
will
walk
us
through
what
those
Bots
look
like
and
any
questions
you
may
have
and
as
always
at
the
end
of
this
call,
there'll
be
time.
A
For
anything
else,
you'd
like
to
discuss
I
will
say
is
a
flag
right
off
the
bat.
We
had
a
request
from
the
data
swap
team
that
if
there
was
any
Mandarin
speakers
on
the
call
that
would
like
to
help
with
the
translation,
it
would
be
greatly
appreciated,
so
we'll
get
to
that
right
before
we
launch.
But
if
you
are
a
Mandarin
English
speaker
and
you
would
like
to
help
with
the
Trans
translation
that'd
be
greatly
appreciated
when
we
get
to
the
community
portion
of
the
call
here.
A
So
let's
take
a
look
at
what
we
have
today
is
the
5th
of
September.
The
next
call
will
take
place
on
the
19th
of
September.
If
you're
joining
these
calls
they're
marked
in
the
shared
calendar,
you
can
follow
along,
and
this
will
be.
The
first
call
second
call
is
taking
place
at
zero
one
UTC
tonight,
if
there's
anything
that
you
ever
want
to
get
on
these
notary
governance
calls
for
a
topic
for
discussion
or
flag,
open
Forum,
just
go
to
the
issues
and
say:
hey
I'd
like
to
discuss
X,
Y
and
Z.
A
Leave
that
as
a
comment
and
I'll
reach
out
we'll
get
slides
whatever
time
you
need
and
we'll
bake
that
into
the
presentation.
So,
if
you're
looking
to
add
an
item
to
the
agenda,
that's
filled
out
right.
There
I'd
love
to
have
it
friendly
check.
Here's
your
governance
team!
If
you
need
support
issues,
these
are
the
best
people
to
reach
out
to
you're,
not
sure
who
to
reach
out
to
you
can
always
reach
out
to
me
and
I'll
be
happy
to
route
you
to
the
right
person
or
team.
That's
working
on
that!
A
So
notary
issues.
First,
off
I'm,
going
to
post
the
link
to
the
air
table
sign
up
notaries
that
are
on
the
call.
Thank
you.
As
always,
when
you
fill
this
out,
we
track
this
for
the
participation
but,
more
importantly
where
the
tooling
resources
are
going,
how
your
time
is
being
spent.
So
there's
always
notaries.
A
Thank
you
for
taking
the
time
to
fill
this
out
if
you're
on
the
call
and
you're,
not
a
notary,
like
a
member
of
the
community
storage
provider
looking
to
get
involved,
this
is
a
valuable
way
to
show
like
your
participation
in
the
program.
We
look
at
this
with
the
reputation
scores
quite
significantly
in
future.
So
if
you
want
a
show
like
yes,
I've
been
coming
to,
these
calls.
Yes,
I've
been
active
in
the
community
signing
up
on.
A
B
B
Actually
just
this
past
weekend
not
listed
here
was
Phil
Jakarta
run
by
our
Community
member
medipals.
It
was
a
very
successful
event.
We
had
over
500
developers
for
that
learning
about
fbm
networking
meeting
each
other
and
hopefully
cultivating
some
business
opportunities
on
the
ground
in
Jakarta,
but
upcoming
we
have
later
this
week,
Phil
Seoul.
B
This
will
be
an
event
for
storage
providers.
So
really
hope
any
of
you
in
the
Asian
region
who
might
be
going
to
Korea
blockchain
week,
could
attend
Juan,
we'll
be
giving
a
keynote
in
an
AMA
as
well
and
there's
a
storage
provider
focused
today
on
on
the
first
day,
which
is
the
sixth
after
that
is
our
Phil
Dev
Summit.
This
is
an
event
for
core
Dems
to
really
shape
the
future
of
the
protocol.
Galen
will
be
there
on
site
as
well,
I
think
Danny
as
well.
B
So
please,
you
know,
please
join
if
you
haven't
already
it's
going
to
be
in
Singapore
at
the
Fairmont
there,
and
it
is
four
days
of
really
diving
into
some
key
themes.
You'll
see
on
that
website,
a
lot
of
the
key
themes
that
will
be
covered
so
please
check
it
out
and
if
you
are
in
the
region
or
can
attend,
please
do
oh
great
great
to
see
that
thank
you.
Casey
will
be
there
as
well
and
then,
finally,
in
October,
we'll
be
hosting
Phil
Vegas.
B
If
you
are
a
file
coin
storage
provider
or
considering
becoming
one,
you
should
be
attending
Phil
Vegas.
It
will
be
alongside
espa
there'll,
be
a
D
Storage
track.
This
will
be
happening
at
the
park
MGM
in
Vegas
and
there'll,
be
so
much
to
learn
about
storage
providers
becoming
a
storage
provider
as
well
as
kind
of
the
optimal
theme
of
data,
integrity
and
AI.
So
really
exciting
speakers
for
this
event
and
we
hope
to
see
a
lot
of
you
there.
B
This
one
is
hosted
by
biocoin
Foundation
and
we
are
really
excited
about
it
and
finally,
in
November
we'll
be
having
a
a
falcoin
network
base
alongside
lab
week
and
devconnect
in
Istanbul.
So
you
know
definitely
check
that
out
as
well.
We're
going
to
be
excited
to
be
partnering
along
with
the
ethereum
community
and
many
of
you
at
lab
week.
B
So
if
you
have
any
questions
about
our
events,
you
can
check
out
phil.org
events.
They're
all
listed
there
or
reach
out
to
me
Meredith
on
filecoin
slack
again,
it's
Meredith
Palante
I'm,
proud
to
meet
you
all
today
and
thanks
for
considering
kind
of
coming
out
and
being
a
part
of
some
of
our
events,
if
you're
interested
in
hosting
an
event
also,
please
reach
out.
We
have
many
ways
that
we
love
the
community
to
get
involved
and
host
events
in
their
own
region,
specifically
through
orbit.
A
A
C
Thanks
Carrie,
the
update
is
pretty
small,
so
all
the
disputes
that
have
been
submitted
on
the
dispute
tracker
are
now
at
the
result
or
have
been
followed
up.
So
if
you
are
involved
stakeholder,
please
take
a
look
and
then
just
a
reminder
that
our
SLA
is
14
days
so
and
we,
our
hope,
is
that
in
14
days
we
can
resolve
or
respond
to
all
of
the
disputes.
The
link
is
there.
So
please
take
a
look
at
the
open
disputes.
C
A
Thanks
Sergey,
anybody
in
the
call
has
questions
feel
free
to
stick
a
hand
up
or
just
interrupt
me
and
we'll
come
back
to
this
or,
if
anything
comes
to
mind
at
the
end
of
the
call
we'll
be
happy
to
Circle
back
all
right,
Community
presentation,
so
I'm
happy
that
we
have
a
special
guest
Wayne
who's
on
the
call
I
wanted
to
see
earlier.
We
said
if
there's
anybody
that
might
be
able
to
help
with
mandarin
to
English
translations.
Is
there
anybody
on
the
call
right
now
that
may
be
able
to
support
that
foreign.
A
What
we
could
do
is
I
can
just
do
the
recording
if
you
want
to
do
it
in
Mandarin,
and
then
we
can
get
the
translation
when
it
goes
to
YouTube
back
to
English.
I'll.
Leave
it
up
to
you
since
you're
the
speaker
on
what
you
would
feel
most
comfortable
presenting
in
and
I'll
just
work
around
it
later,
since
we
don't
have
a
translator
for
you.
E
E
This
is
the
problem
statement
and
we
aim
to
address
the
trustless
lottery
issue
in
fair
plus,
as
mentioned
in
the
following
document
is
about
translate,
is
not
already
discussion
in
our
solution.
We
can
resolve
the
following
two
issues:
one
is
a
flower
of
the
cap
issue.
True
is
issuing
the
right
date
is
imported,
and
now
we
have
accompanied
the
design
under
basic
architecture,
setup
of
our
project
and
our
specs.
Our
best
met
the
document
document.
Hey.
E
E
E
E
To
as
they
do,
some
do
some
submit
and
and
pay
some
code
code
as
well
under
the
first
step.
Two
is
DP
submitted
proofs
and
da
challenge
the
proof
successful,
and
then
this
set
is
approved
as
W3
is
SPS
door
store,
really
they
set
the
date
storage
down
and
as
they
can
will
join
a
data
set
data
cable
corridor,
okay,
okay,
please
let
next
the
page.
E
Yes,
this
is
our
contractor
design.
The
design
I
divide
divided
into
two
layers
at
support
layer
and
the
domain
layer.
A
separately,
including
governance,
access,
Surplus
and
custom
file
plus
is
fair.
Plus
contract
contract
is
including
create
file,
Plus
rules
and
update
fair
plus
rules,
such
as
master
country,
plugs
and
so
on
and
and
custom
is
very
important
in
our
design,
because
hey
because
is
in
charge
of
managing
the
life
cycle
of
car
and
car
replicas,
okay,
the
domain
is,
is
our
main
logic.
E
E
E
E
A
Way
that
was
fabulous,
maybe
I'll
kick
off
the
first
question
and
then
pass
it
around
I
know.
People
are
probably
going
to
have
thoughts,
input
and
questions
for
you
to
get
involved
like
if
this
Call
to
Arms
where's
the
best
place
that
someone
should
go
to
get
started
to
read
more
and
then
get
started
with
you.
Where
would
you
direct
them
to
go.
A
E
E
F
G
I
just
had
a
question
so
I
know
you
mentioned
that
the
data
the
data
preparer
will
have
to
submit
proofs
I.
Think
previously.
There
have
been
concerns
regarding
relying
on
data
preparer
as
a
source
of
yeah
as
a
source
of
I,
guess,
trust
or
proof.
So
can
you
like
share
more
like
what
prevent
what
is
preventing
the
data
preparer
to
kind
of
you
know,
collude
or
be
abused.
E
E
H
A
Sounds
great
Wayne.
Thank
you
so
much
for
coming
to
the
call.
Thank
you
so
much
for
the
work
that
you've
put
in
and
we
have
the
two
links
in
chat
on
the
screen.
I'm
sure
you'll
be
getting
a
lot
more
questions
as
this
develops
and
the
progress
you
make
well
done.
Thank
you
for
coming.
Your
time
was
greatly
appreciated.
A
I
S:
yeah,
hey
everyone,
as
Kerry
mentioned,
this
is
a
proposal
for
the
data
cap,
removal
bot.
This
proposal
stemmed
off
of
the
AKA,
it's
the
other,
so
one
slide
back.
Please
yep.
This
proposal
stemmed
off
of
the
discussion
we
had
in
the
last
notary
governance
call
and
proposal
967
that
was
made
by
hide.
So
thank
you
for
that,
starting
the
conversation
overall.
This
proposal
adds
a
little
more
detail
on
the
criterias
of
removing
data
cap
on
LDN
applications.
I
The
reasonings
are
applications
that
have
become
stale,
so
stale
applications
are
LDN
applications
that
have
had
no
activities
so
no
comments
after
14
days,
and
so
once
the
stale
application
does
not
get
an
additional
14
days
of
activity.
The
data
cap
would
be
removed,
so
that
would
be
28
days
in
total
of
no
activity.
I
The
second
reason
would
be
clients
requesting
the
removal
of
datacap
for
themselves,
and
the
last
one
would
be
applications
that
stay
open
due
to
comments
and
have
not
used
their
data
cap
in
the
meantime.
So
for
another
four
weeks,
which
is
a
total
of
six
weeks
of
data
cap
not
being
used
for
that
specific
application.
I
Just
a
reminder
that
after
data
cap
is
been
removed
from
clients
that
clients
are
always
allowed
to
reapply
again,
I
opened
this
proposal
last
week,
and
so
it
would
be
great
to
get
more
feedback.
I've
been
seeing
some
comments
already,
so
I'll
definitely
definitely
respond
back
to
those.
But
people
who
started
discussion
in
the
last
notary
governance
call
would
be
great
if
you
can
chime
in
and
all
the
notaries
here
as
well.
This
is
going
to
be
a
pretty
big
implementation.
I
Just
it
would
be
really
helpful
to
provide
your
input
on
some
of
the
reasonings
as
to
why
you
might
be
against
or
not
against.
This
proposal,
like
chronologic,
did
in
proposal
967.
He
gave
some
really
good
reasonings,
rather
than
just
kind
of
saying
yes
or
no
I.
Think
providing
those
suggestions
and
reasoning
will
like
actually
help
us
ideate
on
this
on
this
proposal
and
bring
up
new
ideas.
So
please
go
into
the
proposal,
provide
your
input
with
some
reasonings
and
thank
you.
J
I
It's
more
of
like
a
a
refined
version.
I
would
say
we
added
more
details.
He
closed
his
because
I
think
there
was
a
lot
more
controversy
on
the
timeline,
and
so
we
discussed
this
a
little
bit
on
the
trust
and
transparency
working
group.
I
was
looking
at
the
comments
in
the
issue
itself.
So
if
you
see
payday's
original
proposal
that
you
just
posted
967,
he
actually
closed
it.
I
If
you
see
the
I
believe
my
comment
in
that
proposal,
it
links
to
this
new
one,
and
so,
if
you
can
see
you
know
it's
pretty
much
similar,
except
for
the
timelines.
It's
a
little
bit
more
a
couple
more
days
and
a
few
more
reasonings
as
to
why
LDN
applications
should
get
should
have
their
data
cap
removed.
J
I
I
think
again,
just
like
my
comment
before
I
think
there
was
a
lot
of
controversy
and
just
people
were
not
in
agreement
of
the
seven
days
that
he
was
pushing
for
and
so
again.
Essentially,
that's
why
we
extended
it
a
week
more
seven
extra
days
to
make
it
28
days
rather
than
21
I.
Believe
that's
what
he
proposed
so
yeah,
okay,.
J
And
I
mean
I
think
just
to
know
on
on
the
comments
on
that
on
that
issue,
and
yours
I
mean
there's
lots
of
calls
there
for
a
vote
and
lots
of
calls
for
a
good,
a
consensus.
But
my
understanding
is,
we
don't
need
a
vote
or
consensus
to
to
do
something
like
this
within
with
interest
and
and
security
right,
correct.
K
We
don't
need
a
unanimous
notary
agreement
and
we
don't
need
a
vote.
We
use
our
soft
governance
process.
We
want
to
hear
people's
opinions
as
to
who
supports
it,
and
why
and
who
does
not
support
it,
and
why,
and
so,
looking
back
through
967
I
think
a
lot
of
the
conversations
started
to
get
into
more
higher
level.
What
are
all
of
the
other
mechanisms
of
abuse
that
are
happening
on
ldns
and
how?
K
J
Does
that
mean
that
if
people
want
to
keep
the
data
cap
that
they
currently
have
because
there's
clearly
a
lot
of
people
worried
about
that,
they
can
reopen
the
issue
or
is
it
are
we
going
to?
Is
that?
Are
we
going
to
go
after
people
who
have
previously
closed
their
their
issue,
but
not
take
into
account
if
they,
if
they
reopen
it,
even
if
it
can
be
open.
K
Yeah,
a
an
author
can
close
and
reopen
an
issue.
My
understanding
is
that
if
they
do
that
the
reopening
posts,
another
comment
to
say
this
was
reopened
at
this
time,
which
would
trigger
as
activity,
and
so
the
bot
would
ignore
that
issue,
because
it's
sort
of
signs
of
life
from
a
client
who
requested
the
data
cap.
So
this
is
to
go
after
yes,
if
it
if
the
issue
gets
closed
either
by
the
author
or
automatically,
because
it's
inactivity
as
well
as
and
I
think
actually
Simon
correct
me
if
I'm
wrong.
I
K
K
L
Hey
guys
so,
following
on
from
Simon's
big
proposal,
I
have
here
another
big
proposal,
so
we
proposed
today
that
AC
bot,
which
stands
for
the
aggregation
and
compliance
spot,
this
spot
is
meant
to
aggregate
the
different
data
sources.
We
have
so
retrievability
bot,
CID,
Checker
and
many
other
statistics.
We
have
been
tracking
and
use
that
data
to
actually
enforce
compliance
on
clients.
L
We
may
be
issuing
data
cap
based
on
the
statistics
too,
but
for
now
we'll
just
be
removing
data
cap.
We
want
to
do
this
because
I
think
this
is
the
most
actionable
plan
right
now.
It
will
over
the
current
system
of
notaries.
It
just
decreases
bureaucracy
less
for
notorious
to
do
it
recommends
due
diligence,
so
notice
needs
to
do
less.
It's
more
neutrality,
there's
a
set
of
rules
such
that
everyone
is
is
has
to
comply
to.
L
L
So
at
least
the
clients
will
get
at
least
a
recommendation
or
we'll
say,
like
hey,
you're,
missing
something
in
your
in
your
application
or
you're.
Failing
some
requirements.
Can
you
please
fix
this?
The
those
requirements
and
thresholds
are
stated,
or
at
least
the
initial
proposed
ones
are
stated
within
this
application.
I
think
it's
pretty
important
application
for
everyone
in
the
program,
because
it
does
involve
removing
data
cap
from
clients.
So
if
you
want
to
know
what
rules
you
will
need
to
comply
to,
you
can
check
this.
L
This
application.
Of
course,
this
is
even
though
we're
in
development
of
this
we're
not
final
with
many
of
the
parameters
and
thresholds.
If
you
have
any
suggestions,
we
are
completely
open
to
it.
Please
let
us
know,
let
me
know
through
slack
or
just
comment
in
this
application.
If
you
have
any
thoughts
or
comments
yeah
with
that,
let
me
know
if
you
guys
have
any
posts.
A
Well,
thanks
Phil
pretty
straightforward.
If
anybody
does
have
any
comments,
thoughts,
feedback
we'll
have
plenty
of
time
at
the
end
and
discussions
Circle
back
to
this
and
that
kind
of
opens
it
up
with
any
time
that
we
have
left
on
the
call.
This
is
your
Forum
anything
that
you
want
to
flag
raise
or
discuss,
raise
a
hand
unmute
the
floor
is
yours.
K
Danny,
a
quick
check
of
the
math
here,
1.78
exabytes,
have
been
created,
Total
to
give
to
notaries,
but
1.57
of
that
has
been
given
to
clients
from
the
notaries.
That's
because
of
how
much
the
different,
like
the
large
data
set
notary
or
the
e-fill
notary
has
so
from
1.57
that
has
been
given
to
clients.
1.5
has
been
published,
so
it's
0.07
exabytes
that
are
currently
latent.
K
K
K
K
Can
we
automate
that
right?
Can
we
take
things
that
are
easy
wins
that
are
clear?
You
know
clear
cases
and
automate
the
removal
of
data
cap
in
those
situations,
and
so
that's
that's
kind
of
some
of
the
direction
that
we're
trying
to
go.
So,
as
you
read
through
these
Bots
I
just
want
to
make
it
clear.
The
things
that
are
being
proposed
here
are
not
meant
to
be
okay.
K
We
have
now
covered
every
possible
scenario,
and
this
is
it
or
is
also
not
meant
to
say
if
it
doesn't
fit
into
this
bot,
then
it
isn't
eligible
for
a
dispute
or
a
removal,
or
it
isn't
eligible
for
more
data
cap.
There
will
always
be
exceptions
both
in
granting
data
cap
and
and
removing
data
cap.
That's
part
of
having
you
know
a
scaling.
Trust
system
is
that
we
have
to
make
exceptions,
learn
from
whether
or
not
they
work
and
then
iterate
on
the
Bots
themselves.
K
A
Well,
hello
from
the
eyes
welcome
to
the
second
call
of
September
5th.
Let's
take
a
look
at
what
we
have.
If
this
is
your
first
time
dialing
in
calls
broken
into
four
parts.
Part
One
focuses
on
notary
issues.
Tonight
we're
going
to
be
talking
about
events
that
are
upcoming
in
the
next
quarter.
Then
we're
going
to
be
updating
the
status
of
the
dispute
resolution.
Tracker
RG
updated
this
in
the
morning
since.
A
On
this
call,
I'll
do
my
best
to
fill
in
on
his
behalf.
After
that
we
have
the
community
issues.
Typically,
these
are
like
the
working
groups,
Enterprise
field,
plus
trust
and
transparency.
Tonight
we
have
a
presentation
from
a
group:
that's
working
on
trustless
design.
Excuse
me
notary
design
from
data
swap
they
gave
us
a
presentation
in
the
morning.
I
think
they're
coming
back.
If
not,
we
can
kind
of
paraphrase
and
make
sure
that
we're
covering
it
and
Carol's
joined
on
the
call
to
help
with
any
translation
back
and
forth
between
Mandarin
and
English.
A
So
if
you
have
questions
and
you'd
like
to
discuss
something
in
Mandarin,
we
do
have
Cairo
tonight,
so
please
take
advantage
of
it
happy
for
your
time,
thanks
for
coming
Cara
for
the
proposals,
there's
two
new
open
ones,
sign
and
Phil
spoke
to
them
this
morning.
I'll
speak
to
them
tonight.
There
are
two
Bots
that
focus
on
retrieval
of
data
cap
and
how
the
ANC
process
works
and
we'll
have
plenty
of
time
for
open
issues.
A
So,
if
there's
anything
that
you
want
to
see,
added
to
this
call
you'll
have
plenty
of
time
to
bring
that
up.
At
the
end,
or
as
always,
stick
a
hand
up
and
we'll
stop
and
make
sure
that
we're
listening.
This
is
the
call
September
5th
second
call
if
you've
ever
not
come
to
one
of
these
sessions.
This
is
your
first
time
you
can
check
out
this
calendar
link.
This
will
add
it
and
you
can
track
all
the
next
calls.
A
The
next
call
will
be
taking
place
at
zero,
eight
hundred
fifteen
hundred
UTC
on
the
19th
of
September.
If
there's
any
topic
you
want
discussed
on
this
call
open,
Forum,
WE
Post
in
GitHub
every
two
weeks
just
feel
free
to
leave
a
comment:
hey
Kev
I'd
love
to
discuss
XYZ
issue
I'll
reach
out.
If
you
have
slides,
we'll
build
them
in
and
we'll
make
sure
that
that's
out
of
the
agenda
as
well,
if
you
need
help
any
issues
that
go
down,
this
is
your
friendly
governance
team
you're,
not
sure
who
to
reach
out
to.
A
As
always,
you
can
route
through
me
and
I'll
direct
you
to
the
POC
that
can
help
you
with
that
question.
So,
let's
Jump
Right,
In
Another
reason
we're
on
the
call,
thanks
for
being
here,
I'm
going
to
post
in
chat
right
now,
two
links.
The
first
is
the
link
to
the
slide
deck
in
case
you
don't
have
that
as
posted
in
slack.
The
second
is
the
link
to
this
error
table
form.
A
If
you
fill
this
out,
it's
a
great
way
to
kind
of
Mark
your
attendance
and
participation
and
build
your
reputation
score
of
participation,
and
if
you
are
new
or
if
you're
a
storage
provider
or
you
might
want
to
become
a
notary
soon.
This
is
a
great
way
to
kind
of
Mark.
Like
hey
I've,
been
coming
to
sessions
for
six
months,
I've
been
involved.
This
is
a
great
way
to
Market
so
open
if
you're,
a
notary,
also
open.
A
A
Oh
I'm
asking
that,
because
she
joined
on
the
morning
I'm,
going
to
paraphrase
some
of
the
things
that
are
coming
up
and
just
kind
of
give
you
an
overview
what's
on
the
horizon.
If
you
want
to
go
to
anything
in
person,
first,
coming
up
is
September
6
to
September
7
taking
place
in
Seoul.
It's
the
secured
Finance
supported
by
filecoin
Foundation.
Some
of
the
draws
to
this
is
It's
a
developer
Focus
conference,
and
the
second
draw
is
that
Juan
is
going
to
be
giving
a
keynote
at
the
talk.
A
So
this
is
coming
up
gosh
two
days,
if
you
haven't
bought
your
ticket
I
think
it
might
be
a
little
bit
too
late
or
you
can
just
rush
over
there.
The
second,
with
a
little
bit
of
notice,
is
the
dev
Summit.
This
is
strictly
by
developers
working
on
it.
I
think
Gavin
will
be
in
attendance
on
this
one,
and
this
is
like
what
are
the
development
tools
that
are
going
to
shape
the
protocol.
You'll
see
the
link
right
there
at
fielddev.io.
A
If
you
want
to
sign
up
or
get
more
information,
as
that
comes
early,
October
is
filled,
Vegas,
taking
place
in
the
states
in
Las
Vegas,
of
course,
and
if
you're
Keen
to
become
a
storage
provider,
or
you
want
to
kind
of
build
a
network
of
other
storage
providers.
This
might
be
a
really
high
value
event
for
you
to
attend.
A
You
go
through
like
best
practices,
a
lot
of
like
the
tooling
and
it
kind
of
mirrors
that
espa
Journey
as
you
go
forward
and
lastly,
with
a
lot
of
notice
coming
up
in
the
middle
of
November
is
going
to
be
the
fill
day.
The
film
Network
base
taking
place
in
Lisbon
if
you're
able
to
make
it
out
last
year,
it
took
place
I
misspoke
last
year
took
place
in
Lisbon
this
year.
Coming
up
is
going
to
take
place
in
Istanbul,
so
this
is
open
to
all
web
3
developers.
A
Storage
providers
like
a
lot
of
the
development
Community
around
ethereum.
So
again,
if
you're
looking
for
in-person
connections
with
everything
filecoin
that
Istanbul
might
be
your
biggest
bang
for
buck.
So
if
you're
curious
to
see
any
of
these
links
are
in
the
slide,
deck
feel
free
to
reach
out
to
me
and
I
can
route
you
through
the
event
team.
If
you
have
any
other
questions,
I
should
kind
of
walk
through.
A
So
I
think
the
big
talking
points
to
this
slide
that
RG
addressed
in
the
morning
is
that
it's
completely
been
resolved.
There's
no
new
issues,
great
news,
and
so,
if
you
have
any
questions
or
you
want
to
take
a
look,
feel
free
to
look
at
the
tractor
for
any
kind
of
historics.
I.
Think
the
big
call
out
right
now
is
that
there's
no
new
open
issues
right
now,
if
you
have
any
questions
on
this,
want
to
discuss
in
more
detail.
A
Rg
is
the
best
point
of
contact
to
the
trust
and
transparency
working
group
or
shoot
a
hand
and
I'll
be
happy
to
route
you
to
the
best
place,
All
Right
Way
new.
Are
you
on
the
line
by
chance
I'm
going
to
take
a
look
over
at
the
guest
list,
because
I
didn't
see
your
name,
so
we
might
have
a
little
bit
of
fill
in
the
blanks
for
it.
A
D
K
So
we'll
just
take
a
second
and
we'll
get
all
those
links
in
the
chat
here
and
then
they're
also
in
some
of
our
public
slack
channels.
But
if
this
type
of
project
or
architecture
is
interesting
to
you
or
in
your
wheelhouse
or
you
have
feedback
on
it,
we
would
love
to
hear
it.
We
want
to
see
more
and
more
of
these
different
Pathways
where
notaries
are
working
at
a
programmatic
level.
We
have
you
know.
For
example,
we
have
the
glyph
Auto
verifier,
which
is
a
programmatic
notary.
K
So
we're
really
stoked
to
see
these
I.
Think.
A
big
thing
to
like
keep
in
mind
here
is
that
these
kinds
of
proposals
are
for
options.
This
is
not
necessarily
the
governance
team
trying
to
say:
okay,
we're
switching
everything
over
to
one
new
mechanism
that
this
team
is
proposing,
so
check
these
out
and
watch
the
different
recordings
and
look
at
some
of
the
different
links
that
we'll
drop
in
the
chat.
A
A
A
All
right
well,
if
that
could
have
been
awkward,
let's
go
right
into
974..
So
essentially,
what
this
issue
is
is
it's
talking
about
the
data
cap
removal
process,
and
so
this
was
started
a
few
months
ago
from
a
Community
member
and
a
lot
of
the
discussion
ticked
off
in
that
issue.
Then
it's
kind
of
moved
into
this
one
974
and
974
is
a
lot
more
of
like
what
are
the
specifics
for
the
data
removal
bot.
A
So
if
you
haven't
read
this
I
think
the
main
call
is:
please
take
a
look
at
this
and
give
feedback
on
the
timelines.
Is
it
too
conservative
or
is
it
too
generous
and
to
kind
of
refresh
you
if
you
haven't
taken
a
look
right
now,
if
an
LDN
application
has
not
had
a
comment
for
14
days,
this
bot
is
going
to
trigger,
and
after
the
end
of
14
days,
if
there's
been
no
development,
then
what
that
stale
application
is
going
to
do.
A
Is
it's
going
to
be
removed
and
the
data
cap
that
might
be
allocated
will
be
taken
off.
So
this
issue
has
been
open.
What
this
is
confirming
is
28
days
of
inactivity
if
you're
looking
to
give
feedback
either
Pro
or
con
that's
a
great
place
to
get
started.
Another
way
that
this
data
cap
could
be
removal
if
there
was
like
the
option
like
hey
I,
signed
this,
an
error
which
has
happened
from
time
to
time,
or
the
comment
has
not
been
used.
Another
way
that
this
block
could
be
triggered.
A
So
this
is
open
and
this
would
be
a
lot
of
feedback
on.
Is
this
the
right
way
to
approach
this?
Does
this
bot
meet
the
expectations
as
far
as
timeline?
So,
if
you
have
any
thoughts,
please
leave
them
in
the
comments
on
this
issue
or,
if
you'd
like
to
discuss.
This
is
a
great
forum
for
it.
So
I'll
stop
pause
and
open
it
up.
K
J
K
K
This
is
also
only
saying
of
that
amount
of
data
cap
held
at
client
addresses
functionally.
Let's
look
at
the
stale
data
cap
data
cap
where
the
application
has
not
had
any
activity
for
you
know,
weeks
weeks
and
weeks,
and
it's
as
simple
as
you
know,
clients
saying:
oh
we're
still,
you
know
getting
deals
with
our
storage
providers,
we're
still
working
on
transferring
the
data
we
are
making
progress
and
that
kind
of
activity
is
just
showing
engagement
and
signs
of
life.
So
really
this
is
just
a
mechanism
for
us
to.
K
K
He
is
a
is
a
notary
the
same
as
other
community
notaries,
there's
a
kind
of
a
distinction
between
like
the
role
that
he
plays
in
performing
diligence
and
then
the
role
that,
for
example,
I
play
at
the
foundation
on
like
the
governance
side,
so
I
do
not
sign
allocations
as
a
notary,
Danny
functions
in
that
capacity,
and
so,
as
far
as
like,
he
has
something.
To
add
to
that
I
think.
J
J
K
But
I
don't
see
other
hands
or
questions
about
this
one,
so
really
in
the
issue.
What
we
would
like
to
get
most
from
people
is
kind
of
feedback,
around
sort
of
two
main
directions.
One
do
we
feel
that
it
is
reasonable
to
remove
data
cap
from
a
client
when
the
client
has
gone
completely
dark
and
is
not
responding
to
any
communication?
K
Outreach,
that's
sort
of
like
a
philosophical
question
and
then
two
is
the
question
of
how
long
should
we
say
that
someone
needs
to
be,
as
I
said,
you
know
dark
like
it
without
any
communication,
before
we
remove
data
cap
and
again,
knowing
that
this
is
not
necessarily
A
a
blacklist
that
would
say
okay,
this
client
address
can
now
no
longer
ever
receive
data
cap
in
the
future.
This
is
just
saying:
let's
take,
let's
take
still
data
cap
and
remove
that
from
the
funnel.
K
A
Yeah
thanks
again
thanks
Danny
very
similar
to
that
is
this
one's.
This
was
kicked
off
by
Phil
really
recently
I
think
today,
and
what
this
is
talking
about
is
the
A
and
C
bot,
which
is
the
aggregation
and
compliance,
and
essentially
what
this
plot
is
trying
to
do
is
look
at
the
mechanisms
that
that
first
spot
should
run
so
as
it
gets
triggered.
A
So
if
you
have
feedback,
if
you
have
thoughts,
if
you
have
input,
this
would
be
a
great
place
to
leave
that
as
far
as
like
what
should
this
bot
be
running
in
the
last
one,
then,
how
is
that
bot
triggering
this
one
getting
set
up
so
very
similar?
This
one's
got
a
lot
of
engineering
work
that
goes
into
it.
So
again,
if
you
haven't
checked
out
976,
this
was
just
filed
in
the
last
day
or
two.
This
is
a
high
recommendation.
This
is
on
your
radar
to
go.
A
L
H
K
Yeah
they
do,
we
do
go
into
some
of
the
the
conditional
functions.
If
you
go
into
the
issue.
You'll
see
some
of
what
we're
looking
at
is
aggregating
multiple
different
data
sources.
For
example,
we
have
a
CID
Checker
bot,
we
have
a
retrieval
bot
and
in
the
future,
more
teams
could
be
adding
more
Bots
and
apis.
K
Is
the
client
working
with
storage
providers
that
are
also
working
with
Phil
green?
That
adds
to
some
of
the
reputation
in
the
system
that
adds
some
amount
of
accountability,
because
you
know
the
Phil
green
team
is
doing
their
own
sets
of
checks.
So
that's
where
we're
trying
to
take
existing
other
data
sources
and
pull
them
together
and
then
on
the
compliance
side.
K
They
are
out
of
compliance
with
their
application,
and
so
that's
where
we're
trying
to
get
into
the
you
know
more
neutrality.
They
told
us
they
were
going
to
behave
in
a
certain
way.
The
notaries
approved
it
their
deal
making
does
not
match.
If
that
is
the
case,
why
should
we
continue
giving
them
data
cap?
And
so
that's
where
baking
in
some
more
of
these
checks?
K
We
would
like
to
hear
feedback
from
notaries
about
sort
of
philosophically
Are
We
aligned
in
saying,
let's
have
Bots
that
pull
data
from
multiple
sources,
to
make
this
process
easier
and
more
transparent
and
more
consistent
and
and
then
how
do
we
say
you
know,
let's
try
it
with
this
amount
of
forced
compliance
if
they
claim
they
are
going
to
behave
in
one
way
and
they
don't
how?
What
is
the
amount
of
leeway
that
we
have
for
these
different
thresholds
and
then
from
there
we
could
start
making
automated
requests
to
remove
data
cap.
K
Those
requests
would
still
need
to
go
through
there's
a
couple
ways
on
chain
that
we
would
like
to
do
it.
Ideally
in
a
perfect
world,
we
would
have
it
make,
set
up
a
set
amount
of
rules.
If
a
group
of
notaries
agree
to
those
thresholds
which
would
be
open,
sourced
and
transparent,
then
those
notaries
would
say
like
yes,
I
have
approve
of
you
know
this
bot
making
these
decisions,
and
if
we
have
a
quorum
of
notaries,
we
don't
have
to
have
all
current
notaries
have
the
unanimous
consent.
A
Thank
you
for
that.
Galen
I
appreciate
that
we
had
Way
new
Yang
just
joined
a
line,
so
good
news
Carol.
It
looks
like
you're
still
here,
minu
Yang.
Thank
you
for
coming
back,
for
the
second
call,
I
think
what
might
make
a
lot
of
sense
is
that
I'll
back
up
and
just
let
you
kind
of
do
it-
you
were
free
To,
Go
in
Mandarin
and
Kara
will
just
do
a
translation
in
English
afterwards,
for
the
recording
floor
is
yours
thanks.
E
D
E
D
E
E
D
On
the
left,
there
is
Storage
client.
The
first
point
is
data
cap
collateral.
This
I
will
not
dive
too
deep
into
because
it
is
transparent
and
the
data
that
second
one
is
data
preparation
fee.
This
is
because
the
the
data
that
is
stored
that
and
the
data
needs
to
be
transformed
into
Unchained,
so
so
that
the
data
and
this
fee
needs
to
be.
This
thing
needs
to
be
shared
by
both
the
data
preparer
and
the
storage
client.
F
D
F
E
D
D
E
E
D
E
E
E
D
D
We
have
also
thought
about
just
using
continuous
checks,
but
to
lower
the
cost.
We
thought
that
data
auditor
or
DA's
are
probably
the
better
choice
here.
For
example,
if
you
have
the
data
Auditors
randomly
audit
three
people
they
would.
This
is
a
better
way
to
enforce
consistency
of
data
stored
and
lower
the
cost.
E
H
H
E
E
D
So
on
the
right
here
we
have
the
storage
providers.
This
is
a
very
important
role
that
communicates
with
the
rest.
The
storage
providers
on
differently
from
current
situation
is
that
the
storage
provider
provides
a
storing
result
at
the
end,
and
this
result
talks
about
the
number
of
sectors,
for
example,
and
the
size
of
the
data
data
set,
for
example,
if
there's
a
hundred
terabyte
of
data
set
and
how
many
sectors
did
I
use
and
what
are
those
sectors?
D
D
So
here
we
have
a
small
amount
of
collateral
that
storage
providers
need
to
provide
in
trenches.
For
example,
a
50
T
tip
data
set.
Maybe
the
data
cap
allocation
will
be
10
tips
and
10
tip
and
tentative
for
each
of
these
small
trenches,
the
storage
provider
needs
to
provide
collateral
to
guarantee
that
the
previous
tranches
be
been
stored.
E
E
D
E
D
F
E
E
E
D
H
E
D
E
D
D
E
E
D
E
H
K
A
Thank
you
so
much
for
coming
Carol.
Thank
you!
So
much
for
being
here.
We
appreciate
that
I
think
some
of
the
feedback
that
I
saw
in
the
call
was
like
having
more
details,
I
think
that
I'll
post
this
on
YouTube.
That
was
it's
available,
but
you
might
get
even
more
questions
much
more
detailed
than
this
morning.
I'm
gladly
had
Carol
here
with
you.
Thank
you.