►
From YouTube: Filecoin Plus - May 09, 2023 Notary Governance Calls
Description
The 9th set of Notary Governance calls of 2023 May 9th to discuss the Filecoin Plus program.
Slides and Links: https://docs.google.com/presentation/d/1cIRurkAw2uPMvkrRPyyEhsRZKpI_FXLUOQi5HB7JsxE/edit?usp=sharing
________________________________________
Notary
- Election Pre-Update
- Notary KYC requirements
- Github Account Update Procedure
- Bug Reporting Template
- Community Survey https://airtable.com/shrn5ELkgtQwtbY2i
Working Group Updates
- EFil+: 872 Application pathways
- T&T: Well distributed Deals
Proposals
- 821: Removal of Datacap (passing)
- 851: Increasing Limits for DataCap (passing)
Community Issues
- Update: DataCap Stats
- Fil+ App Data Metrics
- April EOM Update https://medium.com/filecoin-plus/fil-quality-phase-end-of-month-update-april-2023-2f89d62e7abb
Community Discussions
_____________________________________
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/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://medium.com/filecoin-plus
Reddit: https://bit.ly/39N4Jmv
Telegram: https://bit.ly/3bkP8Ly
Subscribe to our newsletter! https://bit.ly/3Oy8J9j
#filecoin #ipfs #libp2p #web3 #nft
A
A
To
you
all
good
afternoon
and
welcome
to
the
May,
9th
notary
governance
call
for
filecoin,
plus,
let's
take
a
look
at
what
we
have
on
the
agenda
for
this
session.
We're
going
to
start
with
topics
related
to
notaries,
and
with
this
we're
going
to
introduce
a
little
bit
of
just
updates
about
the
notary,
kyc
process.
This
impacts
organizations
that
may
have
completed
their
diligence
might
have
to
Circle
back
we're
going
to
talk
briefly
about
the
GitHub
procedure.
A
So
if
you
need
to
change
your
GitHub
handle
for
whatever
reason,
what
steps
you
should
follow
for
transparency
and
diligence,
we're
going
to
move
into
bug,
reporting,
there's
been
a
new
template
created
to
try
to
seam
line.
This
position,
make
it
easier
for
capturing
this
and
making
sure
that
we're
fixing
these
issues
timely
for
you
and
then
we're
going
to
leave
you
with
a
survey.
This
is
collected
from
Galen
to
kind
of
measure
the
sentiment
as
we
go
forward
after
those
notary
issues.
A
We're
going
to
talk
about
some
working
group
updates,
so
KZ
will
walk
us
through
this
Pathways
update
that
Enterprise
fill
plus
is
looking
at
and
RG
will
walk
us
through
updates
related
to
the
data
cap
and
CID
deal
distribution
analysis.
After
that
we
have
a
lot
of
updates
related
to
the
proposals.
We
have
two
that
are
passing
in
this
next
coming
week.
A
So
this
is
a
final
opportunity
to
discuss
those
proposals,
kind
of
make
you
aware,
as
the
community
and
share
what's
going
down
that
pipe,
and
we
have
a
lot
of
updates
for
the
discussion
with
the
end
of
month
updates,
as
well
as
the
deal
stats
that
might
be
taking
place.
So
with
that.
As
always,
if
you
have
questions
on
this
call,
feel
free
to
unmute
or
raise
a
hand
or
comment
in
chat
and
also
this
slide.
Deck
is
posted
in
the
file
coin
slack.
A
So
with
that,
if
you're
joining
in
this
call
it's
May
9th,
the
next
call
will
be
taking
place
on
May
23rd
if
you're
watching
this
on
YouTube
and
want
to
grab
these
links,
the
slide
deck
is
posted
in
the
details
below
and
we
post
this
in
the
Google
Agenda.
So
if
you
want
to
follow
along
live,
we
do
this
call
every
two
weeks
at
zero.
Eight
hundred
fifteen
hundred
UTC
and
1800
Pacific
0-1
UTC
so
feel
free
to
join
if
you're,
watching
on
YouTube
man,
we
post
the
agenda.
A
A
Just
leave
a
comment:
Hey
Kevin
I'd
like
to
talk
about
XYZ
on
the
call
or
have
you
guys
talked
about
XYZ
on
the
call
just
leave
a
comment
in
that
repo
and
I'll
be
sure
to
build
it
into
the
agenda
as
we
go
friendly
hello
from
our
governance
team
you're
going
to
recognize
one
new
wonderful
face
in
the
top
right.
That's
Lucas
who's
going
to
be
joining
the
team
for
a
stint
of
around
six
weeks,
I'm
going
to
let
Lucas
unmute
and
introduce
himself
and
just
say
a
friendly
hello.
B
Hi
everyone
thanks
so
much
for
welcoming
me
to
the
team
over
the
next
six
weeks.
As
you
know,
k-ray
already
discussed
and
I'll
be
helping
out,
and
mostly
with
some
of
the
communication
stuff,
to
make
sure
that
you
know
we're,
sharing
and
loudly
and
clearly
all
the
objectives
and
that
we
have
in
this
quality
phase
and
it's
very
clear
what
what
progress
we're
making
towards
the
goals
that
are
defined
there.
So
very
much
looking
forward
to
meeting
all
of
you
and
working
on
that.
A
All
right
well
said
we're
happy
to
have
you
too
Lucas,
thanks
for
coming
on
board,
looking
forward
to
all
that
all
right,
so
with
that,
let's
jump
into
some
of
the
issues
from
notaries.
So
first
off
is
the
election.
Here's
just
what
we
have
tentatively
planned
and
trying
to
keep
this
as
transparent
and
open
as
possible
as
we
work
towards
these
goals.
We're
looking
at
a
fifth
round
of
election
taking
place
in
the
July
time
frame
of
this
year.
A
What
we're
going
to
be
doing
is
hosting
a
fill
plus
day
tentatively
scheduled
for
mid
to
late
June
dates,
TBD
and
during
that
fill
plus
day,
we'll
Circle
back
with
a
lot
of
issues
on
the
road
map.
Some
of
the
work
we've
done
to
the
past
two
quarters,
but
then
also
address
some
of
the
issues
found
with
the
elections.
A
Highlighting
some
of
the
proposals
that
we're
talking
about
making
in
this
fifth
round
is
different
types
of
notaries,
so
some
notaries
may
join
and
just
wish
to
participate
on
a
community
level
we'll
make
that
an
application
process.
Some
notaries
may
wish
to
join,
and
just
do
this
LDN
these
large
application
signing,
and
then
some
may
wish
to
do
direct
so
in
this
fifth
round.
We're
going
to
have
a
lot
more
categories
for
notaries
to
select,
rather
than
this
one-size-fits,
all
with
all
different
standards,
also
really
looking
at
the
scoring
of
applications.
A
So
in
the
fourth
third
and
second
round,
we
had
a
lot
of
proposals
that
talked
about
scoring
based
off
reputation,
State
current
applications.
What
we're
going
to
be
looking
to
do
is
try
to
take
that
from
unstructured
paragraph
format
and
try
to
make
it
much
more
clear-cut,
with
like
selecting
a
category
that
you
fit
in
based
off
contributions
based
off
what
work
you
want
to
be
involved
in
and
then
really
step
up
the
kyc
process
in
the
initial
application.
You
notaries
that
participated
in
fourth
round.
A
We
may
have
become
very
close
in
slack
following
up
with,
like
hey
diligence,
questions,
hey
disclosure,
questions,
hey
sanctions,
questions
set
up
questions,
so
part
of
the
goal
in
the
fifth
round
is
to
make
this
easier
on
you.
So
we're
collecting
this
in
all
one
big
upfront
application
and
then
limit
that
additional
secondary
questions
that
come
so
again.
This
is
just
to
highlight.
This
is
about
three
months
away.
Just
really
keeping
this
on
your
radar.
A
A
Every
single
call
I'm
just
going
to
copy
this
from
the
leaderboard
and
post
it
here
in
chat,
and
what
this
will
allow
you
to
do
is
sign
in
for
notaries
and
kind
of
Mark
your
participation,
and
this
will
let
us
track
and
make
sure
that
we're
adding
your
score
into
the
leaderboard.
So
I'm
just
going
to
do
this
really
quick
posting
this
into
chat,
so
any
notaries
that
are
on
the
call
follow
this
link
right
here
and
that'll.
A
Take
you
back
to
this
leaderboard
and
if
you
don't
have
this
leaderboard
address,
I'll
pop
it
there
one
more
time
for
you
and
again
with
this
leaderboard.
What
we're
doing
with
this
with
the
work
on
fill
is
that
we
can
essentially
see
the
average
time
to
data
cap.
Your
participation
in
the
program,
your
region
and
as
this
builds
up,
if
we
finalize
this,
this
is
going
to
populate
a
notary
score
almost
like
a
scoreboard
and
a
ranking
system.
A
So
if
you
don't
have
a
GitHub
account
if
you're
not
tied
into
the
notary
elections
right
now,
if
you
follow
this
air
table-
and
you
still
want
to
sign
in
as
a
community
member,
if
you
follow
that
link
right
there
that'll,
let
you
participate.
The
reason
why
I
would
highlight
that
if
you're
not
an
existing
notary
is
during
the
elections,
be
pull
heavily
from
past
contributions
to
the
network.
What
have
you
been
doing
to
support
participate
and
contribute?
A
A
This
is
a
great
way
for
you
to
highlight
that
on
a
future
application,
so
you'll
see
all
three
links
there
in
chat,
the
sign
in
for
your
GitHub
for
the
notary
data
cap
airtable,
if
you're
not
currently
a
notary,
if
you
have
any
questions,
feel
free
to
let
us
know
in
the
chat,
all
right
kind
of
a
check-in
for
anybody
who
may
be
interested
recently.
In
the
past
two
weeks,
we've
had
two
separate
organizations
that
have
reached
out
and
said:
hey
for
whatever
reason
we'd
like
to
change,
the
GitHub
account
that's
handling
our
notaries
applications.
A
So
I
just
wanted
to
highlight
this
for
public
transparency,
since
you
might
have
seen
store
Swift
and
Max
come
through
in
our
private
notary
Channel.
Really
what
we're
asking
of
anybody,
not
just
those
two.
If
you
would
like
to
change
your
GitHub
application
for
a
different
name,
here's
the
three
steps.
You
should
follow
step,
one
just
kick
off
a
DM
in
the
private
Channel
you
have
with
Phil
and
myself,
just
hey
I'd
like
to
change
the
name,
give
us
a
brief
description
on
the
reason
and
we'll
help
kind
of
coach
you
through
the
next
steps.
A
Number
two
is
go
back
to
your
application
and
just
leave
a
comment
from
the
original
Creator.
So
if
I
made
the
application,
it
would
be
Kevin
FF,
hey
I'd,
like
to
change
it
to
make
deep.
The
new
account
manager
for
this
I
might
be
stepping
away
from
the
organization
or
I
have
too
many
slacks
in
githubs
to
manage
this
person
will
be
doing
it
and
then
the
step
three
is
modify
the
line
inside
of
your
application
for
your
individual
reputation
score
and
just
add
that
GitHub
account.
A
The
reason
we
ask
all
three
steps
is
it
ensures
transparency.
Everyone
in
the
community
knows.
It
also
helps
us
with
our
reporting
logs
So
within
two
years
in
the
future.
We
have
to
come
back.
We
have
a
good
audit
trail
of
why
this
change
was
made
and
who
those
GitHub
accounts
were
so
again.
Thank
you
for
participating
in
this
store,
switch
and
Max
we're
going
to
be
making
those
modifications
and
changes
for
you.
Anybody
else,
just
clear
essay
for
you.
A
A
What
we're
having
to
do
is
come
back
and
we're
issuing
five
fill
to
cover
the
cost
of
gas
fees
and
part
of
this
requirement
that
we've
been
given
from
legal
is
any
organization
that
wishes
to
participate
in
the
fourth
round,
as
well
as
receive
this
fill
from
the
filecoin
foundation
must
provide
an
individual
name
with
their
organization
maintenance,
so
this
impacts
around
six
notaries.
You
guys
have
been
DMS
with
me
already
I'm
updating
this
right
now.
C
C
So
far,
there's
the
informal
process
has
just
to
report
these
bugs
to
either
Kerry
or
me,
and
then
we
would
just
report
that
to
our
engineers
and
and
it
would
be
a
quick
fix,
but
as
we
scale
and
as
we
have
more
more
and
more
updates,
it
would
be
beneficial
to
both
of
us
if
we
had
a
formal
way
to
record
bugs
and
also
document
them.
So
then,
if
someone
else
has
the
same
bug,
they
can
like
look
at
the
old
bug
that
someone
else
had
before
and
how
it
was
resolved.
C
So
what
we?
What
I
did
was
we
did
a
poll
on
the
notary
channel
to
see
what
is
the
best
way
you
guys
would
like
to
report
bugs
and
I
think
the
vote
of
GitHub
issues
won
so
right
now
to
consolidate
bugs.
We
will
tell
people
to
put
those
bugs
on
GitHub
issues
with
a
formal
template
of
how
to
report
these
bugs
how
to
reproduce,
What
device
you're
using
and
what
a
screenshot
of
the
bug
that
would
all
be
helpful.
C
C
So
it
says
here
bug
report
template
and
it
tells
you
like
what
to
enter.
That
would
be
helpful
to
us,
the
more
stuff
you
complete
the
more
helpful
it
would
be
to
us
to
resolve
your
bug
as
quick
as
possible.
So
yeah,
it's
good.
If
you
have
any
thoughts
or
comments,
let
me
know
yeah
with
that,
giving
it
back
to
Carrie.
A
A
Think,
as
we
start
talking
about
our
filecoin
plus
goals
and
what
we're
doing
on
the
roadmap
a
lot
of
that
ties
in
division,
transparency
which
we'll
get
into
them
a
call,
but
we
wanted
to
make
this
form
available
and
I'm
going
to
drop
it
here
in
chat
here
and
then
I'm
also
going
to
post
this
into
our
surveys
that
we
could
have.
Essentially
what
this
is
It's
a
community
quiz
pulls
check
and
really
the
goal
of
this
is
that
we
can
kind
of
measure
a
little
bit
of
the
sentiment
on.
A
What's
going
on
with
you
as
notaries,
as
well
as
what
your
role
is
on
the
network
and
then
what
you're
doing
with
that
data.
So,
as
you
see,
this
form
probably
takes
around
three
minutes
to
complete,
you
could
multitask
and
do
it
on
this
call
as
we
start
talking.
But
it's
looking
for
some
of
the
basics
like
who
are
you
in
the
network?
What
is
your
role?
Where
are
you
based
and
then,
as
we
work
towards
this
quality
phase?
A
Where
do
you
see
the
eligible
for
data
Capital
qualifications?
Where
do
you
think
that
these
come
through
and
again,
this
gives
us
a
pulse
on
how
you
understand
this
currently,
so
that
we
can
over
communicate
and
correct
anything
that
might
not
currently
be
in
the
system
right
now
again
estimated
time
to
complete
this
three
minutes
put
the
link
here
in
chat.
It's
also
in
the
medium
article
and
we'll
be
posting.
This
in
slack
shortly
so
again,
we
really
appreciate
your
time
to
fill
this
out.
A
This
helps
a
lot
with
how
we're
building
these
roadmaps
out
and
communicating
with
you
and
again.
The
goal
is
to
hit
the
topics
that
you
might
need
corrected,
or
you
might
have
addressed
that
we
were
not
just
harping
on
the
things
that
we
might
think
need
to
be
talking
brought
up
and
with
that
we're
going
to
slide
right
into
the
working
group
update
so
I'm,
going
to
turn
the
floor
over
to
KZ
who's,
going
to
give
us
an
updates
on
the
Enterprise
field,
plus
Pathways,
okay,
Z.
D
E
D
Different
required
flow
for
applicants,
and
so
we
want
to
just
consider
all
the
valid
Pathways
that
are
potentially
out
there
and
begin
to
standardize
those
into
different
flows.
Next
steps
for
this
are
to
sort
of
think
about
the
different
questions
we
would
potentially
need
for
each
flow
develop
requirements
for
any
changes
to
dashboards
automations
and
also
develop
clear
applicant
instructions
per
pathway.
D
So
on
the
right,
you
can
see
a
list
of
pathway
categories
that
we've
come
up
with
broken
out
by
data
type
and
applicant
type,
so
this
will
help
us
not
only
again
standardize
the
information
coming
into
specific
Pathways,
but
also
allow
us
to
manage
measure
and
think
about
each
flow
differently,
so
open
to
any
thoughts
or
feedback.
There's
an
open
issue
now
in
the
notary,
governance
repo
feel
free
to
drop
any
comments
that
you
have,
but
this
is
on
the
radar
on
the
roadmap.
D
A
A
F
Yeah
I
was
just
gonna,
say:
I'm
I'm,
a
big
fan
of
this
line
of
thinking
and
better
Separation
on
types
of
applications
by
both
ways,
because
I
think
it
does
like
two
or
three
really
big
things
that
are
very
underrated.
Number
one
I
think
it
allows
us
to
actually
build
experiences
and
application
templates
and
Bots
that
are
a
little
bit
more
use
case,
specific,
which
is
very
valuable
because
we
can
better
collect
the
information
that
we
need
up
front
from
clients
so
that
notaries
have
what
they
need
like
we're.
F
Learning
this
from
Evil,
plus
and
Casey's
working
on
a
bunch
of
like
upfront,
verification
stuff
as
well.
That
we
know
is
is
good,
but
that
will
help
both
on
the
client
side
and
on
the
notary
side.
The
second
reason
is
because
this
will
give
us
much
better
data
on
what's
flowing
through
flowbus
today.
In
a
way,
that's
even
if
it's
client
reported
it's
much
more
transparent.
F
F
How
do
we
want
to
see
it
changed
over
time
and,
like
that
kind
of
thinking,
you
can
do
much
more
cleanly
now,
because
it's
it's
easier
to
do
the
analysis
when
you
know
you're
getting
upfront
reporting
on
what
the
particular
type
of
pathway
is
and
who's
engaging,
why
they're,
engaging
and
stuff
and
so
I
think
that's
super
useful
and
I
think.
The
third
reason
this
is
extremely
valuable
is,
is
purely
from
a
standpoint
of
the
tooling
itself.
F
It
would
just
be
you
know:
I
am
this
type
I'm
that
type
and
then
it's
like
great
here's,
the
template.
You
should
use
here's
what
you
should
fill
out.
Here's
what
we
expect
to
do
once
you
start
onboarding
data,
and
so
it's
it's
not
like
our
users
are
being
exposed
to
the
mass
confusion.
But
then
we
get
this
tremendous
upside
of
better
organization,
better
labeling,
better
readability
and
so
yeah
I'm.
A
A
G
G
Of
course
you
know
it's
a
very
hard
thing
to
do,
because
everyone
has
a
different
opinion
plus
you
know
it
can
mean
different
things
for
different
people,
but
this
is
the
first
kind
of
effort
to
do
that.
Now,
this
graph
that
you
see
on
your
screen,
okay,
are
you
able
to
kind
of
expand
it
or
I?
Think
that'll
be
super
helpful,
but
yeah,
essentially
as
Kira.
G
G
I'll
share
the
exact
issue
number
that
this
issue
was
created
for,
but
right
now,
I
think.
The
reason
we're
sharing
this
is
to
show
some
of
the
ways
in
which
we're
starting
to
Define
what
might
constitute
abuse
and
what
might
not,
and
so
on
your
on
the
graph
that
you
see
the
green
represents
well
distributed
deals.
This
is,
of
course,
in
the
last
90
days
and
it's
cumulative,
so
a
cumulative
of
the
three
things
that
you
see
on
the
on
the
right
side
as
well.
G
G
G
If
no
one
has
questions,
what
we'll
do
is
we'll
keep
you
updated.
I'll
also
be
talking
about
this
in
the
next
TNT
working
group
call
and,
of
course,
the
goal
here
is
to
see
more
of
green
and
less
of
the
orange
yeah,
and
so,
if
you
are
someone
who
is
interested
in
this
effort
overall,
please
reach
out
would
love
to
brainstorm
and
then
yeah
work
together.
Thank
you.
So
much.
A
Well
done
indeed
right.
The
next
phase
is
we
have
two
proposals
that
have
been
open
for
around
three
Sprints
around
six
weeks,
they're
reaching
that
closing
period.
So
this
is
just
an
update
from
Simon
to
walk
through
what
these
two
proposals
were.
Now
that
they're
passing
and
put
these
to
make
sure
that
they're
on
your
radar
and
talk
about
any
final
questions
you
may
have
so
Simon
floor
is
yours,
yeah.
H
Thanks
Kerry
hi,
everyone
like
Harris
I,
just
want
to
give
everyone
a
quick
update
on
this
as
the
workaround
and
the
original
word
flow
for
the
remove
data
cap
feature
are
being
worked
on
and
I
know.
We
talked
a
lot
about
this
on
the
previous
calls,
but
we
just
want
to
announce
that
the
proposal
will
officially
close
a
few
requests
to
remove
data
cap
from
certain
address.
Client
addresses
have
been
made
and
are
in
the
notary
governance
repo.
H
H
If
this
truly
becomes
an
issue,
we
can
go
back
to
the
five
PIV
limit
for
application
on
ldns,
but
the
governance
team
does
believe
that
a
lot
of
the
assumptions
made
will
actually
help
the
different
stakeholders
and
the
overall
program.
So
let
us
know
if
you
have
any
questions
on
any
of
these
two
proposals.
A
Nice
we'll
go
to
chat
or
hand.
These
two
proposals
have
been
on
the
agenda
for
the
last
three
weeks
or
three
Cycles
department,
so
there
shouldn't
be
anything
new,
but
if
anybody
has
any
thoughts
or
final
comments
that
weren't
captured
in
GitHub
that
you
like
to
make
aware
this
is
a
great
opportunity
and
we'll
kind
of
pause.
A
All
right,
well
with
that,
we
talked
a
lot
about
the
road
map
on
last
week's
call
and
the
week
before,
and
so
we
wanted
to
kind
of
share
some
of
the
updates
that
you
might
see
coming
down
the
pipe
with
like
issues
that
impact
the
community,
whether
you're
a
notary,
a
storage
provider
interested
party.
So
with
that
I'm
going
to
pass
the
floor
over
to
Phil
who's,
going
to
walk
us
through
some
updates
on
the
data
cap,
stats.
C
So
through
this,
we
want
to
show
the
impact
of
fill
Plus
on
this
statistic
still
in
the
early
stages
right
now,
it's
only
two
statistics
and
in
the
future
we
plan
to
add
more
metrics.
To
this
add
more
statistics
to
the
section,
as
well
as
change
the
statistics
from
point
in
time
to
more
overtime
data,
so
it'll
turn
to
graphs
yeah.
So
just
a
small
update,
there's
a
medium
post.
C
C
C
It
will
show
how
many
of
them
are
successful
and
how
many
of
them
failed
right
now
the
statistics
are
not
well
developed
yet,
for
example,
the
failed
still
it
still
needs
to
be
iterated
on
the
failed
statistic
still
shows
encapsulates
all
the
failures,
including
the
the
approvals
and
proposals
that
you
all
abort
yourself.
So
this
is
not
the
likely
failure.
Count
is
much
lower
than
this
and
going
forward.
We
want
to
add
more
statistics
to
this
page.
It's
still
very
much
at
early
stages.
A
Oh
man,
Phil
I'm,
a
fan
I
like
that.
A
lot
I
can't
wait
to
see,
as
that
goes
forward.
Well
done,
I
put
the
link
in
chat.
If
anybody
wants
to
look
at
that
or
kind
of
Click
around,
this
was
obviously
even
the
blog
posts
that
Phil
put
out.
So
if
you
have
any
questions,
please
let
us
know
it's
only
going
to
get
better
Phil!
That's
awesome!
A
F
Totally
I
know
that
again
wanted
to
be
here
to
chat
through
some
of
this
and
I
think
he'll
be
hopping
on
in
a
few
minutes.
So,
if
he's
able
to
make
it,
he
can
definitely
add
some
more
details
but
yeah.
You
know,
April
has
been
a
very
busy
month
for
us
and
I
think
that
this
kind
of
clip
is
what
you
can
expect
from
us
moving
forward
as
well
for
the
next
coming
months.
F
In
light
of
the
governance
call
today
and
sort
of
get
the
conversation
moving
to
think
about
bigger
duration,
changes
and
movements
overall,
as
well
as
give
all
of
you
a
view
into
how
you
can
check
for
yourself
where
progress
is
being
made,
things
that
you
should
read
things
that
are
worth
your
time
and
being
caught
up
in
and
so
I
would
highly
recommend
you
spend.
You
know
the
five
minutes
that
Medium
thinks
it
takes
to
read
this
I
promise.
F
It's
it's
not
that
long
and
there's
a
lot
of
fun
links
that
you
can
choose
to
click
into
if
anything
catches
your
eye
I
just
want
to
take
a
second
and
reset
back
to
where
we
were
almost
exactly
a
month
ago,
which
was
I,
think
April
7th.
We
created
that
Medium
space
we
put
out
the
announcement
for
the
quality
phase.
Some
of
you
that
were
following
along
were
aware
that
this
was
coming
because
we
also
talked
about
it
in
the
recorded
Network
update
session
that
made
its
way
to
YouTube.
F
And
so
there
is
one
and
then
the
specific
goals
that
we're
working
towards
I
I
like
to
call
them
by
their
sort
of
tag.
Name.
There's
this
one
on
enablement,
which
is
you
know,
100
of
all
valid
types
of
clients,
have
a
positive
data
cap,
there's
one
on
transparency,
which
is
the
public
visibility
into
all
key
initiatives
and
goals.
F
And
then
this
key
one
on
quality,
which
is
that
we'd
like
to
Target
95
of
new
data
cap,
is
allocated
to
Quality
data
and
use
cases,
and
so
how
we
measure
that
comes
back
down
to
the
conversation
that
RG
was
having
I
think
it's
up
to
notaries,
beta
owners,
SPS
and
those
in
the
custom.
Transparency
working
group
is
engage
community
members
to
start
to
Define
these
things
and
work
together
on
reasonable
ways
in
which
we
can
measure
our
own
progress.
F
We,
of
course,
will
come
with
some
proposals,
but
we're
also
looking
forward
to
you
being
engaged
on
this
front.
The
medium
post
itself
shows
you
some
of
the
links
to
things
that
have
been
shipped
this
month,
and
so
you
should
take
a
look
because
it's
got
a
link
to
the
roadmap,
both
the
higher
level
one
and
the
detailed
one.
F
It
also
has
links
off
to
specific,
highlight
things
that
were
shipped
so
there's
the
field
plus
dashboard
that
Kerry
just
showed
while
scrolling,
and
you
can
see
you
know
what
the
changes
were,
what
it
looks
like
now
and
sort
of
where
we're
headed.
The
second
thing
that
we
talked
about
I
think
is
storage,
the
app
which,
by
the
way,
has
also
been
open
sourced
and
so
I
know
there
was
some
feedback
somewhere
on
hey.
Can
we
get
this
done
in
a
different
language?
Can
we
get
this
done
in
different
way?
F
The
convenient
thing
we
we
have
in
this
communities
that
are
entire
stack
is
actually
completely
open
and
accessible,
and
so
anybody
could
take
this
and
build
something
that
they
think
you
know
is
more
reasonable
for
the
use
case,
they're
interested
in
so
feel
free
to
check
that
out
and
then
dispute
resolution.
Of
course,
I
think
it's
a
big
one
having
a
public
dispute
tracker.
One
of
the
things
that
I
wanted
to
call
out
here
is
that
it's
been
up
for
about
three
weeks
now.
F
The
first
two
weeks
was
like
three
to
four
disputes
being
opened
per
week.
The
last
week
was
seven
disputes,
so
it
went
like
three
and
a
half
three
and
a
half
seven
on
average
and
of
those
seven
have
already
been
closed
out
some
interesting
takeaways
from
action
and
consequences.
There
we've
had
the
whole
range
like
we've
had
like
at
the
extreme.
F
Today,
we're
working
on
a
couple
of
more
different
views,
some
that
are
like
super
sad
or
overarching
views,
some
that
are
tool
specific,
but
the
quality
of
the
information
available
on
the
quality
of
the
data
being
onboarded
will
continue
to
improve
I
think
the
options
that
people
will
have
to
form
their
own
opinions
will
also
improve.
So
it's
a
matter
of
you
know,
picking
the
right
things
and
making
sure
we're
highlighting
the
right
things
for
the
community
to
index
on.
F
Similarly,
May
is
going
to
be
busy
too
a
lot
of
big
stuff
coming
a
lot
of
this
stuff
already
in
flight,
so
you've
heard
bits
and
pieces
there.
But,
as
you
know,
right,
this
is
all
being
driven
by
roadmap.
That's
completely
public!
You
can
check
anytime,
you
want
and
please
get
in
touch.
You
know
if
you've
got
suggestions,
comments,
questions.
The
best
thing
you
can
do
is
engage
in
GitHub.
F
Every
single
thing
we
work
on
has
an
Associated
GitHub
issue
or
a
GitHub
discussion
topic,
and
so
we'd
love
your
attention
there
and
then
the
second
best
thing
you
can
do
is
check
out
the
roadmap
and
get
in
touch
with
us
and
send
us
your
comments
and
the
way
you
can
do
that
is
in
slack
directly.
So
if
you've
got
questions
about
a
specific
item,
the
roadmap
tells
you
who's
working
on
it
and
you're
welcome
to
bring
them
directly.
F
The
second
best
thing
you
can
do
is
just
bring
straight
info,
plus
the
channel
the
public
Channel
and
start
a
discussion
there.
If
needed.
One
thing
we
are
going
to
focus
on
and
what
we're
really
hoping
to
partner
on
with
Lucas
as
well,
is
sort
of
bringing
in
your
feedback
and
sentiment
in
in
more
predictable
Cycles.
So
if
you've
noticed
our
end
of
week,
updates
now
have
a
little
poll
that
says:
hey
was
this
useful?
F
We
want
to
do
more
of
that
and
we
want
to
make
sure
we're
moving
the
needle
in
the
right
way
and
so
we're
going
to
start
putting
out
more
systematic
polling
and
opinion
Gathering.
So
we
ensure
that
we're
all
focused
on
the
right
things
and
the
stuff
we're
working
is
the
stuff
that
you
think
needs
to
be
prioritized
with
that
Carrie
I
got
a
question
for
you.
F
A
E
E
E
I
want
to
reiterate
that
we
want
everyone
in
the
filecoin
community
to
go,
submit
a
response
on
this
poll.
Please
it
has
some
kind
of
check
your
alignment
questions
just
to
see
if
we
are
thinking
about
these
things
in
the
same
way
or
if
you
know
a
large
portion
of
the
community
has
a
different
understanding
or
or
sort
of
a
a
different
alignment
on
some
of
these
questions,
that'll
be
really
interesting
and
helpful
for
us
to
know
and
then
there's
some
sections
about.
You
know.
E
Overall,
how
satisfied
are
you
and,
and
what
else
could
we
be
doing,
or
should
we
be
doing
so
check
that
out?
We'll
probably
leave
that
open
for
about
a
week
to
capture
responses,
we'll
see
how
we're
doing
we'll
blast
that
in
some
public
channels
as
well,
let
everybody
know
it
is
open
to
everyone,
not
just
notaries.
So
this
is
not
limited
to
one
reply
per
organization
like
that
notary
poll
was
so.
E
If
you
have
someone
who
you
work
with
that,
you
know
handles
more
of
the
SP
operations
and
you
handle
more
of
the
notary
operations.
You
should
each
fill
it
out
independently
and
submit
your
answers
so
check
that
out
it's
on
airtable.
It
should
be
accessible
to
everyone.
We
didn't
restrict
access
to
any
sign
in.
So
let
us
know
again
in
slack
if
you
have
problems
filling
out
that
form
and
we
look
forward
to
seeing
the
replies
thanks.
A
E
And
a
quick
question
for
the
notaries
on
the
call
I
know:
we've
been
pushing
a
number
of
updates
to
the
registry
front
end
to
help
that
load
faster
and
add
some
tooling
I
haven't
really
heard
from
people.
If
that's
working
well,
is
it
loading
faster?
Is
it
more
reliable?
Are
you
able
to
search
and
find
applications
by?
You
know,
proposal
number
or
name
and
sign
them.
You
know
quicker
and
with
more
Fidelity,
or
are
we
still
having
a
lot
of
bugs
on
that
front?
E
E
Sure
I
know
that
we
were
having
some
issues
with
the
registry
load
times.
It
was
taking
a
long
time
to
load
and
pull
in
because
there
were
so
many
open
issues
in
the
way
that
it
was
crawling,
and
we
made
some
updates
with
Kiko
that
were
intended
to
really
speed
up
the
load
time
for
the
registry,
so
that
it
will
populate
faster
and
have
more
reliable
search
and
I
just
wanted
to
know.
If
notaries
were
experiencing
improved
access
of
the
load
time
of
the
search.
E
So
the
next
thing
that
we've
been
working
on
are
the
saves
replies
where
people
can
go
in
and
you
know
tag
whether
or
not
they
are
going
to
sign
it
or
not
and
give
a
reason
as
to
why
they
are
not
signing
it
and
there
could
be.
You
know
a
number
of
legitimate
reasons
to
not
sign
an
allocation
request,
but
that
just
gives
a
little
bit
more
signal
to
the
client
and
to
the
other
notaries
as
to
what's
going
on.
E
So
the
client
doesn't
think
they're
just
being
ignored,
so
love
to
try
and
get
a
little
more
traction
from
our
notaries
on
those
open
allocation
requests
that
we've
been
really
pushing
on
quality,
but
even
going
in
and
saying
I'm
not
going
to
sign
this
and
here's.
Why
we'll
help
give
some
information
like
I,
said
to
the
client
and
to
those
other
notaries.
A
A
Oh
well,
big
friendly
hellos
and
welcome
to
the
second
notary
governance
call
of
May
9th.
Let's
take
a
look
at
the
agenda
that
we
have
on
Deck
to
discuss
so
on.
Today's
call
we're
going
to
be
looking
at
four
different
topics
in
the
first.
Is
all
issues
related
to
notary,
so
we're
going
to
kick
off
with
talking
about
just
some
check-ins
on
the
kyc
for
notaries.
This
will
impact
just
a
few
folks
GitHub
protocol
procedures.
So
if
you
need
to
change
your
name,
how
does
that
process
work?
A
What
do
you
do
to
really
kick
that
off?
A
new
bug,
reporting
template,
hopefully
to
streamline
it,
keep
you
in
the
loop,
so
you're,
not
kind
of
in
the
dark
messaging,
Phil
and
I
wondering
what
the
status
is
we're
going
to
try
to
make
that
more
transparent
for
you
and
then
a
survey
what's
going
on
in
the
world
of
not
just
notaries
but
the
community,
but
trying
to
get
a
pulse
on
how
filecoin
plus
is
being
viewed,
we're
going
to
shift
gears
and
go
through
two
updates
on
the
working
groups.
A
One
comes
from
Enterprise
fill,
plus
cases
on
the
line
and
I'll
be
speaking
on
behalf
of
RG
for
the
trust
and
transparency
team
and
the
CID
dealbot
Checker
that
they
have.
After
that,
we
have
two
proposals
that
are
closing.
This
is
just
a
friendly
update
just
to
make
sure
that
everyone's
aware
of
those
two
proposals
that
are
passing,
give
you
one
last
time
to
voice
any
concerns,
thoughts,
feedback
on
them
before
those
wrap
up,
then
we're
going
to
end
the
call
with
just
a
road
map
summary.
A
So
this
got
pushed
out
by
Deep
a
couple
days
ago
kind
of
highlight
what
changes
you
might
have
seen
for
April
and
then
checking
in
on
where
to
find
work.
In
the
morning
call
we
had
around
15
minutes
left
for
lots
of
q
a
so
if
there's
anything
on
your
mind
feel
free
to
always
shoot
a
hand
up
and
chat,
unmute
ask
as
we
go
or
you
can
wait
till
the
end
of
this
call.
If
there's
something
you
want
to
discuss
in
more
depth,
we'll
have
plenty
of
time
just
to
reiterate
that.
A
So
with
that,
let's
kind
of
kick
off
and
see
what
we
have
in
store.
Is
there
friendly
reminder
if
you're
joining
this
call
we
share?
Are
these
every
two
weeks
today
is
May?
9Th
next
call
is
taking
place
on
May
23rd.
If
you're
curious
to
add
this
to
your
calendar,
you
can
go
to
the
Phil
plus
channel
in
slack
there
you're
going
to
find
the
link
to
this
deck.
If
you're
watching
in
YouTube
You'll
see
all
these
links
below,
but
we
have
this
calendar.
A
Add
this
and
you'll
never
be
remiss
on
when
the
next
meeting
is
taking
place
and
if
there
was
a
topic
that
you
were
Keen
to
see
flagged
or
discussed,
and
you
wanted
to
make
sure
that
got
on
the
agenda.
This
is
an
open
Forum.
Any
topics
feel
free
to
come
into.
Github
I'll
make
this
issue
two
weeks
in
advance.
Any
topics
you
want
to
see
discuss
flag,
just
leave
a
comment
in
that
issue:
I'll
reach
out
help
you
flush
out,
slides
anything
or
just
give
you
time.
A
So
if
you
have
any
questions
want
to
see
anything
added
again
check
out
the
GitHub
for
notary
and
we'll
make
sure
that
we
allocate
time
for
you
as
we
go
forward
as
a
friendly
reminder.
There
are
now
one
bonus
person.
That's
on
our
governance
team
here,
Lucas
is
joining
from
protocol.
Labs
I,
don't
see
him
on
the
call
now
Lucas.
If
you
are
feel
free
to
unmute
and
just
step
right
over
me,
Lucas
is
joining
for
the
next
six
weeks.
A
He
comes
from
protocol
labs
and
he's
going
to
be
looking
at
how
our
communication
process
is
really
working
and
making
sure
that
we
kind
of
give
you
the
best
bang
for
your
buck.
You
might
notice
in
some
of
the
posts
that
we
make
we'll
give
you
a
chance
to
like
give
us
feedback.
Is
this
helpful?
Is
this
not
helpful?
A
Do
you
want
to
see
more
content,
so
Lucas
is
really
going
to
Zone
in
on
that
and
try
to
make
sure
that
everything
that
we're
pushing
out
is
tactical,
helpful
and
not
just
noise
for
the
sake
of
noise,
then
again,
we've
all
got
our
subject
matter.
Expert
areas,
if
you
ever
have
a
question,
and
you
don't
know
who
to
Route
it
to
feel
free
to
send
it
my
way
and
I'll
be
happy
to
plug
you
in
on
the
right
channel
to
go
forward
all
right
with
that
notaries.
A
Looking
at
you
right
now,
here's
what
we
have
coming
on
the
pipe
elections,
so
this
is
all
prepare
to
be
prepared
in
July
of
this
year,
we're
looking
at
hosting
the
fifth
round
of
notary
elections.
All
these
dates
are
tentative
since
they're
still
so
far
in
advance,
but
here's
what
we're
working
on
right
now
in
June
we're
gonna
host
another
Phil
plus
day
during
this
fill,
plus
we're
going
to
dedicate
a
lot
of
time
for
going
through
the
election
process
very
similar
to
how
we
did
it
at
Phil,
Lisbon
back
in
November.
A
For
those
of
you
that
remember-
and
the
point
of
this
is
any
common
questions-
the
workflows.
The
documentation
really
build
that
out
to
try
to
make
it
as
simple
as
possible
for
notaries
wishing
to
join
or
renew
answer
any
questions
and
go
over
it.
Some
of
the
changes
that
you're
going
to
notice
in
this
fifth
round
that
we're
working
on
is
during
the
fourth
third
and
second,
a
lot
of
the
application
in
GitHub
was
set
up
in
like
free
form
text.
A
So
you
had
to
write
a
paragraph
you
had
to
like
really
fill
fill
in
the
blanks
and
then
for
the
governance
team.
We
would
go
through
and
score
that,
so
a
lot
of
questions
came
up
after
the
fact
of
like
why
was
I
scored
X.
It
was
really
kind
of
tricky
to
kind
of
suss
that
out,
if
you
might
not
have
been
selected,
so
one
of
the
purposes
of
the
new
election
that
we're
looking
at
is
really
make
it
like
drop
down
categories.
You
pick
the
category,
it's
very
clear-cut.
A
What
that
score
will
be
it's
going
to
be
much
more
transparent
and
part
of
that
kyc
process.
So
a
lot
of
you,
notaries
that
have
borne
with
dozens
of
DMS
from
me
for
kyc
for
sanctions.
Checks
for
registry
addresses.
The
goal
is
that
we
can
just
get
that
all
at
one
time
for
you
and
spare
you
having
to
go
back
and
forth
through
that
process
again
and
again.
So
this
is
just
prepare
to
be
prepared.
A
A
All
right,
all
right,
all
right
again
feel
free
to
post
it
in
chat.
We've
got
to
multitask
here,
I'll
be
happy
to
see
it
in
patch
over
as
we
go
all
right,
notaries
I
see
this
come
up
in
the
chat.
Someone
asking
about
the
code
here,
it
is
so.
Every
week
we
have
a
sign
in
I'm,
going
to
grab
this
code
and
put
it
here
in
chat,
and
what
this
will
do
is,
if
you
put
this
into
the
leaderboard,
this
will
actually
Mark
your
participation
for
being
here.
A
This
counts
towards
the
SLA
points,
if
you're
new
on
the
call-
and
you
don't
have
that
leaderboard
bookmarked
I-
put
it
right
there
in
chat
as
well,
when
you
fill
out
that
code
under
your
GitHub
address,
that'll
make
a
note
for
calls
attended,
we're
baking
this
into
the
SLA
for
you,
notaries
that
have
been
in
the
program
for
a
while.
Thank
you
thank
you
for
coming
to
these
calls.
Thank
you
for
keeping
the
transparency
high.
Thank
you
for
contributing
newer
notaries.
Again.
This
is
a
great
way
to
kind
of
contribute.
Your
score.
A
We
look
at
this
on
the
election
and,
if
you
are
just
a
member
of
the
community-
and
you
want
to
just
say,
hey
I'm
here-
I
might
want
to
come
back
later
and
be
a
notary
or
I
might
want
to
make
my
voice
heard.
We
have
this
air
table
form
I'm
going
to
post
this
here
in
chat,
I
recommend,
if
you're
a
notary
to
not
use
this
airtight
table.
A
Unless
you
have
a
problem
with
that
registry
on
the
leaderboard,
but
if
you're
a
data
applicant,
if
you're
a
storage
provider,
if
you're
brand
new
to
the
community,
you
might
not
have
a
GitHub,
you
might
not
be
in
the
leaderboard.
If
you
fill
this
out,
we
can
track
and
make
sure
yeah,
hey
Danny's,
been
to
five
of
these
calls
now
he's
applying
to
be
a
notary
his
pump.
Indeed,
this
is
a
great
way
to
just
kind
of
Mark
that
so
again,
both
of
those
links
are
in
chat.
A
If
you
have
any
questions,
any
blockers
feel
free
to
throw
it
up
and
we'll
make
sure
that
we
get
you
the
support.
You
need
all
right,
nitty
gritty,
how
to
change
your
GitHub.
This
has
come
up
twice
in
the
last
three
weeks.
This
was
a
brand
new
process
for
us,
so
store
Swift
Max.
Thank
you
again.
Thank
you
for
your
patience
as
we
kind
of
get
this
completed.
So
essentially,
what
may
happen
is
you
file
a
GitHub
application
to
be
a
notary
a
couple
weeks
couple
months
go
by
maybe
that
person's
left
the
organization.
A
Maybe
there's
been
a
change,
maybe
there's
just
too
many
comms
and
you
want
to
have
a
different
Channel
and
you
want
to
have
a
new
GitHub
account
in
the
registry.
That's
different
from
the
GitHub
to
Major
application,
not
a
problem.
What
you're
going
to
want
to
do
is
just
start
off
with
a
friendly
text
to
fill
in
myself,
use
that
existing
DM
that
we've
set
up
with
you
and
just
say:
hey
Kev
I'd
like
to
change
my
GitHub
handle
it's
from
this.
A
To
that,
and
the
reason
is
this
I'll
say
great:
all
I'm
going
to
ask
you
to
do
is
come
back
into
your
original
application,
leave
a
comment,
same
basic
information
and
then
you're
going
to
edit
the
organizational
represent
representation.
The
reason
why
we're
asking
for
all
of
this
is
just
transparency,
one
giving
Phil
and
I
a
heads
up
lets
us
start
to
get
the
back
end.
All
set
up,
there's
actually
quite
a
bit
of
steps.
On
our
end,
two.
By
adding
the
comment,
everyone
can
see
that
there
was
a
change
to
the
application.
A
It's
open,
it's
transparent
and
three
by
actually
editing
the
application.
It
will
branch
that
application
in
GitHub.
So
just
in
case
somebody
deletes
that
comment
in
the
future.
We
have
a
record
of
like
who
actually
made
that
application
when
it
changed
and
why
so
method
to
the
madness
again.
If
this
ever
applies
to
you
just
let
us
know
and
we'll
give
you
a
hand,
store
Swift
Max,
we're
going
to
finish.
You
guys
up
thanks
again
for
being
the
Trailblazers
in
this
and
we'll
make
sure
that
we
help
others
as
we
go
forward
notary
kyc.
A
So
some
of
you
might
have
got
a
DM
from
me
in
the
last
week
or
so.
Thank
you
for
responding,
we're
working
on
the
back
end.
What's
going
on
with
this
is
if
you're,
following
the
news,
there's
a
lot
more
increased
I,
guess
just
push
in
the
crypto
space
to
kyc
and
really
making
sure
the
diligence
is
taking
place
and
filecoin
is
no
exception
so,
with
fill
plus.
What
we're
doing
is
we're
preparing
to
send
five
fill
from
the
filecoin
foundation
to
the
wallet
addresses
of
all
existing
fill
notaries.
A
This
is
meant
to
cover
the
gas
fees
associated
with
application.
Signing
and
part
of
that
Financial
transfer
goes
through
a
lot
of
steps,
and
some
of
the
notaries
that
have
applied
in
the
fourth
round
are
just
listed
as
an
organization,
and
what
we're
finding
is
that
we
need
to
keep
up
with,
like
the
transparency
laws
of
the
U.S.
So
that
means
that
any
organization
must
name
at
least
one
person
who
is
responsible
and
controlling
that
ledger.
A
So
this
could
be
your
Treasurer,
your
CFO
anybody
who's
really
in
control
of
that
is
going
to
step
up
and
be
the
point
person
for
the
organization.
This
is
going
to
apply
across
the
board,
individuals
and
organizations.
So
again,
thank
you
for
the
increase
in
transparency.
Thank
you
for
taking
the
time
I
have
a
couple:
DMS
open,
I'll,
probably
open
up
just
a
few
more
and
we'll
be
following
up
we're
still
waiting
for
a
question.
A
If
this
is
going
to
be
like
a
hard
requirement
where,
if
we
don't
receive
that
human,
that
means
we're
going
to
have
to
pause,
so
we'll
probably
have
updates
in
the
coming
days
on
that
process,
as
we
hear
back
more
from
legal,
so
those
of
you
that
have
got
those
DMS.
This
is
the
reason
why
thank
you
for
the
time.
Thank
you
for
the
human
name
and
we'll
be
sure
to
kind
of
make
it
all
set
up
for
you
going
forward
easier
in
the
fifth
round.
A
I
A
I
A
If
that's
the
case
feel
free
to
kind
of
ping
back,
we
had
five
notary
addresses,
bounced
back
I
reached
out
and
I
fixed
those.
Let
me
make
sure
if
you
missed
it,
it
was
a
survey,
just
a
sentiment.
Survey,
I'll
repost
it
again
that
way
in
case
it's
not
meant
to
be
private.
It's
not
meant
to
be
any
kind
of
like
check.
So
if
you
didn't
get
that
email
I'll
make
a
note
here
and
I'll
Circle
back.
A
You
can
see
in
the
top
right
a
couple
weeks
ago
about
how
do
we
make
this
process
easier
for
you
and
more
transparent?
The
way
it
works
is,
if
you
do
message,
Phil
and
I,
we'll
still
go
work
with
the
contractors
to
see
like
hey.
What's
the
status
of
this,
can
you
work
this
in
and
we'll
build
it
into
the
Sprint
to
kind
of
get
that
fixed,
but
then
it
becomes
a
black
box
for
you.
While
you
wait
for
updates
so
either
that
means
you
ping,
us
hey.
A
Is
there
any
update,
we
say
yeah
we're
still
waiting
we'll
get
back
to
you
and
that
can
kind
of
be
a
little
bit
nail-biting
for
you
as
you
go
forward.
So
what
we're
rolling
out
is
this
new
bug,
report
template
and
the
way
this
will
work
is
you'll
actually
fill
out.
This
GitHub
form
and
I'll
click
this
link,
so
you
can
see
it,
and
this
just
lets
you
say:
hey
I'm,
this
person
I'm
having
this
issue.
A
Can
you
please
help
me
once
this
automatically
creates
and
I'll
pin
this
in
slack
notaries
Channel
this
makes
it
transparent
so
that
the
teams
that
are
working
on
this,
be
it
Kiko
or
d-mob
or
anybody
involved,
can
see
it.
You
can
see
it,
we
can
see
it.
We
can
leave
updates
if
you
leave
an
update
yourself.
It's
not
just
lost
in
a
slack
DM.
So
again,
this
bug
template
is
meant
to
be
like
an
easier
way
to
keep
the
transparency
again.
A
If
you
forget
about
this
template
and
you
DM
us
no
problem,
what
I'll
probably
do
is
just
fill
this
out
and
tag
you
in
the
issue
that
way
it's
just
more
public
and
going
forward,
but
again,
you'll
see
this
hung
into
fill.
Plus
slack
channel
is
just
an
easy
way
for
you
to
go
out
and
fill
a
bug,
reporting.
J
A
A
So
this
survey
just
got
posted
to
slack
and
I'll
post
this
link
here,
so
everyone
can
see
it
here
in
chat.
This
lets
you
come
through
and
say:
hey
I
am
a
notary
I'm
in
this
organization
or
hey
I'm,
a
storage
provider
or
a
Community
member,
and
then
you
select
your
region,
and
what
these
questions
tell
us
is
what
blind
spots?
Does
the
community
not
understand
with
the
program
that
we
should
work
to
close
like?
A
How
is
should
data
cap
come
on
or
what
does
abuse
look
like
or
what
is
actually
the
quality
phase
mean
the
time
to
complete.
This
survey
is
three
four
minutes
Heck.
If
you
wanted
to
multitask
on
this
call
and
knock
it
out
double
thumbs
up
but
again,
the
point
of
this
is
to
making
sure
that
the
quality
of
information
is
aligned
to
what
you
need
from
it.
A
So
again,
any
questions
you
have,
let
us
know
the
links
right
there
in
chat,
and
it's
also
in
the
Phil
plus
channel
in
slack
as
well,
so
with
that
I'm
going
to
take
a
well-earned
voice,
break
and
stop
talking
for
a
moment
and
hand
it
over
to
the
much
more
wonderful
Kevin
KZ.
Do
you
mind
walking
us
through
the
updates
on
Enterprise
fuel
Plus.
J
D
Not
necessarily
an
Enterprise
fill
plus
focused
update
but
I'm
presenting
it,
because
we've
been
working
on
a
different
pathway
related
to
e-fill
with
the
past
six
months
or
so
where,
as
opposed
to
the
the
normal
flow
that
everyone
is
used
to
we've
added
some
additional
checks,
upfront
checks
and
also
some
SP
notification
and
auto
assigning
of
notaries.
You
know
we've
done
a
lot
of
testing
with
the
e-fill,
so
this
became
its
own
pathway
of
sorts.
D
So
what
we're
looking
to
do
is
build
off
of
what
we
learned
from
that
and
enable
all
valid
Pathways
to
have
a
more
standardized
processes
in
place.
We're
looking
at
you
can
see
on
the
right
here.
The
different
data
types
we're
focused
on
either
being
open
public
data
sets
commercial
public
data
sets
or
private
at
this
point
and
then
also
applicant
type.
I
D
Preparer,
an
SP
or
a
proxy
IE
aggregator.
So
with
these
different
combinations
of
categories,
we
can
then
begin
to
look
create
more
transparency.
Analyze
present
different
statistics
related
to
different
types
of
of
application
Pathways.
So
the
next
steps
in
this
process
will
be
reviewing
sort
of
the
question
flow
and
seeing,
if
there's
any
needed,
changes
for
different
Pathways,
developing
requirements
with
the
tech
teams
related
to
automations
and
dashboards
and
then
developing
some
clear
instructions
for
the
pathways
definitely
open
to
any
ideas
or
feedback
related
to
this.
D
If
anyone
thinks
of
any
other,
you
know
areas
that
were
not
necessarily
addressing
within
this.
Please
let
us
know
this
is
this
has
become
more
straightforward
and
you
know,
like
I,
said
in
the
past
six
months,
with
the
addition
of
e-fill
plus
and
we're
looking
to
this
sort
of
categorize
each
pathway
more.
D
A
H
K
D
It'll
follow
the
same
path,
essentially
we're
just
adding
categories
more
questions
that
are
actually
already
on
the
application,
but
with
that
information
now
we're
able
to
start
to
look
at
the
different
data
types
and
say
you
know
we're
just
making
up
a
majority
of
onboarding
in
this
quarter.
Are
you
know
where?
If
we
have
abuse
concerns,
which
which
categories
or
which
areas
are
we
seeing
the
most
coming
through,
instead
of
just
having
one
General
category
that
it's
hard
to
distinguish?
What's
happening
based
on
some
of
the
the
differences
between
these
categories?
D
But
nothing
is
changing
in
terms
of
the
flow
of
the
the
LDN
process.
It'll
still
be
one
repo
like
I
said:
if,
if
we
do
come
up
with
different
questions
or
changes
that
are
needed,
that
might
might
change
a
little
bit,
but
regarding
open
public
that'll,
that's
pretty
much
the
the
standard
that
was
built
from
day,
one
and
I
don't
think
that'll
change
much
at
all.
F
A
Right,
if
you
guys
have
any
other
questions
again,
we'll
have
plenty
of
time
at
the
end
of
this
call,
or
just
like
Danny
and
Mark
feel
free
to
stick
a
hand
up
and
be
sure
to
come
by
and
address
any
questions.
You
have
all
right,
moving
on
trust
and
transparencies
update
speaking
on
behalf
of
RG.
What
you're
looking
at
at
the
screen
right
now
is
a
CID
deal.
Distribution
chart
and
the
way
that
this
chart
works
is,
on
the
left
hand,
side.
A
When
you
see
those
orange
bars,
what
those
are
telling
you
are,
the
percentage
of
possible
abuse
deals
and
the
percentage
in
green
is
the
percentage
of
well-distributed
deals
now
I'm
going
to
get
into
like
how
to
interpret
this
data,
and
obviously
we
see
this
downward
Trend
in
these
possible
abusive
data
deals,
but
what
we
should
like
really
highlight
and
discuss
and
why
we
have
it
on.
The
call
is
that
there
are
three
factors,
and
you
see
these
on
the
text,
but
just
to
kind
of
really
Drive.
These
home
is
number
one,
no
duplicate
data.
A
This
is
kind
of
a
tenant,
and
we
talk
about
this
again
and
again.
We'll
make
ensure
that
we're
not
seeing
duplicate
data
in
those
cids
number
two
is
that
there's
no
sharing
across
that
CID
data
across
those
addresses
so
making
sure
one
no
duplicate
data,
two
no
sharing
and
that
those
onboarded
data
have
now
made
a
deal
for
the
past
few
weeks.
So
like
really
looking
at
it
in
those
three.
So
it's
very
easy
to
kind
of
see
this
downward
Trend.
A
This
trusting
transparency,
really
steps
up
in
February
and
as
we
look
at
the
last
90
days
from
February
March
to
April,
we
see
this
slow
tip.
It's
not
a
drastic,
there's,
no
sudden
spikes
or
bar
drops.
This
is
a
gradual
process,
but
one
thing
to
highlight
with
this
data
that
we're
looking
at
is
just
being
mindful
that
this
doesn't
like
really
represent,
like
any
kind
of
client,
cancel
deals
or
any
kind
of
issues
that
we
might
have
where
like
that,
might
be
taking
place.
A
So
what
we're
highlighting
is
like
this
right
now
is
still
like
a
private,
very
much
iterative
in
process.
Dashboard,
there's
a
reason
why
we're
not
sharing
the
link?
It's
that
it's
still
very
much
in
development,
but
we
are
sharing
you
the
link
just
as
a
community
to
know
this
is
kind
of
how
trust
and
transparency
is
framing.
The
problem
is
like
at
a
macro
scale.
How
are
we
ensuring
that,
like
the
core
tenants
of
this
filecoin
plus
program
are
being
adhered
to?
And
how
are
we
looking
at
addressing
that?
A
Everyone
can
see
what
the
resolution
is
and
when
that
links
to
GitHub,
it's
really
easy
to
start
like
really
ticking
the
boxes
and
start
to
kind
of
clean
this
up
as
we
go
forward,
and
this
is
going
to
play
into
what
our
end
of
month
is
talking
about-
that
quality
phase
of
Phil
Plus
in
2023.
So
Props
to
RG
and
Phil
and
Simon
for
working
on
this.
A
This
is
looking
great
if
you
guys
have
any
questions
that
trust
and
transparency
working
group
and
slack
is
a
great
place
to
funnel
those
and
again
you're,
probably
going
to
see
this
launch
publicly
in
the
coming
Sprints
right
now
very
much
work
in
progress
and
I'll
kind
of
pause,
just
like
with
KZ.
If
anybody
has
any
thoughts,
any
kind
of
questions
or
any
discussion,
this
is
a
great
time
to
flag
it.
Floor
is
yours,.
F
Right
I
was
just
gonna,
add
that
this
is
this
data
source,
and
this
estimation
is
extremely
specific
to
CID
distribution
right,
which
is
just
one
view
into
interpreting
the
usefulness
and
the
quality
of
the
work
being
done.
Your
distribution
is
a
very
important
facet
and
a
very,
very
good
read
into
how
people
are
onboarding
stuff,
but
it's
not
necessarily
like
a
very
good
indicator
of
potential
abuse
in
and
of
itself
in
that,
like
a
lot
of
stuff,
that's
distributed
well
may
still
be
abuse
with
the
system.
F
F
This
being
one
of
them
and
so
I
think
you
should
expect
to
see
a
lot
more
discourse
and
a
lot
of
traction
in
this
idea
of
trying
to
measure
potential
abuse,
trying
to
figure
out
the
the
sources
of
it
and
then
indexing
on
really
Bringing
Down.
The
higher
proliferation
cases
of
it
said
over
time.
We
can
ensure
that
the
network
back
subsidy
is
actually
occurring
in
the
best
way
possible
to
achieve
the
division
of
Phil
Plus.
K
Now
I
do
have
my
hand
put
up,
which
is
just
a
to
Riff
Off.
What
deep
was
saying
I
mean
this
is
I
mean
one
of
the
things
about
this
is
this
is
something
with
the
bot
that
we've
been
actively
signaling
to
folks
in
the
in
the
GitHub
issues
and
so
I
think
it's
a
good
indication
of
people
are
seeing
that
and
changing
their
behavior
based
on
it
I.
K
Don't
necessarily
think
it's
always
due
to
abuse
I
mean
if
somebody
comes
up
with
a
message
that
says:
look
you
have
to
do
this
then
you're
going
to
do
that
and
you
might
just
it
might
just
be
an
accident
right.
The
same
with
the
feedback
I
have
is
a
lot
of
people
coming
in
legitimate
deals
are
coming
in
and
being
kind
of
confused
about
how
they
can
do
distribution
over
multiple
SPS
because
often
they're
in
the
first
start
of
a
process
with
a
particular
SP.
That's
what
they
have
in
mind.
That's.
K
F
Just
want
to
call
either
this
isn't
like
a
raw
just
what
the
CID
tool
is
doing
so
I
guess,
there's
two
alerts
to
this.
First
point:
I
completely
agree
with
you,
I
think.
One
thing
we've
noticed
with
this
data
is
that
it's
very
like
it's
good
at
identifying
potential
abuse,
but
there's
a
ton
of
false
negatives
in
this
in
that
like
just
because
something
is
distributed.
Well,
doesn't
necessarily
mean
it
is
or
isn't
abuse,
and
so
we
want
to
you
know
ship.
F
This
thing
alongside
other
views
as
well
like
it
in
isolation,
is
not
enough
to
inspire
significant
confidence,
but
to
your
second
Point.
One
thing
we
did
do
is
that
the
CID
Checker
is
not
the
only
source
of
data
diving,
this
graph,
it's
actually
coupled
with
a
Scraper
on
GitHub,
which
is
combining
addresses.
So,
for
example,
when
we
see
somebody
apply
AI,
you
know
in
like
eight
different
data
cap
applications.
F
We
think
that,
for
that
to
have
been
the
case,
there
should
be
traffic
in
the
last
six
weeks
like
they
should
have
been
making
some
sort
of
effort
to
continue
onboarding
data
and
that
six
weeks
is
maybe
enough
of
a
margin
to
say.
Oh,
if
somebody's
been
completely
passive
over
six
weeks
and
somehow
still
stored,
only
unique
data,
only
one
time.
That's
when
we
counted
towards
the
orange
in
this
graph.
So
if
somebody
goes
and
uploads
a
bunch
of
unique
data,
only
does
it
with
one
SP.
F
K
A
H
H
H
A
A
This
is
always
Simon
all
right
with
that.
Let's
kind
of
take
a
look
at
some
of
the
issues
that
we
have
going
on
with
the
community,
and
these
are
some
of
the
updates
that
you
might
have
seen
come
through
in
slack
and
some
of
the
medium
posts.
So
Phil
was
on
the
column
this
morning,
I'm
going
to
speak
on
his
behalf
now
and
the
first
you
might
have
seen
it
was
a
medium
article,
Bill
posted
this
around
three
days
ago,
and
it's
talking
about
the
quality
phase.
A
We
mentioned
this
a
lot
in
our
roadmap
for
how
we're
looking
at
the
data
cap
steps
so
he's
got
a
medium
post
that
got
launched,
but
really
the
driving
point
is
what
you
see
in
bold,
the
new
stats
section
on
network
investment
and
what
they're
really
looking
at
is
that
datacapstats.dio
dashboard
and
looking
at
like
how
do
future
plans
over
time
add
to
those
metrics.
So
this
is
step
two
in
this
iterative
process
that
Phil's
putting
together.
But
again
it's
meant
to
be
on
that
trust.
A
Excuse
me
road
map
of
transparency
and
quality
as
this
moves
forward.
So
if
you
didn't
get
a
chance
to
check
out
that
Medium
article,
it
got
shared
in
the
Phil
plus
Channel,
as
well
as
the
link
here
in
the
slide
deck,
but
again
there's
an
updated
front
page
view
for
the
stats,
Dot,
Page
and
I
O.
You
have
any
questions
feel
free
to
check
that
out.
The
second
update
is
actually
how
that
metrics
looks
in
the
philplus.fill.org
dashboard.
This
Phil's
been
working
on.
A
What's
nice
about
this,
is
this
is
meant
to
be
metrics
on
the
tooling
that
go
forward,
including
the
fill
registry
and
the
essay
bot
so
I'm
going
to
load
this
up.
If
you
haven't
had
a
chance
to
see
it
for
those
of
you
that
are
on
the
call-
and
you
want
to
play
around
with
this
with
yourself-
I
just
put
the
link
here
in
chat
and
what
you
can
do
when
you
load
this
page
is.
A
This
could
be
failed
due
to
like
actually
failed
or
failed
due
to
client
cancel
that
request,
so
just
like
the
TNT
dashboard,
that's
being
put
together
lots
of
iteration
process
on
this,
but
what
this
is
meant
to
be
is
much
more
of
like
a
public
facing
View
of
the
health
of
the
strength
of
where
that
data
is
coming
from,
so
that
you
could
see
this
yourself
as
notaries
as
Community
storage
providers
as
interested
parties.
So
this
is
now
live.
You
can
check
this
out.
This
is
all
for
your
view.
A
This
is
also
very
much
work
in
progress,
so
every
week
on,
the
call
Phil
will
be
updating
as
well
as
posting
in
the
articles
that
he's
sharing.
But
again,
this
is
designed
to
give
you
statistics
on
that,
to
make
it
much
more
transparent
on
where
those
deals
are
coming
from
how
they're
being
addressed
and
how
they're
flowing
through
the
pipeline
again,
this
is
Phil's
baby.
F
Yeah
sorry
I
was
you
still
muted,
totally
game.
I
posted
this
medium
post
yesterday
around
this
time.
This
is
sort
of
a
highlight
and
a
recap
on
everything.
That's
happened
in
the
last
month
has
been
pretty
much
exactly
31
days
now,
since
we
opened
up
the
the
medium
space
and
we
really
made
a
push
towards
increasing
the
visibility
and
transparency
into
the
work
that
we're
doing.
F
There's,
like
the
word
quality,
the
word
legitimate,
and
so
all
these
things
have
been
defined.
We
defined
them
using
a
bunch
of
input
from
various
active
notaries
in
the
program
as
well
as
in
general,
just
like,
like
observing,
what's
actually
come
through
the
data
cap
by
playing
over
the
last
year
and
a
half
that
really
things
have
accelerated,
and
the
idea
here
is
that
there's
a
lot
of
feedback
and
desire
to
actually
Define
these
things,
as
opposed
to
leaving
them
open
and
leaving
them
more
nuanced.
F
And
so
we're
designing
to
do
that
as
a
community.
And
then
you
know
Thrive
within
the
bounds
and
Thrive
within
the
scope
that
we're
studying
for
ourselves,
and
so
this
post
sort
of
gives
you
a
little
bit
of
a
recap
on
the
assumptions,
the
terms
and
sort
of
where
the
bounds
lie,
that
we're
gonna
want
to
work
towards,
and
then
it
Cherry
picks
some
of
the
major
Milestones
from
this
past
month.
F
So
highly
recommend
you
read
it
it's
five
minutes,
plus
or
minus
a
few,
depending
on
your
comfort
level
with
dense
English.
But
the
fun
thing
about
it
is
that
you
know
you
know
we
made
an
effort
to
make
sure
to
link
to
a
bunch
of
other
stuff
too.
So
you
could
really
dig
into
the
details
here
and
look
through
all
the
other
posts
that
were
made,
whether
they're
on
slack
or
on
medium
or
in
other
places.
F
So
you
can
dig
into
the
details
for
yourself
or
the
things
that
you're
interested
in,
but
it
really
covers
like
improvements
made
on
the
app
improvements
made
in
tooling
work
done
on
the
tnd
side.
Measurement
of
abuse
Etc,
as
well
as
a
charity,
takes
a
couple
of
things
that
you
should
look
forward
to
in
the
coming
months.
So,
hopefully
you
know
it's
well
worth
your
while
and
if
you
have,
any
suggestions
would
be
great
to
hear
them.
I
also
want
to
call
out
that
at
the
bottom
you
will
see
your
survey.
F
We
really
really
need
you
to
fill
this
out,
like
it's
super
important
for
us
to
figure
out
like
whether
or
not
we're
indexing
on
the
right
things
and
like
working
on
things
that
you
specifically
care
about
as
you're
listening
to
me
talk
whether
you're,
here
live
or
watching
the
recording
it'll
only
take
you
a
few
minutes,
I
highly
recommend
giving
the
blog
a
post
to
skim
and
then
go
to
the
bottom
and
clicking
this
issue.
Sorry
clicking
the
link
to
this
form
and
really
the
form
is
aimed
at
a
few
things.
F
It's
aimed
at
ensuring
that
we're
able
to
get
to
you
we're
able
to
share
the
information
with
you
where
you
expected,
and
it
makes
sense
to
you,
but
then
in
general.
We
want
to
make
sure
that
we're
prioritizing
the
things
that
you
care
about,
and
so
there's
some
questions
around.
What
do
you
think
are
the
top
issues?
How
would
you
prioritize
some
of
the
things
that
we've
been
thinking
about.
C
F
You
feel
like
we're,
making
the
necessary
progress
that
you
need
to
see
for
this
program
to
get
to
a
better
place,
and
so
it
should
only
take
a
few
more
minutes.
So
all
in
all
the
ask
is
probably
10
minutes
or
less
read
the
link
check
out
some
of
the
the
blog
posts.
You
know
that
you
click
into
that
interesting
and
then
fill
out.
The
survey
I
would
greatly
appreciate
it.
A
Thanks
for
that,
indeed,
thank
you.
Thank
you.
Well
with
that,
that's
kind
of
the
end
of
like
our
pre-planned
programming
with
the
time
we
have
left.
This
is
all
yours,
so
anything
that's
on
your
mind,
flag,
whether
it
was
on
this
call
new
business
issues.
The
floor
is
yours
all
right,
whether
it's
a
warm
cup
of
morning
tea
or
delicious
dinner.
If
there's
anything
that
comes
to
mind,
please
let
us
know
in
chat.
A
I
just
put
the
link
for
the
sign
up
for
you,
notaries,
I'll
put
the
link
if
you
were
a
visiting
party,
and
you
just
wanted
to
fill
out
the
air
table
one
more
time
here
and
chat,
but
again
great
way
to
mark
your
SLA
and
go
forward
if
anything
comes
up
best
way
to
flag.
It
publicly
is
in
the
Phil
plus
Channel,
any
kind
of
specific
notary
issues
or
questions
in
our
private
notary
Channel.