►
From YouTube: Filecoin Plus - May 23 Notary Governance Calls
Description
The tenth set of Notary Governance calls of 2023 May23 to discuss the Filecoin Plus program.
Slides and Links: https://docs.google.com/presentation/d/1KMRnJRJby1egDsguMGHaH598dj3tJWs3rzlInVvqL6g/edit?usp=sharing
Agenda
Notary
Community Survey Results
Http Update @caro
Working Group Updates
EFil+: KYC Check Launches
Proposals
880: Guidelines on what is Valuable Data
882: Behavior Community flag
818: Auto Close of LDN applications after 14 days
Community Issues
Training Diligence - How to perform diligence in filplus.fil.org
Bug Reporting tooling update
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/u/0/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0@group.calendar.google.com&ctz=America/Los_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
ERS
to
you
all,
welcome
to
the
first
notary
governance
call
of
May
23rd.
Let's
take
a
look
at
what
we
have
on
the
agenda
for
you
guys
we
break
the
call
into
four
parts.
Part
number
one
is
going
to
be
the
program
section.
So
this
week
we
have
a
guest
speaker,
Lucas
who's,
joining
us
and
he's
going
to
walk
through
some
of
the
results
that
came
back
from
the
survey.
A
So
if
you're,
a
Community
member
notary,
we
sit
on
a
pretty
detailed
survey
two
weeks
ago
and
Lucas
is
going
to
kind
of
highlight
some
of
the
findings
from
that.
After
we
have
a
special
guest
speaker,
Carol
who's
joining
us
on
the
call
from
protocol
Labs
she's
going
to
walk
through
the
booster
program
in
the
HTTP
update
and
then
at
the
end
of
the
call
Phil
will
be
walking
us
through
the
workflow
we're
associated
with
diligence.
So
how
do
we
do
diligence
in
the
registry
and
a
workflow
specific
side?
A
Point
after
that
for
the
working
groups
we
have
KZ
talking
about
the
kyc
launch,
that's
happening,
Enterprise
field
plus
and
then
on
the
proposal
side
of
the
house.
We
have
three
open
issues.
We
wanted
to
flag
for
discussion
to
two
raised
by
the
community,
one
that
was
an
update
that
Simon
will
be
talking
about
and
then
anytime
at
the
end
for
discussions,
this
call
might
be
a
little
bit
Limited
in
time
towards
the
end.
A
So
if
there
was
a
topic
that
you
saw
that
you
wanted
to
speak
to
feel
free
to
raise
your
hand
as
we
go
rather
than
waiting
till
the
end
of
the
call
in
case
we
run
into
time
so
with
that
very
quickly.
This
is
the
May
23rd
version
next
call
will
be
taking
place
on
zero
six
June.
If
you
want
to
follow
along
all
the
invite
links
are
in
this
deck,
which
is
in
the
field
plus
channel
on
slack
the
agendas
for
any
topic
that
you
want
to
see
can
post
ahead
of
time.
A
So,
if
you're
watching
this
after
the
fact-
and
you
want
to
see
anything
added
to
the
Mexico-
feel
free
to
log
into
the
repo
and
add
it
we'll
put
it
on
the
agenda,
we
make
up
your
governance
team.
If
you
need
an
issue,
help
or
have
a
technical
problem
or
any
input
around
the
community
for
filecoin
plus
feel
free
to
reach
out
to
any
of
us,
if
you're,
not
sure,
always
reach
out
to
me
on
slack
and
I'll,
be
happy
to
route
you
to
the
best
important
contact.
A
So
with
that
notaries
are
on
the
call.
We
are
going
to
be
doing
the
air
table
for
the
SLA
participation
this
week.
I
just
put
the
link
here
in
the
chat
box.
So
if
you
are
a
notary
on
the
call
go
ahead
and
grab
that
airtable
and
fill
it
out,
also,
if
you're
a
storage
provider
or
new
member
to
the
community,
if
you
grab
that
air
stable
link
and
sign
up,
you
can
mark
yourself
here.
We
look
at
this
for
future
elections
and
participation
in
programs,
notaries.
B
B
But
this
is
kind
of
gives
us
a
good
overview
and,
and
it
kind
of
helps
us
at
the
Baseline.
We
will
probably
be
repeating
in
these
surveys
at
some
regular
interval
and
to
see
how
we're
progressing
against
some
of
the
things
that
we
measure
and
with
that
Let
Me
Maybe
share
some
of
the
initial
survey,
insights
and
I'll.
Let
Kevin
take
to
the
next
one:
lots
of
charts
here:
I'll,
walk
us
and
through
it
together
and
so
on
the
left
kind
of
against
the
gray
back
backdrop.
B
You
can
see
some
of
the
you
know
respondent
profiles
we
had
70
people
participate
and
most
of
them
from
North,
America,
37
there
and
then,
and
the
second
largest
share
of
respondents
came
from
the
greater
China
region
with
26.
But
we've
had
representation
across
all
regions
across
all
regions
of
the
world
and
that's
great
and
people
have
identified
primarily
as
community
members
or
notaries,
no
surprise,
that's
kind
of
and
who
we
you
know
where
we
put
most
of
our
energy.
B
B
You
know,
according
to
the
respondents
that
you
know
participated
here,
are
the
frequency
at
which
you
know,
firecon,
plus
quality
phase
updates
are
shared
and
and
the
ability
to
shape
the
M5
contrast
program.
I,
take
this
and
kind
of
with.
With
you
know
the
meaning
here,
like
one
interpretation,
could
be
that
there
are
actually
sufficient.
B
You
know
quality
phase
updates
and
so
there's
no
need
to
kind
of
like
fine-tune
or
like
tune
it
up
and
but
we'll
kind
of
have
a
have
a
look
at
how
that
can
go
progress
over
time.
The
takeaway
from
this
is
that
Ione
is,
and
sometimes
you
know,
really
preparing
some
talking
points
and
and
statistics
around
the
5.
B
program
benefits
and
then
drive
to
communication
strategy,
and
you
know
that
we
can
share
with
the
broader
community
and
identify
maybe
some
some
folks
from
the
community
who
can
you
know
amplify
some
of
these
messages.
So
that's
what
we'll
be
working
towards
and
next
and
then
as
we
switch
into
kind
of
the
next
next.
B
But
if
you
look
at
the
distribution-
and
you
can
kind
of
see
from
Left
of
that,
like
distribution,
chart
of
being,
you
know
absolutely
not
identifying
any
abuse
or
data
cap
eligibility
scenarios
correctly,
you
can
see
that
you
know
a
good
chunk
of
people
actually
either
corrected
identify
the
majority
of
what
constitutes
data
cap
and
abuse
and
what
scenarios
are
eligible
for
data
cap.
So
what
we'll
take
away
there?
B
Are
mostly
aligned
and
I
think
that's
great,
and
then
we
see
that
the
average
satisfaction
of
the
vibrant
progress,
five
grand
plus
program
is
currently
3.9
out
of
five,
and
there
is
some.
You
know:
variation
there
in
regions
and
Europe
and
kind
of
is
at
the
bottom
there,
with
the
lower
satisfaction
score
in
Asia
and
outside
of
the
greater
China
region,
and
it
appears
to
be
the
you
know
most
satisfied
with
the
program.
B
Thank
you,
Kevin
and
here's
just
a
few
of
those
qualitative
and
insights,
and
you
know
I've
kind
of
grouped
them
into
three
main
topics,
but
it's
a
little
hard,
obviously
to
you
know,
make
sure
that
all
voices
are
heard
but,
like
some
things
that
I
wanted
to
share
is
that
there's?
You
know
some
doubts
around
the
merits
of
the
five
coin
plus
program
in
its
current
form.
B
You
know
some
people
are
I'm,
saying
it's
it,
it
apparent
it
makes
the
network
more
permissioned
and
that
it
should
be
one
down
and
that
you
know
the
quality
of
data
that
it
attracts,
must
have
some
kind
of
like
a
representation
of
a
data
storage,
client's
willingness
to
pay
so
kind
of
ideas.
On
on
how
to
shift
the
program
and
I
encourage
you
to
keep
voicing
those,
and
we
can
kind
of
as
the
governance
team
and
kind
of
take
those
into
consideration.
B
Then
there
is
some
issues
around
the
speed
of
data
cap
allocation,
just
kind
of
like
making
sure
that
that's
happening
faster
and
here
once
again,
I
think
even
later
on.
This
call
we'll
hear
about
some
of
the
things
to
make
it
easier
and
then
finally
handling
of
abuse
right.
So
some
books,
you
have
said
that
abuses
are
very
common
and
there
should
be
more
effective
ways
to
resolve
and
data
cap
reviews.
So
we'll
continue
to
have
these
discussions.
B
A
C
D
Thank
you,
hi
everyone,
it's
great
to
great
to
be
on
this
call
my
first
time.
Actually
so,
thanks
for
having
me
I
wanted
to
jump
into
some
booster
HTTP
updates
for
the
for
those
who
are
on
the
call
we
release
booster
hdp,
probably
back
in
January,
where,
basically,
you
were
able
to
as
a
storage,
Fighter
retrieve
a
full
piece
to
any
clients
who
asked
for
it.
D
Basically,
we
also
added
a
number
of
additional
features
here,
where
you
can
basically
retrieve
a
range
of
a
piece.
So
if
the
client
has
maintained
an
index
of
their
own
offsets
here,
they
can
actually
go
directly
to
booster,
HTTP
and
retrieve
a
range
they
provide
the
offsets
themselves
and
you
can
get
whatever
range
you
want
in
that
particular
piece.
You
can
now
retrieve
a
full
car
file
as
well.
You
can
also
retrieve
by
block
which
is
useful
for
any
future
ipfs
interop,
that's
required.
D
You
can
also
retrieve
the
original
file
by
CID
via
padding,
which
has
been
added
recently
so
yeah
like
store
Charters,
actually
can
serve
data
through
ipfs
Gateway
web
interface
directly.
This
has
been
implemented
in
boost,
so
that's
pretty
neat.
We
actually
added
a
bunch
of
these
capabilities
recently,
so
makes
it
a
lot
easier
to
retrieve
data
with
booster
HTTP
and
makes
it
easier
from
the
client
side
as
well,
depending
on
what
use
case.
D
They're
looking
for
I
do
want
to
call
out
if
you're
retrieving
the
original
file
by
CID
storage
writers
should
be
careful
there.
If
you
enable,
if
you
enable
it
basically
yeah
depending
on
you,
know,
web
services,
your
domain
could
be
blocked
if
it's
a
suspected
that
you
have
questionable
content
being
served,
but
don't
worry,
this
is
not
enabled
by
default.
Depending
on
your
client.
Maybe
you
know
you're
retrieving
for
like
private
clients,
you
can
always
turn
this
on
and
it's
disabled
by
default.
D
D
Oh
I
actually
have
one
more
slide,
but
no
worries
I'll
just
talk
through
it
really
quickly.
So
I
did
want
to
chat
really
quickly
before
Carol
jumps
into
retrievability
guidelines
on
why
we
included
httpny
were
kind
of
yeah.
Why
we
included
it
even
so:
we've
gotten
feedback
from
Storage
routers
that
HTTP
is
generally
like
easier
to
use
and
I.
Think
from
our
perspective,
you
know:
HTTP
has
been
around
the
block.
D
It's
been
used
for
many
years
and
there's
lots
of
tooling
available
out
there
and
there's
folks
that
have
lots
of
familiarity
with
HTTP.
So
there's
like
yeah,
obviously
like
browsers,
curl,
there's
nginx
tooling,
to
basically
limit
traffic
and
accessibility
and
there's
various
like
apis.
That
folks
can
use
that
works
well
with
HTTP,
so
yeah,
that's
pretty
much
it
from
my
side,
pass
it
on
to
Caro
thanks.
Everyone
thank.
C
You
Brenda
for
the
special
parents,
really
appreciate
it.
I
know
it's
early
for
you.
I
asked
you
to
come
on
board,
so
I
can
dive
into
my
topics
in
a
more
natural
flow,
so
Kevin.
If
we
can
go
to
the
next
slide,
I
want
to
have
a
discussion
on
receivability
guidelines.
So
retrievability
has
been
a
topic
of
top
of
mind
for
a
little
bit
recently
and
it's
right
in
line
with
our
quality
face
that
we're
pushing
this
year.
C
I
want
to
have
a
discussion
with
this
group
on
a
receivability
because
it
is
going
to
help
with
the
quality
that
we
on
board
of
data
that
we
onboard
by
having
more
accountability
on
the
the
players
in
in
our
community
right
so
have
a
receivability.
Can
you
know
for
from
the
P
outside
I
work
on
the
data
programs
team
and
come
from?
You
know
a
point
of
view
that
I
want
to
help
all
of
you
and
all
of
us
to
have
a
brighter
brighter
future
by
not
sacrificing
anything.
C
You
know
in
in
the
short
term,
medium
term.
Having
this,
you
know,
trade-off
I
know.
Market
has
been
hard.
You
know.
Storage
providers
have
been
having
a
hard
time
so
I'm
not
trying
to
like
force
anything
upon
all
of
us.
This
is
why
I
want
to
come
to
you
and
have
this
open
discussion.
So,
from
my
point
of
view,
I
want
to
provide
a
clear
track
record
of
the
client's
password
data
data
set
retrievability.
This
is
going
to
help
their
notaries.
C
C
You
know
and
reduce
friction
that
has
been
there.
You
know
caused
by
disagreement
about
among
notaries
how
they're
doing
different.
You
know
due
diligence
processes
we're
here
to
help.
So
that
is
my
goal
here.
Kevin.
If
we
go
to
the
next
slide,
Brenda
also
talked
over
this
a
little
bit
as
well.
Why
did
we
choose
HTTP
over
other
receiver
methods?
C
So,
from
the
technical
point
of
view,
graph
sync
relies
on
the
payload
CID
graph
sync:
what's
you
know
the
native
ratio
method
of
of
filecoin,
but
because
it
relies
on
payload
CID?
And
you
know
the
filecoin
deals,
don't
record
the
payload
CID.
We
only
have
the
pcid
and
bit
swap
also,
you
know,
requires
the
payload
CID.
C
This
is
why
we
come
from
an
angle
that
we
want
to
make
it
easier
for
all
of
us
what's
the
fastest
way
or
like
the
easiest
path,
to
enable
to
enable
retrievals
that
will
have
you
know
the
lowest
cost
to
to
to
make
it
happen.
You
know
from
our
point
of
view,
so
HTTP
is
the
better
Choice
right
now
that
we
see
that
this
is
why
we
feel
like
and
also
as
Brenda
said,
we
can
benefit
from
a
wide
array
of
Open,
Source
tooling.
C
C
This
is
also
a
spec
that
we
are
Will
from
the
Brett
Rock
team
has
pushed
out
that
we
can
use
to
I
just
want
to
call
attention
to
this
PR
that
defines
the
semantics
for
piece
retrieval
that,
as
storage
providers
can
use
to
serve
retrievals
on
on
the
peace
level
and
I
want
to
die,
I
want
to
spend
the
most
time
on
the
next
slide.
Kevin.
C
Yes,
so
I
have
taken
some
time
and
drafted
a
retrieval
guideline
from
kind
of
from
the
client's
perspective.
I
want
kind
of
from
the
client
side
to
kind
of
push
for
accountability.
Retrievals,
so
I
want
to
spend
some
time
going
through
each
items.
There
are
two
slides
here,
so
the
first
one
is
data.
Clients
participating
the
bill
plus
program
commit
to
ensuring
the
retrievability
of
open
data
sets
through
HTTP
from
their
SPS
and
the
second
one
is
data.
C
Clients
are
advised
to
meticulously
choose
storage
finders
that
align
with
their
specific
data
retrieval
requirements.
So
you
know
the
data.
Clients
are
in
charge
of
choosing
the
SPs
that
best
suit
their
needs
and
also
clients
enhance
their
reputation
by
holding
their
storage
provided
providers
accountable.
This
is
where
the
notary
due
diligence
piece
comes
in.
You
know
notaries.
C
Then
this
is
the
fourth
one
consider
the
client's
track
record
in
retrievability
as
part
of
their
due
diligence,
so
that
we
can
allow
you
know
better
transparency
into
how
this
client
is
doing
and
what
their
needs
are
right
are
they?
Is
this
an
organic
demand
for
storing
data,
or
is
there
some
kind
of
abusive
Behavior
number?
Five?
Multiple
storage
providers
can
share
a
single
ship
on
sale
copy,
so
this
we're
coming
from
a
perspective
to
save
cost
for
USPS.
C
I
know
that
we
are
all
going
through
a
hard
time
and
we
are
not
saying
that
every
SP
must
maintain
an
unsealed
copy
and
maintain
a
HTTP
endpoint.
You
know
if
we
have
multiple,
replicas
and
and
all
those
SPS
work
together
to
share
one
on
sale
copy
and
all
the
retrieval
requests
will
get
routed
to
this
copy,
and
that
is
fine
as
long
as
the
data
is
retrievable,
that
is,
that
is
fine.
That
means
we
are
storing
data
as
as
intended.
C
C
Next
slide,
okay,
so
this
slide
I
want
to
also
call
out
some
precautions
or
risk
management
that
we
could
use
as
storage
providers
and
as
the
coming
Community
Players
data
clients
and
storage
providers
should
be
working
together
to
see
if
you
know
there
any
Network
overloader
attacks,
so
you
can
use
some
great
limiting
tools
to
set
the
maximum
number
of
requests
per.
Second,
you
can
also
limit
the
maximum
bandwidth
right.
A
single
retrieving
client
can
consume
and
you
can
also
work
on
load
balancing.
C
C
I
don't
want
us
to
like
suddenly
do
everything
overnight.
That
will
shock
the
system
right,
but
I
want
to
lead
a
discussion
so
that
we
all
arrive
on
the
long-term
goal
of.
In
of
enabling
retrievability-
and
that
is
what
you
know-
will
help
us
and
will
help
the
PowerPoint
price
too,
if
we
all
have
better
data
quality
that
is
going
to
help
the
community
as
a
whole
in
the
long
term.
So
that's
where
I'm
coming
from
I
hope
you
all
understand.
C
I
know
it's
not
an
easy
ask,
and
it's
not
a
personal
asset.
I
think
we're
all
working
together
to
to
make
our
community
better
so
I'm
just
here
to
to
help
so
yeah.
If
there's
a
threat,
I
think
someone
dropped
a
link
in
the
chat
as
well
that
we
have
in
the
in
the
in
GitHub
and
yeah.
We
can
come
and
continue
the
conversation
here.
I
know
we
are
sure
around
time,
but
Galen
you
have
a
hand.
E
Yes,
we
are
running
out
of
time.
Sorry,
this
is
all
like
super
useful
information
and
I
think
really
important.
Where
is
there
going
to
be
like
a
best
single
place
where
a
lot
of
us
is
like
captured,
or
this
conversation
will
continue
like?
Is
it
going
to
be
in
that
FRC
like
PR,
or
is
there
another
place
where
people
could
like
go
kind
of
follow
along
on,
like
all
the
different
reasons
why
we
chose
HTTP,
how
they
could
start
testing
it?
Where's
the.
E
C
F
E
F
E
A
G
G
That's
not
always
the
true,
not
always
true,
because
because
sometimes
client
made
mistake,
they
just
put
random
string
or
just
put
the
PC
ID
into
the
label,
which
makes
it
not
retrievable
it.
Also.
We
also
have
we
actually
already
have
about
24
million
retrievals
performed,
that's
covering
most
of
the
active
deals
right
now
in
ficon
Plus.
G
So
we
have
probably
a
dashboard
for
you
to
actually
view
the
virtual
reality
results
as
well
at
the
house.
This
will
be
a
dashboard
for
the
house
of
the
toolbar.
Next
up
is,
and
this
is
per
this
is
the
overall
view
of
the
whole
retrieving
actual
ability
of
the
whole
network
we
can
see
there
are
like
top
20
Graphics
champions
for
graphing
for
HTTP
and
forbids
web,
and
we
know
that
another
SP
has
hdb
and
respond
with
neighbors.
G
We
only
see
a
few
in
HTTP
and
this
web
check
panel
and
exactly
is
as
I
move
on
to
promoting
HD
retrieval
as
the
standard
of
the
five
convertibility
I
want
to
talk
about
the
new
HPV
retrieval
sampling
and
want
to
get
feedback
from
the
community,
because
we
really
want
to
be
very
transparent
for
what
we
are
doing
in
Virtual
ability
for
what
each
specific
step
are.
First,
we
are
going
to
do.
Please
header
check.
G
We
know
that
the
protocol
of
ficon
does
not
limit
the
format
of
the
deal,
but
we
want
to
say
that
all
the
properties
that
must
be
used
in
car,
V1
or
V2
format.
Well,
if
you
are
Enterprise
customer,
you
might
just
use
any
encryptencing,
but
we're
asking
that
all
politics
must
be
using
car
format
and
since
we're
using
we're
having
HTTP
retrieval
it's
possible
to
enable
partial
retrieval
using
the
wrench
header,
we
are
going
to
take
a
randomly
select.
G
If
we
are
seeing
that
so
many
like,
if
there
is
a
32
gigabyte
of
deal
and
most
of
them
are
just
zero
bytes
and
we're
going
to
Market
somehow
like
the
developed
car,
has
been
underutilized,
we're
going
to
look
for
VAR
in
CID
block
Tuple,
because
the
because
the
car,
the
car,
the
deal
the
car
file
is
basically
a
list
of
CID
block.
Once
we
find
this
blog
we're
trying
to
validate
that,
it's
the
CID
is
valid.
G
According
to
information
Theory,
it
should
be
not
a
very
high
entropy
and
not
a
very
low
entropy,
indicating
that
it
has
some
real
value
if
there
are.
If
the
data
is
highly
repetitive,
for
them
to
be
at
all
one
zero
one
zero,
then
it
will
be
a
very
high
conversion
ratio
or
low
entropy.
If
the
data
is
random
or
compressed
or
encrypted,
that
means
it
is
having
a
very
low
compression
ratio
or
very
high
entry.
G
Both
are
not
ideal,
for
both
are
not
a
little
bit
fishy
for
if
the
data
is
actually
a
real
data
and
finally,
we're
also
going
to
try
hard
piece
retrieval.
This
is
basically
make
sure
that
when
we
are
trying
for
a
piece-
and
the
SP
is
not
lying
about
that
piece-
and
here
they
are
actually
serving
the
exact
piece.
According
to
the
pcid,
but
that
will
be
a
very
low
frequency,
basically
we're
going
to
be
download
the
whole
piece
and
make
sure
that
it
resolves
to
the
same
pcid
and
peace
size.
G
G
There's
an
option
in
boost
poster
HTTP
to
enable
file
retrieval
sampling
by
default.
It
allows
block
retrieval,
but
not
the
file
level
retrieval
on
the
rid
of
a
file.
Retrieval
is
because
I
actually
want
to
download
the
actual
file
and
then
another
examine
whether
they
are
actually
serving
the
actual
file
or
is
it
just
random
file
carrier
is
leading
a
separate
thread,
a
working
group
to
improve
transparency
or
data
set
by
incurring
the
clients
to
present
a
list
of
files
associated
with
this
data
set.
G
If
we
agree
on
that,
then
we
will
be
able
to
do
value
retrieval
by
downloading
the
file
and
hosting
on
some
kind
of
a
cheap
cloud
storage
or
just
five
constant
providers
for
another
to
check
the
actual
content
of
file.
Also,
with
a
with
a
much
higher
frequency,
we
can
also
try
to
retrieve
just
the
first
one
kilobytes
of
the
file
and
use
a
library
called
the
magic.
The
live
magic
will
actually
check
the
magic
number
from
the
file
and
indicate
the
type
of
file.
G
For
example,
it
is
the
image
file,
is
the
text
file
or
is
it
the
video
files
and
then
over
time,
we'll
actually
get
a
good
statistic
about
the
data
set
like?
Is
this
that
consists
of
like
80,
of
video
files
to
20
of
image
files,
or
is
it
is
config,
consists
of
like
a
hundred
percent
of
just
random
binary
files?
H
Gay
Ray
hi
everyone,
quick
update
from
me.
This
is
a
topic
we
discussed
on
the
past
few
governance
calls.
This
is
a
cross-functional
topic
related
to
kyc
checks,
know
your
customer
applicant
checks
that
are
coming
live
and
we're
actually
going
to
roll
this
out
with
e-fill
plus
first
so
likely
later
this
week,
it'll
go
live
and
efo
plus
applicants
will
be
prompted
to
complete
the
check
on
philplus.storage.
So
when
they
log
in
there'll
be
an
option
to
complete
a
kyc
check.
H
I'll
work
with
each
applicant
manually
right
now
to
do
that
and
make
sure
that
it's
done
and
once
they
do
it
you'll
be
able
to
see
on
the
application
a
new
label
which
will
be
called
kyc
validated
so
for
now,
you'll
see
the
the
efo
plus
applicants
that
have
completed
the
process.
You'll
see
the
label
there,
especially
for
notaries.
H
This
is
great
to
be
aware
of
so
something
for
you
to
look
out
for
on
the
application
and
then
for
all
other
applicants,
as
you
log
in
you'll
also
see
the
option
to
complete
the
kyc,
but
for
now
you
know
this
is
an
opt-in
process.
It's
not
required
for
applicants
outside
of
the
e-fill
private
15,
plus
data
set
categories.
H
A
Well,
so
it
is
always
Casey
looking
forward
to
that
all
right.
We
have
three
proposals.
We
are
looking
for
input.
These
are
meant
to
be
discussion
proposals.
So,
if
you're
on
the
call,
as
we
talk
about
these
very
keen
to
get
your
thoughts
and
discussions,
the
first
one
is
valuable.
Data.
Galen
can
I
hand
it
over
to
you
to
kind
of
spearhead
this
one
for
us.
E
E
E
E
I
I
If
things
are
stored
on
the
network,
which
might
be
not
yeah
not
presentable
under
the
current
legal
laws
of
a
country
or
whatever
it
is,
then
I
think
those
things
should
not
be
in
the
valuable
data
like
let's,
let's:
okay,
let's
call
it
by
name
like
child
pornography
or
something
yeah.
You
should
block
that
out.
Yeah.
It.
E
Has
always
been
part
of
the
definition
that
it?
It
must
be
local,
legal
and
Regulatory
guidelines,
so
I
think
that
we
have
all
always
agreed,
and
that
is
baked
in
to
the
definition
that
we
use,
that
it
meets
local
regulatory
guidelines.
And
so
that
is
one
place
where
we
do
draw
a
line
to
say
things
that
in
a
particular
geopolitical
region
are
deemed
illegal
in
that
region
on
the
network
should
not
qualify
for
data
cap.
E
Yeah
I
think
one
of
the
other
things
that
where
we
we
run
into
misalignment
with
the
community
is,
should
we
over
emphasize
defining
and
investigating
the
data,
or
should
we
look
at
sort
of
the
deal
making
Behavior
or
should
we
look
at
both
I?
Think
where
we've
consistently
tried
to
land
is,
it
will
be
very
hard
to
ever
fully
vet
all
of
the
data
that
is
being
onboarded
right.
E
Doing
any
kind
of
screening
bit
sampling
to
have
100
percent
guarantee
that
we
have
reviewed
all
of
the
data
that
that
a
client
or
data
owners
bringing
but
a
notary
would
have
the
ability
or
the
tooling
to
look
at
terabytes
petabytes
of
data
and
Sample
it.
But
also
we
can't
you
know
just
look
at
the
deal-making
behavior
and
say
if
it's,
if
we
only
focus
on
one
thing
like
tracking,
you
know
a
CID
and
seeing
if
it
goes
to
a
certain
place.
E
If
we
only
look
at
the
deal
behavior
that
that's
sufficient
I
think
that
it
needs
to
be
this
mix
of
both
that
we
should
try
and
care
about
the
valuable
data
who
is
bringing
it
to
us.
How
do
we
know
that
it
is
valuable?
How
do
we
know
that
it
meets
these
local
regulations
as
well,
as
are
they
participating
in
good,
distributed
decentralized
deal,
making
processes.
E
And
yes,
we
want
to
do
as
much
to
like
weed
out
the
things
that
we
can
all
agree
should
not
qualify
for
data
cap
to
the
best
of
our
ability
and
things
like
you
know,
illegal
data
or
data.
That
is,
you
know,
not
being
distributed
or
data
that
is
being
computer
generated,
and
you
know
flash
sealed
and
not
distributed
from
SPS.
We
want
to
like
that's
where
we're
trying
to
like
build
more
tooling
and
also
other
teams
are
building
tooling.
E
A
Well
said:
Galen,
thanks
for
stepping
in
and
same
with,
you
white
I'm,
going
to
appreciate
you
guys
vlogging
this,
the
next
one
came
through
from
the
community.
This
came
from
heresy
and
essentially,
what
we're
looking
at
with
this
issue
882
was
that
hey
we've
seen
some
issues
with
some
notaries
that
are
essentially
kind
of
going
through
these
applications,
but
we're
not
seeing
like
the
steps
followed
for
what
some
notaries
would
consider
like
proper
diligence,
proper
40
and
proper
flow.
So
what's
nice
about
this
application,
is
it
does
two
things?
J
Even
if
you
look
at
the
dispute
tracker,
a
lot
of
the
disputes
have
been
raised
against
notaries,
which
is,
is
a
really
specifically
designed
history
tracker
for
clients,
but
it
has.
You
know
we
learned
as
we
are
not
about
the
basically
plays
out
so
two
main
things
as
listed
out
here.
We
want
to
kind
of
pull
those
more
accountable.
J
Now
that
is,
you
know
that
is
to
SLA,
engagement
and
tracking,
which
is
in
the
works
that
is
through
kind
of
giving
better
guidelines
on
our
end,
as
well
as
making
rotary
is
part
of
the
conversation
as
to
as
proposing
new
produce
to
the
program,
and
so
with
this
particular
issue.
If
you
go
look
at
the
issue,
the
challenge
becomes
that
you
know
both
parties
and
when
I
say
both
parties.
J
J
So
yeah
I
think
that's
one
big
aspect
of
this,
but
that
is
not
to
say
about
you
know
in
the
short
term,
while
we're
building
those
tools,
we
won't
do
anything
so
right
now.
What
I
would
like
to
propose
is
if
the
community
members
here
feel
strongly
that
all
notaries
who
are
under
abuse
should
be
should
pause,
signing
that's
one
potential
proposal
that
we
can
go
through
I
personally,
don't
have
enough
confidence
to
create
the
purpose
of
myself.
J
But
if
you
are
a
Community
member
and
you
think
like
that
is
absolutely
necessary,
please
go
ahead
and
create
a
proposal,
and
we
can
discuss
that
in
the
next
TNT
working
group
call
as
well.
As
you
know,
one
of
the
part
of
the
part
of
the
part
of
an
aspect
of
being
a
notary
on
this
network
is,
you
know
there
is
always
diplomacy
and
you
know,
like
kind
of
like
you
know,
working
with
others
involved.
J
So
you
you
you,
you
need
to
go
ahead
and
like
get
other
people
Buy
in
into
this,
it's
not
kind
of
like
our
job
as
the
governance
team
to
get
people
to
buy
in
into
certain
issues.
That's
what
we've
worked
here
for
us.
If
you
can
show
us
data
and,
like
you
know,
convince
learn
more
notaries
and
get
the
issue
passed,
then
sure
you
know
in
like
two
weeks
time
all
notaries
who
are
on
the
dispute
tracker
will
be.
You
know,
pause
from
signing
anything
else
for
patients,
while
they're
under
dispute.
J
Now
the
other
aspect
is
improving.
The
discrete
tracker
itself
is.
This
was
raised
that
the
you
know
it's
very
easy
today
to
just
open
a
dispute
and
potentially
Gaslight
other
people,
so
we
are
working
towards
that.
One
of
the
ways
in
which
we
are
exploring
this
is
essentially
is
after
integration,
in
which
I
myself
would
have
the
ability
to
lack
certain
issues
that
will
eventually
automatically
become
they
have
issues,
and
then
we
can
try
to
track
the
discussion
there.
So
we
are
making
improvements
on
that
front.
J
Yeah
broadly
I.
Think
this
issue
is
a
really
good
example
of
some
of
the
tensions
that
currently
exist
between
the
different
notaries
and
how
we're
defining
you
know
like
valuable
data
like
good
behavior
in
the
network.
So
if
you
haven't
had
a
chance
to
look
at
issue
8,
it's
82,
please
go
ahead
and
take
a
look
and
for
everyone,
who's
actively
involved
in
this
issue.
J
A
Yeah
RG
thanks
again
for
that
point,
I
think
the
follow-up
to
this,
and
why
not
just
put
it
into
chat
is
like
what
are
we
doing
with
notaries
that
we
see
this
this
Behavior?
Do
we
allow
them
to
continue
signing
while
we
review
business
as
usual
or
if
notaries
are
put
on
hold
during
this
review
process?
I
know
that
this
is
a
topic
that
you're
working.
So
thank
you
for
that.
K
Yeah
thanks
Kerry
and
I'll
also
try
to
be
quick.
I
know
we're
kind
of
low
on
time,
but
hey
everyone,
I
know
this
proposal
was
introduced
in
a
past
notary
call,
but
we
finally
got
the
workforce
finished
and
we'll
be
closing
this
probe.
This
proposal
as
well,
to
give
a
quick
reminder
about
this
proposal.
I'll
do
an
applications
that
do
not
receive
any
comments
will
be
closed
automatically
after
14
days.
K
K
Also,
clients
will
receive
a
warning
message
after
10
days
explaining
how
the
client
will
have
an
additional
four
days
to
provide
a
status
update
regarding
their
process
and
the
allocation
process.
So,
for
example,
if
you
need
more
time
to
find
notaries
or
you're
trying
to
collect
all
the
information
when
you're
going
through
the
due
diligence
process,
you
can
just
kind
of
make
a
comment
and
just
provide
more
clarity
on
where
you
are
during
the
process
in
the
future.
K
A
Simon,
thank
you
for
that.
I
appreciate
that
update.
So
we
have
two
parts
left
on
the
call
I'm
just
going
to
kind
of
call
an
audible.
We
have
10
minutes
left.
We
have
a
walk
through
on
how
the
diligence
process
works
when
you're
in
the
registry,
making
sure
that
everybody
understands
this
start
to
finish,
but
I
want
to
make
sure
that
those
of
you
on
the
call
that
joined
and
took
your
time
to
be
here
live
have
a
voice
for
anything
that
you
wanted
to
flag
or
discuss
earlier
on.
A
This
call
so
I'm
going
to
kind
of
open
it
up
and
if
there's
time
at
the
end,
then
we'll
do
the
walk
through.
But
right
now
before
is
yours.
So
if
you're
on
the
call
any
issues
that
you'd
like
to
come
back
to
or
raise
for
the
team
or
community
all
right
well,
something
does
come
to
mind
or
you
want
to
come
back
pop
it
in
chat
we'll
come
over
to
it.
I
guess,
with
the
time
that
we
have
Phil
good
news,
love
to
hear
about
this
walkthrough
on
the
diltons
for
us
yeah.
L
So,
hey
guys
I
just
want
to
quickly
go
through
this
notary
due
diligence
proposal
we
finally
implemented
it
originally
The
Proposal
was
proposed
in
issue
850
and
after
implementation
we
made
some
changes
to
simplify,
simplify
the
whole
feature
on
a
technical
standpoint,
also
on
a
ux
standpoint.
So
it's
less
glitchy.
It's
also
easier
to
use
these
changes
and
instructions
of
how
to
use.
This
feature
is
on
issue
884
and
so
for
the
interest
of
time.
I
wanted
to
wait.
L
I
wanted
to
go
through
a
quick
how-to
of
how
to
use
this
node
reader
diligence
flow,
but
I
think
for
the
interest
of
time.
I'll
just
put
that
into
a
separate
due
diligence,
video
and
and
then
send
it
to
everyone
that
way,
it's
a
recording
and
you
guys
can
re-watch
it
for
now
all
the
instructions
on
how
to
use
this
feature,
as
well
as
the
changes
that
were
made
are
in
this
issue.
884
again,
like
many
features
with
fill
plus
tooling.
This
is
like
a
first
iteration.
It's
version
0.1.
L
Essentially,
what
this
feature
is
is
that
it
allows
notaries
to
action
on
items
on
on
LDN
applications
other
than
just
approve,
so
now
notaries
can
actually
say
no
on
LDN
applications
and
they
can
decline
LDN
applications.
They
can
also
ask
for
more
evidence
from
clients
when
they
do
that.
They'll
get
a
notification
whenever
the
client
replies
to
them
when
they
ask
for
more
evidence
and
so
yeah.
So
that's
the
gist
of
this
feature
way
more
details
are
in
that
issue.
L
L
L
L
The
full
bug
management
standards
are
are
highlighted
in
this
medium
post
here
in
this
slide.
If
you
want
to
report
any
bugs,
please
click
this
link
here.
It's
in
the
file
coin
front
end
verifier
repo.
Here
you
can,
it
will
give
you
a
bug
template
you
can
like
put
in
all
the
information
you
need.
That
would
be
helpful
for
us
to
fix
your
bug
as
fast
as
possible
and
yeah.
So
that's
pretty
much
it
if
you
have
any
questions
or
want
to
like
improve
this.
A
Oh
Phil
awesome
awesome,
updates,
I'm,
looking
forward
to
watching
that
diligence
workflow
that
you
put
together
and
the
ability
to
put
no's
on
the
applications.
I
know
this
came
up
in
the
last
topic.
So
just
to
answer
this
question
again,
if
one
notary
says
no,
does
that
deny
the
application
or
could
another
notary
thing
come
in,
get
more
information
and
approve
it.
L
L
The
purpose
of
this
was
one
it
signals
to
us
that
you
guys
have
been
engaging
in
these
applications,
even
though
you
haven't
approved
and
two
it
allows
you
to
just
tell
other
notaries
that,
like
hey,
this
application
has
been
declined
before
so,
ideally
notice
can
then
filter
through
all
these
applications,
all
the
ones
that
have
been
declined
before
and
yeah.
So
that's
about
it.
It's
just
it's
just
a
signaling
mechanism.
It's
just
yeah.
E
Yeah
jumping
in
on
this,
like
I,
think
this
goes
to
part
of
the
conversation
that
that,
like
wine
and
was
bringing
up
in
the
chat
around
you
know
if
they
ask
a
client
for
a
car
file
or
if
the
client
says
that
the
data
is
going
to
be
retrievable
and
then
it
is
not
what
happens?
What
do
we
do
like?
How
do
we
stop
them?
What
happens
if
the
other
notaries
like
continue
to
sign
it
and
so
I?
E
Think
having
more
of
these
like
standard
saved
replies
and
some
of
this
tooling,
there
are
a
number
of
reasons
that
a
notary
would
say:
I'm
not
going
to
sign
this,
and
it
doesn't
have
to
be
limited
to
something
like
you
know.
If
the
client
is
not
responding
or
following
the
rules
or
giving
me
like
the
files
they
need,
there
are
other
reasons
that
a
notary
might
choose
not
to
sign
an
application,
but
it
just
gives
more
information
to
the
other
notary
Community,
as
well
as
to
us.
E
The
governance
team
as
to
you
know,
are
these
applications
being
reviewed
at
all
I.
Think
there's
something
like
over
400
open
allocation
requests
right
now.
It's
a
lot
of
clients
that
want
data
cap
and
one
of
the
things
that
like
came
up
that,
like
Lucas,
brought
up
in
the
feedback
form
it's
like
speed
to
data
cap.
It's
like
balancing
speed
to
data
cap
with
abuse
and
mitigating
abuse
and
responding
to
it.
E
If
we
can
get
more
notaries
telling
us
and
adding
signal
to
why
they're
not
signing
something
or
buy
an
issue
shouldn't
get
data
cap,
you
can
close
those
bad
issues
faster.
We
can
see
which
notaries
are
signing
things
that
other
notaries
have
set
no
to
and
if
there's
a
pattern,
and
that
gives
us
more
evidence
for
when
we
need
to
potentially
flag
or
remove
a
notary
from
the
system.
So
all
these
things
are
like
helping
us
move
both
of
those
initiatives
forward.
E
Giving
a
client
their
first
allocation
and
letting
them
start
making
deals
and
see
what
happens
and
then
taking
some
of
that
qualitative
like
deal
making
Behavior
quantitative
deal,
making
behavior
and
then
saying:
okay,
did
they
do
what
they
said
they
were
going
to
do?
Should
we
give
them
more
data
cap
and
so
taking?
You
know,
taking
a
risk
analysis
approach.
If
we
just
blanket
approved
every
470
open
allocation
requests
right
now.
How
much
data
cap
would
that
be
in
the
scheme
of
the
entire
program?
How
much
data
cap
would
that
change?
E
I'm,
not
saying
we
should
do
that,
I'm
saying
that
we
are
still
like
a
drop
in
the
bucket
for
each
of
these
decisions
and
I
think
that
we
can
sometimes
get
a
little
over
indexed
on.
You
know
making
these
decisions
apply
to
like
all
of
the
program
versus
just
the
current
state
of
the
program.
So
keeping
that
in
mind
check
out
the
new
tooling
check
out
the
new
diligence
process.
E
A
Man,
I'm
gonna,
go
to
just
calm
down
a
little
bit
after
this
call,
so
much
good
stuff,
so
much
good
stuff
way
in
10
hours.
We're
doing
the
second
one,
just
big.
Thanks
to
all
you
guys
that
I
see
on
the
line
you're
watching
on
YouTube
thanks
for
tuning
in
all
the
best
see
you
guys
on.
The
next
call
cheers.
A
A
Second,
is
we
have
some
guests
from
protocol
lab
they're
going
to
be
walking
us
through
the
HTTP
update,
really
informative
session
in
the
morning,
so
we're
gonna
be
looking
to
recapture
that
this
morning,
with
you
again
and
then
at
the
end
of
the
call,
Phil
will
walk
us
through
the
diligence
portion
of
being
a
notary.
Some
steps
in
the
process-
things
you
might
not
know
with
the
registry
as
well
as
some
new
tooling,
to
make
it
a
lot
more
effective
for
you,
notaries
to
leave
your
input.
A
Second
part
of
the
call
is
the
working
groups
just
for
the
Enterprise
field,
plus
I'll
speak
to
that
and
kind
of
update
you
that
really
briefly
for
proposals.
There
are
three
on
the
radar
making
sure
that
you,
as
the
community
and
notaries,
have
a
chance
to
hear
about
these,
see
where
the
discussion
is
and
capture
any
feedback
that
you
have
and
at
the
end
of
the
call
any
discussions
in
the
morning
we
used
every
second
of
the
call.
I.
A
Don't
think
it's
going
to
take
us
that
long,
the
second
time
so
with
that,
let's
jump
right
into
it.
If
you're
coming
to
these
calls
welcome.
Thank
you.
The
next
one's
going
to
take
place
on
zero
six
June,
if
you
were
Keen
to
get
the
slide
deck
that
I'm
looking
at
right
now,
if
you
go
into
slack
in
the
field
plus
Channel
you'll,
see
a
comment
by
me.
That
is
where
the
deck
lives
and
you
can
always
grab
any
of
these
links.
A
If
you're
watching
on
YouTube
they're
below
in
the
comments
we
post
this
agenda
every
two
weeks.
So
if
there
was
a
topic
that
you'd
like
to
see
discussed,
feel
free
to
add
a
comment,
Hey
Kevin
I'd
like
to
talk
about
X,
I'll,
add
it
on
the
agenda
and
if
you
have
any
slides
or
talking
points
otherwise,
I'll
be
happy
to
help
you
get
those
all
set
up
so
again.
This
is
your
time,
our
time,
whatever's,
on
your
mind,
we
can
discuss,
lag
and
review.
A
Where
is
a
governance
team
here
to
help
you
with
any
issues
you
may
have?
If
you
don't
know
who
to
reach
out
to
or
you're
new
in
the
program
or
you're
stuck
feel
free
to
come
to
me
and
I
can
help
route
you
to
the
right
place
and
kind
of
take
you
wherever
we
need
to
as
far
as
we
go
all
right.
So
with
that,
let's
take
a
look
at
the
notary
issues
that
are
coming
up.
A
Those
of
you
on
the
call
we
are
going
to
be
using
the
air
table
for
the
SLA
tracker
this
week,
so
we
are
previously
using
the
leaderboard
we're
going
to
go
back
to
that.
One
of
the
reasons
why
we're
going
to
this
air
table
here
and
I
just
put
the
link
in
chat
for
you
guys
to
sign
in
it's
the
notaries
we
are
working
on
an
SLA.
A
You
know
review
audit
of
how
much
time
the
notaries
are
having
to
spend
in
the
program
which
notaries
are
really
active
and
need
more
support
and
seeing
what
we
can
do
to
help
them
as
well
as
which
notaries
might
not
have
already
gotten
started
or
might
be
blocked.
So
this
form,
when
you
scroll
through
it
you'll
see
that
it
allows
you
to
pick
your
self-reported
hours.
This
is
really
helpful.
A
So
if
you
say
hey
I've
been
doing
this
for
eight
or
ten
hours,
then
you
could
say
my
time's
going
to
reviewing
applications
or
commenting
on
slack
or
going
to
the
trusting
transparency
groups.
What
we're
looking
to
do
is
make
you
as
effective
as
possible
and
remove
blockers.
So,
ideally,
you
can
do
as
much
as
you
are
with
less
time.
So
this
is
really
helpful.
A
I'll
be
updating
everybody
with
the
status
on
that
as
we
go
forward.
So
again,
thanks
for
filling
that
out
notaries
that
will
directly
impact
anybody
on
the
call
who's,
not
a
notary,
if
you
sign
in
for
that,
we'll
take
it
into
account
during
the
next
election,
all
right,
so
the
community
service.
So
what
happened
was
two
weeks
ago
Lucas
from
protocol
Labs
put
together
this
survey
or
just
walk
through?
Essentially
how
well
do
some
of
the
systems
in
the
product
file
coin
plus
ecosystem?
A
How
well
are
they
understood
so,
with
this
survey
came
a
lot
of
feedback,
not
just
about
how
we
felt
about
the
program.
But
how
is
the
program
viewed
and
seen
so
Lucas
put
together
this
really
detailed
graphic,
and
let
me
see
if
I
can
give
you
some
of
the
highlights
that
he
talked
about
and
that
what
we've
seen
coming
through
as
a
community
first
off
regions
reporting,
so
you
can
see
that
mostly
North
America
and
greater
China
region,
Oceana
may
I
love
you
guys
to
pieces.
A
Three
percent
Asia
Europe
17,
equally
tied
most
of
the
feedback
came
from
community
members
and
notaries.
This
was
kind
of
surprising.
We
weren't
expecting
community
members
to
be
filling
this
out
and
the
same
level
that
we
saw
at
notaries
and
again
37
notaries,
I
appreciate
that
make
it
nice
to
come
in
there
I'm
going
to
pause
talking
about
this,
because
volcano
Dao
is
requesting
to
record
this
meeting
locally.
What
I'm
going
to
do
is
I'm
going
to
deny
that
Dao,
because
I'm
going
to
post
this
to
YouTube.
A
So
if
you
want
to
grab
this
I'll
put
it
on
YouTube
and
you
can
grab
it
there
for
the
community
profiles
here
at
the
top
you'll
see
that
we
focused
on
what
was
most
important
and
what
was
least
important,
and
we
got
your
feedback
according
to
you
in
the
community.
What's
most
important
is
that
the
benefits
of
Bill
plus
align
with
like
the
broader
ecosystem
of
file
noise,
we're
going
to
talk
a
lot
about
that
in
the
coming
calls
great
feedback.
What's
not
important
is
advertising
the
quality
phase
and
goal
updates
with
you.
A
So
we
took
this
as
like
great
I.
Hope!
That's
because
we've
been
doing
this
in
slack,
we've
been
doing
this
in
blog
posts,
but
we'll
probably
follow
up
some
more
to
make
sure
that
we're
hitting
the
main
points.
Understanding
of
Phil
plus.
This
was
really
Keen.
If
you've
been
looking
at
the
program,
it's
that
80
could
not
identify
all
the
correct
scenarios
for
how
data
cap
is
allocated.
80,
that's
a
huge
number.
A
So
what
that
means
on
our
part
is
that
there
is
an
education
push
that
we
could
do
to
make
the
program
better,
documented,
better
communicated
and
that's
why,
on
this
call,
we're
going
to
have
Brenda
talk
about
the
Boost
program,
we're
going
to
have
Phil
talk
about
how
registry
can
work
from
like
eight
filling
this
out
on
the
fill
plus
site
so
loud
and
clear.
We
appreciate
that
signal
coming
back
from
it
and
then
also
like
the
satisfaction
in
a
line.
A
If
you
look
at
this
57
percent,
mostly
aligned,
22
percent,
completely
aligned
and
then
22
percent,
not
aligned,
so
I
think
one
of
the
things
we're
looking
at
is
like
what
can
we
do
to
get
someone
from
Mostly
aligned
to
completely
aligned?
What
can
we
ask
of
the
completely
aligned
people
that
they
got
there
so
a
lot
of
really
fun
stuff
to
tease
out
on
this
again
again,
thank
you
to
the
37
notaries
that
build
this
out.
I
went
through
and
I
pulled
all
of
your
names
from
that
list.
A
I
added
it
to
your
SLA
points,
and
that
goes
a
long
way
as
like
what
we
total
on
the
leaderboard
and
again
we
action
off
this,
so
you
notaries,
it
took
the
time
you're
going
to
have
an
outsized
Voice
versus
someone
who
didn't
do
this
and
how
we're
responding
and
coming
back
so
again,
great
work.
Thank
you.
Second
part
of
the
survey-
and
the
last
part
is
where
are
some
highlights
that
we
could
just
call
out
for
you.
A
So
if
you
see
top
mind,
it's
like
what
is
the
benefits
of
doubts,
so
some
of
this
really
comes
down
to
look.
If
we
have
this
data
cap,
that's
pushed
out,
it's
got
to
be
Quality
quality
data
right,
so
we're
going
to
talk
a
lot
about
what
does
quality
data?
Look
like
it's
even
a
topic
of
one
of
the
proposals
tonight,
the
speed
you
know
if
it's
blocking
and
it
takes
two
weeks
for
an
application
and
then
two
weeks
for
a
comment,
then
two
weeks
for
an
application.
A
Two
weeks
for
a
comment:
that's
just
too
long,
it's
too
long!
So
how
can
we
speed
that
process
up
either
with
Automation
and
again?
That's
where
a
lot
of
our
focus
on
the
tooling
is
coming
in
and,
lastly,
is
the
abuse
we
heard
this.
We
saw
this.
We
see
it,
it's
that
when
we
have
these
situations
of
abuse.
What
specifically,
should
we
be
doing
about
handling
it?
What
process
does
it
follow?
How
how
Stern
is
it
so
these
three
big
aspects
that
we're
really
pulling
back
that
onion
and
focusing
on
work?
A
So
thank
you
again
for
filling
this
out.
It's
greatly
helpful.
So
with
that
I'm
going
to
take
a
talking,
break
and
I'm
going
to
hand
it
over
to
Brenda
from
protocol
labs
and
she's
joined
the
call
to
kind
of
introduce
this
HTTP
update
that
they're
working
on
and
kind
of
highlight
some
of
the
Boost
programs.
So
Brenda
I
appreciate
you
taking
two
times
in
one
day.
The
floor
is
yours,.
D
D
You
might
be
aware
that
we
have
had
the
capability
of
being
able
to
retrieve
a
full
piece,
including
planning
over
booster
HTTP
since
around
the
January
time
frame
and
in
the
past,
maybe
like
a
month
and
a
half
or
so
we've
added
a
number
of
additional
ways
that
you
can
also
retrieve
more
granular
pieces
of
data
over
HTTP.
So
I'll
just
go
over
a
couple
of
couple
of
them
now
and
feel
free
to
type
questions
in
the
chat
or
ask.
D
If
you
have
more
questions
so
person
being,
you
can
retrieve
a
range
of
a
piece.
So
if
the
client
basically
has
an
index
of
offsets
based
on
where
specific
files
are,
you
can
actually
go
and
retrieve
specific
ranges
in
a
piece
from
position.
Http.
You
can
also
retrieve
a
full
car
file,
which
is
helpful
for
retrieving
basically
unpatted
data
and
a
deal
you
can
also
retrieve
by
block.
So
this
is
really
useful
for
future
ipfs.
D
Interoperability
and
then
you
can
also
retrieve
the
original
file
by
a
CID,
and
this
also
includes
padding,
and
essentially
the
nice
thing
about.
The
original
file
is
that
you
can
basically
serve
the
data
through
an
ipfs
Gateway
like
interface.
This
is
really
nice
for
folks
that
maybe
you
have
clients
that
want
to
be
able
to
easily
retrieve
their
data
through
some
basically
like
through
the
through
internet,
something
that's
very
familiar
to
them.
D
One
call
out
here
that
we
mentioned
is
that
if
you
enable
this
mode,
basically
you
want
to
be
careful,
because
in
case
that
you
know
just
in
case
that
it's
suspected
that
you're
serving
questionable
content
as
a
storage
provider,
the
domain
could
potentially
be
blocked.
So
just
to
share
that
this
is
not
enabled
by
default.
The
last
option
is
not
enabled
by
default.
You
have
to
explicitly
go
and
kind
of
like
turn
it
on
yourself,
so
you
should
be
fine
here,
but
just
wanted
to
call
it
up
there
and
additionally
kind
of.
D
Why
did
we
invest
so
much
in
booster
HTTP
and
why
we're
kind
of
recommending
folks
use
this
one
being
a
lot
of
the
feedback
from
Storage
providers?
That
we've
heard
in
the
past
is
that
HTTP
is
something
that
they're
familiar
with,
and
they
basically
know
that
there's
like
existing
tooling,
they
can
use
that
has
been
tried
and
trusted
over.
D
M
You
totally
so
the
if
you
don't
mind
heading
to
the
next
slide.
There
you
go
so
we
kicked
off
a
discussion
topic
on
the
achievability
of
open
data
stored
through
Falcon
plus.
You
know,
there's
always
been
sort
of
like
an
unsaid
Norm
around
this,
but
there's
never
actually
been
a
policy
or
or
a
process.
M
You
know
setting
a
Baseline
and
actually
bringing
the
community
together
on
a
new
requirement
that
hasn't
really
been
since
Stone
in
the
past,
and
so
that's
why
you
know,
firstly,
big
shout
out
to
the
Boost
team
for
really
leveling
up
the
way
in
which
we
can
serve
retrievals
in
the
fileco
network.
That's
it's
been
a
challenge
for
a
long
time
and
it's
really
good
and
very
promising
to
see
the
updates
recently
from
the
team
and
then.
M
So
we're
looking
for
like
low
friction,
we're
looking
for
high
indications
of
true
positives
and
low
signal
to
noise
ratio,
we're
looking
for
something
that's
maintained
and
should
be
low
overhead
over
time
for
everybody
involved
and
then
obviously
we're
looking
for
something
that
can
be
independently
verified
and
so
HTTP
gives
us
a
clear
path
to
all
of
these
and
with
the
commitments
made
from
the
Boost
team,
as
well
as
like
work
that
will
be
coordinated
with
other
implementations.
This
is
a
very
good
way
for
us
to
go.
M
M
M
Okay,
I
think
one
of
the
things
that
we
talked
about
this
morning.
This
came
up
via
Galen
as
well.
We
need
to
figure
out
like
the
right
way
to
set
this
as
a
standard.
Of
course,
we
can
just
you
know,
State
this
as
a
flip
plus
Community
thing.
We
probably
also
want
to
look
at
looking
at
what
the
rest
of
the
network
is
doing
and
so
will
Scott
who
also
works
on
the
Endra
stream
at
protocol
Labs.
M
It
started
out
on
FRC
on
the
Beast
Gateway,
which
talks
about
semantics
for
how
you
identify
a
piece
and
retrieve
against
it
to
ensure
that
the
data
being
retrieved
is
what
you'd
expect,
and
so
this
is
for
those
of
you
more
interested
in
technical
details
and
how
we
could
pull
this
off
leveraging
the
latest
and
greatest
technology
in
the
system.
Please
take
a
look
at
this.
M
I
think
I'm
gonna
skip
this
one
for
knock
area,
because
I
think
this
goes
into
the
details
that
are
covered
in
the
discussion
topic
so
for
those
of
you
that
are
really
interested
in
checking
it
out.
Please
check
out
the
discussion
topic
or
take
a
look
at
the
recording
from
the
morning
where
Cairo
went
in
depth
with
each
of
these,
and
if
you
have
any
questions,
please
feel
free
to
reach
out.
Thank
you
so
much!
M
M
Shinana
you
around
I,
don't
see
him
deep,
okay,
cool!
Let
me
speak
to
this
is
a
slightly
different
Vector.
So
shinan
works
on
something
called
the
retrieval
bot
in
our
team
over
at
PL.
The
reason
we
brought
this
up
is
because
we
wanted
to
talk
to
like
how
we
could
actually
eventually
get
to
testing
these
retrievals.
M
Shinan
also
works
in
a
different
organization
and,
as
part
of
that
organization
is
applied
to
be
a
notary
and
so
he's
versed
in
the
needs
of
the
primary
stakeholders
of
the
philplus
program
as
well.
So
the
medieval
bot
is
a
piece
of
technology
that
just
attempts
making
retrieval
requests
for
all
data
transfer
protocols.
That
means
HTTP
graph
sync
and
bit
Swap
and
publishes
those
results
publicly.
It's
currently
been
running
for
about
four
weeks
during
which
we've
attempted
24
million
retrievals,
where
we
are
either
testing
directly
against
the
CID.
M
So
in
the
case
of
HTTP
we're
able
to
take
the
pcid,
but
in
the
case
of
graph
sync
and
bit
swap
we
needed
the
payload
CID.
A
lot
of
the
onboarding
tooling
sets
the
payload
Cid
in
the
label
field
for
a
deal.
So
we've
made
the
assumption
that
that
is
indeed
the
root
payroll
CID
and
we've
been
testing
retrievals
against
that
in
the
case
of
graph
sync
retrieval
the
bot
attempts
to
retrieve
the
root
Block
in
the
case
of
HTTP,
retrieval
it
just
retrieves
the
first
megabyte
in
the
case
of
bit
swap
retrieval.
M
It
also
retrieves
a
root
block
and
then
the
intent
is
effectively
to
publish
this
in
a
public
database.
The
reputation
working
group
has
an
as
an
Open
Access
mongodb
that
is
accessible
to
anybody
in
the
community
to
see
these
results.
They
are
not
currently
published
directly
to
LDN
applications
or
to
the
GitHub
applications
themselves,
but
we're
hoping
to
get
that
in
the
near
future,
and
then
we
want
to
then
segment
this
based
on
clients,
as
opposed
to
just
crawling
through
the
network
and
trying
to
figure
out
what
could
be
attempted
to
be
retrieved.
M
The
bot
will
need
to
have
logic
that
understands
the
concept
of
a
data
cap
application
and
a
test
retrieval
against
that
particular
application.
The
set
of
things
stored
by
that
particular
client,
the
issues
here
are
the
things
we
need
to
improve
against
are
number
one.
It's
difficult
to
assume
every
time
that
the
label
field
is
actually
a
CID
against
which
retrieval
can
be
tested.
M
M
What
was
the
success
rate
in
my
attempts
to
do
that?
Not
was
I
able
to
retrieve
something
and
was
it
what
I
expected
it
to
be,
which
is
a
second
question
that
I
think
we
will
start
and
need
to
ask,
especially
for
open
data,
because
it
should
be
retrievable
and
people
should
know
what
is
actually
being
stored
because
that
should
align
with
the
data
cap
application.
M
If
you
look
at
the
next
slide,
it's
a
screenshot
of
the
current
dashboard
that
sort
of
shows
you.
This
is
a
public
dashboard.
You
can
check
out
this
link
anytime,
but
I'll
show
you
the
operations
of
the
retrieval
bot,
so
you
can
take
a
look
at
what
we're
testing,
what
we're
testing
against
what
the
results
are.
Looking
like
so
far
across
graph
sync
bit
Swap
and
HTTP,
and
it's
tasking
automatically
at
the
moment,
and
so
we
need
to
change
the
tasking
logic
to
align
with
the
needs
of
the
field
plus
community.
M
M
It
will
also
Define
what
gets
published
as
a
result
of
this
automation,
because
that
is
how
opinions
will
be
shaped
over
time
on
client
applications
and
expectations
from
the
community
and
assumptions
being
made
about
those
that
are
upholding
the
principles
and
sort
of
complying
with
the
requirements
that
we
set.
So
really
big
topic
super
important
steps
being
made
here.
I
know
the
communities
made
a
lot
of
Headway
on
this
direction
and
it's
generally
really
interested
in
seeing
how
this
is
going
to
play
out,
and
so
this
is
your
chance
to
be
part
of
the
conversation.
M
M
I
think
the
main
takeaways
for
you
here
are
to
actually
understand
how
the
retrieval
is
happening
for
HTTP,
specifically
like.
If
you
make
the
assumption
that
you
know
the
pcid,
which
you
can
and
you
make
the
assumption
that
you're
going
to
test
against
HTTP,
which
we're
claiming
is
a
good
thing
to
do.
Then,
just
with
those
two
pieces
alone,
you
can
do
something
called
a
range
request
where
you
sample,
or
you
test
against
a
small
sample
of
the
entire
piece
and
just
look
at
that
small
sample.
M
As
you
know,
these
files
are
image
files
of
cats,
then
really
if
the
files
are
small
enough,
the
retrieval
testing
software
should
download
a
couple
of
full
files,
of
which
we
should
be
able
to
check
those
files
and
see
that
they're
CAD
files
or
pictures
of
cats,
and
so
that's
what
we'd
like
to
get
to
it's
going
to
take
several
steps
and
a
lot
of
time
to
get
there.
But
I
think
we're
serious
about
this.
M
A
Last
slide
deep
last
slide
and
I
could
listen
to
your
sweet,
buttery
voice
all
night
man.
Thank
you
for
stepping
in
on
that.
Thank
you
all
right,
hey
working
group
update.
We
just
have
one.
This
comes
to
you
all
from
the
Enterprise
field
plus
and
pretty
much.
The
update
on
this
one
is
at
the
kyc
process
is
Gonna
Roll
out
this
week.
A
So
Casey
was
on
the
call
this
morning
and
he's
talking
about
how
this
kyc
step
works,
and
we've
talked
about
this
on
some
of
the
past
calls,
but
essentially
those
of
you
that
are
seeing
these
large
15
petabyte
datas.
These
are
going
in
the
Enterprise
field,
plus
right
now.
You'll
now
see
that
label
that
kyc
verified
notaries
that
are
on
the
call
community
members
that
are
on
the
call
for
the
fill
plus
program.
A
What
we
are
doing
is
we're
looking
at
these
lessons
learned
that
Enterprise
fill
plus
is
able
to
implement
in
their
pilot
and
then
taking
the
best
features
from
those
Lessons,
Learned
and
rolling
it
out.
So
I
wouldn't
be
surprised
if
in
the
next
quarter
or
two
we're
able
to
adopt
and
Implement
very
similar
structure
on
the
kyz
process
for
notaries,
as
well
as
the
application.
So
look
for
great
things:
they
have
this
link
in
the
discussions
to
come.
Kyc
is
going,
live
for,
Enterprise
fill
Plus
all
right.
A
There
are
three
proposals
and
two
of
these
were
just
flagged
from
the
community.
They
wanted
to
give
a
chance
to
kind
of
discuss
these,
so
maybe
what
I'll
do
is
I'll
introduce
this
then
I'm
going
to
mute
the
mic,
and
hopefully
people
have
thoughts,
comments
or
input
on
it.
But
essentially,
what
this
is
saying
is:
how
do
we
look
at
valuable
data
Us
in
the
filecoin
ecosystem?
What
do
we
think
is
valuable
quote
unquote
with
the
data
that
we're
storing
you've
heard
the
moniker
Humanity's
most
important
data?
A
Well,
when
we
talk
about
that,
what
does
that
mean?
Do
we
put
rails
on
it?
Do
we
limit
it?
How
do
we
limit
it?
How
do
we
look
at
it,
so
this
was
filed
by
one
of
the
storage
providers
in
the
community
heresy
and
he's
on
the
call
tonight,
but
what
he
was
trying
to
say
is
like.
Can
we
Define
this
very
clearly?
A
He
posted
some
links.
If
you
haven't
seen
it
open,
Panda,
dot,
IO,
it's
where
you
can
see
these
public
data
sets,
so
should
the
data
sets
go
to
there,
should
it
go
somewhere
else.
I
know
that
we
on
the
governance
team
have
been
working
on
this
very
same
question.
So
this
is
an
open
question
for
you
on
the
call.
What
do
you
think
is
valuable
data,
any
thoughts
on
how
we
Define
this
and
discuss
it
as
a
community?
What
is
yours.
N
N
Oh
okay,
I
I,
just
accidentally
hit
the
all
new
button,
but
yeah
so
I
I
think
for
a
valuable
data.
It's
very
objective
to
everyone,
so
so
I
I
think
sometimes
it's
very
nice
that
we
have
the
guidelines
set
up,
but
most
of
time
we
should
involve
like
military
or
Community
to
Define.
What
is
the
valuable
data.
O
Hi,
this
is
Kenneth
and
I
think
all
datas
are
important,
but
how
what
defines
valuable
data?
It
will
be
data
that
have
proven
that
they
have
been
used
elsewhere
and
in
being
implemented
elsewhere.
It
could
be
an
Ami
model
or
ml
model,
and
they
they
can
prove
that
those
data
sets
are
the
one
that
contribute
to
the
project
and
have
viewed
available
results.
Yes,.
A
A
Well,
if
you
think
of
anything
else,
please
unmute
I
could
tell
you
that,
like
behind
the
scenes
how
we've
been
talking
about
this,
it's
you
don't
want
to
over
regulate.
So
if
you
say
valuable
data
has
to
be
X
number
of
terabytes
big
used
by
X
number
of
organization
to
do
X,
Y
and
Z
things,
and
now
what
you've
done
is
you've
constricted
yourself
into
having
a
really
clear,
unusable
definition.
A
So
this
is
the
chance
to
really
put
some
rails,
but
it
also
is
a
cautionary
Tale
on
how
we're
looking
at
this
data,
and
that's
why
notaries
are
so
important.
You
bring
a
unique
perspective
from
your
geographic
region
and
your
subject:
skill
sets
and
your
area
of
operations,
and
you
will
see
things
that
everyone
else
has
a
blind
spot
to
so
again.
Notaries
on
this
call.
Thank
you.
You
are
greatly
appreciated
for
being
here.
A
The
second
issue
that
we
had
flagged
this
was
another
Community
issue-
was
about
abusive
Behavior.
So,
rather
than
getting
into
like
the
issues,
the
people
that
it
was
directed
to
that
might
be
better
suited
for,
like
a
trust
and
transparency,
call,
maybe
the
best
way
to
kind
of
talk
about
this
issue.
While
there's
you
know,
37
of
us
on
this
call
right
now
is
what
are
some
of
the
responsibilities
that
we
share
as
notaries,
and
how
do
we
do
that
role
as
a
notary
effectively?
A
So
to
kind
of
paraphrase
this
issue,
there
was
some
diligence
that
may
or
may
not
have
taken
place.
There
were
some
steps
that
may
or
may
not
have
been
communicated,
and
so
how
do
those
notaries
communicate
that
effectively
going
forward
and
we're
going
to
get
into
this
on
the
call
Phil's
going
to
walk
us
through
some
steps
for
like
a
technical
training
for
these
notaries,
because
this
is
a
blind
spot.
You
know
we
saw
this
in
the
data
that
Lucas
collected,
and
we
see
this
in
an
issue.
A
It's
that
we
do
a
really
powerful,
like
technical
dive
for
notaries,
bringing
them
on
the
program.
We
do
these
calls,
but
we
don't
really
have
a
follow-up.
It's
like,
we
give
you
a
license.
We
give
you
a
forklip
and
then
we
just
get
out
of
your
way,
rather
than
checking
in
a
little
bit.
So
Phil
will
walk
us
through
some
of
these
steps,
but
I
was
curious
as
we
go
through
on
this
one.
Rg
I
know
from
a
trust
and
transparency.
You
spoke
to
this
in
the
morning.
A
Rg,
if
anything
comes
up,
just
feel
free
to
unmute
and
jump
back
in
I'll
paraphrase
from
you
until
you
do
essentially
with
trust
and
transparency
is
doing,
is
they're.
Looking
at
all
of
these
that
come
through,
these
have
been
put
in
the
dispute
resolution
tracker.
Oh
rgic,
unmute
I'm,
going
to
stop
talking.
P
Yeah
thanks
so
much
Carrie,
so
yeah,
essentially
I
think
there
are
two
main
things
that
we
want
to
flag.
The
first
one
is:
there's
been
a
lot
of
flags
raised
against
notary
Behavior.
So
one
of
the
things
that
we
did,
we
created
the
dispute
tracker
mostly
to
focus
on
client
abuse,
but
we've
seen
a
lot
of
notary
abuse
come
through,
and
so
one
of
the
things
that
we're
doing
right
now
is
measuring
node
free
SLA.
P
B
P
This
specific
issue
raises
a
lot
of
good
Flags
about
what
are
some
of
the
pressing
issues
in
the
community
right
now.
So,
if
you
haven't
had
a
chance,
if
you
haven't
had
a
chance
to
take
a
look
at
the
issue
yet,
please
take
a
look
and
provide
your
input,
because
it's
a
good
representation
of
why
it's
very
hard
for
us
to
take
an
objective
stance
on
defining
abuse.
P
A
All
right
we'll
follow
this
up
on
the
dispute
tracker
as
well
as
the
issue.
Thanks
for
that
RG
I
will
comment
on
this.
Simon
spoke
on
the
morning.
Call
about
this
proposal
and
just
to
catch
you
up.
This
is
818
and
what
it's
doing
is
it's
Auto,
closing
the
LDN
applications
after
14
days.
So
what
essentially
this
gitbot
will
do
is
it
will
go
through
and
it
will
give
a
warning
so,
after
10
days
of
zero
activity,
zero
issues
back
this
get
bot
will
comment
like
hey.
Do
you
want
to
keep
this
application
open?
A
It's
been
10
days
and
if
there's
no
activity
over
the
next
four
days,
then
it
will
auto
close
the
application
now.
What's
the
goal
of
this
is
right
now,
I
think
there's
three
or
four
hundred
applications
that
are
open.
You,
as
a
notary,
know
that
that
experience
in
the
registry
isn't
always
as
clean
and
easy
to
use
because
of
all
these
open
applications,
and
then
it
really
is
hard
for
you
to
kind
of
fork
your
time.
A
So
the
goal
of
this
is
to
give
you
time
back,
make
sure
that
you're
looking
at
applications
that
matter
so
again
if
an
application
gets
closed
and
someone
still
wants
that
data
cap,
they
just
reopen
it.
So
it's
not
like
it's
blocking
turning
it
off
it'll
just
reopen
this.
This
issue
will
go
through
so
you're
going
to
see
this
rolled
out
here.
818.
If
you
have
any
thoughts,
this
is
the
first
iteration
on
this
one,
so
we'll
probably
develop
this
bot
in
a
little
bit
iterate
it
to
get
it
just
right.
A
But
again,
the
goal
of
this
is
to
make
your
lives
as
notaries
easier,
so
you
can
really
go
in
there
and
start
signing
and
reviewing
and
diligence
on
applications
that
are
communicating
back
with
you
all
right
so
for
Community
issues,
Phil
I
see
you
on
the
call.
Thank
you
so
much.
We
ran
out
of
time
in
the
mornings
call,
but
now
we
have
lots
of
time
here
Phil
floor.
Is
yours
really
looking
forward
to
this
session
right.
L
Yeah,
hey
guys,
so
the
the
this
issue
is
was
proposed.
I
think,
a
month
ago
it
was
issue
850..
It
was
a
feature
to
be
implemented
in
the
philplus
registry
called
the
notary
due
diligence
flow.
Essentially,
the
gist
of
it
is
that
it
would
allow
notaries
to
act
on
certain
LDN
applications
other
than
just
approve
of
it.
You
can
start
asking
for
more
information
or
declining
it
with
a
template
comment,
so
we
finally
implemented
this
issue.
L
The
actual
implementation
of
it
and
how
to
use
it
I
think
the
reason
the
big
reason,
the
biggest
of
why
we
want
this
feature
is
two
things.
First,
we
hope
that
this
would
allow
your
life
to
be
easier
as
a
notary,
because
it
allows
you
to
signal
to
each
other
that
you're
declutting
or
are
asking
for
more
information
on
this
application.
L
Another
reason
why
is
because
it
allows
us
to
analyze
you
as
a
notary,
your
engagement
in
the
ecosystem.
So
if
you
don't
like
an
application
and
you
decline
it
that
shows
that
you've
engaged
with
the
application,
which
is
sort
of
like
a
it's
a
show
of
engagement
as
a
notary,
which
is
a
good
thing,
so
Carrie
next
slide.
L
So
now,
with
a
bit
of
time,
I'm
gonna
go
over
the
this
feature
and
how
to
actually
use
it
on
the
registry.
If
you
open
it
now,
there's
this
new
column
on
the
right
called
the
actions
column
that
allows
you
to
act
on
certain
applications.
If
you
click
on
one
of
the
pencils
you
get
into
next
slide,
okay,
there's
a
lot
of
slides,
so
bear
with
me
yeah.
L
Right,
so,
if
you
select
a
request
for
more
information,
you
can
write
a
reason
saying
what
why
why
you
want
more
information
or
or
what
information
you
want.
You
can
also
add
your
own
reasons
why,
over
here,
I
have
a
drop
down
of
many
different
reasons.
Why,
in
this
case,
I
say
I
want
to
request
more
information
because
you're
lacking
data
samples
and
then
I
click
Send
status
updated
successfully,
and
then
what
will
happen
is
next
slide.
L
So
a
comment
will
be
posted
by
the
bot
on
your
behalf
on
the
application
saying:
I
have
reviewed
but
I'm
not
ready
to
support.
There's
there's
insufficient
information
about
certain
things,
data
samples
in
this
case
and
then
what
will
happen
is
that
there
will
be
a
label
on
the
application
called
waiting
for
client
reply.
L
So
now,
if,
let's
say
like
the
the
client,
which
in
this
case
is
also
me,
if
the
client
replies
saying
like
here
are
my
new
data
samples,
sorry
I,
didn't
I
didn't
give
them
to
you
XYZ.
What
will
happen
is
this
will
add
a
notification
onto
the
registry
itself,
so
next
slide
so
right
now
it
will
stay
here
here.
There's
two
comments
that
this
this
client
posted.
L
You
said
you
were
waiting
for
the
reply
and
he
has
since
he
or
she
has
since
replied
with
a
comment
over
here
if
there's
a
plus
two
notification.
So
if
you
click
on
that
now,
what
happens
is
sorry
next
slide
in
the
menu
instead
of
just
the
actions,
you
can
also
see
you
can
actually
also
see
which
what
what
their
replies
are.
What
the
clients
replies
are
to
your
request
for
more
information.
L
L
Okay,
next
slide,
Carrie,
okay
and
then
there's
another
side
of
the
flow
which
is,
if
you
decline.
If
you
decline,
what
happens?
Is
you
can
post
a
reason
for
why
you
decline?
Oh
I,
say:
I
declined
this
and
I
say
that
this
is
for
false
information
that
that
was
provided.
Can
you
please
reapply
or
not
apply
it
yeah?
So
next
slide.
What
happens
when
you
do
this?
All
it
does.
Is
it
adds
one
notary
decline
label
here?
L
L
Just
because
what
node
has
a
client
doesn't
mean
that
another
notary
can
come
in
and
accept
your
application
or
still
read
your
application,
and
your
applications
process
is
just
completely
stopped
right.
Why
I
have
this?
Is
that
in
the
future,
notaries
can
use
this
to
kind
of
just
filter
through
applications,
and
you
can
actually
say:
hey,
let's
filter
by
things
that
other
nodies
have
declined
before
or
filtered
by
things
that
no
nobody
has
declined
before
right.
L
I
think
it's
super
useful.
It
also
increases
transparency
and
it
shows
like
that
you're
engaged
in
the
system
if
you
decline,
if
you
decline,
applications
and
yeah
I,
think
that
should
be
it
for
the
notary.
Due
diligence
flow
again,
the
for
the
notary
due
diligence
flow.
The
link
is
way
back
all
the
way
to
the
start.
Thank
you
so
much
Carrie
issue.
L
884
will
tell
you
a
whole
we'll
give
you
a
whole
rundown
on
how
how
to
how
to
do
this
with
the
same
screenshots
and
basically,
a
text
version
of
this
tutorial
that
I
just
gave
you
so,
if
you're
curious
about
how
it
works,
why
it
works.
Why
we
did
it
everything
is
in
this
issue
in
A4.
You
can
also
look
at
850
for
the
original
idea
on
to
the
next
topic,
very
quick,
which
is
book
standards.
L
So
over
the
last
few
weeks
months
we
have
been
rapidly
iterating
over
fill
plus
tooling,
because
of
this
inevitably
we've
run
to
bugs
in
the
past
gov
call
sessions.
Many
people
have
been
asking
hey.
Is
it?
Is
there
a
place
where
I
can
formally
post
this
these
bugs
that
I
have
there's
a
lot
of
bugs
I?
Don't
like
just
messaging
you
or,
and
then
sometimes
it
gets
lost
right.
L
So
what
we
did
is
we
created
a
poll
on
what
the
best
place
was
to
report
bugs
everyone
agreed
on
GitHub
and
to
to
be
honest,
we
agree
too,
because
GitHub,
we
already
use
that
a
lot
for
the
LDN
applications.
It
also
creates
structure
to
track
bugs.
So
we
think
it's
a
great
idea
that
we're
using
GitHub
so
now
to
bring
that
forward.
We
are
creating
bug
standards.
So,
if
you
look
at
this
medium
post
over
here,
it
has
all
the
bug
standards.
L
Basically,
what
how
how
you
should
report
and
also
how
we
will
handle
your
bug
once
it
is
reported
to
this
GitHub
repo,
the
link
to
the
GitHub
repo
is
right
here.
Please
report
any
bugs
counter
using
this
link
here.
It
is
also
linked
in
this
medium
article
here
that
you
can
check
out.
It
is
the
latest
medium
article
in
in
the
fill
plus
medium.
So
if
you
want
to
look
at
that
and
see
how
exactly
we'll
handle
your
bugs,
you
can
check
that
out
and
yeah.
L
L
Q
L
L
A
You
so
much
yeah
I
feel
awesome
notaries.
That
last
point
that
Phil
said
that's
awesome.
So
sometimes
we've
heard
this
feedback
from
notaries.
It's
like
hey
I'm,
doing
my
job
I'm
doing
my
diligence,
but
you
know
what
I
looked
at
this
application.
I
didn't
want
to
sign
it
so
I'm
kind
of
losing
out
on
credit.
What
Phil
is
saying
with
this
diligence?
Workflow
is
now
you
can
essentially
get
credit
for
not
granting
that
data
cap
and
that's
a
great
way
to
kind
of
say,
look
I've
reviewed,
10
applications.
A
I
gave
it
to
two,
and
these
eight
still
took
my
time,
but
still
where
I'm
focused.
So
thanks
for
using
this,
it's
a
great
way
to
show
your
participation
and
kind
of
wine
it
out.
Bill
thanks
for
taking
the
time
to
walk
through
I'm
sure
we'll
have
lots
of
questions,
as
we
start
to
just
say.
Kick
the
tires
on
this
one.
All.
A
I
have
a
community
discussion
that
I
wanted
a
flag
and
then
we'll
turn
it
over
anything.
You
want.
Hey
young
I,
see
you're
on
the
call.
Max
I
see
you're
on
the
call
good
news.
We've
got
that
Json
file
updated
with
your
new
GitHub
handles
I,
just
want
to
say
a
big
big.
Thank
you.
You
two
were
like
the
first
Trailblazers
to
ever
request
this.
So
man
did
that
require
a
lot
of
steps,
a
lot
of
checks,
a
lot
of
double
checks,
so
we've
got
you
all
set
up,
came
with
a
fancy
new
workflow.
A
If
anybody
else
wants
to
change
their
GitHub,
but
I
just
wanted
to
give
a
big
thank
you
to
Young
and
Max
for
their
patience.
You
guys
should
see
that
come
through
tomorrow
and
I'll
be
set
with
your
new
GitHub
handles
likes
again,
all
right
so
with
that
I
will
turn
it
over.
If
there's
anything
on
your
minds,
anything
you
want
to
discuss
flag
talk
about
floor
is
yours.