►
From YouTube: Filecoin Plus - March 28 Notary Governance Calls
Description
The six set of Notary Governance calls of 2023 March 28 to discuss the Filecoin Plus program.
Slides and Links: https://docs.google.com/presentation/d/1xehEvtVGXGfVYLPaGmvzjNXBqhtKlFNnpdpEUWT2i2A/edit#slide=id.g1184233f2bd_0_34
Agenda
Governance
Mission Statement
Road Map Updates
Notary - Pulse survey email
Proposals
Recently Closed
840: Bug Allocation
815: Proposal T&T Metawave
829: Proposal T&T Code of Conduct
845: Converter Bootcamp (Greaterheat)
850: Diligence Flow
851: Increasing Datacap requests
Working Group Updates
E-Fil+ Notary Assignment Pilot
E-Fil+ Group Assignment Discussion
T&T - 846: Staking Updates
T&T - 849: Dispute Resolutions
Tooling - Starboard Dashboards
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
ly
hellos
and
welcome
to
the
first
notary
governance
call
of
March
20.,
8th
2023
on
the
agenda.
For
this
call,
we
are
going
to
look
at
some
updates
for
the
notary
leaderboard.
We
are
going
to
have
an
update
on
the
pulse
survey
that
went
out
to
you,
notaries
in
the
private
Channel
and
galen's,
going
to
walk
us
through
a
road
map
and
Mission
updates
from
The
Proposal
side
of
the
house.
We're
going
to
highlight
three
of
the
recently
closed
proposals
make
sure
that
that
was
tracking
for
everybody.
A
We
have
greater
heat
that
submitted
a
proposal
along
with
protocol
Labs
we'll
highlight
that
and
answer
any
questions
you
have.
We
have
updates
around
the
diligence
flow
as
well
as
increasing
the
limits
on
size
requests
we'll
get
into
those
in
more
detail.
We
also
have
KZ
and
RG
on
the
line
that
will
be
giving
updates
from
their
respective
working
groups.
A
Kz
will
be
talking
to
the
pilot
program
that
they're
implementing
over
Enterprise
field,
plus
and
RG
will
be
walking
us
through
the
dispute
trackers,
as
well
as
the
resolution
template
that
they've
been
developing
on
this
call,
as
always,
we'll
have
plenty
of
time
at
the
end.
So
if
there
was
a
topic
that
you
weren't
able
to
add,
we
will
be
able
to
get
to
that
at
the
end
of
the
call,
like
always
we'll,
be
able
to
address
it.
So
with
that
this
is
the
governance
call.
These
take
place
every
other
week.
A
If
this
is
your
first
time,
dialing
in
the
next
call
will
be
on
April
11th
calls
take
place
two
times
throughout
the
day:
zero,
eight
hundred
and
eighteen
hundred,
that's
fifteen
and
zero
one
UTC,
and
if
you
follow
this
link,
you
can
add
this
to
your
calendars.
We
put
this
slide
deck
in
the
fill
plus
channel.
So
if
you
check
slack
right
now,
you'll
see
this
agenda
for
me,
as
well
as
in
the
comments
will
be
this
slide
deck
if
you'd
like
to
follow
along.
A
If
you
want
to
add
a
point
to
this
agenda,
feel
free
just
to
make
it
an
issue
in
the
GitHub.
These
get
posted
two
weeks
in
advance,
and
this
will
include
anything
that
might
be
on
your
mind
that
you
want
to
see
on
these
calls
for
those
of
you
that
are
notaries.
We
have
a
new
way
for
you
to
sign
in
the
leaderboard
is
now
live.
The
link
is
here
and
I'm
going
to
drop
it
here
in
chat
momentarily
and
with
this
we're
going
to
create
a
meeting
Link
at
the
start
of
every
call.
A
So
let
me
show
you
what
this
looks
like.
So
essentially
this
is
the
leaderboard
that
was
developed
by
Phil,
and
you
can
see
each
time
that
there
is
a
call,
there's
a
call
attended
session.
So
what
I'll
do
is
before
every
notary
governance
call.
I
will
create
a
new
meeting
that
will
have
a
specific
code,
and
if
you
take
this
code,
you
can
then.
B
A
It
into
your
leaderboard
in
order
to
get
the
participation
for
it.
So
since
I've
already
managed
this
meeting
I'm
just
going
to
grab
this
specific
code
for
everyone
on
the
line
right
now
and
I'm
going
to
drop
it
in
chat
right
here
and
just
in
case
you
don't
have
the
link
to
get
onto
the
leaderboard.
If
this
is
your
first
time,
I'll
put
that
right
there
in
the
chat
as
well,
so
any
notaries
on
the
call.
A
If
you
follow
that
link
and
input
that
this
will
automatically
put
this
under
your
calls,
attended
so
big
props
and
shout
out
to
Cataline
props
to
you
Phil
for
setting
this
up
and
making
this
so
much
more
easy.
If
you're
on
the
call-
and
you
are
not
a
notary
or
a
storage
provider-
you're
a
community
participant
you're
anybody
who's,
not
a
notary,
we
are
going
to
continue
using
this
airtable
form
for
you
and
the
time
being.
A
So
I
can
see
on
the
line
right
there,
but
this
will
be
the
way
that
we
sign
in
going
forward,
and
this
will
make
it
all
automatic
in
a
really
easier
way
for
all
of
us
to
to
get
our
names
down
and
really
put
that
process
in
so
I'll
pause
and
see.
If
anybody
has
any
questions
before
we
go
on
as
far
as
like
signing
up
and
going
on
this.
C
A
C
A
A
Sweet
so
moving
right
along
friendly
reminder
on
who
your
governance
team
is
so
my
name
is
Kevin.
You
can
come
to
me
with
any
kind
of
support
or
notary
issues.
Kz
leads
our
Enterprise
working
group
for
Phil
plus
and
all
the
large
data
sets.
Rg
leads
to
trust
and
transparency.
Working
group
bill
has
been
working
on
notary
tooling,
like
the
leaderboard
we
just
saw.
Simon
has
been
working
on
client
onboarding
and
he's
going
to
give
a
couple
of
updates
on
his
projects.
A
E
E
So
we
may
need
to
look
at
Zoom
settings,
but
also
people
may
need
to
update
their
Zoom
software
because
you
shouldn't
be
able
to
do
things
like
add
reactions
and
emojis
and
threads
in
Zoom
chat,
and
it's
like
a
relatively
recent
past
few
months
update,
so
your
Zoom
client
might
be
out
of
date,
but
yeah.
We
will
look
at
the
zoom
setting
on
the
website
as
well
for
copying
chats
so
that
people
can
copy
the
the
meeting
code.
E
But
that's
that,
thanks
for
ironing
out
those
Kinks
Shifty
gears
mission
statement,
we
have
been
working
on
this.
We've
had
a
number
of
meetings,
meetings
with
various
stakeholders
and
kind
of
workshopping
like
finalizing
a
a
version
to
to
publicly
align
and
Orient,
we'll
be
posting,
some
additional
blog
posts
that
add
some
more
kind
of
copy.
E
Some
more
context
for
like
how
we
landed
here,
unpacking
it
a
little
bit
we're
sort
of
in
the
work
of
of
pulling
together
a
number
of
different
resources
right
now,
and
we
we
want
to
have
this
as
a
more
cohesive
thing
so,
rather
than
just
releasing
them
piece
by
piece.
So
here's
the
mission
statement,
The
Fill
plus
program,
supports
use
cases
for
data
onboarding
and
utilization
of
filecoin's
decentralized
storage,
Network
through
Community
governed
trust
mechanisms.
It
should
be
like
non-controversial.
E
This
is
the
same.
You
know
functionally
the
same
stuff
that
we
have
been
doing
and
supporting
for
a
long
time.
A
lot
of
people
have
kind
of
taken,
a
mission
statement
that
deep
and
I
put
on
some
slides
or
a
statement
that
deep
and
I
put
on
some
slides
like
two
years
ago
and
used
that
canonically
as
the
mission
statement.
Even
though
it
was
not
really-
and
it
was
functionally
the
same
thing-
it
was
you
know,
data
onboarding
with
social
trust.
E
You
know
social
trust
layer
so,
like
I,
said,
stay
tuned
for
a
blog
post,
we'll
be
announcing
it
in
various
slack
channels
and
and
blasted
it
out.
That
has
a
little
bit
more
context
around
this
mission
statement,
but
use
cases
for
data
onboarding
and
utilization
Community
governed
trust.
That's
what
we're
about
up
next
next
slide.
I
think
is
also
me.
E
Yeah.
We
got
a
road
map.
We
had
a.
We
had
a
public
version,
we're
restructuring
it.
It
was
kind
of
oriented
around
some
buckets
of
work
around
like
documentation
or
strategic
change.
Proposals
were
sort
of
in
the
process
like
deep
and
I
at
the
rest
of
the
governance
team
re-arranging
this
into
these
sort
of
six
themes.
These
like
six
work
areas.
So
with
the
mission
saved
that
we
previously
talked
about,
we
really
want
to
highlight
these
six
work
areas.
E
This
is
this
is
kind
of
going
to
be
our
prioritization
of
focus,
and
then
the
roadmap
will
be
bucketed
around
these
six
within
the
specific
kind
of
strategic
projects
that
we
will
be
doing
to
work
towards
them,
and
some
timelines
and
Milestones
across
the
next
couple
weeks.
So
again,
when
we
post
that
blog
post
it'll
have
a
link
to
that
roadmap,
so
stay
tuned
for
that,
but
so
just
go
over
them
now
also
should
not
be
surprised
or
controversial.
E
These
are
things
that
we've
we
have
always
cared
about,
we're
just
kind
of
codifying
them
and
writing
them
out.
The
program
enables
Falcon's
master
plan
to
onboard
massive
amounts
of
data
to
the
network.
This
is
this.
Comes
from
the
top
level.
I
mean
that
the
go
check
out
the
file
coin
master
plan
with
some
Talks
by
Mr
Juan
Benet,
and
he
will
touch
on
this
and
explain
like
how
it
is
you
know
the
functional
importance
of
the
filecoin
network.
E
Number
two
is
one
that
people
have
been.
You
know
really
calling
out
and
and
interested
in
and
invested
in,
and
we
think
that
it
is
significantly
important
data
cap
abuse
and
the
system
is
minimized.
We
have
been
working
on
that
for
the
entire
time.
We
continue
to
work
on
that.
We
have
like
I,
said:
we'll
have
some
strategic
initiatives
that
focus
on
this
explicitly.
E
Some
people
have
different
opinions
about
where
we
are
where
we
might
be.
That's
great.
We
welcome
those
like
dissenteen
opinions.
Everybody
is
is
going
to
have
a
different
viewpoint
on
like
what
is
qualified
as
abuse
and
how
much
is
in
the
system
we'll
be
releasing
some
statistics
that
explain
what
our
stand.
Summit
is
based
on,
how
we
are
defining
data
cap
abuse
and
then
producing
some
more
metrics
and
some
changes
to
try
and
address
that
to
make
it
even
less.
E
We
want
to
minimize
the
abuse,
because
that
will
maximize
sort
of
the
value
of
the
program,
the
value
of
the
data
cap
subsidy,
the
value
of
all
the
work
that
we're
doing
number
three
notaries
perform
robust
diligence
commensurate
with
the
data
cap
granted
not
controversial.
If
you
were
granting
a
lot
of
data
cap,
you
are
probably
needing
to
do
a
lot
more
diligence
and
look
at
some
of
our
tools
like
the
auto
verifier.
E
E
That's
really
what
that
one's
about
number
four
disputes
and
allegations
reviews
are
investigated
with
an
emphasis
on
restorative
justice.
This
is
something
we
care
about.
People
make
mistakes,
people
in
this
program,
people
in
this
community
ourselves.
We
miss
things.
We
design
something
to
function,
one
way
and
something
goes
off
the
rails.
You
know
if
somebody
misses
something
everybody's
busy.
A
lot
of
like
our
notaries
are
people
that
are
that
are
volunteering
their
time
to
do
this
work
disputes,
happen,
mistakes,
happen,
people
say
things
in
a
heated
moment.
People
are
highly
invested
in
this.
E
We
get
it.
We
also
want
to
investigate
those
and
resolve
them,
but
we
want
to
do
it
with
an
area
of
trying
to
keep
this
a
productive,
healthy
and
welcoming
Community,
where
people
have
coached
back
into
you
know
best
behavior,
five
legitimate
client
use
cases
have
scoped
Pathways
for
obtaining
data
cap.
This
is
something
we've
worked
really
hard
on
doing
is
how
do
we
set
up
a
scoped
pathway
for
all
the
different
types
of
clients?
E
You
know
this
is
work
that
you've
heard
Casey
talk
about
a
lot
of
like
how
do
we
support
different
levels
of
Enterprise
and
not
all
Enterprise
is
going
to
need
the
same
thing
and
Enterprise
is
not
going
to
need
the
same
thing
that
a
very
large
non-profit
public
data
set
needs
right.
So
how
do
we
have
Pathways
that
are
really
designed
for
that
particular
client
to
serve
their
best
needs
and
keep
that
process
standardized?
So
the
client
experience
is
really
Pleasant,
while
also
providing
the
level
of
diligence
that
we
want.
E
And
lastly,
our
governance
model
encourages
rapid,
iteration
and
process
Improvement
for
diverse
stakeholders.
Believe
it
or
not,
you
know
the
28
people
on
this
call
don't
necessarily
have
the
same
interests
or
Investments
or
opinions.
They
may
want
the
program
to
look
a
different
way.
I,
don't
always
agree
with
k-ray
I,
know
shock
and
awe,
but
be
that
as
it
may
like,
we
are
still
stakeholders
invested
in
this
and
we
have
to
come
together
and
collaborate
and
try
things.
We
want
to
try
things
rapidly.
We
want
to
iterate
on
them.
E
We
want
to
learn
from
them.
We
want
to
move
forward
and,
just
like
I've
said,
I
think
that
we're
doing
a
pretty
good
job
we've
pushed
a
lot
of
proposals
out.
We
push
a
lot
of
proposals
really
quickly.
It's
on
certain
things.
We
very
intentionally
need
to
go
slower
and
certain
things
just
take
longer.
You
know
designing
and
shipping
some
of
these
Tech
implementations
that
require
a
lot
of
interlap
behind
the
scenes
it
takes
a
while
to
get
those
different
Dev
teams
polluted
in
the
same
direction.
E
When
there's
a
network
upgrade
and
we've
gotta,
you
know,
invest
a
lot
of
tooling
Time
coming
back
and
making
sure
that
things
haven't
busted
from
Network
upgrades.
So
we
move
I,
think
we
move
pretty
rapidly.
I
think
that
we
we
bias
towards
action.
I,
think
that
we
bias
towards
proof
of
concept
and
testing
and
I
think
that
we
can
demonstrate
that
again
with
some
metrics
and
continue
to
make
it
better.
I
think
that
there
are
ways
that
we
have
to
improve
on
that.
E
So
those
are
the
six
main
work
areas
that
we
are
really
focusing
on
and,
like
I
said,
we'll
be
releasing
a
public
roadmap
where
you
can
kind
of
dig
into
some
of
these
we'll
be
releasing
some
new
metrics
where
we
will
hold
ourselves
accountable
and
we
want
you
guys
to
help
hold
us
accountable,
so
so
stay
tuned,
very
exciting
and
then
I
think
I
have
the
next
slide
as
well.
Y'all
gonna
be
sick
of
me,
notary
pulse
email,
there
believe
it
or
not.
E
There
have
been
some
some
spicy
conversations
at
the
community
recently
are
around
a
couple:
different
fips
fifth
discussions
and
around
this
program
that
was
brought
about
by
503.
So
again,
if
you
want
to
think
about
like
where
we,
as
a
fileco
network,
have
come
from
Falcon
plus
go
back
and
read,
503
or
don't
and
then
and
then
stay
tuned
and
look
at
56
and
these
various
things.
So
we,
the
governance
team,
want
to
sort
of
get
a
a
pulse
check.
This
is
not
a
vote.
This
is
not
a
poll.
E
This
is
more
like
an
opinion.
Gathering
survey,
where
we
want
to
come
up
with
a
consistent
and
low-lift
way
where
we
can
get
feedback
on
a
couple.
Different
topics
and
we're
gonna
try
this
mechanism
of
using
a
scale
of
zero
to
five
five
being
I
fully
support
this
like
if
this
goes
through.
I
think
this
is
the
best
idea
ever
I
like
I'm,
very
excited
about
this.
E
E
You
know,
I,
don't
really
have
a
better
idea
like
I'm,
neutral
and
I
I
will
I
will
work
to
support
it.
I'm
I'm
cautiously
optimistic
that
this
could
work
two,
a
moderately
unsupportive.
It's
the
community
thinks
this
is
the
direction
if
most
people
you
know
want
to
push
this
thing.
You
know
whatever
the
the
idea
or
the
topic
is
I.
I
have
some
concerns.
You
know
I'm
I'm,
cautiously
unsupportive
about
this
thing.
E
One
like
moderately
unsupported
I
do
I'm
I
I,
have
strong
reservations
about
this
idea
and
I
have
another
idea:
I
have
an
alternative.
I
have
a
justification.
I
have
something
I
I
want
to
add
to
this,
because
I
I
think
there
is
a
better
way
to
do
this
thing.
So
that
is
a
one
and
then
a
zero
is
like
I
am
I.
Would
you
know
I
will
do
what
I
can
to
like
try
and
block
this
and
prevent
this
I
think
this
is
like
a
bad
idea.
I
think
this
is
a
bad
situation.
E
E
So
that's
the
structure
that
we're
going
to
use
I
sent
that
email
out
based
on
email
addresses
that
we
had
for
notaries
in
one
of
our
databases,
I've
already
gotten
some
notifications
from
people
that
we
don't
that
you
didn't
receive
it
so
we'll
be
working
to
keep
cleaning
up
those
emails.
What
I
ask
is
that
you
use
the
use
the
slack
messages
between
k-ray
that
he
set
up
where
you
guys
have
your
code,
your
slack
and
email
code,
so
that
we
can
then
vet
and
make
sure
things
happen.
E
People
lose.
You
know
access
to
to
comms
or
Tech.
We
just
want
to
make
sure
that
we
have
consistency
of
who
we
are
talking
to
and
communicating
with
we'll
get
that
email
address,
updated
and
the
vision
for
these
forms
is
that
it
would
be
one
per
notary
organization.
So
I
know
some
of
your
organizations.
You
have
multiple
people
working
as
notaries.
E
We
ask
that
you
elaborate
communicate,
get
together
and
come
to
a
cohesive
opinion
on
the
forms
and
submit
one
reply
and
we'll
be
tracking
to
one
reply
per
organization
and
those
links
will
be
unique
to
your
organization.
So
that's
that
if
you
didn't
get
a
form
this
time
and
you're,
you
know
very
concerned
that
your
opinion
won't
be
heard
on
this.
One.
We're
working
to
get
the
form
out.
I
know
that
the
FIP
is
still
in
56
is
still
in
last
call.
E
We
are
also
just
working
to
get
this
feedback
and
pass
it
up
to
the
various
decision
makers,
so
they
have
heard
from
the
notary
community.
So
that's
that
I
think
there's
some
conversation
in
oh
gosh.
There's
a
couple
conversations
in
the
chat.
We're
investigating
some
login
issues,
copying
SSA
bot
is
down
for
maintenance
and
it's
56.
So
my
knowledge
56,
is
not
a
poll.
E
What
they're
doing
is
they
are
sourcing
feedback
from
the
various
community
members
and
passing
that
to
different
stakeholder
decision
groups
like
the
court
devs,
so
that
they
can
have
kind
of
a
sense
of
how
different
stakeholder
groups
feel
about
it.
That
was
one
of
the
reasons
we
wanted
to
capture
some
of
the
feedback
of
the
notaries,
knowing
that
notaries
are
also
usually
played
multiple
roles
and
have
multiple
ways
to
provide
that
feedback.
We
wanted
to
present
it
as
specifically
the
filecoin
plus
notary
community
that
thank
you
for
the
time.
Okay,
raid
back
to
you.
E
A
I'm
gonna
skip
these
and
go
right
into
the
proposals,
so
we
recently
closed
out
three
proposals:
I'm
just
flagging
this.
Just
in
case
you
aren't
watching
GitHub
like
a
hawk.
This
was
just
on
your
radar.
The
first
was
there
was
a
bug
report
about
the
wrong
allocation.
Static,
that's
been
corrected
and
closed.
The
second
was
the
TNT
review
of
meta
wave,
since
there
have
been
no
more
discussions
on
that
since
February
we've
gone
and
cut
and
closed
that
out.
A
But
as
always,
if
you
have
additional
thoughts
or
comments,
feel
free
to
comment
on
that
issue
and
reopen
it
and
third
was
the
TNT
code
of
contact
conduct.
We
discussed
these
in
great
detail
back
in
February
and
RG
has
some
updates
on
a
new
proposal.
That's
moving
forward,
so
this
is
just
for
transparency.
We
closed
out
these
three
issues,
but
there's
been
a
few
more
so
the
first
one
Alan
from
greater
heater
you
on
the
call,
if
not
I'll,
speak
to
this.
A
I,
don't
see
him
on
the
call
so
feel
free
to
interrupt
me
if
you're
on
the
call
or
anybody
who's
representing
this
from
protocol
Labs
or
greater
Heat.
This
is
kind
of
an
interesting
opportunity,
so
essentially,
what's
coming
up
in
the
mid
part
of
2023
is
protocol
labs
and
greater
heat
are
going
to
be
sponsoring
essentially,
a
boot
camp
for
onboarding
of
very
large
data
sets.
These
can
be
a
combination
of
like
high
quality
data
sets
like
ldns
or
the
e-fill
plus
program
data
sets
for
that.
A
Enterprise
data
they've
created
an
issue
in
GitHub
and
what
they're
seeking
is
30
participants
from
the
Asia
regions
that
want
to
participate
in
this
boot
camp
to
Fast
Track
this
data
onboarding
and
going
forward.
So,
if
you're
looking
to
learn
more
about
this
project-
or
you
might
be
interested
in
joining
this
bootcamp
from
large
data
set
providers,
issue
845
is
live.
This
is
very
much
like
the
this
is
coming.
This
isn't
the
call
this
isn't
the
sign
up.
A
This
is
just
making
sure
that
you're
aware
that
this
will
be
coming
in
mid
2023
free,
so
there's
not
even
really
like
a
definitive
start
date
on
this,
but
in
the
middle
of
2023
30
storage
providers
from
the
Asia
regions
will
be
selected,
and
this
issue
845
is
open.
If
anybody
wants
to
check
it
out,
I'll
pause
and
see.
If
anybody
has
questions
before
we
move
on
to
the
next.
F
Right,
Hey
guys,
so
what
wanted
to
propose
this
is
issued
on
proposal
number
850..
It's
proposed
change
to
for
notaries
to
have
template
comments
that
they
could
comment
on
an
application.
Essentially,
notaries
can
put
these
comments.
The
saved
replies
on
applications,
it
auto,
pastes
it
and
then
you
can
choose.
You
can
write
a
justification
as
to
why
you
approve
or
reject
or
disapprove
of
a
certain
application.
F
Depending
on
whether
you
approve
or
disapprove,
it
will
add
a
label
to
the
application,
and
these
labels
are
very
significant,
as
they
can
signal
to
other
notaries.
Your
your
position
on
that
application,
as
well
as
give
us
data
for
tooling
decisions
in
the
future.
So
we
think
this
is
a
good
idea
and
we're
testing
it
right.
Now
we're
going
forward
to
that
and
I
think
going
for
it.
It
helps
create
transparency
in
the
in
the
LDN
application
process
and
yeah.
You
can
go
ahead
and
read
it.
F
G
Hey
everyone,
so
we
will
be
resurfacing.
This
proposal
idea
that
was
introduced
some
time
ago
by
deep
and
Galen
in
the
past
due
to
incoming
projects
that
are
requesting
for
more
than
five
pibs
The
Proposal
will
introduce
the
idea
that
the
data
cap
request
limit
on
ldns
should
increase
to
a
maximum
amount
per
application
of
15
pids.
G
This
idea
of
increasing
the
data
cap
request
limit
would
just
help
decrease,
redundant
client
applications
and
provide
a
more
accurate
Insight
on
the
total
data
set
size
that
clients
are
requesting,
but
with
a
high
data
cap
request,
a
risk
that
people
might
be
concerned
about
is
the
allocation
size
that
clients
might
receive
throughout
the
process.
So
with
the
new
limit
introduced,
we
would
also
change
the
allocation
math
to
avoid
that.
G
So,
if
you
look
at
the
current
allocation
process,
that
we're
using
today
for
the
program
and
below
is
the
max
request
scenario
so
KRA,
if
you
could
just
maybe
hover
over
that
part
yeah
right
there,
it
kind
of
points
out
all
the
the
current
scenario
right
now.
So
if
a
client
requests
for
five
Pips,
a
total
data
cap,
one
bit
per
week,
onboard
rate,
you
know
you
can
see
that
the
first
allocation
is
about
0.25
pibs.
G
G
So,
if
you
see
the
tranche
sizes
for
the
allocation
will
still
be
similar
to
how
the
program
currently
is
and
the
speed
that
clients
are
receiving
data
caps,
shouldn't
change
so
what's
changing
is
the
LDN
limit
request
so
that
we
can
just
help
clients
with
creating
less
redundant
applications,
but
the
speed
of
allocation
will
still
stay.
The
same
last
thing
to
mention
as
part
of
this
change,
the
scope
is
adjusted
to
if
clients
would
like
to
apply
for
more
than
15
pibs,
they
should
go
through
the
e-fill
plus
pathway.
G
The
e-fill
plus
pathway
just
serves
as
a
testing
ground
for
Enterprise
data
and
new
use
cases
for
client
onboarding.
So,
if
you're
interested
in
this
or
have
any
questions
you
can
reach
out
to
Kevin
z,
yeah,
thank
you
and
again
always
appreciate
feedback
in
your
input.
So
if
you
have
any
time,
go
ahead
and
comment
on
the
proposal.
E
I
think
I
would
like
to
hear
if
there
are
any
participants
on
the
call
like
this
has
been
like
a
something
Blakes.
Hadn't
said
deep
and
I
like
brought
this
up
many
moons
ago,
and
we
got
a
lot
of
opinions
in
both
directions.
Supporting
it
or
calling
against
it.
I
think
our
plan
here
is.
We
want
to
try
and
I
think
we're
saying
decrease,
although
like
duplicate
applications,
but
still
have
the
tranche
sizes
be
a
way
to
gate.
How
much
data
cap
could
go
out
at
any
given
time
does
this
live
15
yeah?
E
C
What
is
your
rationale
for
not
increasing
the
speed,
though,
because
from
from
what
I'm
seeing
a
lot
of
SPS?
Actually
they
do
when
they
do
large
data
set,
do
making
they
typically
start
at
300,
400
or
even
one
petabyte
I
mean
I,
don't
think
they
can
do
15
petabyte
in
one
shot,
but
for
the
very
first
one
they
can
easily
do
a
few
hundred
heavy
bite.
E
In
this
model,
the
first
allocation
is
still
throttled
right,
they're
still
getting
a
scoped
amount
that
allows
us
to
see
what
notary
signed
it.
How
much
diligence
did
the
notaries
perform?
Where
is
that
data
cap
ending
up?
You
know
we
can
use
tools
like
CID
Checker
bot,
so
we
can
apply
a
lot
more
of
our
quantitative
analysis
once
they've
gotten
an
allocation
and
as
of
now
doing
a
smaller
allocation
again
back
to
the
stuff
we
talked
about,
like
that.
E
I
talked
about
with
the
roadmap,
a
commensurate
amount
of
data
cap
to
the
amount
of
diligence
that's
being
done.
You
know
someone
can
go
in
and
put
in
an
application
right
now
and
say
15
and
you
know
put
in
a
lot
of
information
that
is
not
necessarily
accurate
and
that
group
of
memories
could
look
at
it
and
say
well,
we
have
we
want
this
to
move
quickly.
E
We
don't
want
to
gate
on
trying
to
vet
all
of
the
details,
let's
give
them
their
first
allocation
and
see
what
they
do
so
we'd
like
that
first
allocation
to
still
be
scoped,
because
at
the
scale
of
the
footprint
of
the
network,
giving
somebody
a
quarter
of
a
PIV
of
data
cap
is
not
the
worst
thing
in
the
world.
If
we
then
learn,
we
could
quickly
pull
it
back.
We
we
can
shut
them
down.
We
can
track
bad
behavior
if
we
gave
somebody.
E
You
know
four
pibs
of
data
cap
right
away.
That
becomes
like
a
much
bigger,
Threat
Vector
bigger
risk.
So
we
want
to
balance
notaries
being
able
to
support
clients
quickly.
You
know
bias
towards
yes,
give
them
enough
rope
to
get
started
and
see
what
they
do
with.
How
much
can
we
give
them
right
away
for
it
to
not
be
a
Threat
Vector.
H
C
E
Yeah,
it
just
becomes
complicated
as
like
another
thing
to
track,
and
also,
if
you're
a
first-time
applicant,
you
know,
we've
seen
a
number
of
people
that
come
to
the
network
and
their
onboarding.
You
know
steel
is
an
example
right
like
they
want
to
do:
they're,
they're,
doing
Enterprise
level
like
big
projects
and
they're,
a
first-time
applicant
where
they're
you
know
getting
started
doing
these
like
big
projects,
and
so
we
want
to
get
them
a
scoped
like
Fast
Pathway,
to
get
started
that
could
grow.
E
E
You
know
it.
We
tried
it.
It
was
a
hypothesis
of
saying
what,
if
you
open,
five
copies
of
this
application.
You
know
at
five
petabytes
each
and
what
that
leads
to
is
you
know,
tracking
different
client
addresses
and
someone
signs
on
one
when
they
should
have
signed
a
different
one,
and
you
look
in
the
dashboard
and
there's
you
know
500
open
issues,
but
that's
because
how
many
of
them
are
duplicates.
E
So
it's
just
leading
to
more
at
the
top
of
the
funnel
more
of
these
open
applications
to
deal
with
that
are
just
duplicates
and
redundant,
and
so
we
could.
We
could
decrease
the
number
of
hoppies
as
part
of
the
hypothesis,
while
not
introducing
you
know,
like
you're,
saying
this
new
thing
of
okay.
Well,
now
we
have
to
track
GitHub
account
and
we
have
to
say,
as
this
GitHub
account
opened
an
issue
before
what
happens
if
their
first
issue
is
using
the
auto
verifier.
Does
that
count
you
know
so
then
we
we
we're
adding.
E
You
know
additional
decision
making
into
it,
but
I
like
that
idea
of
like.
Could
we
scale
and
say
if
once
you've
done
once
you've
done
five
pibs
successfully,
then
you
could
do
you
know
X
more
pids.
That
said
that
behavior
should
fit
into
notary's
decision
making
when
a
notary
goes
to
check
an
allocation.
G
Yeah
I
think
just
like
one
last
thing
is
I
think
we
should
move
on,
but
if
anyone
has
like
you
know,
concerns
or
comments
just
like
UCB
and
I
bet
other
people
on
this
call
just
have
some
too
just
please
post
it
on
the
proposal
and
we'll
we
can
either
idea
from
there.
We
have
two
weeks
before
this
proposal
might
get
closed
or
not
so
we
can
make
adjustments
or.
However,
thank
you
thanks.
A
I
So,
as
for
those
of
you
that
have
been
following
along
with
efl
plus
pilot,
in
addition
to
being
a
pathway
to
onboard,
not
only
private
data
sets,
but
also
larger
Enterprise
data,
we're
using
it
as
a
testing
grounds
for
different
areas
of
the
program
that
we
want
to
sort
of
you
know
see
what
we
can
iterate
on.
One
of
those
is
notary
assignments,
so
in
the
general
LDN
process,
notaries
are,
as
you
all
are
aware,
allowed
to.
I
You
know,
review
and
sign
or
decline
on
any
application
and
you
see
fit,
but
in
the
efo
program
we
have
a
select
group
of
35
notaries
that
have
volunteered
to
be
part
of
the
multi-sig
and
they
are
randomly
assigned
to
Applications,
so
they
they're
not
allowed
to
choose
which
ones
they
want
to
sign,
which
ones
they
don't
so
today,
I
just
wanted
to
quickly
present
the
key
findings
that
I've
had
created.
Thus
far
from
you
know
what
we've
put
together
just
to
quickly
go
through
this,
and
you
can.
I
I
At
a
high
level,
there
was
106
notaries
that
were
randomly
assigned
to
review
an
allocation
and
either
sign
the
client
or
do
nothing
63
of
those
that
were
assigned
engaged,
meaning
they
within
the
within
the
time
frame
that
we
set.
They
reviewed
the
application.
They
submitted
a
comment
with
a
client
or
they
signed
the
application.
I
D
I
It's
just
saying
that
it
takes
a
lot
of
time
and
energy
not
only
to
assign
notaries
to
have
notaries
look
into
these
applications,
but
it
also
takes
energy
on
the
clients
to
have
to
wait,
especially
those
clients
that
are
putting
in
the
time
and
effort
to
do
kyc
KYB
put
together
an
application
that
is
deemed
trustworthy
and
the
notaries
aren't
paying
attention
so
I
I.
Think
overall,
this
is
this
is
there's
room
to
iterate
here
this
isn't
meeting
the
expectations
that
we'd
like
to
to
to
set
here.
I
Engagement
is
high,
though
I
will
say
right.
The
test
we
put
forward
is
a
good
one.
Notaries
are
engaged
more
than
they
would
be
in
just
any
other
random
applications
that
are
available
for
them
to
review,
but
it's
not
necessarily
on
the
on
the
time
needed
basis
that
we're
looking
for.
So
this
is
something
else
to
consider,
and
then
I'd
say.
I
Lastly,
only
five
notaries
that
were
assigned
actually
declined
to
sign
an
application,
and
it
could
have
been
for
for
a
variety
of
reasons,
but
you
know
notaries
can
choose
not
to
sign
for
whatever
reason
they're
being
fit
as
long
as
they
explain.
So,
only
five
percent
overall
didn't
sign
an
application
that
were
engaged
to
me
that
that
speaks
strongly
towards
what
we're
doing
up
front
with
these
applications
and
we're
making
the
clients
build
trust
coming
into
the
program.
I
So
it
makes
the
notary
job
a
lot
easier
once
they're
engaged
and
they're
looking
at
these
applications,
I
think
this
is
showcasing
that
you
know
having
that
upfront
kyc
done
having
the
SPs
listed
out
and
the
allocation
plans
all
very
clear.
It
makes
it
super
simple
for
notaries
to
follow
those
that
are
engaged
so,
okay
right
to
the
next
slide.
I
have
one
more
quick
slide
here.
So
one
thing
I'm
thinking
about
moving
forward
with
this
test.
I
I
Instead
of
assigned
notaries
per
allocation,
it
could
be
randomly
for
any
application
that
they're
a
part
of
you,
Phil
I,
would
rather
have
either
a
group,
or
you
know
this
goes
back
to
the
maybe
a
smaller
multi-sig
idea,
where
notaries
are
involved,
not
only
from
the
beginning
or
the
initial
phase.
Is
this
idea
of
like
reviewing
the
client
up
front
talking
to
them
reviewing
their
kyc?
I
You
know,
building
that
trust
up
front
and
then
there's
the
phase
two,
which
is
once
they've
they've,
received
at
least
their
first
allocation
of
data
cap
working
with
them
to
see
how
they're,
using
the
data
cat
are
they
doing
what
they
said
they
were
going
to
do
in
their
application.
Are
they
having
issues?
Do
they
need
to
change
dsps?
You
know
whatever
those
things
are:
a
set
of
notaries
that
are
dedicated
and
involved
from
the
beginning
to
the
end,
in
my
opinion,
is
more
valuable
than
just
randomly
assigning
notaries
through
view
allocations.
I
You
know
a
proposal,
yet,
let's
say
I'd
like
to
just
have
an
open
discussion
feel
free
to
reach
out
in
the
in
the
link
listed
there,
but
I
think
overall
by
signing
notaries
from
start
to
finish,
we
can.
We
can
really
focus
on
that
upfront
Trust.
We
can
allow
notaries
to
to
remain
active
and
aware
of
what's
going
on
from
from
the
beginning
through
the
through
the
end,
and
then
we
sort
of
reduce
the
time
and
effort,
and
we
minimize
a
negative
experience
for
clients
that
are
real
clients,
with
real
data.
I
A
C
J
Is
currently
focused
on
so
the
first
thing
that
is
top
of
the
priority
list
is
formalizing
the
dispute
resolution
process
by
introducing
staking
so
this
issue
number
846
right
now
it's
open
for
discussion.
There
are
two
proposals
that
were
recommended
by
FF
legal,
so
we
created
this
form
with
a
bunch
of
proposals,
and
these
are
the
two
options
that
we're
currently
considering.
So
we
still
have
one
more
week,
which
is
this
week
for
discussion.
J
J
The
second
priority
right
now
is
essentially
increasing
visibility
into
disputes
that
have
been
raised,
and
so
right
now
we
recently
launched
the
tat
T
the
TNT
dispute
resolution
tracker.
This
also
has
a
Google
form
that
you
can
find,
so
you
can
find
all
of
this
on
issue
849,
and
so
the
hope
is
that
we
can
move
away
from
these
large
threads
that
are
started
on
slack
and
essentially
have
a
better
way
to
manage
disputes.
J
So
what
I'll
be
doing
is
for
the
for
the
time
being,
I'll
be
populating
it
based
on
the
disputes
that
we
see
in
the
Google
form,
but
down
the
line
we
will
have
Integrations
so
that
we
can
automate
the
music.
You
can
automate
how
the
the
dispute
resolution
tracker
is
populated.
So
if
you
have
suggestions
on
how
to
improve
the
tracker,
just
the
perspective
of
ux
or
also,
if
you
wanted
to
add
fields
to
this
tracker,
please
comment
on
the
show
issue,
or
you
can
even
just
DM
me
on
Slack
next
slide.
J
Third
thing
that
we're
focused
on
is
supporting
new
use
cases.
This
is
directly
connected
to
what
Galen
mentioned
at
the
beginning
of
the
call
given
palcon
plus
submission
statement,
and
so
over
the
last
year,
we've
aspired
to
take
more
of
a
preventive
approach
than
a
reactionary
approach
every
once
in
a
while.
J
We
do
react
to
kind
of
big
allegations
about
data
cap
abuse,
but
we
want
to
move
towards
a
kind
of
a
world
where
we
can
work
ahead
of
time
with
potential
potential
clients
and
SPS
so
that
we
can
kind
of
understand
their
needs
based
on
the
discussion
that
I
I
had
in
Q4.
I
still
believe
that
a
lot
of
people
are
trying
to
do
the
right
thing,
and
it's
also
important
to
understand
why
data
capabilities
is
happening.
J
For
example,
I
had
a
great
discussion
with
the
large
SP
trying
to
understand
you
know
like
why
were
they
buying
data
cap
on
the
open
market
right
and
so
I
think
the
discussion
there
isn't
so
much
about?
Oh,
you
did
so
so
that
we
don't
abandon
you.
The
discussion
is
about
understanding
the
underlying
causes
and
reasons
so
that
we
can
understand
and
that's
why
we
have
increased
focus
on
client
tooling.
We
have
a
dedicated
person
on
that
because
that
seemed
to
be
one
of
the
challenges
in
the
blockers.
People
were
like.
J
J
So
right
now,
I'm
focused
on
improving
the
adoption
for
this
for
this
dashboard,
which
will
include
tutorials
and
different
languages
as
as
well
as
making
improvements
to
this
dashboard
as
well
and
I
want
to
understand.
You
know
how
can
this
be
useful
for
notary?
So
if
you
are
notary
on
the
call
or
just
a
Community
member-
and
you
have
ideas
of
how
we
can
improve
this
Dashboard,
please
reach
out
to
me
and
yeah.
We
can
collaborate
and
then
we
also
have
other
tooling
that
is
currently
being
built.
J
That
can
support
no
traditional
digits.
So
those
are
kind
of
the
high
level
priorities
that
currently
on
my
plate
and
The
Trusted
transparency
working
group.
But
if
you
think
that
there
are
other
things
that
we
need
to
prioritize
or
that
we
might
have
missed,
please
reach
out
to
me
and
I'll
be
happy
to
connect.
Thank
you.
A
F
F
A
All
right,
hello,
welcome
to
the
second
notary
governance
call
of
March
2023
March
28th
on
the
agenda.
We
have
a
full
packed
session.
We're
going
to
kick
off
with
some
updates
around
signing
in
with
the
notary
leaderboard
make
sure
that
everyone
on
the
call
has
the
link
and
is
tracking
how
to
sign
up
for
participation,
galen's
going
to
walk
us
through
some
updates
around
the
pulse
survey
that
was
recently
sent
out
to
the
notaries,
as
well
as
give
some
updates
around
the
mission
statement
and
the
road
map
for
what's
taking
place
on
the
government's
team.
A
As
far
as
updates
we're
going
to
be
walking
through
some
of
the
recently
closed
proposals,
as
well
as
making
sure
that
you're
tracking
three
of
the
new
proposals
that
recently
came
through
GitHub,
which
are
the
boot
camp,
the
diligence
flow
and
the
increased
limits.
After
that,
we
have
two
updates
that
are
coming
from
the
working
groups,
the
Enterprise
Phil
plus,
as
well
as
trust
and
transparency,
and
just
like
the
morning.
We
expect
lots
of
time
at
the
end
of
this
call
for
any
discussions
or
questions
you
have
so
at
any
time.
A
In
this
call,
if
there's
something
that
you
wanted
to
flag
with
the
speaker
or
raise
for
the
community,
please
shoot
a
hand
up
and
we'll
call
and
we'll
make
sure
that
the
floor
is
yours.
We
go
forward
so
with
that,
if
you're
joining
the
call
or
watching
on
YouTube,
you
can
always
add
these
on
your
Google
shared
calendar.
We
host
these
every
other
week.
The
next
call
will
be
on
April
11th
and
we
post
season
the
file
coin
slack
if
you
wanted
to
follow
along
with
the
slide
deck
as
well.
A
If
you're
curious
to
put
an
item
on
the
agenda.
As
always,
if
you
go
to
the
notary
governance,
repo
you'll
see
an
issue.
That's
created
every
two
weeks.
Just
comment
under
that
issue:
Hey
Kevin
I'd
like
to
have
this
proposal
spoke
to,
or
this
comment
in
slack
or
anything
that
might
be
linked
to
it
and
I'll
put
it
on
the
agenda
and
make
sure
that
there's
a
talking
point
for
it
all
right,
hey
notaries.
We
have
a
new
way
for
you
guys
to
sign
in
on.
These
calls
we're
kind
of
excited
about
it.
A
So
in
this
notary
leaderboard
that
I'm
sharing
screen
right
now
and
galen's
dancing
about
you'll,
see
there's
this
call
attended,
so
big,
huge
props
to
Catalin
and
Phil
for
setting
this
leaderboard
up
what's
possible.
Now
is
I'm
gonna
drop
a
link
here
in
the
chat
of
our
conversation
that
we
have
going
so
I'm
gonna
drop
this
here
in
chat.
A
If
you
come
over
to
the
leaderboard
page
right
now,
you
can
enter
this
code,
and
this
will
link
your
profile
to
this
meeting
now
quick
caveat
you
have
to
be
signed
into
GitHub
and
that
GitHub
account
has
to
be
the
one
that
your
application
was
filed
under.
So
if
you
go
ahead
and
just
copy
that
link
that
we've
shared,
you
can
then
paste
that
in
and
have
that
need
an
invite
and
just
like
Galen
posted
in
chat.
A
If
you
have
any
issues
with
copying
that
or
pasting
it,
please
let
me
know
and
we'll
be
sure
to
get
you
set
up
anybody
who's,
not
a
notary
who's.
On
this
call,
like
a
Community
member,
a
storage
provider,
anybody
an
applicant
I'm
going
to
share
the
link
to
the
air
table
form
that
we've
been
using,
and
what
this
will
allow
you
to
do
is
also
get
credit
for
coming
to
these
meetings
really
helpful
in
future
elections,
to
show
your
participation
or
ask
any
questions
so
you'll
see
two
links
in
the
chat
right
now.
A
One
is
for
the
leaderboard
for
you,
notaries,
anybody
who's,
not
a
notary.
There
is
a
link
to
the
error
table.
Any
questions,
please
let
us
know
in
chat
and
we'll
go
to
help
you
out
again,
big
props,
Catalina
and
Phil
for
getting
that
leaderboard
set
up
really
looking
forward
to
that
coming
along
all
right
on
to
governance.
If
you
haven't
seen
our
smiling
faces,
we're
the
governance
team
here
to
help
you
with
any
issues.
E
Hello-
everyone,
yes,
so
the
entire
governance
team
we've
been
sort
of
working
at
this
for
a
while
workshopping
it
with
some
various
stakeholders
and
wanted
to
sort
of
go
ahead
and
take
time
to
pitch
out
this
public
mission
statement.
There
will
also
be
an
upcoming
blog
post,
where
we
sort
of
unpack
this
some
more
and
also
point
to
a
couple
additional
sort
of
things
that
are
coming
down
the
funnel,
but
I
wanted
to
talk
about
it
here
for
the
past.
E
E
We
are
then
going
to
unpack
that
mission
statement
into
sort
of
a
road
map
of
action.
We
have
been
working
on
kind
of
setting
some
three-month
four-month
kind
of
Target
milestones
for
what
the
governance
team
is
working
towards.
We've
had
a
couple
different
iterations
of
this
roadmap
that
we've
been
workshopping
as
well
and
I.
Think
that
we're
we're
very
close
to
kicking
this
off
publicly
we'll
be
announcing
it
in
slack.
E
What
our
expected
timeline
is
in
our
milestones
and
how
we
will
get
there,
and
then
we
want
to
help
create
some
new
metrics
and
places
where
the
community
can
go,
see
those
and
understand
sort
of
the
progress
that
we're
making
in
a
pretty
public
way.
So
again,
you
know
these
I,
don't
think
these
as
they
are,
should
be
that
controversial
people
may
have
different
opinions
about
them
or
about
whether
or
not
how
accurate
one
of
these
statements
may
be
right
now.
E
So
the
program
talk,
one
plus
program
enables
filecoins
master
plan
to
onboard
massive
amounts
of
data
to
the
network.
If
you're
not
familiar
with
the
file
coin,
master
plan
go
check
out
some
talks
by
the
ever
gregarious
entertaining
one
Binet.
He
will
help
demystify
what
the
filecoin
master
plan
is
and
explain
that
to
you
at
length
number
two
data
cap
abuse
in
the
system
is
minimized.
This
is
something
that
all
of
us
care
about
at
different
levels.
E
We
have
different
opinions
on
what
defines
it
where
we
are
right
now,
we'll
be
releasing
sort
of
our
governance
team's
thought
on
it
and
the
specific
metrics
we
look
at
to
Define
it
as
well
as
the
new
metrics
that
we
want
to
track
towards
and
how
we
are
going
to
continue
to
push
to
minimize
data
cap
abuse
in
the
system.
Number
three
notaries
perform
robust
diligence
commensurate
with
the
data
cap
granted.
I
think
that
this
is
true.
E
I
think
that
the
amount
of
diligence
that
is
happening
is
and
should
remain
mapped
to
the
amount
of
data
cap
that
is
being
granted
in
the
scale
of
the
entire
network
and
the
scale
of
the
footprint
of
Falcon
plus,
but
also
of
the
overall
Network
itself
number
four
disputes
and
allegations
of
abuse
are
investigated
with
an
emphasis
on
restorative
justice
and
in
this
team
like
we
really
want
to
emphasize
that
restorative
justice.
There
are
a
lot
of
people
in
this
ecosystem.
It
is
a
complicated
ecosystem.
E
You
know,
rules,
change,
information,
changes,
there's
qualitative
things
that
can
be
misunderstood,
there's
language
barriers-
people
are,
you
know,
moving
fast
and
prioritizing
things,
and
also
you
know,
a
number
of
these
people
are
are
functioning
as
notaries.
You
know
effectively
as
volunteers
to
like
do
this
work.
People
make
mistakes,
people
drop
something
people
sign
the
wrong
thing,
people
you
know
a
client
misunderstands
or
misrepresents
like
these
things
happen.
Sometimes
it's
a
mistake.
E
Sometimes
it's
abuse
either
way,
but
we
want
to
investigate
with
an
eye
to
correcting
the
behavior,
not
an
eye,
to
punishing
everybody
as
as
partially
as
possible,
and
so
in
that
way
our
goal
is
always
to
to
change
the
behavior
to
learn
from
it.
While
we
can
to
make
the
system
better
and
to
understand
how
to
prevent
you
know
those
mistakes
and
those
bad
behaviors
in
the
future.
So
that's
our
Focus
area.
There,
five
legitimate
client
use
cases,
have
scoped
Pathways
for
attaining
data
cap.
E
We've
been
working
really
hard
on
this
with
the
projects
that
we
do
around
Auto
verifiers
projects
that
we
are
doing
that
you
know
maybe
have
not
gotten
a
ton
of
traction
yet
around
fvm
and
how
we
are
working
to
scope,
support
for
smart
contract
projects,
how
we
work
to
add
support
for
ldns
at
different
scales.
How
we
work
to
investigate
you
know
ways
to
support
Enterprise,
be
it
public
or
private.
E
There's
you
know,
28
participants
on
this
call
right
now
and
I
I
guarantee
that
not
all
20
of
it.
Eight
of
us
have
the
same.
Prioritization
have
the
same.
Incentives
have
the
same
boss
have
the
same
thing
that
we
want
to
see
in
this
network
in
six
months
or
in
six
years,
but
we're
all
here
trying
to
make
it
the
best
that
we
can
and
meet
those
compromises
and
design
in
a
collaborative
way.
E
Sometimes
we're
not
going
to
agree.
How
do
we,
as
the
governance
team,
keep
pushing
for
Rapid
testing
that
is
still
safe
enough
to
try
knowing
we
can
make
these
changes
and
revert
back
if
necessary,
and
how
do
we
demonstrate
whether
or
not
these
processes
are
working?
So
these
are
the
like.
I
said
these
are
the
six
Focus
areas.
There
will
be
a
more
public
information
about
specifically
how
we
are
tracking
them
with
metrics
quantitatively
and
the
work
that
we
are
doing
on
like
a
project
scale
Tube
map
towards
them.
So
I'm
really
excited
for
this.
E
I
really
appreciate
all
the
work
the
governance
team
has
put
into
it.
I
appreciate
all
the
different
stakeholders
that
have
given
us
feedback
in
this
process,
as
we've
been
going
and
I
think
that
the
next
three
months
are
going
to
be
a
lot
of
velocity
change,
so
stay
tuned
and
then
I
think
you
have
the
joy
of
hearing
from
me
for
one
more
slide
is
that
right
boom?
Yes
to
that
in
there
have
been.
E
If
you
are,
you
know,
have
a
if
you
have
a
pulse
and
you're
in
the
Falcon
community
and
you've
been
here
for
more
than
two
weeks,
you
probably
have
been
tracking
a
couple
spicy
conversations
in
fips
around
SDM
and
some
other
discussions
around
CDM.
Some
conversations
around
you
know:
quality
multipliers
around
should
the
filecoin
plus
program
as
a
multiplier
continue
to
exist.
Should
other
subsidy
models
be
added.
E
There's
a
lot
of
different
opinions
out
there
there's
a
lot
of
people
that
are
backing
up
their
opinion
with
an
amount
of
data
and,
like
I
just
said,
this
is
a
complicated
and
very
diverse
set
of
stakeholders.
So
one
of
the
things
that
the
governance
team
has
we
kicked
it
off
last
week
wasn't
perfect,
but
we
want
to
keep
iterating
on
this
and
trying
it.
We
want
to
do
pulse
surveys.
This
is
not
a
poll.
E
E
So
the
structure
of
this
pulse
check,
we
did
it
on
a
scale
of
sort
of
zero
to
five
I
think
that
that
is
probably
how
we
will
continue
to
do
them,
because
they
think
that
it
is
a
meaningful
way
to
capture
sort
of
various
people's
stance
on
it.
Five
being
I,
fully
support.
This
I
think
that
it's
an
incredible
idea
if
this
passes
like
this
is
the
best
thing
that
we
could
do
right
now
for
being
I
moderately
support
it.
E
You
know
looking
forward
to
trying
it
three
being
I'm,
pretty
neutral,
I,
see
the
pros.
I,
see
the
cons.
I,
don't
have
a
better
opinion,
I
think
we
should
just
do
it
and
move
on
tubing.
I'm
I'm,
you
know
cautiously
unsupportive,
one
being
I'm
pretty
moderately
unsupportive
I.
Don't
think
this
is
a
good
idea
if
it
passes
I'm
still.
You
know
here.
I
think
that
this
is.
We
are
a
community
we're
gonna,
sometimes
I'm,
not
gonna,
win
every
argument,
but
I
have
an
idea.
E
If
you
did
not
get
it,
if
you
are
a
notary
and
you
did
not
get
the
survey
sorry,
it
may
have
been
a
mistake
in
an
email,
we're
working
to
make
sure
that
we
have
everyone's
email
address.
If
you
didn't
get
it
and
you
think
you
should
we'll
work
through
slack
with
k-ray,
he
has
slack
channels
that
he's
set
up
with
everybody
where
he
swapped.
E
You
know
token
codes
to
like
connect
and
verify
this
email
address
that
we
have,
with
with
this
set
of
slack,
handles
to
know
that
we're
talking
to
the
right
person
and
the
intent
with
this
was
to
send
one
per
organization.
So
if
you
are
a
member
of
an
organization
where
you
have
of
kind
of
multiple
staff
and
peers
who
have
signed
up
to
be
notaries,
we
want
one
reply
for
your
organization
on
these.
E
Okay,
not
a
poll,
not
a
vote,
but
we
want
you
guys
to
synthesize
your
opinions
into
one
and
present
one
unified
opinion
from
your
notary
organization
about
these.
Wearing
your
notary
hat
and,
like
I,
said.
We
hope
to
continue
doing
this
so
that
we
can
keep
like
capturing
where
you
know
as
we
launch
these
strategic
initiatives
We'll
be
asking.
You
is
this:
is
this
the
most
important
strategic
initiative
that
we
need
to
be
tracking
towards?
Are
we
missing
something,
and
then
you
know
give
us
give
us
feedback
to
help.
Keep
us
aligned.
E
A
F
Hey
guys
so
very
quick,
there
are
a
few
bugs
very
common
bugs
that
were
issued.
I
mean
thing
to
me
on
the
LDN
applications.
The
first
most
common
bug
is
this
bug.
That
says
we
could
not
find
ID
field
and
the
information
provided-
and
this
has
been
stopping
multiple,
multiple
LDN
applications
from
getting
their
data
cap,
even
though
there
was
a
proposal
and
an
approval,
and
so
this
should
be
fixed
for
now
we're
tracking.
F
If
it
happens
again
and
if
it
happens
again,
you
should
let
me
know
another
bug
that
we
get
is
double
proposal.
So
if
you
see
an
LDN
application-
and
there
are
two
proposals
for
the
same
request-
something's
wrong
going
on
there-
we
added
an
extra
check
to
see
if
this
happens
and
it
should
prevent
it
from
happening.
F
We
we
also
track
when
it
happens.
So
if
it
does
happen
again,
there's
really
something
wrong,
and
you
should,
let
me
know,
there's
one
double
request
bug
that
is
happening
right
now:
we're
investigating
it
and
sa
bot
is
still
under
maintenance.
It
should
be
up
again
tomorrow,
so
there
will
be
no
data.
New
data
cab
requests
coming
up
in
the
next
few
hours,
I'll,
let
you
know
when
it
comes
up
again,
but
sorry
for
the
inconvenience
and
we're
trying
our
best
to
get
it
solved.
A
It
back
to
Carrie:
hey
thanks
Phil.
If
anybody
has
any
questions
or
encountering,
these
feel
free
to
stick
a
hand
up
now
and
we'll
also
have
time
at
the
end
of
the
call
for
any.
Like
other
additional
questions
you
have
thanks
for
that
Phil
great.
We
have
four
slides
about
proposals.
I'll
take
the
first,
it's
just
the
recently
closed.
Just
in
the
guise
of
transparency.
Always
we
closed
out
these
proposals.
Since
the
last
governance
call
first
proposal
was
the
bug
Phil
kind
of
spoke
to
this.
Briefly,
it
was
the
allocation
report.
A
Had
the
wrong
static
information
on
it.
We
were
able
to
address
that
and
close
that
bug
out
thanks
for
flagging.
The
second
was
the
trust
and
transparency
review
of
metawave
lots
of
good
conversation
took
place
in
January
and
February.
The
conversation
really
hadn't
moved
forward
since
that
time.
So
we
closed
it
out,
but
as
always,
if
you're
in
the
community-
and
you
see
something
and
want
us
discuss
this
feel
free
to
comment
on
that
issue.
A
While
it's
closed
and
the
third
one
we
closed
out
was
the
initial
proposal
for
the
trust
and
transparency
code
of
conduct,
we've
been
working
on
this
with
RG
pretty
closely
there's
a
new
proposal.
That's
up
so
we
closed
out
this
old
one.
So
just
for
transparency.
These
three
issues
have
closed,
but
if
there's
anything
else
feel
free
to
comment
those
as
we
go
forward
great
with
our
next
slide,
we
have
a
guest
speaker.
H
Hello,
everyone,
yeah
hello,
I'm,
Ellen,
melee,
responsible
for
great
heat,
that
growth
and
then
I
will
briefly
introduce
this
boot
camp
project,
which
is
jointly
released
by
great
heat
and
appear
yeah.
The
tspa
project
introduction
projector
video
is
to
hear
from
Azure
FPS,
complete
their
fear,
plus
business
transformation
and
the
expanded
elective
data
storage
yeah.
The
girl,
the
main
girl
is
two
here-
is
30.
Welcome.
Ccsp
is
successfully
transferred
into
DCS
piece
with
six
months,
creating
a
admitted
educator,
qap
or
one
Eid
for
Qualcomm
Network.
H
So
then,
maybe
someone
asked
we
why
we
apply
for
a
large
DC
reason,
I
think
there
are
two
reasons:
the
one
is
conventional
ldm
application
for
a
Max
maximum
amount
of
5
PID
is
more
difficulture
to
meet
boot
camp
requirements
for
100
pivdc
amount;
yeah,
maybe
a
audience
needs
at
least
20
different
applications,
but
currently
but
quality
diet.
That
might
only
need
two
to
three
to
meet
the
dfps
goals,
the
second
the
developer,
high
quality
diets
and
create
a
collective
example
of
data
storage.
Yes,
the
usage.
We
think
the
application
DC
will
see.
H
H
Then
we
blow
mail.
We
promise
that
the
project
team
will
first
complete
the
KYB
flow
sense
in
strict
complex
with
the
Silicon
Plus
network
rules.
The
second
issue
accepts
KYB
from
volunteers
and
the
Northwest
throughout
the
philcom
community.
The
third
as
the
dspa
organizer
great
heat,
is
happy
to
make
some
HP
notes
know
the
ideas
available
for
Community
review.
H
Then
the
welcome
plus
guided
to
transparency.
We
first
made
the
major
problems
for
the
entire
project
in
the
natural
governance
report.
The
second
223
20
to
30
PID
applications,
each
updates
the
same
same
client
date,
the
third
each
debt
cap
application
will
be
assigned
to
hp's
participants.
According
to
the
project
team
alignment,
then
the
data
storage
plan
we
think
apply
for
DC
culture.
H
H
A
A
A
D
F
F
On
the
other
hand,
it
also
creates
a
lab
triggers
a
label.
So
when
the
notary
pays
these
saved
replies,
the
bot
will
see
it
and
change
the
label
of
the
application.
This
is
just
for
better
signaling
to
other
notaries
that
this
this
application
has
been
approved
or
disapproved
before
and
also
it
gives
us
some
more
data
from
these
applications.
It
creates
LD.
It
makes
the
LDN
application
process
way
more
transparent
and
yeah.
This
data
can
be
used
for
decision
making
in
the
future
to
create
better
tooling.
A
G
Thanks
Carrie
hi
everyone
so
we'll
be
introdu
reintroducing
this
proposal
idea
that
was
introduced
in
the
past
by
deep
and
Galen.
So
with
the
increase
of
just
projects
that
are
requesting
for
more
than
five
pibs
The
Proposal
will
introduce
the
idea
that
the
data
cap
request
limit
on
ldns
per
application
to
increase
to
15
Pips.
G
A
concern
that
some
people
might
be
raising
is
that,
with
the
high
data
cap
request,
there
might
be
raise,
clients
might
receive
throughout
the
process.
So
just
with
that
new
limit
introduced,
we
would
also
change
the
allocation
math
to
avoid
that,
if
you
look
at
the
current
allocation
process
that
we're
using
today
in
the
proposal
and
below,
is
the
max
request
scenario.
G
So
if
you
look
at
the
proposal,
sorry
Carrie,
if
you
could
just
hover
over
like
the
middle
of
it,
a
little
bit
more
down
yeah
right
there.
It
shows
that
a
client
request
can,
if
a
client
requests
five
Pips
of
total
data
cap,
one
PID
per
week,
onboard
rate
you'll,
see
that
the
first
allocation
is
about
0.25
Pips,
second
allocation,
half
a
PID
third
one,
fourth,
two,
and
so
on.
G
If
you
see
the
charge
sizes
for
the
allocation,
it
will
still
be
similar
to
how
the
program
currently
is
and
the
speed
that
clients
are
receiving
data
caps
shouldn't
change.
So
the
only
thing
that's
really
changing
is
the
LDN
limit
request
so
that
we
can
just
help
clients
with
creating
less
redundant
applications,
but
the
speed
of
allocation
will
just
stay.
The
same
last
thing
to
mention
as
part
of
this
change
within
the
LDN
application
process,
the
scope
will
be
adjusted
to
if
clients
would
like
to
apply
for
more
than
15
Pips.
G
They
should
go
through
the
e-fill
plus
pathway,
and
essentially
this
is
because
the
e-fill
plus
pathway
just
serves
as
a
testing
ground
for
Enterprise
data
and
nuke
use
cases
for
client
onboarding.
So
if
you,
if
you're
interested
in
this
or
have
any
questions
you
can
reach
out
to
Kevin
z,
yeah,
so
thank
you
and
again
always
appreciate
feedback
and
your
inputs.
So
please,
if
you
have
any
time,
go
ahead
and
comment
in
The,
Proposal.
A
G
Yeah
so
I
think
I.
Remember.
One
question
was
like
why
15
over
like
20
or
25
I,
think
personally
for
us
we're
realistically
we're
actually
tripling
the
limit
itself.
So
that's
already
a
big
increase.
I
think
that
was
just
something
we
want
to
go
ahead
and
start
with
and
I
think
anything
realistically.
Clients
are
applying
for
more.
A
G
A
Think
a
lot
of
people
mirror
this,
that
this
will
cut
down
on
the
amount
of
applications
and
make
it
a
little
bit
easier
to
get
those
tranches
pushed
through
at
a
more
rapid
way.
Thank
you
for
spearheading
this.
If
anybody
has
any
questions,
feel
free
to
shoot
a
hand
up
comment
on
issue
851
and,
as
always,
we'll
have
time
at
the
end
of
the
call.
D
D
A
I
So
for
the
e-fill
pilot,
all
applications
are
randomly
as
notaries
are
randomly
assigned.
I
have
a
group
of
35
notaries
that
have
volunteered
to
be
part
of
the
working
group
and
as
applications
and
allocation
requests
come
in
they're
they're
randomly
assigned
to
review
within
an
SLA
of
72
hours.
So
essentially
three
days.
I
So
we've
been
testing
that
for
the
past
few
months
and
I
wanted
to
share
some
of
the
results.
Thus
far,
I
won't
go
into
all
the
details
that
there's
a
link
on
the
on
the
slide.
You
can.
You
can
check
that
out
on
GitHub
a
little
bit
more,
but
just
at
a
high
level
when
we
looked
at
the
14
active
applications,
I
had
106
notary
assignments,
so
I
and
I'm-
and
this
is
manual
right
now
so
I'm
manually,
assigning
randomly
notaries
to
the
different
allocation
requests.
I
I
So
what
do
all
these
numbers
mean
to
me
at
the
bottom?
The
key
takeaways
right
now
that
I'm
having
overall,
only
30
about
30
of
those
assigned
signed
per
the
guidelines,
and
that's
not
saying
that
they're
they're.
They
don't
want
to
sign.
It's
just
saying
that
it
takes
a
lot
of
time
and
energy
to
get
the
notary's
attention
and
hold
them
accountable
towards
looking
at
these
applications
and
not
only
the
notaries
but
also
the
clients.
I
Clients
are
going
through
a
lot
of
their
own
checks,
confirm
that
they're
real
with
real
data
and
they're
waiting,
they're
waiting
on
notaries.
So
I
think
this
is.
This
is
an
area
we
can
definitely
iterate
on.
I
want
to
propose
some
things
here
later
on,
but
engagement
overall
is
high.
Notaries
are
engaged.
I
I
This
is
working
well,
but
and
finally,
overall,
so
only
five
percent
of
notaries
that
were
assigned
declined
to
sign
an
allocation,
meaning
that
you
know,
for
whatever
reason
they
did
not
support
the
application
which
to
me
this
speaks
strongly
to
the
fact
that
they're
being
presented
with
applications
and
clients
that
have
gone
through
a
lot
of
checks
and
they're
they're
being
presented.
As
you
know,
trustworthy,
valid
data
sets
and
I.
I
You
know
one
of
the
ideas
that
comes
to
my
mind,
right
away
is
like
I
mentioned,
where
we're
putting
a
lot
of
energy
and
effort
into
assigning
different
notaries
each
allocation,
but
but
I'm
learning
that
if
we
can
have
notaries
that
work
with
applicants
from
the
beginning
through
their
entire
Journey,
there's
really
two
phases.
There's
this
before
the
first
allocation
phase,
where
a
client
is
going
through
a
series
of
kyc
KYB,
ESP
plan
checks
and
based
on
that
trust
up
front.
I
B
B
I
I
I
was
testing
slack
manually
tagging
in
Slack,
but
then
I
was
having
conversations
in
both
channels
and
it
was
becoming
too
much
to
manage
as
the
applications
are
growing.
So
this
is
something
that
it's
on
Phil's
radar
as
well
to
potentially
automate
different
ways
to
communicate
out
to
notaries,
whether
it's
via
direct
email,
slack,
automation
as
well
as
GitHub,
but
I
agree.
This
just
just.
B
B
Yeah
I
wonder
if
there's
something
so
my
interface
on
a
lot
of
this
stuff
is
the
fill
plus
single
page
application.
I
wonder
if
we
I
mean
I
know
it's
already
passing
all
of
the
GitHub
comments
to
kind
of
construct
its
look
on
it
I
wonder
if
there's
there's
something
there
where
I
can
like
black
ones,
where
there's
been
an
active
kind
of
AD.
B
E
The
registry
to
action
to
like
actually
yeah
yeah,
we're
we're
actively
looking
at
some
additional
ways
to
restructure
those
columns
to
be
able
to
hide,
filter
or
like
see
ones
that
may
get
assigned
to
you,
so
that
when
you
as
a
notary
sign
in
instead
of
you,
would
still
be
able
to
see
the
full
list
of
everything.
But
you
could
also.
E
This
was
also
an
idea
when
the
before
the
recent
refactor,
where
load
times
were
really
bad,
but
the
the
hypothesis
is,
if
you
sign
in
and
there's
only
10.
But
you
know
that
those
10
are
for
you
that
you
would
be
able
to
like
more
quickly
bump
through
and
parse
or
use.
The
save
reply
templates
from
before
that
we
mentioned
to
be
able
to
say,
like.
A
E
E
B
E
Foreign,
that
was
on
the
Enterprise
fill
program,
we're
working
on
some
Auto
assigning,
but
not
random,
assigning
initiatives
for
all
notaries
for
all
ldns,
but
stay
tuned
for
that
we
will
be
looking
at
things
like
if
you
are
a
notary
in
a
particular
region.
If
an
LDN
comes
in
and
says
that
it's
in
that
region,
we
may
do
something
like
pick
all
of
the
notaries
in
that
region.
End
Auto
assign
a
pool
so
rather
than
it
being
random
selection.
A
All
right,
we
have
a
question
in
chat,
we'll
pin
that
until
I
give
the
updates
from
trust
and
transparency
and
then
Chloe
will
come
back
to
that.
Do
a
group
thread
on
that
for
you
sweet.
So
speaking
on
behalf
of
RG,
just
quick
check
RG
if
you're
on
the
call
feel
free
to
unmute
I
didn't
see
you,
they
are
essentially
forming
issue
846,
and
this
has
to
do
with
formal
dispute
resolution.
So,
as
you
know
right
now,
the
dispute
resolution
kind
of
forms
in
the
way
of
a
slack
Channel
or
a
GitHub
conversation.
A
It
can
be
very
opaque.
It
might
not
have
very
clear-cut
information
on
like
what
needs
to
happen.
So
what
they're
looking
to
do
is
essentially
have
like
a
tracked
wallet
and
what
this
will
do
is
they'll
have
like
a
specific
amount.
That's
sent
to
that
wallet
by
the
governance
team.
Then
we
can
always
monitor
to
see
like
what
the
specified
fill
is
in
that
wallet
and
then
penalize
based
off
the
amount
of
participation
and
lack
participation,
fraud
whatever
it
may
be,
that
comes
up
in
that
process
access.
So
this
is
eight
four
six.
A
This
is
kind
of
migrated
from
the
staking
proposals
that
we've
had
in
the
past.
This
is
definitely
worth
checking
out
if
you're,
a
notary,
not
just
if
you're
on
the
working
groups,
because
what
this
is
going
to
apply
to
is
how
are
we
taking
this
group
participation
in
on
this?
So
please
check
out
846
dealing
with
that.
A
The
second
is:
how
does
that
trust
and
transparency
working
group
look
at
these
applications
and
then
respond
to
their
status
so
again,
as
the
program
grows,
and
as
we're
trying
to
make
this
a
more
sustained
process,
with
much
more
structured
and
clear-cut
guidelines
on
how
this
data
is
being
onboarded
audited
and
really
contributing
to
that
core
mission
that
Galen
outlined
what
RG
is
working
on
is
essentially
having
increased
visibility
into
that
dispute
process.
So
this
is
going
to
be
a
big
lift
coming
up
on
their
radar
over
the
next
Sprint.
A
We
should
see
a
lot
more
updates
on
the
trust
and
transparency
call
that
takes
place
at
the
same
time
next
week.
So,
if
you're
interested
in
learning
more
about
that,
but
essentially
what
this
will
be,
is
that
they'll
have
a
dedicated
way
to
handle
that
dispute
resolution
versus
these
proposals
and
going
forward
on
it
and
then.
Lastly,
what
they're
looking
to
do
is
having
this
collaboration
between
the
trust
and
transparency
and
the
project
that
KZ
is
leading
and
then
accelerator
support
as
they
go
through
there
on
this.
A
So
right
now,
the
way
the
trust
and
transparency
works.
It's
very
reactive,
it's
flagged
by
the
community,
it's
flagged
by
you
as
notaries.
It's
flagged
by
issues
that
might
come
up
and
what
they're
looking
to
do
is
like
try
to
understand
the.
Why?
Behind
this,
so
rg's
had
a
couple:
calls
with
storage
providers
that
actually
purchased
data
cap
and
I
think
his
intent
was
to
not
be
more
of
like
an
investigator
or
police
officer,
but
more
of
like
why?
A
What
what's
missing
in
the
program
that
someone
would
need
to
purchase
that
data
cap
in
order
to
make
their
business
model
so
I
think
that's
like
a
big
takeaway
for
how
RG
is
approaching
this
problem.
It's
not
meant
to
be
a
gotcha.
It's
meant
to
be:
what
are
we
doing
wrong,
that
we
can
improve
and
streamline
this
so
that
we're
all
growing
this
project
together
and
a
long-term
solution
is
put
not
just
catching
one-offs
but
figuring
out?
A
So
we
have
the
link
in
the
slide
deck.
If
you
haven't
taken
a
look,
it's
absolutely
beautiful,
so
Props
to
you
guys
for
making
this
work,
and
essentially
what
this
does
is
you
can
look
at
these
improvements
and
objectively
Define,
where
this
data
cap
is
going
who's
pulling
it
in
what
are
they
doing
with
it?
How
did
that
data
cap
get
applied?
Did
it
come
through
like
the
glyph
Auto
verifier?
Did
this
come
through
an
LDN?
A
So
what
we're
really
looking
to
do
with
this
tooling
is
again
step
out
from
like
Prosecuting,
one-off
cases
and
look
at
streamlining
this
solution
to
be
a
lot
more
helpful
for
you
in
the
community
and
then
all
of
us
with
like
quality
data
that
comes
on
for
it
with
it.
So
speaking
on
behalf
of
RG,
he's.
Definitely
the
point
of
contact
for
all
these
updates
and
as
well
as
the
trust
and
transparency
working
group.