►
From YouTube: Filecoin Plus - March 02 Notary Governance
Description
The community governance call to discuss the specific mechanisms and operations of the Filecoin Plus program.
A
Happy
tuesday,
folks,
I
believe
it
should
be
tuesday
for
everybody
on
the
call,
because
we're
doing
this
early
enough
in
the
morning
here
hope
everybody's
doing
well.
Welcome
to
I
don't
know
what
iteration
this
is,
but
the
the
march
2nd
dame
governance
call.
I've
got
a
few
interesting
topics
to
cover
today,
so
I
pasted
the
link
to
the
deck
in
the
chat.
A
I'm
going
to
do
that
again
because
a
couple
of
you
joined
afterwards
nice
to
see
everybody
here,
you
know
feel
free
to
drop
where
you're
dialing
in
from
so
we
can
continue
to
get
to
know
each
other
a
little
bit
yeah,
I'm
going
to
share
my
screen
hop
over
to
the
deck
get
started,
and
then
we
can
continue
to
continue
the
conversation
as
the
topics
come
up.
Can
somebody
give
me
a
quick
thumbs
up?
Who
has
a
video
on
that?
You
can
see
my
screen
cool.
A
Okay,
great
okay,
so
with
that,
let's
get
let's
get
started.
Let's
talk
about
notaries,
so
the
first
topic
is
fleek
reached
out,
and
let
us
know
that
they're
not
currently
in
in
a
position
to
service
the
nursery.
So
for
those
of
you
that
remember,
the
application
they
filed
was
around
serving
as
a
notary.
A
That
would
basically
allow
services
to
be
built
on
filecoin
and
automatically
get
access
to
datacap
for
clients
of
those
services,
and
that
was
interesting
because
it
would
effectively
allow
a
service
to
be
built
on
which,
when
other
services
were
built
or
software
was
built,
that
would
run
on
top
of
file
coin.
The
clients
interfacing
with
that
intermediary
to
the
network
could
actually
receive
data
cap.
A
Like
I
in
general,
I
think
when
we
were
reviewing
the
applications,
it
seemed
like
a
valuable
use
case,
and
so
it
is
important
to
have
a
notary
like
this.
However,
it
seems
like
they
don't
finally
have
the
time,
so
that
leads
to
an
interesting
conversation
we
haven't
had
before,
which
is
this
idea
that
a
notary
now
maybe
needs
to
be
removed
and
that's
not
something.
A
We've
we've
set
a
process
for
that's,
not
something
we've
considered,
because
typically,
it's
been
more
about
notice
to
want
to
become
noticed
today
and
so
there's
a
couple
of
things
that
we
can.
We
can
talk
about
in
terms
of
the
path
forward
here,
there's
an
idea
that
we
actually
remove
their
current
data
cap
allocation.
A
What
are
the
implications
on
that
particular
notary
for
their
future
ability
to
serve
as
a
notary
and
then
what
are
the
implications
on
other
applicants
in
the
region
that
want
to
become
a
notary?
I
have
some
opinions
here,
but
it's
more
important
to
ensure
that
we
hear
everybody's
opinion
and
so
actually,
why
don't
we?
Why
don't
we
stop
and
talk
about
it?
A
So
my
two
cents
are
basically
that,
like
there's
a
relatively
easy
part
where,
through
the
root
key
holders,
we
allocated
data
cap
to
node
trees
once
we
elected
them
as
a
community
through
keyholders,
we
can
set
that
allocation
back
to
zero
and
effectively.
That
notice
doesn't
have
data
cap
anymore
and
then
maybe
we
treat
future
applications
to
being
a
notary
as
and
independent
of
previous
performances
of
notary.
A
I
don't
know
if
that's
the
right
path,
I'm
curious
to
hear
if
others
have
opinions,
especially
other
notaries
that
are
present
today.
If
you
have
thoughts
on
what
it
means
for
you
to
feel
like
you
can't
serve
anymore
and
what
you
think
the
implications
of
that
are
I'd,
love
to
hear
them
feel
free
to
use
the
chat
or
unmute.
A
Yeah
so
we're
basically
talking
about,
like
a
notary,
that's
electing
to
get
themselves
removed
as
a
notary.
So
there's
a
there's
two
different
questions.
One
is:
how
do
we
actually
like
tactically
remove
them?
Is
it
more
that
we
set
their
allocation
to
zero
or
we
just
let
them
be
and
tell
people
to
not
send
them
requests,
because
maybe
in
the
future,
they'll
have
time
to
like
do
their
duty
again
and
then.
C
A
No,
so
I
I
hope
not
I
mean
there's
a
bunch
of
nobodies
that
are
still
you
know,
allocated
very
small
amounts
of
their
ground
to
data
cap,
many
as
some
single-digit
percentages
so
but
there's
progress
being
made,
at
least
so.
I
think
I
think
in
general,
at
least
from
what
I've
read
they're,
the
only
ones
so
far
that
have
approached
the
topic
of
saying:
hey,
like
self-electing
themselves,
out
of
israel.
D
A
D
A
Is
this
three
times
plus?
No,
maybe
more,
because
I
think
we
have
noticed
in
north
america,
europe,
western
asia,
china,
those
are
the
four
and
then
north
america
and
china
both
had
additional
three
two
two
north
because
of
thais.
Basically,
so
I
think
we
ended
up
with
like
15
or
16
notaries
in
the
end,
but
yeah
like
about
half.
E
C
Yeah
there
is
a
scorecard
rob
that
you
have
to
fill
and
then
you
see
what
is
the
score
and
if
you
are
eligible
to
be
a
notary
and
then
when
you
have,
I
don't
know
if
when
we,
when
we
start,
I
think
we
are
not.
We
are
we.
We
have
less
notary
that
the
position
that
were
open,
so
we
didn't
have
the
question
to,
I
think,
decide
who
is
going
to
be
notary
or
not.
A
A
Okay,
basically,
there's
a
there's
a
rubric
and
the
rubric
is
community
governed
as
well,
so
like
we've
had
people
create
issues
in
the
repo
to
modify
the
rubric,
and
so
it
is.
I
think
it's
realistic
for
you
to
assume
that
the
rubric
will
change
over
time,
because
the
needs
of
the
network
should
change
over
time.
E
A
I
agree
with
that,
which
is
why
I
was
kind
of
wondering
like
is:
is
there
a
path
where
we
actually
need
to
like,
like
in
this
case
right?
It's
not
that
they
don't
want
the
service
and
notice
that
they
can't
right
now.
Does
that
mean
you,
like
you,
just
put
them
in
a
pause
as
well
right,
there's
like
a
way
in
which
we
just
say
clients,
don't
don't
get
to
request
data
cap
from
you
for
like
n
number
of
months,
but
then
is
that
fair
to
like
the
liquidity
of
the
data
cap
in
that
market?
A
I
don't
know,
and
so
my
initial
thought
was
yeah,
basically
like
we
remove
them
by
setting
them
to
zero.
Then
if
that
brings
the
number
of
notaries
in
a
region
down
below
the
minimum,
which
is
currently
a
three,
then
we
replace
them
with
the
next
notary
that
was
in
line
and
in
the
future
if
they
want
to
reapply
that
they
should
be
welcome
to
reapply.
But
maybe
that
now
means
it's
part
of
the
application.
There's
also
like.
B
So
I
think
the
way
I
I
sort
of
like
proposing
that
we
are
implicitly
penalizing
notaries
that
you
know
have
backed
off
their
responsibility
once
approved
by
kind
of,
like
you
know,
having
them
going
undergoing
extra
scrutiny
in
the
case
they're
reapplying
to
kind
of,
like
you
know,
really
tell
folks
what
is
different.
This
time
is
that
is.
A
B
Right
and
I
mean
kind
of
like
they
still
have
to
go
through
the
application
process.
You
know
they
still
would
have
to
potentially
kind
of
like
speak
up
at
the
sort
of
like
the
governance
meeting,
and
you
know
in
the
end
of
the
day.
I
think
this
would
just
add
another
element
of
subjectivity
into
this
evaluation
process
because,
like
oh,
we,
you
know
this
person
or
this
entity
kind
of
like
broke
the
word
kind
of
versus
sort
of
like
let's
just
try
to
be
as
objective
as
possible
as
unopinionated
as
possible.
F
Doesn't
that
open
up
a
kind
of
rough
precedent
where
you
could
have
notaries
in
the
future
actually
apply
when
they're
not
ready,
like
it
kind
of
allows
you
to
have
people
that
aren't
really
committed
at
the
moment?
Yes,
letting
them
step
down.
Unpenalized
just
allows
them
to
come
back
at
any
time,
but
doesn't
open
that
up.
A
F
A
E
A
A
What
that
does
do
is
it
does
give
like
the
community
a
chance
to
see
the
the
influence
you've
had
as
a
notary.
The
rubric
itself
has
like
a
built-in,
like
idea
of
like
building
upon
your
past
experience
and
performances
notary.
So,
as
you
successfully
dole
out,
certain
amounts
of
data
gap
you're
effectively
eligible
to
unlock
higher
and
higher
amounts
of
data
cap
to
you
as
a
notary,
so
that
you
can
increase
the
influence
and
the
impact
that
you
have
to
bring
useful
workload
to
the.
A
Okay,
so
any
other
thoughts
on
the
second
point
on
like
replacing
them.
My
current
thinking
is
to
keep
the
minimum
as
the
stable
minimum,
just
because
we
don't
want
to
like
unfairly
then
effectively
for
people
that
didn't
tie
on
the
rubric.
They
suddenly
now
had
a
shot
to
become
a
notary
where,
if
they
were
in
any
other
region,
they
wouldn't
have
had
that
opportunity.
D
A
There
is
a
right,
consistent
metric
and
what
we
can
instead
do
is
increase
that
minimum
over
time.
As
we
start
to
see,
usefulness
come
in
from
more
notaries,
and
so,
if
we
feel
that
the
time
is
knife
or
like
moving
from
three
to
five,
then
maybe
that's
the
conversation
that
to
me
seems
like
an
independent
conversation.
A
A
Well,
then,
there's
a
second
option,
which
is
effectively
that
there
needs
to
be
like
a
technically
verifiable
path
that
actually
uses
just
software
to
make
the
change.
So,
for
example,
kiko
is
working
on
a
path
that
supports
both
the
multi-stick
address,
as
well
as
like
a
a
ledger
on
chain
for
somebody
to
sign
it.
It's
a
notary
and
then
make
allocations
from
that.
So
I
have
a
little
screenshot
of
their
current
beta
version,
which
shows
that
you
can
add,
like
your
ledger,
as
well
as,
like
your
multisig
address
on
chain.
G
Hey,
hey
deep
sorry,
I've
just
been
lurking
in
the
back.
I
had
one
question
around
region
going
back
to
your
previous
question:
how
is
location
determined?
Is
it
where
legally
the
entity
is
registered
or
is
it
something
else
like
just
just
curious
because
obviously,
there's
probably
a
certain
amount
of
notaries?
I
can
imagine
all
registered
in
switzerland
that
may
or
may
not
legally.
A
That's
a
it's
a
good
question.
We
had
a
lot
of
conversation
around
this
like
when
we
were
doing
the
first
set
of
like
whatever
the
version
of
the
rubric
was
that
we
used
to
do
the
scoring.
I
think
it
was
technically
the
second
version
of
the
rubric
and
I
think
in
the
application
process
and
philip,
you
know,
please
feel
free
to
add
your
opinion.
A
If,
if
you
have
one
the
what
we
finally
went
with
is
more
like
what
the
notary
self
selected
themselves
into
in
terms
of
operation
like
what
community
they
knew
they
could
be
active
in
and
where
they
knew
they
could
easily
provide
the
resource
that
they
needed
to
be
for
that
particular
set
of
clients.
And
so
we
did
have
like
a
fair
amount
of
applicants
that
like
cross-border,
and
we
felt
that
it
was.
A
It
was
fair
to
do
that
if
they
could
actually
like
participate
in
the
conversations
that
were
required
of
them
and
actually
serve
the
needs
of
that
particular
community,
and
so
in.
In
some
cases,
I
think
if
doctor
and
shin
is
here,
for
example,
she's
a
good
example
of
an
organization-
that's
based
like
outside
of
north
america,
but
they're
still
serving
as
a
military
in
north
america
and
actually
reviewing
actively
like
applications
in
north
america.
A
B
The
falcon
foundation
is
a
better
example
case
right.
The
falcon
foundation
actually
is
a
u.s
entity,
but
I
am
physically
in
europe,
so
kind
of
like
it
makes
most
sense
that
you
know.
We've
been
mostly
ahead
of,
like
looking
we're
like
now
progressively
more
looking
at
applications
that
are
coming
out
of
europe,
we're
sort
of
like
in
the
beginning,
given
that
for
the
first
notary,
considering
everything
globally.
B
So
I
think
sort
of
like
these
are
just
as
we
kind
of
like
bootstrap
the
program
you
know
kind
of
like,
and
we
have
great
liquidity
on
notaries
and
kind
of
like
there'd,
be
more
kind
of
like
processes,
best
practices
that
sort
of
like
certain
regions
align
on
over
time.
I
think
that
will
become
less
of
a
discussion.
B
A
Claire,
I
think
that
should
answer
your
question.
If
not
bringing
continue
in
chat
so
again
talking
about
this
particular
case.
Does
anybody
have
an
opinion
on
like
pursuing
this
path,
where
we
keep
on
iterating
on
the
software
as
well
or
are
we
comfortable
with
changing
data
cap
allocations
to
node
3
addresses
because
that's
the
same
mechanism
we'd
use
in
the
previous
case
with
fleek,
for
example,
as.
A
F
It
just
adds
a
little
overhead,
not
a
huge
deal,
but
for
people
that
don't
want
to
do
the
overhead.
I
just
have
them
wait
until
that
pull
request
is
ready.
It's
not,
it
seems
like
way
less
problem
than
setting
up
a
pathway
to
move
those
addresses
for
now
like
deal
with
that
headache.
Later,
maybe
that's
all.
A
I
see
jv
is
sharing
that
the
the
technical
parts
should
be
ready
by
the
end
of
the
week.
Hopefully,
that
was
going
to
be
one
of
my
questions
was
basically
how
long
like.
If
it's
going
to
be
something
that's
delayed,
then
maybe
we
look
at
because
in
general,
one
of
the
issues
we
have
today
is
data.
Cap
is
a
little
more
scarce
than
it
needs
to
be.
A
A
Maybe
a
question
for
the
room
is:
do
we
foresee
other
issues
like
this,
like
notaries?
Have
you
run
into
other
similar
programs
like
problems
like
this,
when
onboarding
or
ramping
up
that
might
be
worth
flagging
or
calling
out?
Because
if
there's
like
many
such
problems,
then
we
should
also
talk
about
ensuring
that
they're
addressed
quickly
or
we
have
an
alternate
path.
F
Okay,
I'm
just
going
to
jump
in
because
nobody's
so
two
smallish
ones.
One
people
changing
the
addresses
they're
applying
with
might
be
better
if
we
could
standardize
that.
So
I
had
one
applicant
that
just
applied
with
the
existing
address
that
they
had
already
received
data
cap
for
which
is
actually
good,
because
then
you
can
check,
we
could
check
what
they
had
actually
already
received,
but
maybe
we
can
set
it
up,
so
they
can
apply
for
what
the
next
one
should
be.
F
So
we
can
actually
because
we
can't
assign
new
data
cap
to
the
old
one,
so
that's
one
and
then
other
and
then
actually
very
related
to
that
we
had
in
that
flow.
I
asked
the
applicant
what
the
new
address
should
be
and
they
gave
it
and
then
I
worked
with
my
co-worker
ignacio
to
get
it
signed.
But
in
the
time
that
I
had
given
him
the
address
from
the
issue
and
he
was
going
to
make
the
assignment
they
had
edited.
F
The
comment
which
is
my
other
problem,
is:
what
do
we
do
about
history
there
and
I
think
it's
in.
I
think
it's
in
the
get
history,
but
it's
a
little
bit
it's
a
little
bit
hairy
if
we
don't
standardize
some
of
those
things,
maybe
not
an
emergency
like
no
fires
here,
but
something
to
think
about
long-term
notaries.
Those
kind
of
workflows.
A
Yeah,
that
makes
sense
I'd,
be
curious
if,
like
having
the
initial
address,
helped
with
validating
some
of
the
application
path,
because
otherwise
there's
a
there's
a
route
here
where
basically,
you
just
get
the
address
like
right
at
the
end
when
you
need
to
do
the
actual
allocation,
but
I
also
know
that,
for
some
notaries,
it's
part
of
their
actual,
like
evaluation
of
a
client,
is
to
look
at
activity,
and
things
like
that
on
that
address.
So.
A
A
A
All
right
cool,
so
let's
talk
about
some
of
the
issues
that
were
called
out
last
week
that
that
have
a
little
bit
of
follow-up,
that's
worthwhile.
So
the
first
one
was
just
this
idea
of
having
like
data
cap
markets
and
like
what
the
distribution
data
cabinets.
Look
like
there's
a
clear
point
that
was
brought
up
and
it's
probably
worthy
of
being
brought
up
again
is
nobody
should
not
be
selling
data
caps.
That's
not.
A
A
The
data
with
them,
then,
maybe
there's
not
enough
data
cap
circulating
as
as
they
should
be,
and
so
we
went
and
do
quite
a
bit
of
conversation
last
call.
So
for
those
of
you
that
weren't
there
please
check
out
the
recording,
but
basically
going
through
a
set
of
questions
for
for
notaries.
That
were
there
on
like
what
was
blocking
them
from
enabling
the
clients
that
were
applying
to
them,
and
it
was
interesting
because
there
was
an
opinion
that
there
was
not
enough.
A
Some
are
definitely
more
active
than
others,
but
some
of
the
questions
that
were
raised
last
time
that
we,
we
probably
should
just
surface
again,
are
these
three,
which
is
one.
Do
we
have
a
sense
from
notaries
on
the
reasonable
timeline
for
responding
to
requests?
So
the
current
was
about
five
days,
and
so
what
what's
happening
right
now
is
people
are
effectively
waiting
five
days
and
then
bringing
a
notary,
which
I
just
wanted
to
ask
the
nurses
in
the
room,
if
that's
working
for
them.
C
Okay,
julian
speaking
again
start
go
for
it,
okay,
so
actually,
I
think
that
at
the
beginning
we
see
many
many
people
arguing
that
there
is
not
enough
data
cap
and
there,
but
on
all
the
requests
I
received
from
the
beginning.
Just
two
were
valid
requests
actually,
and
I
would
say,
like
50
of
the
time
when
I
was
asking
questions,
I
get
no
answers,
so
I
close
it
after
maybe
two
or
three
weeks,
and
otherwise
it
was
like
a
minor,
especially
from
china.
C
They
were
like
applying
to
all
the
different
notaries,
but
I
just
get
two
valid
requests
from
the
beginning.
I
got
a
few
other
valid
requests,
one
from
actually
I'd
which
is
connected
on
this
call,
but
it
was
also
he
already
applied
before
to
philip.
So
we
said
we
said
that
we
stick
with
just
one
notary,
but
otherwise
there
is
not
so
many
clients
right
now.
C
I
think
maybe
we'll
get
more
when
slingshot
will
start
again,
but
for
now
everybody's
waiting.
There
is
not
so
much
I
don't.
I
don't
know
I
don't
have.
Maybe
you
have
better
analytics
that
what
I've
got,
but
for
the
the
market?
The
store
storage
market,
but
as
far
as
I
see
there
is
not
so
much
deep
right
now
so
yeah.
A
A
C
Right
now,
I
I
just
want
to
say
that
to
conclude
that
I'm
fine
with
the
process
right
now,
I'm
I'm
fine
with
the
volume
of
information
we
have
to
manage,
but
I
mean
for
for
me
everything
is
good
based
on
the
number
of
clients
we
have
today.
Of
course,
if
tomorrow
we
have
to
get,
we
have
hundreds
of
clients
coming
then
at
that
time,
maybe
we
need
to
find
something
different,
more
industrialized,
but
based
on
what
we
have
today,
I
think
it's
enough.
A
A
B
A
Okay,
so
that's
still
quite
a
bit
of
buffer
right
because,
theoretically,
like
the
client
should,
is
the
one
applying
and
should
probably
be
tracking
that
the
question
to
the
room
is
probably
then
like.
Do
we
want
to
standardize
that
or
are
we
okay
is
every?
Does
everybody
feel
relatively
comfortable
with
their
individual
processes,
and
it
was
like
I'm
going
to
drop
mine
to
10
knots.
H
Yeah,
I
don't,
I
think
it's
not
not
necessary
to
like
standardize
it
because
like
so
so
we
we
like
bushy
capital
like
some.
Sometimes
you
may
know
that
we
have
just
published
our
car
line
last
week,
and
so
so
we
actually
asked
our
clients
to
provide
lots
of
the
materials
and,
if
they
don't
like,
didn't,
provide
enough
we're
going
to
ask
them
more.
So
it
will
like
take
us
some
more
times
than
other.
H
A
A
great
perspective,
thank
you
for
sharing
that
I
think
andrew
is
still
going
to
go
down
to
10.
If
you
ask
me,
but
that
sounds
useful,
let's
keep
let's
keep
going
because
I
know
we're
also
now
getting
into
the
last
sort
of
quarter
of
the
time
slot
philip.
If
you
wanted
to
share
like
you
know,
for
a
minute
or
two
on,
unlike
any
updates
to
the
tools
that
are
being
built
in
the
ecosystem
and
also
like
past
getting
grounds
and
rfps
yeah
100.
D
B
Currently,
building
we're
expecting
a
first
build
to
be
ready,
hopefully,
by
end
of
this
week
as
soon
as
we
have
something
we
can
share
with
the
broader
community
we
will,
and
what
to
expect
is
that
this
is
really
a
simple
dashboard
that
allows
folks
to
just
trace
clients
and
notaries
and
just
see
kind
of
like
everything.
That's
been
happening
on
chain,
and
the
neat
twist
is
that
you
know
that
address.
Then
you
know
actually
gets
connected
with
the
github
issue
that
served
as
the
notary
or
decline
application
so
effectively.
B
You
kind
of
have
all
the
important
data
within
sort
of
like
one
interface
and
allows
you
to
kind
of
like
track
and
trace
sort
of
like
what's
been.
What
sort
of
like
what's
said
in
the
application
versus
what
has
been
happening
on
shane,
I
think
sort
of
like
a
next
step
would
be
to
kind
of
automate
a
whole
bunch
of
these
different
things.
But
I
think
initially
this
is
sort
of
like
just
a
way
to
kind
of
like
get
get
get
some
layer
of
transparency
into
the
program.
B
It
could
be
in
the
context
of
transparency.
It
could
also
not
be
does
really.
Any
idea
would
gladly
always
brainstorm
on
those.
There
is
the
developer
grants
program,
that
is,
that
is
being
managed
by
the
falcon
foundation,
so
there's
money
available
for
ideas
to
be
built
and
really
for
any
more
information
and
there's
a
I'll
post,
a
link
to
the
to
the
github
repo
for
the
developer
grounds
program,
where
you
can
find
all
information
on
general
application
guidelines
and
so
forth.
A
A
So
if
there
were
miners
looking
to
serve
five
one
plus
demand,
they
created
a
little
comment
on
the
issue
that
then
was
used
to
populate
a
miners.md
file
which
finally
now
actually
shows
up
on
the
500
plus
site.
So
if
you
are
a
client
like,
if
you
navigate
to
the
filecoin
plus
side
as
a
client,
you
actually
see
like
a
listing
of
miners,
and
that
listing
is
populated
directly
with
this.
A
This
markdown
that
I've
linked
below
many
of
you
have
already
seen
this
and
pr
it
to
add
yourselves
to
the
list
this
week.
So
that's
awesome
and
last
week
as
well,
and
so
for
those
of
you
that
in
the
room
that
are
also
minors
and
want
to
ensure
you
appear
on
the
list
and
for
those
of
you
watching
the
recording
in
the
future
make
sure
to
head
over
to
that
link
and
feel
free
to
pr
it
I'm
going
to
them
as
soon
as
I
can
to
approve
them.
A
It's
a
relatively
quick
thing
for
you
to
comply
with
with
a
line
and
just
adding
a
row
and
a
table
basically,
and
so
it's
a
pretty
quick
check
for
me
as
well
to
verify
that
it
looks
good
and
and
we'll
merge
these
as
soon
as
we
can
moving
on
to
the
next
newer
sort
of
set
of
issues.
First,
one
data
cap
allocation,
inconsis
inconsistencies
across
regions,
there's
issue
96
that
was
filed
by
fat,
fatman13
513.
A
I
I
I
mean,
of
course,
individual
experience
may
vary.
It
basically
took
us
around
14
days
to
to
get
10
gig
of
data
cap.
So
I
mean
meanwhile,
the
automated
process
would
grant
you
eight
gig,
so
I
mean
it
kind
of
it's.
It's
kind
of
the
process
is
a
bit
slow
and
we
also
have
to
sync
with
the
miners
we
work
with,
because
the
miners
are
always
trying
to
grow
their
capacity
and
they
don't
they
may
or
may
not
have
enough
funds
to
to
to
actually
accept
the
do2
file.
I
A
Yeah
yeah,
thank
you
for
sharing
that.
So
I
have
a
couple
thoughts
of
this
on
I'd
love
to
hear
you
know.
Others,
one
was
basically
we,
I
think,
like
no
reason
in
general,
still
sort
of
ramping
up
so
like
a
great
example
of
this
is
like
the
fanbooshi
folks
have
activated
like
quite
a
bit
in
the
last
couple
of
weeks.
A
I
don't
know
if
your
application
went
through
them
as
a
notary
or
through
a
different
notary,
but
that's
like
they
have
a
massive
amount
of
data
capture,
the
largest
notary
right
now
and
as
that
process
becomes
smoother
for
them.
My
hope
is
that
the
turnaround
time
becomes
quicker.
The
second
is
notaries
that
I've
seen
that
are
careful
about
the
first
data
cap
allocation
are
that
are
typically
doing
that
because
they're
expecting
you
to
come
back
and
it
becomes
easier
and
easier
for
that
notary
to
then
give
you
more
data
cap
in
the
future.
A
So
I'm
kind
of
hoping
that
this
is
just
like
an
early
friction
like
issue
and
over
time
it
becomes
a
little
bit
easier.
But
if
this
is
yet
another
data
cat.
Like
another
point
in
like
that,
oh
we
need
to
improve
the
abundance
of
data
cap.
Maybe
we
need
to
think
about
like
adding
even
more
notaries.
Maybe
we
need
to
have
additional
conversations
down
that
line,
but
I'd
like
to
hear
other
opinions
in
the
call
as
well.
If
there
are
any
or
if
you
have
any
thoughts
on
that.
J
Some
of
it
is
like
a
configuration
thing,
so
I've
reached
out
to
some
of
the
teams
as
well,
so
that
people
can
like
specify,
like
a
minimum
piece
size
for
verified
deals
versus
like
unverified
deals
and
like
being
able
to
distinguish
that
way,
but
I
think
the
the
two
gigabyte
minimum-
and
I
think
at
least
in
the
minor
x
channel
some
folks
were
mentioning
that,
like
four
gigabytes
is
their
minimum.
I
think
this
is
like
highlighting
a
need
potentially
for
like
a
service.
J
I
think
there's
maybe
like
a
couple
solutions
to
this.
I
can
share
some
of
like
the
preliminary
thoughts
that
people
are
like
kicking
around
like
one
idea
is
like
a
batching
type
service
where
it's
like.
Could
there
be
clients
that,
like
do
you
deal
packing
on
behalf
of
clients
to
like
ship,
larger
quantities
together,
and
then
they
like
for
clients?
The
clients
will
like
get
back
when
the
deal
does
eventually
go
through?
J
They
can
get
back
like
a
selector
and
like
a
cid,
so
like
you
as
like
an
end
user
client
would
go
through
like
a
broker
or
like
a
batching
service
or
something
that
can
like
handle
the
deal
packing,
which
would
make
it
easier
to
get
the
deal
on
chain.
But
these
are
like
currently
like
higher
level
ideas
that
people
are
talking
about,
but
the.
J
A
A
B
B
It
can't
be
that
you
know
a
client
is
running
for,
like
multiple
verification,
diligence
processes
at
the
same
time,
so
that
can't
work
it
can
always.
You
know,
can
always
be
a
case
where
a
client,
you
know
kind
of,
like
you
know,
doesn't
come
through
a
it,
doesn't
get
through
a
application
process.
Be
it
because
the
notary
you
know
has
too
busy
or
whatever.
There
are
many
different
reasons
why
it
could
happen.
B
A
Yeah,
that's
a
good
point.
I
think
one
of
the
things
we
should
think
about
between
this
call
and
the
next
is
like
what
is
like
the
the
way
in
which
we
reasonably
set.
I
think
he
you
brought
this
up
in
the
past
as
well
right
where
you
just
saw
people
spamming
like
no
days
with
applications
and
just
like
this
is
not
reasonable
and
probably
not
like
a
good
way
to
go
about
ensuring
that
there's
like
a
successful
interaction
in
the
ecosystem.
A
I
I
think
that's
completely
fair
point.
It
might
be
worth
thinking
about
the
the
relationship
across
divisions
is
like
maybe
part
of
the
application
of
the
client.
Is
you
also
just
like
link
to
the
other
issues
that
you've
opened
or
something
like
that,
and
so
notaries
also
know
when
to
prioritize
or
not
prioritize
like
an
application.
That's
coming
in.
K
A
Me
so
technically
yeah,
I
think
it.
It
depends
on,
like
your
use
case,
if
you're
serving
something
that
actually
extends
beyond
regions
and
is
valuable
in
a
different
region.
Then
the
point
of
that
notary
is
to
understand
the
contacts
and
the
nuances
of
the
region
that
they
serve
right.
So,
if
you're
bringing
a
use
case,
that's
valuable
to
the
region,
then
I
think
it's
it's
reasonable,
philip.
If
you
want
to
talk
about
some
of
the
apps
that
you're
seeing
outside
of
europe,
that
would
be
probably
good
perspective
to
share
sorry.
B
A
Cool
thanks
for
sharing.
We
have
about
three
minutes
left
in
the
call,
so
I
just
wanted
to
use
this
time
to
also
just
highlight
two
new
issues
that
have
come
in.
Maybe
we
won't
have
a
discussion
around
them,
but
at
least
we
can
just
hear
from
the
people
that
filed
so
issue
94,
which
is
around
onboarding
projects
that
have
large
data
cap
requirements
sonic.
I
believe
it
was
actually
you
know
something
that
came
up
in
the
call
from
you.
C
C
So
so
doing
this,
we
we
can
have
just
one
notary
impacted
by
this
specific
customer
and
we
can
have
a
specific
relationship
between
the
the
client
and
the
the
notary.
We
are
not
creating
bottleneck
by
consuming
all
the
notaries
that
are
kept
just
for
one
client
and
all
the
other
notaries.
They
can
still
work
on
other
clients,
yeah,
and
I
mean
I
see
a
lot
of
benefits
doing
so,
but
I
I
just
don't
know
if
we,
if
we
can
do
it
and
also
I
have
one
open
question
about
that.
C
C
A
A
J
Think
this
is
actually
like.
We
should
figure
out
what
is
the
so,
I
think,
discover
is
also
in
a
similar
boat,
though
even
after
replication
will
be
much
smaller
than
80,
petabytes
or
whatever,
but
I
do
think
so,
one
from
like
the
process
of
like
practically.
If
we
don't
have
a
process
to
like,
have
some
sort
of
community
consensus
on
like
how
do
we
allocate
data
cap
to
these
projects?
It's
gonna
have
to
go
through
the
existing
notaries,
which
means
we're
gonna
have
to
run
through
like
right.
Now.
J
J
We
like
have
to
figure
out
how
we
scale
like
how
fast
the
data
cap
can
grow
to
support
some
of
those
use
cases
or
the
other
thing
that
could
happen
is
like
this,
like
special
purpose
like
oh,
we'll,
have
to
define
a
process
so
that
the
community
can
say
like
no
like
you're
not
doing
proper.
Due
diligence
like
how
is
the
data
because,
like
I
think
julian
brings
a
good
point
like
if
starling
wants
to
store
a
large
amount
of
data
like
we
have
a
mechanism
to
like
support.
J
This
use
case
on
falcon,
which
is
fantastic
but
like
it
seems
quite
scary,
to
suggest
that,
like
10,
specific
miners
are
like
the
ones
that
are
going
to,
like,
I
don't
know,
potentially
get
like
a
massive
boost
in
power
and
so
like
how?
How
are
they
thinking
about
like
the
decentralized
like
decentralization
of
that
like
there's,
also
like
a
whole
logistics
side
of
it,
which
maybe
I
I
can
add,
more
comments
and
thoughts
on
that
issue?
But
I
think
yeah
personally.
A
I'm
going
to
say
the
same
thing
for
the
next
issue,
which
is
basically
we
we
had
this
pretty
big
conversation
in
issue.
66
on
clients
make
the
most
data
cap
pricing
power.
There
was
a
fork
sort
of,
or
actually
multiple
forks
of,
conversation
that
emerged
from
that
issue.
One
of
them
was
on
decentralization
of
deal
making
and
like
how
many
miners
should
a
client
be
data
cap
actually
store
with,
and
so
in
previous
calls.
You
know,
we've
tossed
around
the
idea
of
like
having
a
percentage
cap.
A
We've
also
talked
about
the
difficulty
of
finding
miners,
sometimes
that
actually
meet
the
needs
that
are
required
of
a
client
to
actually
deliver
storage
in
a
way
that
that
is
required
for
that
particular
use
case,
and
so
I
just
filed
a
separate
issue
for
it,
and
so
I'd
love
to
just
use
that
issue
as
the
sort
of
specifically
scope
of
that
conversation
on
like
how
can
we
ensure
that
there's
like
a
reasonable
decentralization
in
the
application
and
workflows
that
are
being
brought
to
falcon?
So
that's
issue
98.
A
If
you
have
opinions
on
that
topic,
I've
just
taken
a
screenshot
to
sort
of
give
you
a
sense
of
what
I
propose
in
there
and
I'd
love
to
hear
some
opinions,
we're
also
a
little
bit
over
time.
I
know
we
had
a
couple
of
technical
issues
getting
started,
but
should
be
good
to
go
now.
So
unless
there's
anything
yeah.
J
Yeah,
I
have
one
other
one
I'll
file
an
issue,
but
I
I
think
andrew
actually
mentioned
it
in
the
chat
which
is
worth
discussing
so
for
something
like
the
automatic
verifier
right
now.
It
is
set
to
give
out,
like
eight
gigabytes
like
once
a
month,
and
I
wonder,
like
I
think,
everyone's
probably
like
used
up
their
eight
gigabyte
allocation
just
for
like
testing
stuff
and
like
a
good
question
would
be
like.
J
D
J
It
would
also
fundamentally
go
against
this
idea
of,
like
notaries,
have
a
predefined
plan
that,
like
they
have
to
like,
execute
against,
and
so
do
we.
This
is
like
creating
a
new
process
as
well.
Maybe
it's
like
as
simple
as
like
their
the
notary
has
to
like
submit
a
thing
to
the
community.
We
have
like
some
period
of
time
for,
like
I
don't
know,
another
governance
call
at
least
for
people
to
like
talk
about
it
to
like.
D
J
Say
like
we
feel
good
or
not
get
about
it,
but
I
don't
know
I'll
raise
an
issue.
I
think
it's
an
interesting
use
case
also.
I
do
think
it
would
be
great
if
the
automatic
verifier
could
like
support
more,
but
I
don't
think
we
have
a
process
that,
like
really
answers
like
how
that
would
be
possible.
Yeah.
B
K
Deep,
are
there
any
any
near
future
upgrades
of
the
notaries
in
europe
because
we
have
only
called
philip
the
last
few
times
but
he's
also
extremely
busy,
and
it's
maybe
a
little
bit
too
much
load
only
on
his
shoulders.
So
is
there
anything
in
the
near
future?
Are
they
more
like
100,
terabyte
or
larger
data
cap
allocations
to
maybe
sonic
or
other
ones,.
A
Yeah,
I
think
that
we
need
to
have
the
conversation
on
like
like
what
is
the
next
round
of
applications.
Look
like.
I
don't
think.
We've
had
that
conversation
yet
just
because
we're
still
seeing
that,
like
a
lot
of
notaries,
haven't
even
started
like
grounding
data
cap
and-
and
maybe
it
means
that
we
need
to
separate
based
on
region.
D
A
A
K
For
us,
it's
it's
just
we
we
follow
everything
every
day
and
we
are
just
on
one
side
of
the
issue
and
almost
everybody's
on
the
other
side
of
the
issues.
So
everybody
is
having
difficulty
with
their
setup
and
starting
and
growing,
and
we
are
on
the
side
of
just
exploding
with
all
new
data
capture,
new
ideas.
So
we
are
on
the
leash
and
we
need
to
do
a
little
a
little
bit
more
calm.
A
Yeah,
I
just
wanted
to
clarify
sorry,
I
I
mixed
up
kiko
and
fleek.
Fleek
is
the
one
that's
stepping
down
as
another
kiko
is
still
very
much
serving
as
another,
and
they
have
100
terabytes,
so
I
would
certainly
say
reach
out
to
them
yeah
on
the
topic
of
the
issues.
This
is
why
it's
important
to
have
like
you
as
a
perspective
and
have
all
these
various
perspectives
in
the
ecosystem,
because
that's
sort
of
how
hopefully
we'll
come
together
as
a
community
drive
consensus
and
make
progress.