►
From YouTube: Filecoin Plus - March 30 Notary Governance
Description
Community governance in which we discuss the the definitions for active/good notary practices, methods for new Notary Elections, and further input on the formation of a tribunal of Filecoin-Plus stakeholders.
A
Hey
everyone
welcome
to
the
notary
governance
call
for
march
30th
at
2021.
I
just
noticed
our
slide
says
2020,
so
we
got
to
get
that
updated
with
new
year.
I'm
excited
to
have
you
all
yeah.
Today's
today's
agenda
is
pretty
packed.
We've
got
a
bunch
of
topics
around
content
updates,
stuff
around
notaries
and
notary
elections,
and
then,
of
course,
the
usual
open
issues,
space
for
questions
and
discussion,
etc.
B
So
here's
where
we
stand
right
now
with
the
frequently
asked
questions
doc
last
turned
the
sync.
We
told
you
that
this
was
coming.
We
made
some
modifications
internally
based
off
like
other
people's
comments
and
feedback.
So
now
this
link
is
live.
So
if
you
look
at
it
here
in
the
doc,
you
can
click
on
that.
It's
a
google
doc
which
allows
you
to
comment
on
it.
What
we're
looking
for
is
your
feedback.
If
somebody
was
new
to
the
program.
B
Does
this
address
some
of
the
main
questions
and
what
we're
hoping
to
do
is
take
that
burden
off
of
you,
so
that
it
can
actually
be
floated
into
questions
into
the
slack
once
you've
had
a
chance
to
look
at
it.
The
next
phase
is
we're
going
to
broaden
this
out
to
the
repo
that
we
have
then,
after
that
we'll
be
putting
it
actually
in
the
field
plus
room
for
even
wider
dissemination
on
feedback,
and
then
that
way
we
have
ideally
an
all-encompassing
doc
that
can
walk
us
through
all
these
points.
B
So
if
you
haven't
clicked
on
this
link,
you'll
see
it
right
here
on
the
top.google.
Everybody
should
have
common
permissions
to
go
ahead
and
any
feedback.
The
feedback
that
we're
looking
for
again
is.
Does
the
question
actually
or
does
the
answer?
The
question
actually
like
give
somebody
enough
to
be
tactical.
We
didn't
want
to
go
too
too
too
deep
in
the
weeds
on
this,
but
does
it
hit
home
on
what
needs
to
be
said
and
then
is
there
anything
that
we
missed?
B
Have
you
heard
some
frequently
asked
questions
or
have
you
had
questions
that
come
up
and
that
we
should
include
in
this
doc
again?
The
goal
was
not
to
make
this
a
400
item
frequently
asked
question,
but
just
the
key
points
that
we
can
share
this
with
somebody
coming
up
so
feedback's,
open,
feedback's,
welcome
and
thank
you.
A
Thanks
yeah,
it
would
be
great
to
get
as
many
eyes
and
hands
on
this
as
possible.
You
know,
as
you
know,
this
community
is
constantly
growing,
there's
more
and
more
people
who
are
entering
the
the
falcon
plus
ecosystem
and
so
we'd
like
to
create
resources
and
and
better
documentation
stuff,
and
so
this
is
one
important
piece
to
ensure
that
we
publish
soon
just
so
that
those
people
that
offer
we
often
see
some
of
the
questions
be
asked.
A
Second
bullet
brief:
shout
out,
we
finally
have
a
playlist
as
of
like,
I
think
the
last
call
actually,
but
not
all
of
you
at
the
last
call,
so
just
want
to
call
it
out
briefly,
but
on
youtube
under
the
falcon
account
on
youtube,
you
can
basically
find
a
playlist
called
the
notary.
Governance
calls
and
everything,
starting
in
february
onwards,
will
be
recorded
and
uploaded
there.
So
you'll
have
access
to
it.
A
The
last
bullet
is
on
the
falcon
plus
day
summit,
so
this
is
currently
now
planned
for
may
11th,
which
is
as
you'll
notice,
also
a
tuesday
and
also
a
day
on
which
we
would
have
had
a
notary
governance
call,
and
that
was
intentional.
A
More
about
farmland
plus
so
sessions
on
the
the
history.
A
The
context
why
it's
important,
where
it's
headed
some
of
the
governance
challenges
we
face
along
the
way
and
the
learnings
that
we've
had
and
then
a
second
category
of
or
a
secondary
goal,
basically
to
serve
as
a
platform
where
people
in
the
community
are
able
to
showcase
work
that
they've
done
so
we've
seen
some
pretty
cool
things
in
the
last
couple
of
weeks
where
people
have
been
shipping
reputation,
systems,
dashboards,
interesting
tools
for
helping
notaries
get
through
faster
andrew
was
even
pinging
people
in
slack
with
stats
on
github.
A
So
these
are
all
really
interesting
examples
of
things
that
we're
doing
together
as
a
community
to
improve
our
processes
and
our
efficiency,
and
so
it
would
be
great
if
we
you
know,
can
use
this
as
an
opportunity
to
effectively
bring
this
in
a
shared
context
with
sessions.
And
so
a
lot
of
you
have
been
very
active
and
I'm
sure
a
lot
of
you
would
have
great
ideas
and
suggestions
for
topics
and
things
you'd
like
to
share.
So,
as
we
figure
out
like
what
the
schedule
would
look
like
and
things
like
that.
A
Please
reach
out
to
me
on
falcon
slack,
we're
going
to
be
starting
the
the
process
of
curating
and
like
identifying
like
what
needs
to
happen
and
what
the
what
the
day
may
look
like,
and
so
the
ask
to
you
is
think
about.
If
either
of
those
topics
is
interesting
to
you
like
either
doing
a
session
on
education
or
showcasing
your
experiences
or
tooling
and
work
that
you've
done,
and
then
let's
get
it
in
to
our
planning
for
what
this
summit
could
look
like.
A
Hopefully
this
will
be
the
first
of
many
summits
as
well
so,
but
we
definitely
want
this
to
be
a
nice
solid
start
to
the
the
way
in
which
you
know
falcon
plus
will
move
forward
cool
notary
updates.
So
this
is
a
action-packed
session
in
in
my
opinion,
for
today
the
first
is
just
covering
data
cap
movements.
A
It
looks
like
you
know,
especially
with
xn
matrix
publishing
their
guidance
and
1475
and
fembushi
having
a
lot
more
traction
with
with
applications
in
china
and
then
just
in
general
note
readers
responsiveness
going
up
on
github
we're
seeing
that
data
cap
allocations
are
going
up.
A
Two
notaries
are
still
blocked,
so
masaki
navatani
from
border
college,
japan
and
math
wallet
are
still
blocked,
but
I
have
good
news,
which
is
that
both
the
messages
that
will
unblock
them
are
now
with
roorkee
holders
as
of
this
morning,
and
so
hopefully
it
should
be
another
day
at
most
until
the
unblocked,
and
at
that
stage
every
notary
should
be
able
to
be
making
allocations
and,
in
general,
just
looking
at
some
some
highlights
in
the
last
week,
and
this
is
something
I'd
like
to
start
tracking
with
historicity
as
well,
and
so
we
can
aggregate
our
output
as
a
community
over
the
next
several
months
but
yeah.
A
I
just
looked
through
the
github
issues
and
a
couple
of
the
applications
that
were
coming
in
it
looks
like.
Last
week
we
had
10
allocations
could
go
out.
There
were
about
20
applications
that
were
closed.
10
of
them
were
closed
because
of
timeouts
or
our
clients
acknowledging.
There
was
an
accidental
application,
but
half
of
them
were
valid
applications
that
were
grounded
data
cap
and
then,
during
the
same
period
time
about
15,
new
applications
came
in,
and
so
ideally
we
want
this
number
to
be.
A
So
thank
you,
notaries,
for
those
of
you
that
have
been
stepping
up
being
more
proactive,
doing
a
better
job,
ensuring
that
people
that
are
applying
are
getting
data
cap
and
that
note
I
also
wanted
to
have
a
little
bit
of
a
discussion
on
what
it
meant
to
like,
be
an
effective
notary
in
the
ecosystem,
especially
how
it
pertains
to
like
elections
and
things
like
that
as
well
in
the
future,
but
just
scoping
the
conversation
to
like,
like
what
we
consider
as
like
active
notary
practices
or
good
notary
practices.
A
I
put
down
a
couple
of
bullets,
but
really
this
is
more
as
a
prompt
to
get
the
conversation
going,
especially
with
other
notaries,
but
also
the
rest
of
you
in
the
community
who
are
watching
and
learning
from
the
experiences
of
the
notaries.
So
for
me,
I
think
a
good
or
active
notaries.
You
know
somebody
is
responsive
on
applications
such
that,
like
the
time
it
takes
for
a
client
to
get
data
cap
is
reduced.
A
Somebody
is
actually
actively
making
allocations
and
allocation
decisions
and
is
also
finding
ways
to
improve
decisions
in
the
processes
around
governance
for
falcon
plus.
This
is,
of
course,
a
very
basic
description
of
what
I
think
would
describe
like
a
good
active
contributor,
as
a
notary
in
the
ecosystem.
I'd
love
to
hear
some
more
answers.
I
know
many
of
you
been
doing
thinking
around
like
how
we
can
be
more
effective
as
notaries.
A
A
I'd
love
to
hear
if
there
are
any
other
thoughts
on
this
particular
topic,
because
I
think
this
will
become
an
important
thing
for
us
to
align
on,
as
we
think
about
like
the
next
round
of
notice
that
we'd
like
to
bring
in
so
on
that
note,
I'd
like
to
open
up
the
phone
for
a
few
minutes
and
see
if
there
any
ideas
or
thoughts,
especially
from
other
notaries,
on
how
they'd
like
to
define
what
active
and
good
notary
practices.
D
E
Yeah,
okay,
so
like
so
so.
For
the
first
point,
the
time
to
data
cap,
I
mean
it's
quite
hard
for,
for
others
to
define
it,
especially
for
for
some
cases
that
we
have
encountered
to
today,
yeah,
because
for
some
of
the
applications
they
just
opened
the
issues
on
github
and
so
like
based
on
the
guideline,
we
required
them
to
like
send
us
some
materials
to
us,
but
it
takes
a
lot
of
time
for
them
to
like
prepare
all
those
materials.
A
Yeah,
I
agree
with
that,
because
the
the
amount
of
time
that
they
take
to
respond
to
your
questions
is
really
what
will
be
perhaps
the
longest
like
factor.
But
I
think
the
maybe
what
we
measure
is
like.
A
I
don't
think
this
needs
to
be
like
a
strict
metric,
but
one
of
the
things
that
we
were
talking
about
in
the
last
call
was
like.
Oh,
what's
the
reasonable
amount
of
time
for,
like
a
notary,
to
respond
to
a
client
application,
then
what's
a
reasonable
amount
of
time
for
the
client
to
respond
back,
because
at
that
stage
we
should
also
do
a
more
active
effort
of
just
like
closing
out
issues
like
just
looking
at
our
repo
right
now.
A
I
think
the
issue
count
is
like
in
in
the
mid
60s,
which
is
quite
high,
and
a
lot
of
them
are
basically
clients
that
are
taking
like
a
lot
of
time
to
get
back
to
questions
that
are
being
asked
from
notaries.
And
so
we
we
talked
about
like
maybe
like
a
reasonable
amount
of
time
for
no
tree
to
respond,
is
like,
in
the
magnitude
of
like
a
week
like
three
to
five
days.
A
Kind
of
a
thing,
and
then
a
client
should
also
respond,
maybe
a
in
a
similar
or
maybe
like
two
weeks
ish,
and
if,
in
that
stage
they're
not
responding,
then
it
might
be
worth
like
closing
out
the
issue
but
yeah.
I
agree
with
you.
I
think
the
the
measurement
and
like
the
way
we
should
track
this
from
a
notary
perspective,
is
the
responsiveness
of
the
notary.
A
E
Yeah
yeah,
especially
like
when
we
contact
the
clients,
we
use
the
email,
so
I
mean
it's
very
hard
to
track
that,
if,
like
everyone
doing
that
on
github,
they'll
be
like
trackable,
but
I
mean
like
for
some
clients
they're
like
we're
not
used
to
like
using
github
like
especially
for
some
early
cases.
Like
I
I
like
I
write,
I
wrote
the
I
wrote
them
on
on
the
github
to
like,
let
them
to
provide
me
and
like
email
address
and
like
after
a
month
or
two
months.
A
E
A
F
Something
here
because
I
think
it's
an
interesting
point
where
I
kind
of
like
the
entire
diligence
process
currently
is
built
on
github
per
default
is
open,
and
you
know
kind
of
like
one
of
the
core
principles
of
the
program
is
that
it's
an
open
program
and
sort
of
like
you
know
we
should
you
know
we
should
pay
it
forward
with
trust.
So
I
think
for
that-
and
you
know
like
it's
interesting
to
think
through.
You
know
basically
we're
in
this.
F
You
know
infancy
stage
where
many
of
these
different
clients,
you
know
effectively.
Are
you
know
people
like
like
like
like
ourselves
so,
probably
mostly
technically
minded,
but
as
we
kind
of
grow
as
an
ecosystem,
we'll
you
know
have
many
more
people
that
may
not.
You
know
either
want
to
engage
on
github
or
it
cannot
engage
on
github,
so
there
may
be
some
abstraction
or
some
kind
of
tooling.
F
That
needs
to
be
built
over
the
long
term,
but
I
think
one
thing
that
I
just
wanted
to
mention
in
in
in
relation
to
like
the
prior
comment
is
that
you
know,
I
think
it's
it
totally
makes
sense
to
actually
also
engage
sort
of
like
offline
as
a
not
in
the
open
and
public
and
kind
of,
like
you
know,
have
a
meeting,
but
I
think
it's
important
to
document
that
and
then
sort
of
like
as
a
notary.
F
If
you
engage
in
a
meeting,
if
you
I
know,
had
an
email
conversation,
you
know
set
the
expectation
that
that
you
know
is
to
be
made
public,
or
at
least
parts
of
that
should
be
public,
and
then
that
is
manifested
on
github.
I
think
sort
of,
like
expectation,
should
be
that
the
notary
you
know,
if
he's
if
he
or
she
is
serving
clients
that
are
not
native
to
github
or
don't
want
to
use
github
that
they
they
didn't
kind
of,
like
you
know,
follow
up
and
make
that
trail
visible.
E
It
will
be
like
quite
like
costing
our
time
to
do
that
because
you
know
like
we
had
emails
like
every
day,
and
I
mean
to
ask
materials
I
mean
like
especially
for
us.
We
require
clients
to
send
us
like
a
lot
of
materials
to
us
and
so
forth
for
some
reason
they
need
to.
I
mean
to
send
us
the
materials
again
again,
because
we
are
not
satisfied
with
some
of
the
matters
they
have
sent
us
sent
to
us
yeah.
So
I
mean
it's.
A
G
F
Okay,
I
was
just
going
to
maybe
push
back
a
little.
You
know,
I
think
you
know.
F
Yes,
you
have
sort
of
like
a
diligence
process
that
is
in
an
email
chain
and
you
may
kind
of
like
have
a
conversation
that
is
on
on
sort
of
like
a
video
or
so
maybe
even
a
person
who
knows,
but
I
do
think
you
know
again,
given
that
it's
an
open
program
and
given
that
we
have
to
pay
for
it
as
trust
you
know,
maybe
this
becomes
less
important
over
time
as
there's
motivation,
more
automation
and
more
tooling
available
that
you
know
eases
that
you
know
burden
or
workload
for
you
as
a
notary,
but
I
still
think
it's
important
specifically
in
the
current
stage
to
you
know:
try
to
pay
it
forward
with
trust
and
really
kind
of
like
make
that
as
public
as
possible.
F
So
I
don't
think
in
probably
it
won't
be
necessary
to
really
document
the
entire.
You
know
email
chain
or
whatever,
but
maybe
you
know
it
could
be
even
sort
of
like
I
talked
you
know
it
could
be
sort
of
like
a
comment.
I
talked
to
this
person
in
person
or
via
video.
F
You
know
answered
these
three
key
questions
and
that's
it,
but
I
do,
but
I
do
you
know,
think
it's
important
that
the
majority
of
what
it
is
kind
of
like
there's,
a
there's,
a
there's,
a
trail
that
is
visible.
That
folks
can
look
at
as
opposed
to
kind
of
like
you
know
that
just
happening
in
the
dark.
E
Yeah
sure
I
think
we
can
do
that.
I
mean
just
like
having
comments
on
the
github
that
we
like,
like
I
said
we
had
have
already
contacted
them
and
like
it's
in
process,
so
we
can
totally
do
that
yeah
without
like
putting
any
records
on
it
if
like.
If
a
community
requires
us
to
do
to
like
prove
that
we
are
like
we
did
like
email
them
like.
We
can
also
prove
that
and
like
put
record
on
it
is
okay
for
us,
but
it's
on
request.
A
Yeah,
I
think
that's
reasonable.
Maybe
the
starting
point
then,
is
just
putting
a
comment
that
says
we
restart
over
email
and
we're
waiting
for
a
response
and
then,
if
further
documentation
is
asked
because
we
want
to
like
based
on
how
the
client
is
behaving.
Maybe
right,
then,
on
that
basis,
maybe
like
a
screenshot
of
some
of
the
emails
might
be
helpful
but
yeah.
E
A
Yeah
right,
perfect,
andrew.
G
Yeah
sure,
I
think
that's
awesome
conclusion
totally
agree
with
all
the
sentiment
there
about
pushing
towards
transparency
and
and
making
it
open,
but
I
wanted
to
actually
come
back
to
the
time
to
data
cap
piece
because
one
of
the
important
pieces
I
I
think
that
was
a
something
that
I
initially
had
proposed
and
if
you're
working
in
github
it
there
should
be
ways
that
we
could
parse
out
whether
the
time
was
with
the
client
or
the
notary,
but
at
the
end
of
the
day,
I
don't
think
it
matters,
because
I
think
the
purpose
of
measuring
this
isn't
always
to
measure
the
quality
of
the
notary.
G
It's
to
measure
the
quality
of
the
onboarding
experience,
and
if
that
time
to
data
cap
is,
is
really
high
and
not
coming
down
over
time,
then
we're
doing
a
bad
job
so
tracking
this
through
time,
I
think,
is
going
to
be
important
and
not
thinking
of
it
as
like.
Oh
my
time
to
data
cap
is
really
high
and
everybody
else
is
really
low.
This
is
a
measure
of
how
bad
I
am
compared
to
everybody
else.
G
Is
a
measure
of
us
as
notaries
and
improving
the
file
coin
onboarding
ecosystem
through
time
and
are
the
decisions
we're
making
on
these
calls
and
on
github
improving
that
time.
We
need
to
measure
that
and
so
yeah.
I
just
think
that
we,
I
think
we
need
to
collect
it
and
actually
like
and
collect
it
someplace
on
github
or
elsewhere,
where
we
can.
We
can
track
that
through
time
across
all
the
notaries.
A
Yeah,
I
think
I
think
that
generally
makes
sense,
and
I
think
I
think
most
people
are
supportive
of
that.
I
actually
really
thought
it
was
good
andrew.
You
were
posting
for
a
couple
of
days.
You
know
like
the
average
sort
of
issue,
stats
and
stuff
as
well.
I
thought
it
was
great,
but
I'm
also
not
a
notary
and
so
I'd
I'd
love
to
hear
opinions
from
from
other
notaries.
A
G
Other
thing
is
like:
if
we
just
start
posting
it
and
start
putting
our
eyes
on
it,
we'll
start
improving
that
measurement
and
say:
okay.
What
other
tools
do
we
need
to
make
that
measurement
more
accurate
to
collect
the
different
dimensions
of
it,
but
we
have
to
start
somewhere
and
so
yeah.
I
think
the
key
thing
is.
We
can't
use
this
measurement
as
a
measure
of
quality
of
the
notary.
We
just
need
to
use
this
measurement
as
the
quality
of
the
onboarding
experience
for
the
clients
and
start
and
start
improving.
It.
A
A
Questions
yeah
so
we'll
address
that
right
in
the
below
this
and
talk
a
little
bit
about
it:
okay,
yeah!
So
all
right,
maybe
doctor,
and
let's
give
the
room
like
a
minute
or
two
to
see
if
there
any
other
topics
on
on
this
particular
section.
And
then
let's
chat
about
that.
Okay,
thanks
cool!
Okay!
Let's
talk
about
this
concept
of
an
election,
so
the
first
time
we
did
this.
We
opened
up
like
an
application
form
where
we
had
about
30
applications
or
something
like
that.
A
I
think
it
was
like
30,
32
or
36..
One
of
them
was
a
repeat
application,
which
is
from
the
falcon
foundation,
but
all
the
other
applications
are
new
and
the
only
reason
we
had
a
repeat
was
because
we
had
done
some
testing
and
needed
to
make
sure
that
the
flows
were
the
interesting
thing.
A
A
You
should
get
the
chance
to
apply
once
every
you
know
x,
amount
of
time
which
is
deemed
reasonable
either
based
on
like
outstanding
data
cap
or
like
a
schedule
or
whatever.
We
think
the
appropriate
process
is
and
there's
a
there's
a
bunch
of
conversation
around
this
in
like
the
december
january
time
frame,
I
think
it's
like
issue
number
76
is
something
where
people
going
back
and
forth
on
how
to
time
like
concepts
like
collections,
but
in
general,
like
one
thing
that
I
think
we've
learned
through
this
process.
A
Is
that
there's
not
a
lot
of
there's,
not
a
lot
of
like
consistency
in
the
rate
at
which
the
data
cap
gets
allocated
across
the
board.
Of
course,
people
have
different
due
diligence
processes.
Client
demands
are
different.
We've
also
learned
a
lot
about
how
to
do
due
diligence,
I
think,
and
and
processes
that
become
more
efficient
over
time,
but
yeah
like
in
general.
A
It
it's
been
relatively,
like
high
variance
like
we've
got
notice
today
that
have
run
out
of
data
cap,
and
then
we've
got
notice
that,
because
of
like
technical
issues,
haven't
even
started
issuing
data
cap
and
so
having
like
this
like
blanket
sort
of.
Oh,
we
need
to
do
a
round
of
elections,
and
everybody
needs
to
regardless
of
whether
or
not
they're
existing
and
need
to
get
a
top-up
versus
those
that
want
to
be
electronics.
A
New
notaries
need
to
go
through
the
same
system
on
the
same
schedule
and
like
all
data
cap
is
like
blocked
on
this
to
me,
doesn't
feel
like
the
most
effective
and
efficient
path.
So
I
have
some
ideas
that
I'd
like
to
propose,
but
before
I
do
that,
I
wanted
to
hear
if
there
were
any
already
from
from
other
notaries
other
members
of
the
community
in
the
room.
H
Yeah,
I
think
probably
starting
the
new
application
process
would
make
more
sense
because,
like
you
said
it's
it's
consistency,
it
would
be
an
issue
if
you
know
like
you
know,
how
do
you
validate
the
same
notary
keeps
on
getting
more
database,
I
mean,
what's
the
consistency
in
criteria,
so
probably
starting
a
new
application
process
will
make
make
more
sense.
Yeah.
A
And
the
the
rubric
today
does
have
a
row
for
like
retroactive,
like
accounting
for
for
previous
activity
is
a
notary.
Basically.
So
if
you
like
effectively
allocated
some
amount
of
data
cap
in
the
past,
then
you
get
like
additional
points
in
your
app,
and
so
the
likelihood
of
getting
re-elected
also
continues
to
increase.
What
the
gating
sort
of
criteria
in
the
first
round
of
elections
was
like
this.
A
We
pick
the
election
based
on
like
some
metric
that
we
agree
on,
like
you
know
the
amount
of
data
cap
that
exists,
and
then
we
just
keep
increasing
the
number
of
notaries
that
are
that
that
we
strive
for
in
each
region,
so
right
now,
for
example,
that
we'd
started
with
the
number
three
and
then
because
of
ties
they're
more
than
three
in
in
china
and
north
america,
but
in
general
they're.
Three
note
race
is
the
conversation
then
that
oh
like
once
we
get
to,
like.
I
don't
know
ten
percent
of
remaining
data
cap.
A
A
Cool
any
other
opinions
on
that
would
love
to
hear
okay.
So
I
think
that
definitely
is
one
one
part
that
we
should
consider
going
down
and
was
probably
like
the
original
part
that
we
had
in
mind
in
many
ways,
and
so
I
think
that
is
reasonable
and
makes
sense.
A
Like
couple
of
calls,
I
think
at
some
point
you
know
somebody
raised
that
like
for
whatever
reason
data
cap
allocations
in
china
were
going
slower,
but
I
think
that
should
be
solved
now,
given
all
the
all
the
notaries
that
come
online
and
have
very
clear
guidance
and
principles
at
this
stage,
but
it
does
show
that
you
know
at
some
stage
where,
basically,
europe
is
effectively
run
out
of
data
cap
and
other
regions
is
just
starting
to
deploy
data
cap
that,
like
doing
this
selection
process
as
on
on
across
the
world
basis,
may
may
not
work
or
but
but
at
the
same
time
we
don't
want
to
create.
A
Like
data
cap,
disparity
where,
like
a
region,
is
favored
just
because
notaries
were
getting
rid
of
data
cap
like
faster,
and
so
I
don't
know
what
the
right
like.
I
don't
know
what
the
right
measure
is
for
when
we
should
kick
off
a
new
election.
My
initial
instinct
was
to
propose
something
around
percentage
of
remaining
data
cap
between
like
what
was
allocated
in
the
last
round
and
what's
left,
but
I'd
love
to
hear
the
other
opinions
on
this.
F
Yeah,
I
was
just
thinking
because
from
like
a
purely
technical
point
of
view,
it's
kind
of
difficult
to
align
everyone
on
sort
of
like
a
new
top
update,
because
we
can't
yet
top
up
addresses.
Is
that
correct.
E
E
A
Add
that
fib
12
was
passed
last.
E
A
So
that
was
the
other
point
of
talking,
for
this
bullet
was
that
drop-offs
are
going
to
be
supported.
It's
come
up
in
the
implementers.
Think
lotus
is
agreed
on
a
schedule
to
implement
it
by
the
next
actors,
update,
which
is
slated
for
I
think,
sometime
in
june,
at
this
point,
and
I'm
I'm
still
waiting
to
hear
what
the
plans
are
from
some
of
the
other
implementations
but
yeah
it
will
be
supported
in
the
near
future.
But
not
for
this
round
of
elections
is
my
guess.
F
Got
it
because
you
know
once
kind
of
like
that
happens,
we
can
kind
of,
like
think
through,
like
developing
a
more
flexible
framework
that
is
more
individualized
on.
You
know
like
if
a
notary
say
you
know,
drops
below
20,
then
he
or
she
can
just
flexibly
reapply
and
then
maybe
there's
ways
to
kind
of
like
batch
it
to
make
sort
of,
like
the
workload
more
more
easily
more
easy
for
for
the
folks
that
are
evaluating
these
applications
or
these
top
ups.
F
But
I
think
until
then-
we'll
probably
I
you
know,
I
think
it's
a
great
idea
to
kind
of
like
you
look
at
the
total
percentage
of
data
cap
spend
on
the
notary
side
or
across
all
notaries,
and
take
that
sort
of
like
as
a
point
to
kind
of
at
least
start
the
process
right,
because
I
think
it
also
takes
some
time,
and
I
think
maybe
it's
worthwhile
talking
about
that
process
as
well
and-
and
I
think
sort
of
like
the
second
thing
that
we
could
do
just
to
get
a
pulse
on
on
you
know,
what's
happening
within
the
notary
community
is
to
like
just
you
know,
maybe
have
a
slack
paw,
perhaps
on
a
kind
of
like
you
know,
it
seems
like
there's
a
lot
of
velocity,
less
velocity
or
a
lot
of
just
you
know
velocity
just
to
get
a
sense,
for
you
know
how
fast
people
are
spending
their
data
caps
as
notaries.
F
A
F
Yep,
I
think,
maybe
also
we
can
start
thinking
about
just
from,
like
a
purely
you
know,
less
from
like
an
individual,
but
purely
from
like
a
program
perspective
or
like
a
file
coin
project
perspective,
you
know
what
do
we
want
to
avoid?
F
What
we
probably
want
to
avoid
is
that
we
run
out
of
available
data
cap
in
a
certain
geography
and
very
specifically
those
geographies,
where
you
see
a
lot
of
demand
from
clients,
so
we
should
somehow
kind
of,
like
you
know,
be
flexible
towards
sort
of
like
the
broader
demand
you
know,
and
I
think
we
should
align.
F
A
Yeah,
I
think
what
one
manifestation
of
that
was.
Basically,
you
know
once
certain
notaries
and
regions
were
running
out
of
data
cap,
the
call
was
effectively
made
that
other
notaries
in
other
regions
were
supporting
taking
applications
from
there,
and
so
we've
seen
sort
of
the
the
region
based
boundary
in
some
cases
hasn't
really
been
held
as
strongly,
and
that's
probably
a
good
thing,
because
it
is
unblocking
useful
development
and
usage
of
the
network,
and
so
it
also
makes
me
like.
A
I
understand
why
it's
important,
like
it
is
important
to
have
geo
distribution
in
our
notary
selection,
but
the
the
the
individual
policies
that
each
notary
chooses
to
uphold
in
terms
of
the
geographies
that
they
choose
to
serve
in
terms
of
incoming
client
applications
will
also
influence
this
pretty
substantively
right
and
then
there
was
also
this
whole
element
of
certain
notaries
prioritizing
and
serving
specific
types
of
use
cases,
and
that
sometimes
requires
additional,
like
engineering
work
to
be
done
so
like
kiko,
is
a
notary
still
working
on
figuring
out
how
they
want
to
do
their
automated,
like
multi-sig,
sort
of
solution
for
online
websites
being
built
and
as
a
result,
there's
no
allocation,
and
so
that's
that
also
leads
to
some
interesting
and
and
sort
of
difficult
to
build
a
general
purpose
solution
around
without
like
generalizing
or
simplifying
the
problem
quite
a
bit,
and
so
I
guess
the
the
sort
of
ultimate
like
question
here
is
like.
A
Can
we
align
on
a
simplification
that
we
think
is
reasonable,
that
we
then
use
as
a
a
process
and
a
method
to
continue
to
make
progress
in
this
direction?
Charles
you
mentioned
that
it
seems
any
region
needs
to
onboard
more
clients.
Do
you
mean
in
terms
of
like
in
general,
there
are
more
clients
than
any,
or
do
you
mean
that
any
applications
are
not
going?
No.
D
No,
no,
sorry,
sorry,
it's
not
an
unclear
sentence,
I'm
not
saying
that
should
give
more
clients.
It
means
that
the
ecosystem
side,
the
entire
ecosystem
in
the
north
america
may
be
needed
to
working
a
little
bit
to
find
the
more
rare
customers
who
is
willing
to
save
data
on
the
frago
network.
So
I
I'm
talking
with
lots
of
friends
and
enterprise
locally.
D
A
common
scenario
is
that
they
have
data,
but
there's
a
concern
about
the
security
and
the
privacy,
because
I
don't
know
how
is
in
other
regions,
but
in
north
america,
while
talking
with
them
about
videos
and
some
content.
They
really
worry
about
about
the
copyright,
because
if
you
save
the
content
on
the
virtual
network,
it
basically
is
open
to
the
public.
Everybody
can
retrieve
it
from
the
fractal
and
the
pay
for
by
far
coins,
but
when
they
pay
by
five
points,
this
thing
is
maybe
defined
as
a
commercial
behavior.
D
So
some
videos
like
they
get
from
youtube,
was
not
a
them,
may
be
evaluated
as
the
lessons
so
a
copyright,
but
if
they
are
using
their
own
data,
then
they
are
not
another
limitation.
Is
the
data
usually
like
if
they
encrypt
it?
I
don't
know
how
to
pass
the
notary
verification
and
also
when
they
split
it
on
different
miners.
D
This
is
also
considered
about
existing
enough.
So
this
is
something
like
I
try
to
convince
him:
it's
safe
to
save
the
fry
coin,
and
but
they
still
have
doubts
so
there's
some
difficulties
that
currently
encounter
when
trying
to
onboarding
customers.
A
That's
a
great
feedback,
I'm
I
yeah.
I
think
that
it
makes
sense.
I've
heard
similar
one
of
the
conversations
I've
had
with
people
along
those
lines
has
been
that
they're
also
welcome
to
encrypt
this
stuff
that
they
put
onto
the
network
but
yeah.
I
think
it's
a
good
point
there.
There
is
space
in
the
spec
for
like
things
around
like
content
policy
in
terms
of
service
and
stuff,
but
I
think
some
of
those
areas
have
not
been
fleshed
out
as
well.
Yet.
D
So
my
question
is
that
so
because
I'm
the
miner
of
north
america
right
so
I'm
not
I'm
not
sure
how
to
define
myself,
but
when
I
was
onboarding
those
customers.
I
think
I'm
more
like
a
boarding
agent
or
something
like
that.
So
I
kind
of
needed
some
help
of
lawyer
about
the
something
related
to
the
law,
the
local
law,
those
kind
of
help.
So
I
have.
D
That
look
this
copyright,
if
you
are,
if
you
are
using
this
for
education
or
other
purpose,
is
safe
or
something
like
that,
and
this
is
this
kind
of
a
legal
service.
Health
nurseries
foundation
can
provide
some
help
of
this
or
we
needed
to
find
our
own
lawyer
and
the
prisms
and
consulting
fee
to
do
this
right.
D
A
Yeah
I
I
would
generally
call
this
like
category
of
work
like
business
development,
for
the
network,
which
is
like
bringing
in
more
interesting
use
cases
to
network.
I
think
those
are
very
good
points,
charles
respectfully
they're,
probably
outside
the
scope
of
the
current
conversation,
but
I
do
think
it's
worth
like
talking
about.
Maybe
we
can.
A
We
can
chat
about
a
little
bit
further
on
slack
or
if
other
notaries
would
like
to
get
involved,
but
I
I
would
propose
you
actually
raise
this
as
a
conversation
in
the
film
plus
channel
on
slack
and
let's
get
some
opinions
on
it
to
wrap
up
this
sort
of
conversation.
I
think
the
general
sentiment
is
that
from
what
I'm
seeing
we're,
probably
reaching
a
time
where
we
should
start
the
process
for
another
round
of
elections.
A
If
people
have
thoughts
based
on
the
conversation
we
had
today
on
how
that
election
should
go,
you
know
please
share
them.
I'm
gonna
create
an
issue
on
the
next
round
of
elections,
probably
sometime
this
weekend.
So
we
can
use
that
to
finalize
what
we
believe
is
a
good
process
for
it,
and
it
would
be
great
to
aggregate
some
thoughts
on
that
with
that,
let's
move
over
to
the
set
of
issues.
I've
divided
them
into
two
categories,
this
time,
because
I
wanted
to
just
explicitly
align
on
on
next
steps.
A
So
one
of
them,
so
this
issue
was
filed
about
18
days
ago.
I
think
we
we
talked
about
in
the
last
united
governance
call.
There
was
some
conversation
about
it
on
github
there's
a
lot
of
conversation
about
in
the
lost
governance
call.
The
proposal
is
basically,
it
was
from
andrew
hill
andrew.
A
If
you
don't
mind,
I'm
just
gonna
speak
for
it
in
the
interest
of
time
for
like
30
seconds,
but
the
the
proposal
is
basically
to
get
the
auto
verifier
that
was
shipped
by
infinite
scroll
at
verified.lift.io,
up
from
eight
gigabytes
to
32
gigabytes
of
data
cap,
and
this
is
primarily
increase.
The
amount
of
data
cap
available
for
testing
purposes
make
it
easier
and
faster
for
people
to
get
their
initial
allocation.
A
That
they'd
want
to
get
started
and
just
generally
reduce
the
friction
for
people
that
just
need,
like
a
tiny
amount
of
data
cap
to
validate
like
the
proof
of
concepts
or
validate
things
inside
the
ecosystem,
because
8
gigabytes
just
ends
up
being
way
too
little
and
32
seems
like
a
good
sweet
spot,
where
it's
not
too
much
that
people
will
try
to
abuse
the
system.
A
The
verifier
still
has
like
a
like
a
high
bar,
which
is
like
a
github
account
that
needs
to
be
open
for
more
than
half
a
year,
and
they
can
only
get
that
bunch
of
data
gap
like
once
a
month,
etc,
and
so
the
reception
to
this
proposal
was
incredibly
positive
last
week.
A
So
in
the
last
call,
which
is
two
weeks
ago,
I
haven't
seen
anybody
flag
any
issues
on
github
other
than
let's
figure
out
how
we
can
do
this.
What
I'd
like
to
just
open
up
the
flow
for
one
minute
effectively
is:
does
anybody
think
this
is
not
a
good
idea,
because
if,
if
we
were
generally
aligned,
I
think
we
need
to
start
moving
forward
towards
implementing?
A
We
have
a
lot
of
proposals
in
general.
In
the
ecosystem,
and
so
just
moving
towards
implementing
on
a
few
of
these,
that
we're
aligned
on
is
something
I'd
like
to
push
for,
and
I
think
this
might
be
a
really
good
one
that
we
can
pursue
in
the
coming
week,
and
so
before.
We
get
that
sort
of
wanted
to
just
open
the
floor
up
for
any
other
opinions
that
weren't
accounted
for,
or
anybody
thought
that
we
should
reconsider
this
as
a
community.
G
Maybe
I'm
very
pro
this
obviously,
but
maybe
we
can
do
it
also
as
an
experimental
period
of
time
and
have
them
measure
try
to
measure
how
much
people
try
to
game
at
and
we
can
review
it
over
in
some
near
and
decide
to
continue
it
or
not.
You
know
yeah.
A
I
think
that
sounds
like
a
that
sounds
like
a
reasonable
idea.
I
don't
think
jonathan
schwartz
is
in
this
call.
It
would
have
been
good
to
just
get
his
opinion
on
whether
or
not
that
would
be
difficult,
but
I
think
that's
that's
a
good
point,
I'll
andrew.
If
you
want
to
flag
it
in
the
issue,
that's
probably
a
good
suggestion.
A
I
was
also
going
to
propose
that
he
goes
and
updates
his
notary
application
with
the
expected
changes,
because
there's
no
reallocation
strategy
fundamentally
is
going
to
change
from
his
original
allocation
and
so
for
transparency
and
tracking
purposes,
like
I
view
that
as
a
blocker
to
him
changing
this,
but
it
seems
like
we're
generally
aligned.
This
is
an
experiment
worth
running,
and
so
I
think
we
should
proceed
with
the
next
steps
of
this.
A
Let's
talk
about
open
issues
and
last
time
we
went
in
this
order
and
we
ended
up
not
having
as
much
time
for
the
governance
one.
So
I
proposed
we
go
in
inverse
order
so
for
the
governance
sort
of
section
that
I've
put
here,
the
issues
relating
elections
and
data
cap
top-ups
et
cetera.
I
think
we've
sort
of
had
good
conversation
about
that
in
the
previous
section
of
this
column,
so
I
have
nothing
further
to
flag
there.
A
I
wanted
to
give
nelson
or
nsc
dash
phil
the
floor
to
chat
a
little
bit
about
their
proposal.
105.
I
Yeah
hi,
so
I
basically
came
up
with
this
idea
only
because
we
had
a
major
dispute
as
minors
in
terms
of
self-dealing
the
data
cap.
So
we
need,
I
think,
it's
it's
imperative
for
the
community
as
a
whole,
not
just
the
file
plus
community
to
to
have
to
voice
their
opinions
on.
You
know,
violations
of
rule
rules
in
general
first
and
then
also
violations
of
rules
and
how
we
handle
them.
I
So
one
suggestion
that
I
think
deep
you
put
put
into
the
github
was
to
use
the
phil
paul
method
to
get
to
do
ball,
polling
to
to
get
the
general
opinion
of
and
the
majority
of
community
members
on
issues
and
also
how
to
maybe
rectify
or
penalize
people
who
who
have
broken
the
guidelines
or
the
rules.
I
I
I
think
it's
one,
one
of
the
things
that
I'm
finding
difficult
is
to
to
really
figure
out
what
the
the
actual
guidelines
for
use
of
data
cap
or
from
a
minor's
perspective.
There's
no
real,
you
know
like
anything
written
down.
No.
This
is
pretty
much
discussions
in
different
places,
slack
and
github,
so
it
would
be
good
to
have
a
one
place
where
everybody
could
understand
what
their
roles
are
and
the
guidelines
to,
and
also
the
ramifications.
If
those
guidelines
aren't
aren't
handled
properly.
A
Yeah
and
just
to
share
some
additional
contacts
doesn't
correct
me
if
I'm
wrong,
but
this
the
the
conversation
that
you're,
referring
in
the
context
around
like
guidelines.
A
This
primarily
came
up
because
there
were
cases
in
which
people
were
both
clients
and
minors,
and
so
this
is
not
like
the
self-dealing
conversation
of
your
notary,
but
rather,
if
you
allocate
to
data
capture
client
that
then
goes
and
stares
like
stores
that
data
with
themselves,
you
effectively
have
like
a
world
where
the
the
network
is
subsidizing,
somebody
for
something
they
already
have
on
on
the
hard
disk,
etc,
but
at
the
same
time,
it's
important
to
ensure
those
valuable
use
cases
being
brought
into
the
network,
and
so
the
conversations
we
had
in
the
past
were
like
what
is
the
reasonable
degree
to
which
that
should
be
supported.
A
I'd
opened
up,
I
think
it
was
like
issue
98.
If
I
remember
correctly,
which
is
like
oh
like
can.
We
propose,
like
some
kind
of
percentage
to
which
this
is
acceptable,
depending
on
the
the
presence
of
miners
in
a
particular
region
where
that
data
needs
to
be
stored,
and
so
there
was
some
active
conversation
on
that.
A
couple
of
weeks
ago,
but
it's
hard
to
arrive
to
decision
on
controversial
topics
like
that,
because
we
don't
have
a
clear
decision-making
sort
of
framework
is
that
is
that
fair?
Is
that
a
fair
okay.
I
Yeah,
that's
that's
how
I
think
it's
it's.
You
know.
The
discussion
is
good
though,
and
I
think
it's
it's
in
different
pockets.
Right
now,
like
you
know,
sometimes
on
slack
sometimes
in
github.
Sometimes
just
you
know
in
dms
and
and
people
have
different,
obviously
very
different
perspectives
and
and
and
understandings
and
sometimes
they.
You
know
there
are
violations,
but
it
may
just
be
out
of
ignorance.
The
point
is
we.
I
We
probably
should
have
a
more
mechanized
method
to
to
to
to
really
hammer
out
what
the
actual
guidelines
are,
for
instance,
if
if
a
client
in
the
case
that
that
this
issue
came
up
for
me,
was
if,
if
a
client
is
also
a
minor
and
then
they
start
to
deal
all
their
data
cap
to
their
own
mining
operation,
there
there's
many
people
who
say:
that's
fine,
that's
just
the
way
the
market
works
and
then
the
other
people
who
say
that
that's
not
fair,
but
in
general,
we've
never
really
done
a
poll
or
a
vote
on
that,
and
so
maybe
some
people
are
doing
it.
I
Some
people
are
not.
I
mean
we
need.
I
think
it's
it's
it's
good
for
the
community
as
a
whole,
not
just
notaries
and
and
people
in
the
file
plus
program,
but
the
popcorn
plus
program.
They
it's
for
us
to
all,
have
a
clear
guideline
on
on
these
details
and
then,
but
also,
how
do
we
enforce
them
when
people
actually
blatantly
violate
the
guidelines
that
we
that
we
came
up
to
came
up
with
as
a
community
yeah.
A
A
Never
mind:
okay,
please
feel
free
to
share
thoughts,
chat
as
well.
If
you
have
them
so
I
think
I,
the
the
second
part
of
your
question,
is
a
little,
I
think
clear
in
my
opinion,
which
is
like,
what's
the
carrot?
What's
the
stick,
then?
A
First,
and
I
think
pretty
much
that
comes
down
to
most
clients
that
have
legitimate
use
cases
need
data
cap
more
and
more
in
the
future,
like
they're,
typically
not
coming
for,
like
a
single
data
cap
allocation,
that's
going
to
serve
their
like
lifetime
need,
and
so
I
think
that
the
immediate
and
easy
stick
is
just
you
don't
get
any
more
data
cap
right
and
that
that's
probably
like
a
really
good
way
to
incentivize
this
behavior.
A
I
don't
know
if
it's
enough,
but
I
definitely
think
it's
enforceable
and
likely
a
good
starting
point
as
a
mechanism
to
incentivize
the
right
right
behavior.
I
think
the
bigger
challenge
is
ensuring
that
everybody's
on
the
same
page
with
what
that,
like
right,
behavior
actually
looks
like
and
so
yeah.
I
I
I'd
love
to
hear
if
there
are
any
opinions
on
mechanisms
driving
to
that.
I
know.
A
We've
got
some
folks
from
the
falcon
foundation
as
well,
philip,
if
you
want
to
speak
to
any
thinking
from
that
end,
or
you
know
at
least
I
would
urge
you
all
to
look
at
issue
105
and
see
if
you
can
propose
any
suggestions
for
for
tactical
next
steps
and
how
we
can
become
more
effective
as
the
as
a
governing
group
and
as
a
community.
I
How
how
do
we
go
about
getting
a
poll
done
officially
like
the
one
that
was
just
done
for
on
the
field
website.
A
That's
a
great
question:
I
have
some
steps.
I
don't
know
how
easy
it
is
for
just
anyone
to
do
it
as
far
as
I
know
it
has
to
like,
they
are
typically
aligned
with
fips.
A
So
I
don't
know
if
this
would
fall
into
the
category
of
fip
or
not
because
it's
just
modifying
like
our
practices
for
program,
but
I'm
sure
that
there's
a
way
nelson,
maybe
you
and
I
can
follow
up
offline
with
some
of
the
some
of
the
people
on
the
implementation
like
side
of
things
who
are
working
on
the
different
falcon
implementations,
because
that's
typically
the
mechanism
they'd
be
using,
and
so
I'm
sure
we
can
find
a
way
to
leverage
that.
B
F
Yeah,
I'm
actually
also
curious,
because
I
know
that
the
the
default
polls
tool
that
was
proposed
or
announced
recently
is
specifically
for
falcoid
network
governance,
but
wouldn't
it
be
possible
to
also
use
it
for
certain
elements
of
the
falcon
plus
program,
or
you
can
just
fork
it
and
use
it
for
it
or
you
have
a
you
know.
Falcon
plus
poll.
I
That
would
have
to
be
probably
also
change,
so
it's
not
just
based
on
power
based
on
sure
and
if
we
want
to
include
we
have
to,
we
should
probably
include
all
all
you
know:
particip
participants,
including
just
node
holders
and
miners.
F
You
know
we
we
would
be
happy
to
to
kind
of
like
fund
that
work
via
dev
crab.
If
someone
wanted
to
fork
it
and
adapt
it
for
falcon
plus.
F
F
A
Fine
for
the
barnard,
okay,
cool,
I
think
that's
that's
an
interesting
concept
and
definitely
something
that
I'd
love
to
see
build
if
possible.
Nelson
thanks
for
pushing
the
conversation
on
this,
the
ask
for
the
community
take
a
look
at
105
think
about
if
we
should
fork
for
the
poll
and
and
how
we
can
make
it
more
effective
as
a
as
a
tool
for
the
falcon
plus
ecosystem
moving
upwards
issue
94.
A
So
I
just
proposed
something
yesterday,
which
I
think
would
be
an
interesting
like
initial
implementation
of
this,
which
is
basically
along
the
lines
of
having
a
massive
like
open
application
format
for
a
client
and
so
like
a
client
that
has
a
use
case
that
requires
greater
than
500
terabytes
of
data
cap
would
apply
using
this
like
more
global
application,
similar
to
a
notary
application
which
should
be
open
for
everybody,
and
anybody
from
the
community
can
help
in
the
due
diligence
process.
A
So,
let's
say
like
an
app
is
open
for
two
weeks
during
those
two
weeks.
Anyone
in
the
community,
any
notary
or
any
community
member
can
ask
questions
of
that
client
and
we
effectively
vet
that
client
together
then
we
use
whatever
you
know,
voting
mechanism
we
choose
or
have
a
conversation
in
a
notary
governance.
Call
that
deems
that
client
to
be
like
worthy
of
like
a
dedicated
data
cap
faucet
and
effectively.
A
That
client
can
then
go
and
ask
for
messages
of
like
100
terabytes
at
a
time
at
most,
like
maybe
per
day
or
per
week,
where
at
least
four
out
of
seven
volunteered
notaries
have
to
sign
on
that
message
for
that
allocation
to
be
made
so
like
combining
some
constructs
of
like
just
multi-stake,
but
also
this
notion
of
like
how
we've
used
root
key
holders
as
executors.
We
can
now
have
no
reasons
executors,
but
also
notaries
that
have
volunteered
to
be
watchful
of
the
clients
anyway.
A
I
don't
want
to
go
super
in
depth
to
this,
because
I
know
we
only
have
about
five
minutes
left,
but
I
did
want
to
briefly
explain
that
and
encourage
people
to
look
at
the
issue.
Julian,
do
you
have
anything
you'd
like
to
add.
C
No,
I
think
it's
it's
a
great
idea.
I
didn't
read
your
your
message
on
slack,
so
so
sorry
on
github.
So
that's
why.
But
I
think
yes,
it's
it's
okay
using
the
multisig.
I
think
it's
a
it's
the
very
good
approach.
C
What
we
just
need
to
tell
to
to
care
about,
maybe,
is
that
this
client
may
need
a
single
point
of
contact
in
a
way
in
in
one
at
some
point
like
we
may
need
to
verify,
I
mean
he
may
need
to
to
have
a
single
point
of
contact
for
not
for
all
his
notorious
question
and
if
we
just
use
the
multisig-
and
there
is
like
seven
people
that
are
just
signing
just
to
to
allocate
the
data
cap,
maybe
this
would
be
not
enough,
like
I
don't
know
if
at
one
point
we
want
to
to,
someone
may
need
to
audit
what
what's
happening
for
this
customer.
A
Okay,
so
then,
maybe
there's
like
one
notary
sort
of
lead
or
champion
sort
of
thing,
like
a
captain,
in
a
way
that
that,
like
volunteers,
to
be
responsible
for
some
of
that
auditing,
as
well
as
being
the
dri
for
communications
with
the
client
and
also
becomes
the
sort
of
main
voice
for
the
remaining
notaries.
Who
may
have
questions
on
like
the
client's
dealings
and
things
like
that,
yeah
yeah,
I
would
like.
I
would
love
if
you
could
add
that
suggestion
in
the
the
conversation
and
and
that's.
C
A
Because
I'd
love
to
sort
of
get
to
a
place
where
we
can
have
like
a
initial
poc
in
the
next
couple
weeks
as
well.
I
know
that
you
know
starling
is
looking
for
massive
data
cap
allocation.
I
know
some
of
the
miners,
as
well
as
the
notaries
like
1475
and
china,
have
been
doing
some
incredible
work
with
business
development
and
brought
on
like
two
or
three
massive
use
cases
that
are
all
looking
for,
like
pebby
bytes
of
data
caps.
A
So
I
think
it's
pretty
good
time
to
be
building
a
mechanism
like
this
yeah.
C
Exactly
and
I
have
sorry
that
just
to
come
back
to
105,
I
just
have
something
to
say
about
that.
You
said
that
maybe
it's
not
going
to
be
a
fit,
because
it's
not
really
related
to
the
protocol,
it's
more
like
how
we
we
manager
of
this
in
education.
I
I
had
a
side
conversation
with
jonathan
and
with
andrew
last
week
and
and
earlier
this
week.
C
I
think
that
if
we
have
like
a
tribunal
or
something
that
to
manage
the
dispute
and
so
on,
they
need
to
be
able
to
to
do
some
action.
So,
and
one
of
the
action
that
could
be
is
that
we
can
remove
the
data
cap
to
someone
who
game
the
system,
and
I
mean
removing
what
is
already
on
chain
on
the
existing
sectors,
like
we
canceled
the
the
the
flag.
That
said
it's
verified,
and
if
we
do
that,
I
mean
I
don't
know
we
need
to
discuss
if
what
people
think
about
this.
C
But
if
we
can
do
that,
then
this
is
going
to
be
a
flip
anyway.
A
Yeah,
that
is
true,
that
is
true,
yeah
interesting
in
the
interest
of
time.
I
would
propose.
Let's
have
that
conversation.
The
issue
I
know,
z,
has
a
hand
up
and-
and
we
should
wrap
up
soon,
thanks
julian,
that
that
is
completely
valid,
plus
one
makes
sense.
Thank
you
see.
How
do
you
have
anything
you
want
to
share.
E
Yeah
so
like
for,
for
this
largely
the
requirements
to
do,
should
we
do
it,
like
I
mean
by
cross-border
or
like
by
by
the
specific
regions,
I
mean
like
if
this
for
the
specific
region
like
so
we
can
like
ask
all
the
data
in
their
regions
to
to.
I
mean
execute
on
that
requirements,
and
I
mean
it
can
like
reduce
the
burden
for
other
notaries
in
other
regions.
So
yeah.
C
A
A
great
question
my
instinct
in
the
proposal,
was
to
have
a
cross-border
like.
I
would
imagine
that
these
are
like
massive
use
cases
that
are
like
fundamentally
game
changing.
You
know
in
the
way
that
they
they
use
the
network
and
stuff
as
well,
and
so
I,
the
initial,
like
proposal
for
me,
is
probably
that
it
should
be
cross-border.
I
don't
think
that
that
needs
to
be
what
happens.
So
I'd
love
to
hear
the
other
opinions,
if
you
think
it's
difficult
to
pull
this
off
cross-border.
A
Please
share
that
in
the
issue.
If
you
think
it's
going
to
be
difficult,
especially
because
of
language
barriers
or
contacts
or
anything
like
that,
I
think
that
that
is
a
valid,
valid
concern
and
we
should
think
about
it.
But
my
initial
suggestion
was
like,
let's
find
a
way
to
ensure
that
it
is
like
a
global
thing,
because,
because
these
kinds
of
use
cases
are
so
big
and
and
often
will,
will
want
to
store
data
and
replicate
it
outside
one
region
for
even
just
redundancy
and
reliability's
sake,.
A
Cool,
I
think,
with
that,
I'm
just
going
to
give
you
know
30
seconds.
If
anybody
has
any
open
topics.
I
know
there
are
two
other
issues
that
flag
day
103
104.
We
we
sort
of
had
the
chance
to
talk
about
these
in
the
previous
call,
not
so
much
in
this
call
andrew
sorry,
we
ran
out
of
time,
but
you
know
please
folks,
take
a
look
andrew
if
you
want
to
talk
about
them
for
30
seconds.
Maybe
the
open
discussion
sort
of
is
a
good
good
space
for
that.
A
A
Yep
cool:
unless
there's
any
other
topics,
I
I
don't
want
to
keep
you
focused
too
late.
Thank
you
so
much
as
usual
for
making
the
time
just
a
super
productive
call,
then
we
covered
a
lot
of
interesting
topics,
so
this
is
great
julian.
Anything
you
want
to
add.