►
From YouTube: Filecoin Plus - Jun 8 Notary Governance Call
Description
Filecoin Plus governance call, in which we discuss recent DataCap allocation trends, clients applications for Large Dataset Notaries, and the ongoing Notary elections.
A
And
we're
off
hey
folks,
welcome
to
the
notary
governance
call
for
tuesday
june
8th,
I'm
just
gonna
kick
off
with
slides
as
usual,
and
I
think
the
focus
this
time
will
pretty
much
be
on
elections
and
and
the
large
data
set
notaries.
Can
somebody
give
me
a
quick
thumbs
up
if
you
can
see
the
blank
black
slide
with
falcon
perfect?
Thank
you
very
much
so
yeah.
Let's,
let's
get
started
again
as
usual.
A
If
you
have
any
questions
or
any
thoughts,
raise
your
hand
interrupt
me
by
unmuting
yourself
drop
something
in
chat.
This
is
an
open
forum.
It's
an
open
conversation!
No
sweat,
don't
perceive
any
friction
of
interrupting
the
flow,
because
this
is
supposed
to
be
a
forum
for
discussion
so
yeah
with
that.
Let's
get
started
so
things
that
I
want
to
talk
about
this
time.
So
we'll
do
a
quick
data,
cap
flow
overview
and
and
delta
from
the
last
time
we
talked.
This
is
become
sort
of
a
fixture
in
our
bi-weekly
calls.
A
As
we
see
the
progress
that
we're
making
as
a
community,
then
let's
talk
about
support
for
logistics
and
notaries
and
not
re-elections,
and
then
we
will
definitely
keep
some
time
for
open
issues
and
discussion.
If
there
are
any
topics
that
people
would
like
to
flag.
A
First
things:
first,
we
finally
had
some
movement,
so,
as
I
called
out
in
the
previous
call,
the
two
weeks
prior
to
the
election
sort
of
application,
do
you
think,
we're
very
quiet.
We
actually
had
zero
applications
accepted
by
notaries
and
people
generally
just
pointed
at,
like
you
know,
thinking
about
applications
and
getting
the
applications
in
order,
and
so
in
the
last
few
weeks,
while
we've
been
doing
scoring,
it
looks
like
some
applications
are
definitely
going
through.
A
So
seven
allocations
went
through
the
repo
with
about
45
stubby
bytes
of
data
data
cap
being
allocated
through
github
there's
a
net
of
two
new
applications.
So
there's
15,
if
you
look
in
the
repo
of
which
13
are
actually
notaries,
that
don't
actually
have
data
cap
because
it's
ran
out
of
it
from
the
previous
election.
A
Of
course,
these
notaries
are
also
some
of
them
reapplying
for
data
cap.
In
this
round
of
elections,
so
that
might
fix
the
problem,
but
it
does
point
to
us
needing
to
figure
out
a
flow
where,
once
notary
runs
out
of
data
cap,
what
happens
to
the
people
that
want
it
to
apply
to
that
notary,
and
so,
if
anybody
has
any
tips
or
suggestions
for
redirection
or
expectations
that
we
should
set
on
notaries
in
terms
of
once,
you
run
out
of
data
cap
like
what
do
you
want
to
do
with
your
open
applications?
A
I
would
love
to
have
that
conversation.
I
know
some
of
you
have
run
into
that
issue
before
and
some
of
you
actually
received
applications
like
masaki
before
he
could
even
approve
them
because
of
bugs
that
we
had
in
getting
him
set
up.
So
I
just
wanted
to
take
a
second
and
see
if
anybody
had
ideas
around
how
we
can
operationalize
or
do
some
more
systematic
readdressing
of
applications
in
the
case
that
it
not
really
can't
serve
an
application.
A
A
So
for
for
those
of
you
that
are
no
juries
in
the
call
the
question
to
you
would
be
in
the
case
that
you
receive
an
application
that
you
can't
actually
address,
whether
that's
because
you
don't
want
to
or
because
you
can't,
what
do
you
think
is
a
reasonable
expectation
the
community
should
have
or
a
client
should
have
and
how
you
redirect
them
somewhere
or
if
you
know
the
conversation
that
you
do
have
with
them
in
terms
of
how
they
can
get
set
up
for
data
cap,
don't
need
to
collect
or
arrive
on
an
opinion
today.
A
It's
just
something
to
think
about
next
up
data
cap
distribution
and
where
it
lies
in
the
flow.
At
the
moment
we
have
775
debbie
bytes
roughly.
I
think
it's
774
or
something
like
that.
But
it's
pretty
close.
You
know
up
a
substantive
amount
and
I
think
I
typo
this
instead
of
50
from
verified
like
left,
it
should
be
350
or
250,
something
like
that.
Go
properly
substantial
amount
from
verified
at
io,
of
course,
because
that's
the
automated
notary
and
I
think
what's
what's
actually
interesting,
is
we
I
think
we
crossed.
A
Actually,
I
remember
seeing
this
so
we
crossed
our
100th
actual
successful
allegation
from
github,
so
verified
like
glyph.io
should
be.
You
know
a
little
bit
less
than
that,
but
congratulations
to
the
community.
It's
kind
of
awesome
to
see
you
know
more
than
100
applications
getting
granted
to
the
github
repo.
A
That's
fantastic
about
30
of
that
data
cap
is
being
used,
11
of
total
to
still
definitely
progress
there
in
terms
of
operationalizing
clients
and
ensuring
that
they
understand
what
to
do
with
it
time
to
date,
a
cap
continues
to
go
down
slightly
so
four
weeks
ago
to
two
weeks
ago
it
was
down
three
hours.
Now
it's
down
about
three
and
a
half
hours,
so
we're
continuing
to
trend
in
the
right
direction.
I
think
ideally
we'd
like
to
get
that
number
substantively
less,
but
it's
still
running
standing
in
the
right
way.
A
So
that's
awesome.
The
auto
close
bot
that
we
had
all
talked
about
a
couple
of
weeks
ago
is
finally
in
operation
and
it's
doing
quite
a
lot
of
work
and
so
are
active
notaries.
So
congrats
to
all
of
you,
folks
that
are
working
together,
because
the
stats
are
looking
a
lot
better
in
terms
of
how
we're
addressing
things,
as
you
can
see,
101
granted
applications
days
to
ground
to
dropping
median
days,
granted
dropping
number
of
issues
open
substantively
less.
A
This
is
a
report
that
I
just
grabbed
from
the
url
that
andrew's
steam
and
textile
maintains
for
just
notary
stats
that
they
publish
but
just
good
to
see
general
reactions
trending
that
I
wait,
of
course,
as
a
notary.
If
you
have
any
ideas
or
suggestions
or
feedback
on
the
tooling
that
is
available
to
you
or
the
the
path
to
giving
data
cap
out
to
clients
and
ways
in
which
we
can
make
it
more
efficient
or
make
it
easier
for
you
or
lower.
Friction
then,
would
love
to
have
that
conversation
anytime.
A
And
if
you
have
specific
ideas
on
how
to
improve
it,
then
please
feel
free
to
kick
off
an
issue,
and
we
should
definitely
have
that
conversation
because
we're
still
pretty
young
in
this
community
we've
got
quite
a
ways
to
go,
and
we've
got
big
ambitions
in
terms
of
making
the
network
useful
and
so
working
together.
To
do
that,
especially
at
these
early
stages.
To
make
you
operationally
efficient
should
be
a
priority
actually
before
we
head
on
to
this.
Are
there
any
questions?
A
I
think
we
should
just
move
on
to
that.
That's
all
good!
Let's
do
it
so.
Last
time
we
had
our
first
conversation
around
the
large
data
set
notaries.
So
quick
refresher
for
those
of
you
that
are
new
to
the
concept.
A
The
idea
was
basically
proposed
in
issue
number
94,
which
is
labeled
onboarding
projects
with
large
data
cap
requirements,
and
the
idea
was
we
needed
to
come
up
with
a
way
that
we
could
support
open
public
data
sets
that
were
meant
to
be
detailed
by
anyone
at
scale
with
so
we
initially
targeted
a
range
of
between
500
heavy
bytes
to
five
per
bytes
of
data
cap
and
clients
could
apply
on
a
per
project
or
per
data
set
basis
for
that
amount
of
data.
A
Cap
and
seven
notaries
would
effectively
volunteer
or
will
volunteer
themselves
to
be
signers
on
a
multi-sig
notary.
That's
established
for
that
specific
client
request,
and
so
there's
a
repo
that's
been
stood
up.
You
may
have
seen
applications
already
coming
in.
You
may
have
also
seen
that
we've
been
doing
some
testing
with
the
bot
because
we're
trying
to
set
up
the
bot
the
same
way.
A
We
have
it
for
today's
flow
for
setting
up
a
notary
as
well
as
managing
and
facilitating
client
onboarding,
and
so
hopefully
you
know
we
can
do
make
progress
on
that
front.
A
The
quick
point
of
discussion
that
was
raised
last
time
actually,
which
I
wanted
to
circle
back
on,
was
we
had
this
conversation
on
the
three
3k
right
engineering
project,
where
people
had
split
opinions
on
whether
or
not
we
should
support
like
projects
that
are
coming
in
from
the
slingshot
competition.
A
So
some
notaries
expressed
support
for
that
and
some
notaries
expressed
dissent,
and
then
members
from
the
community
also
whispered
on
this,
and
so
andrew
hill's
request
to
me
was
actually
as
somebody
that's
helping
facilitate
slingshot
like
I
should
present
sort
of
my
opinion
as
well
on
the
whether
or
not
we
should
be
supporting
slingshot
projects
and
so
from
lost
call.
I
I
want
to
share
my
update,
but
I
also
want
to
open
the
room
up
to
conversation
about
my
opinion.
A
There's
also
a
really
high
rate
of
self
attribution
for
the
deal
making
like
slingshot
allows,
for
you
know,
storing
data
with
just
four
miners,
and
you
can
score
up
to
30
of
your
data
with
the
same
miner
and
there's
not
a
lot
of
tracking
there
on
like
self
dealing
and
things
like
that,
and
so
it
could
probably
lead
to
pretty
disproportionate
data
cap
gains
for
certain
miners,
especially
when
they're
already
being
incentivized
and
effectively
being
paid
by
their
participation
in
the
competition.
A
I
would
much
rather
that
notary
time
is
spent
actually
serving
clients
that
are
net
new
to
the
network
are
looking
at
ways
to
onboard
and
ramp
up
on
the
network
and
are
doing
it
because
they
have
a
use
case
for
the
network
directly
and
aren't
just
incentivized
to
participate
in
the
competition
and
so
yeah.
My
perspective
is
that
we
should
probably
keep
this
for
like
other
projects
that
exist
like
the
many
applications
that
have
already
been
received
and
many
more
to
come,
but
you
know
open
for
conversation.
A
I
know
charles
you're,
here
you
had
some
ideas
about
this
faye.
You
were
the
one
that
opened
the
application,
I'm
sure
you've
got
ideas
and
thoughts,
there's
a
couple
other
slingshot
participants
and
singstar
organizers
and
also
members
of
the
community
that
might
have
thoughts.
So
maybe
let's
take
a
pause
here
and
have
a
few
minutes
of
conversation.
A
B
So
can
I
can
I
speak
absolutely:
okay,
okay.
I
think
this
need
to
be
discussed
case
by
case
because
lots
of
if
everybody
in
the
screenshot
team
applies
here
most
of
them
are
self
dealing.
So
it's
kind
of
a
reverse
in
their
perspective,
so
they
get
more
efficient
sitting
process.
But
for
me
I
send
my
deals
to
other
people
to
minor
x,
fellows
to
small
manners.
B
A
And
so,
without
very
good
auditing
systems
in
place
where
we
can
track
how
data
gap
is
being
used.
I
think
it's
it
becomes
tricky
and
then
charles
also
yeah
go
on
sorry.
So
sorry,
yeah.
B
Also
also
the
minor
x
2.0
gives
small
miners
some
file
coins
to
use,
and,
I
think,
having
be
able
to
receive
more
verified
deals
per
per
per
mana
x
fellow,
can
make
better
use
of
the
coins
that
they
get,
because
I
can
send
them
out
very.
A
Fair
enough,
but
then
those
miners
also
being
avoided
the
ground
and
being
incentivized
to
take
the
deals
right,
whereas
the
one
of
the
benefits
of
data
cap
ensuring
that,
regardless
of
what
the
additional
incentives
are
that
are
being
provided
to
help
bootstrap
the
network
at
this
early
phase,
like
we're,
ensuring
that
clients
have
a
clear
path
to
making
like
reliable
storage
or
getting
valuable
storage
on
the
network.
A
C
Yes,
actually
like
for
me
like,
I
was
thinking
that
yeah,
it
does
have
some
effect
as
a
double
insensitive
incentives.
So,
but
I
also
do
agree
with
fijian
that,
while
doing
the
dr
making
he
needed
to
spend
the
time
and
management
those
deals
as
well.
So
I
said
we
discussed
last
time.
It
can
be
either
part
of
the
program,
but
it
may
be
difficult
to
be
both
in
the
both
program.
A
D
Hi,
can
you
hear
me?
Yes,
we
can
sorry
so
like
I
I
I
was
like
mentioned
the
last
time,
so
I
I
think
this
kind
of
clearly
sounds
good
because
actually
their
friends
like
want
to
helping
like
minor
ex
fellows,
but,
like
I
like
what
I
have
said
last
time,
we
have
to
make
sure
there's
no
any
like
money
exchange
between
them,
which
I
think
will
be
quite
hard
to
monitor.
A
B
A
That
I
wholeheartedly
agree
with
as
well
yeah.
I
agree
with
that.
That
makes
perfect
sense.
I
think
the
other
thing
that
charles
raised
last
time,
which
resonated
strongly
with
me
was
some
teams,
will
have
disproportionate
benefit
as
a
result
of
this
in
terms
of
their
participation
and
have
inflated
like
client-side
rewards.
Other
teams
may
not
there's
also
in
general
today
there.
There
is
not
that
much
consistency
like
if
you
look
across
applications.
Some
notaries
are
definitely
giving
data
cap
first
thing
shot.
A
Some
notaries
are
not,
and
so
I
think,
there's
like
two
levels
at
which
we
could
have
this
conversation
right.
One
is
like
do
we
want
to
say
that
slingshot
is
outside
the
scope
of
large?
Did
it
set
notaries?
Only
or
do
we
want
to
say
slingshot
is
out
of
scope
of
falcon
plus,
I
think
for
both
of
those
conversations.
There's
there's
arguments
to
be
made
on
either
side,
but
it
might
be
important
to
separate
those
two
as
well,
because
I
don't
know
like
to
some
extent
like
fey.
A
I
think
what
you're
saying
makes
sense,
and
and
if
a
nerd
is
able
to
do
the
due
diligence
and
follow
up,
then
maybe
it's
okay.
Maybe
there's
there's
like
an
upfront
sort
of
disclosure
on
what
minors
you're
storing
data
with
and
what
the
logic
is
that
you're
using
to
identify
those
minors
and
there's
agreements
that
sort
of
in
place
and
there's
follow
through
right,
like
if
upfront
the
client
says
I'll
make
deals
with.
A
You
know
x,
amount
of
minor
ids,
that's
something
that
we
can
monitor
and
we
can
see
what
those
minorities
are
and
whether
or
not
they
line
up
with
the
expectations
of
the
client
set.
So
yeah,
I
think,
depending
on
the
rigor
of
the
due
diligence,
there
are
ways
in
which
you
could
probably
support
this
at
different
scales.
A
I
just
think
that
the
large
days
that
notary
stuff,
where
we're
looking
at,
like
you
know
hundreds
of
tabby
bites
or
fever
bites
that
becomes
more
and
more
unwieldy
and
difficult
and
and
a
hard
point
to
to
support.
But
again
you
know
if,
if
the
majority
of
the
notaries
are
in
consensus,
then
I
think
that's
sort
of
part
of
community
governance
as
we
work
together
to
figure
out
what
the
right
thing
is.
A
I
I
think
last
time
we
had
notaries
that
were
supportive
and
unsupportive,
and
so
that's
why
the
question
came
on
like
what
does
the
slingshot
organization
team?
Think
and
that's
why
I'm
just
expressing
this
opinion
that
I
think
that,
but
clients
are
already
being
rewarded
to
bring
that
data.
So
I
think
large
scale
data
cap
is
may
not
be
necessary,
but
clients
don't
have
to
be
necessarily
banned
from
being
able
to
apply
if
they
so
choose,
because
some
notaries
are
still
providing
that
data
cap.
B
Yeah,
I
mean
if,
if
the
client
is
all
sent
into
themselves,
they
can
stop
granting
more.
I
guess,
because
it's
a
stepped
in
different
steps.
The
large
dataset
is
granted.
B
E
Yeah,
I
was
just
thinking:
are
you
going
to
send
those
deals
without
the
verified
data
get
to
the
miners,
because
I
don't
think
normally
you
would
send
those
deals
only
to
your
own
miner
right
in
slingshot,
so
the
data
cap
basically
enables
you
to
send
the
deals
to
the
minor
x
minors
right.
B
E
Yeah,
because
slingshot
is
a
little
bit
tricky
because
you
have
a
risk
that
the
deal
ain't
retrievable,
so
you
always
depend
on
others.
So
I
I'm
not
involved
in
slave
shot,
but
to
my
belief
it
was
that
you
were
allowed
to
send
it
to
your
own
mind.
So
that's
the
reason.
A
lot
of
the
students
deals
basically
were
stored
on
people's
own
mind,
but
that's
how
far
I
understood
it.
E
So
from
that
perspective,
when
you
use
verified
etiquette
to
enable
you
to
send
it
to
other
miners
without
having
the
risk
of
well
yeah
without
having
to
retrieve
a
wisdom,
then
I
would
say
I'm
all
in
favor
of
doing
this.
A
A
Yeah,
so
there's
no
way
to
prove
that
a
minority
doesn't
belong
to
you
easily.
So
the
part
that
was
removed
was
no
self
dealing
being
tracked,
but
you
still
have
four
minorities
at
least
being
represented,
and
so
you
could
have
four
minor
ids,
which
I'm
sure
some
teams
do.
Yeah
yeah.
E
So
from
that
perspective,
if
somebody
takes
the
risk
to
send
it
elsewhere,
like
you
send
your
data
to
like
eight
or
twelve
miners
instead
of
four,
that
the
the
verified
data
cap
enables
you
to
do
this
and
benefit
others.
A
A
So
it's
just
offloading,
and
so
then
the
conversation
we're
really
having
is
like.
Do
we
want
to
provide
compensation
for
that
like
because
really,
when
we
give
data
cap,
it's
that
we're
saying
that
we
as
a
community
are
choosing
to
leverage
the
network
to
reward
a
certain
kind
of
behavior,
correct,
yeah,
yeah,
yeah,
and
so
then
the
conversation
then
turns
into
do
we
as
a
community
believe
the
network
should
additionally
subsidize
slingshot-based
deal
making
when
it's
already
subsidized,
because
one
of
the
organizations
in
the
ecosystem
is
paying
for
it.
B
F
A
It
makes
sense
any
other
thoughts
or
opinions
on
this.
I
think
this
is
still
an
ongoing
conversation,
because
we
have
the
other
group
of
folks
that
aren't
here
in
today's
call
that
we're
in
the
other
one.
So
probably,
we
should
bring
this
up
one
more
time
and
then
wrap
it
up
in
the
next
governance
call.
So
if
those
of
you
are
here
today
that
do
have
an
opinion
on
this,
especially
if
you're,
a
slingshot
participant
or
if
you're
a
notary
that
has
an
opinion,
it's
an
excellent
time
to.
A
A
So
the
the
we
have
nine
applications
that
are
open
right
now,
and
so
that's
a
good.
I
think
we
can
switch
over
to
this,
so
these
are
the
nine
applications
that
are
open
the
last
time
we
had
this
call
only
the
first
four
were
open
and
then
there's
five
additional
that
have
opened
since
then.
None
of
these
have
received
seven
notary's
support,
and
so
what
I
wanted
to
do
today
was
also
talk
about
that
a
little
bit
and
say
hey,
like
no
trees.
A
It
would
be
great
if
you
could
go
and
ask
the
questions
that
you
need
to
ask.
This
is
not
about,
like
you
have
to
say
yes
to
these
things,
it's
more.
We
should
be
pushing
the
conversation
and
raising
the
standard
and
the
bar
for
these
clients
and
how
they
represent
their
data
and
their
data
sets
on
the
network.
C
A
A
I
think
the
only
reason
we
need
the
notice
is
so
we
have
like
people
that
are
being
held
accountable
to
like
manage
the
signing
and
tracking,
but
everybody
in
the
community
should
feel
free
to
you
know,
flag
an
opinion
share
their
thoughts
on
these
applications,
because
these
are
massive
right,
like
the
total
amount
of
data
cap
that
was
allocated
to
all
notaries,
with
less
than
two
pebby
bytes
in
the
first
election
cycle
in
the
second
election
cycle.
A
But
it's
also
like
an
awesome
like
lever,
improving
the
rate
at
which
we're
onboarding
data
onto
the
network
yeah,
so
yeah,
please,
I
mean,
please
feel
free
to
speak
through
any
of
these
applications.
I
have
the
list
pulled
up
here.
You
should
just
point
at
it
talk
through
it.
Let's
have
the
conversation.
C
Yeah,
it's
like,
I
go
through
each
of
them
and
I
think
it
can
be
categories
like
three
major
categories.
One
is
foundation
like
category,
so
those
categories
like
they
have
some
logic,
large
directions.
So
I
won't
do
this
type
of
data
set,
but
we
don't
really
have
specific
data
yet
so
this
kind
of
a
one.
So
if
we
go
to
this
part
according
to
what
we
have
on
the
condition
criteria
that
we
want,
500
terabytes
larger
can
be
defined
a
larger
size.
C
I
don't
know
how
can
we
define
it
because
we
just
don't
have
that
much
yet.
So
this
is
one
type,
another
type
of
certificate
data,
for
example
the
fractal
discovery
and
the
3
000
right
still,
and
those
does
that
from
the
data
itself.
There's
I
think
it's
no
argument
about
how
important
they
are
so
those
ones
if
we
don't
take
something
like
screenshot
or
not
selling
chart
as
a
consideration.
C
C
A
Only
the
data
that
he
knew
would
not
be
issues
like
there
would
be
no
issues
with
copyright,
so
he
did
address
that,
but
I
do
agree
with
you
that
that
is
an
additional
layer
of
complexity
that
we
should
be
extremely
pedantic
about
in
this
process
like
we
should
expressively
say
that
hey
this
is.
This
is
what's
happening,
we're
going
to
ensure
that,
like
it's
only
the
stuff
that
is
compliant,
it
should
be
retrievable.
We
should
be
able
to
test
that
as
a
community
to
retrieve
it.
A
But
at
least
for
this
first
round,
like
we
scoped
this
program
to
be
a
50
pepe
by
program
to
test
it
out.
So
for
these
first
50
peppy
bytes.
I
think
adhering
to
that
is
probably
the
right
thing
to
do,
mostly
from
a
perspective
of
minimizing
the
complexity
and
maximizing
the
likelihood
that
we
learn
how
to
audit
these
things,
because
the
challenges
that
we
will
face
as
a
community
in
ensuring
that
like
data
cap
is
being
distributed
well
to
open
data
sets
will
be.
A
A
It
looks
like
we
have
oh
reba
is
here
from
falcon
discover
and
looks
like
nelson
is
relatively
supportive
reba.
Do
you
want
to
share
your
thoughts
on
copyright,
or
do
you
want
to?
Are
you
just
here
generally
to
talk
about
discover.
F
No,
not
really.
I
I
basically
just
made
this
comment
that
I
would
be
very
cautious
saying
something
needs
to
not.
You
know
not
have
copyright
claims
on
it,
because
copyright
names
are
very
jurisdiction
specific,
so,
while
in
general,
like,
obviously
I
don't
know
just
general
wares-
and
you
know
movies
and
stuff
like
that-
that
is
obviously
not
a
fit
for
file
coin.
It
gets
more
tricky.
F
For
example,
in
the
case
of
there
is
they,
for
example,
data
orders
ever
going
on
right
now
to
save
all
the
psycho
research
articles
and
basically
put
them
out
of
reach
of
you
know
of
u.s
copyright,
where
it's
questionable,
whether
you
know
public
research
should
be
copyrighted
by
anybody
and
so
on
and
so
forth.
So
this
is
something
that
falconer's
community
should
be
a
little
bit
more
nuanced
about,
as
opposed
to
just
slapping
like
well
somebody's
copyrighted.
This
and
no,
it
has
no
place
in
falcon
plus.
A
That
makes
sense
yeah
jonathan,
please.
G
Yeah,
I
think,
there's
a
difference
between
going
from
data.
That's
not
online
today
and
putting
that
onto
filecoin,
because
then
you've
got
questions
around
you
know.
Is
there
copyright
or
isn't
there
if,
if
the
content
already
online
somewhere
and
has
been
online
for
a
number
of
years,
I
suppose
you
have
more
peace
of
mind
that
you
can
move
it
from
another
network
to
to
file
coin,
but
there
there
is
a
a
a
responsibility
around
who
moves
it
due
to
them,
putting
it
on
the
network
with
this
thai
pipe.
I
think
it
is.
G
You
know
somebody
ultimately
needs
to
be
responsible
for
that
that
content
it
so
it
can't
be.
It
can't
be
the
notaries,
but
it
it
must
be.
G
You
know
there
must
be
a
point
where
somebody
has
to
validate
that
we
are
responsible
and
also
if
you,
if
the
content
goes
into
the
sectors
and
a
sector's
sealed
for
one
and
a
half
years,
but
you
get
a
cease
and
desist
which
has
got
a
30-day
timeline.
G
G
You
move
it
to
a
place
where
it's
open
and
everybody
can
see
it
and
it
sits
there
in
limbo
for
a
certain
amount
of
time,
and
then
you
allow
in
just
to
give
you
that
kind
of
extra
assurance
that
you
know
the
the
that
it
is
online
that
nobody's
sent
you
a
cease
and
desist
for
a
while,
and
then
it's
allowed
to
move
into
to
file
coin
long
term.
But
maybe
maybe
we
could
even
look
at
like
data
going
on
to
the
network
but
unsealed.
G
So
it's
easy
to
pull
out
quickly
for
the
first
six
months.
I
don't
know
like
I'd,
have
to
speak
to
my
head
of
engineering,
but
there
might
be
some
some
way
just
to
have
a
halfway
house
for
a
while.
F
Yeah
yeah,
I
have
a
good
comment
on
that.
Don't
speak
to
your
engineer.
Speak
your
lawyer.
I
am
not
your
lawyer
and
I'm
not
a
lawyer.
However,
there
is
some
amount
of
prior
prior
cases
around
github
proposed,
not
sorry,
git
repositories
containing
stuff
that
was
later
subject
to
assistant
assistant
removal
and
in
the
case
of
the
linux
kernel
multiple
times,
the
accepted
response
was:
oh
we're
just
going
to
add
an
extra
commit
to
effectively
this.
You
know
mini
blockchain
that
removes
this
stuff.
F
F
It
effectively
no
longer
exists,
so
I
would
generally
not
you
know,
not
introduce
panic
in
terms
of
like
oh
crap.
Now
I
need
to
delete
the
sector.
No,
you
just
need
to
add
steps
that
this
particular
cid
particular
route
cannot
be
retrieved
and
a
lotus
at
least
already
provides
some
rudimentary
tuning
for
this,
where
you
can
literally
hook
every
retrieval
and
have
a
yes,
no
filter
in
front
of
it
that
you
implement
yourself.
G
So
maybe
we
just
need
a
a
a
blacklist
for
the
cid
hashes,
then
so
we
can
update
the
content,
but
with
a
black
image,
you
know
with
an
image:
that's
up,
you
can't
see
the
old
one
and
then
and
then
that
that
would
mean
that
people
wouldn't
be
able
to
access
it.
F
Precisely-
and
there
are
actually
some
efforts
by
an
external
team
trying
to
build
a
way
for
minors
to
communicate
such
between
themselves.
I
am
not,
however,
exactly
sure
how
far
this
effort
is.
I
know
not
much.
G
Perfect
sounds
like
we
need
a
file
coin
404,
so
you
know
you.
We
can
just
update
images
with.
You
know
a
certain
error
message
once
we
want
to
not
allow
people
to
see
them.
C
B
C
B
G
Just
one
more
sorry,
deep
due
to
us
being
a
regulatory,
we
have
a
australian
financial
license
and
we
respond
report
report
to
asic
for
us
to
have,
like,
I
don't
think
as
a
minor.
We
could
even
have
that
information
on
our.
A
Yeah,
that
makes
sense,
I
think,
the
so
there's
a
couple
of
thoughts
just
with
these
out
here.
So
the
first
is:
let's
separate
the
conversation
for
from
the
large
data
set
notaries
and
the
regular
industry
applications.
So
talking
about
the
large
data
set
notaries.
I
think
we
should
just
be
scoping
this
for
public
and
open
data.
A
Like
I
said
before
that,
that's
going
to
educate
us
a
bunch,
we
have
a
lot
of
learnings,
we
need
from
it
it's
something
that
we
can
grow
from
and
we
have
even
even
ways
to
at
least
test
it
and
validate
that
it's
working
and
doing
the
things
we
needed
to
do
and
that's
not
really
an
opinion.
That's
like
what
we've
been
talking
about
for
the
last
like
several
weeks
and
now
a
couple
of
months
on
that
issue.
A
Issue
number
94
that
led
us
as
a
community
to
believe
that's
what
we
want
to
support,
then
there's
the
ques
and
so
specifically
for
taopaipai.
They
are
only
looking
to
onboard
this
set
of
photos.
So,
charles
to
your
point,
they
have
a
very
large
amount
of
data.
From
what
I
understand
it's
you
know
double-digit
peppy
bytes,
but
only
like
six
pebby,
bytes
or
eight
pebby
bytes,
they
said
was
like
open
data
that
was
like
non-copyrighted
infringed
photos
where
they
had
permissions
from
photographers
to
share
that
publicly.
A
That
was
a
set,
at
least,
as
I
understood
it,
from
the
conversation
that
they
wanted
to
onboard
through
this
program,
which
to
me
makes
sense.
If
anybody
can
look
at
that
today,
online
as
jonathan
is
saying
like
anybody
can
go
to
their
website
and
download
a
copy,
then
it
existing
on
falcon
is
the
same
level
of
risk
and
the
same
level
of
like
authorization
or
copyright
that
might
exist
on
that
data.
A
And
so
that's
okay,
then
there's
a
question
of
like
falcon
plus
in
general,
like
to
what
extent
can
we
encourage
dealer
making
or
storage
of
content
that
could
lend
itself
to
these
kinds
of
problems?
And
I
think
that's
where
the
conversation
gets
a
little
clickier,
because
there
are
notaries
who
are
surveying
requests
from
companies
who
want
to
store
encrypted
data
that
don't
want
to
share
what
that
data
is,
and
so
actually
fembuchi
has
a
phenomenal
sort
of
offline
verification
process
as
well.
A
D
So
like
we
have
like
our
like
tutorial
process
and
listed
on
on
github,
so
our
basic
principle
is
that
we
have
to
make
due
diligence
and
like
to
see
like
first
of
all,
is
this
company
like
really
exist,
so
we're
gonna
check
a
lot
of
like
you
know,
coins,
or
something
like
that
to
to
to
to
see
that
that
like
and
also
likes
to
see
if
they
have
like
paying,
rent
and
other
like
information,
and
we
also
going
to
check
their
like.
You
know,
equity
everything
which
could
be
the
the.
D
I
mean
the
equity
structure,
something
like
that.
This
kind
of
information
can
be
like
easily
found
on
chinese
website
if
they
were
if
they
are
a
like
chinese
company,
so,
secondly,
we're
gonna
check
on
their
data,
like
we
will
see
like
how
they
will
proceed
with
their
data.
Will
they
like,
before
uploading
to
the
file
coin
network?
Will
they
like
do
they
have
like
a
necessary
process
to
make
sure
that
that
their
data
will
be
no
problem?
No
copyright
problem
and
also
like
their
data,
will
not
be
like.
D
A
So
I
think
that
works,
but
I
don't
know
to
what
extent
that
works
at
scale,
and
I
also
don't
know
to
what
extent
that
works
for
companies
that
aren't
even
comfortable
sharing
that
and
so
that
that's
one
thing
and
then
I
guess
jonathan
and
riva's
point
that,
like
the
nature
of
how
the
rest
of
the
world
interprets
that
data
may
also
change
over
the
course
of
like
the
lifetime
of
that
deal,
which
also
has
other
problematic
implications,
and
so
I
I
think
in
general,
like
you
know,
skewing
towards
public
stuff
makes
sense.
A
We
are
also
working
on
a
bunch
of
tooling
to
help
validate
that
public
stuff
is
being
stored
correctly,
but
yeah.
I
think
in
in
certain
cases.
If
you
can
build
that
confidence,
I
think
it
makes
I'm
curious
to
hear
actually
jonathan
if
you
have
any
responses
to
that
or
any
any
thoughts
based
on
on
their
process
at
finbushi.
G
Not
at
this
moment,
I'm
gonna
have
to
think
about
this.
One
is
quite
multifaceted
and
also
you
know
it's
going
to
be
regional
as
well
right,
like
you
know,
some
things
are
going
to
work
in
china.
Some
things
are
going
to
work
in
oceana,
australia,
so
yeah.
I
just
need
to
think
about
this.
One.
D
Yeah,
like
a
four
hour
like
a
due
division
process
like
for
some
parts.
So
if
it's
not
like
easy
to
describe
it
through
the
you
know,
mail
or
github,
we
will
just
ask
them
to
like
provide
us
like
powerpoint
on
their
product
to
to
like
demonstrate
how
how
hot
their
data
is
dealing,
how
how
their
product
like
where
their
product
we
will
check
on
their
product
to
see
like
if
there
is
any
potential.
A
Risk
sorry,
I
muted
so
one
of
the
questions
I
was
going
to
ask
you
actually
is:
these:
are
all
regional
rules
too
right,
so
does
that
work,
because
you're
doing
this
for
clients
that
are
in
the
greater
china
region
that
are
also
storing
with
miners
in
the
greater
china
region,
like
what
happens
when
you
cross
that,
like
geopolitical
boundary,
what
happens
is
that
it
is
being
stored
outside
the
region
or
if
clients
are
trying
to
you
know,
or
do
you
just
count
that
as
out
of
scope
for
now,
because
of
the
complexity
that
comes
with
that.
D
I
mean
like
for
the
equity
part.
I
think
it's
not
gonna
be
easy
to
check
for,
like
I
mean
outside
china,
but
like
for
other
products,
I
think
it
is
all
makes
sense,
but
but
but
the
the,
I
think
the
difference
will
be
like
how
how
you
will
define
their
data
will
be
like
legal
or
illegal
in
different
regions.
D
So
I
can
make
sure,
like
their
data
will
be
legal
in
china,
but
we
do
need
like
because
you
know
like
for
for
for
their
application
to
be
perceived.
We
need
three
regions
and
the
trade
to
be
represented
right,
so
I
think
the
other
two,
and
also
like
as
their
application,
was
just
describing
like
how
their
plan
on
I
mean
sending
their
deals.
D
To
the
I
mean
the
miners,
so
I
mean,
if
I
mean,
if
the
listed
miners
are
in,
like
you
know,
oceana
or
in
in
other
regions-
and
I
mean
the
representatives
of
that
region-
should
check
on
like
the
validity
of
their
data.
C
A
Yeah
I
mean
that
is
that
that
risk
extends
beyond
falcon
plus
then
right,
yeah,
but
yeah
yeah
yeah.
I
mean
sure.
A
Yeah,
I
think
the
I
think
one
thing
I'd
love
to
understand
is:
are
we
generally?
It's
afford
the
scope
of
large
data
set
notice?
Is
there
anybody
that
feels?
We
should
make
an
extra
effort
to
support
non-public
data
sets,
because
that's
to
me,
that's
like
something
we've
agreed
upon
is
like
outside
the
scope
of
the
program,
but
given
that
we
are
discussing
it,
I
think
it's
worth
flagging.
A
I
think
we
yeah.
So
if
you,
if
you
believe
we
should
make
an
effort
to
support
private
company
data
or
encrypted
data
through
the
large
data
set
notary,
then
I
would
say
you
know
you
should
flag
that
we
should
have
a
conversation,
maybe
the
right
next
step.
There
is
to
just
create
an
issue
where
you
say
we
should
expand
the
scope
of
the
program
because
right
now,
the
way
it's
defined
is
very
specifically
for
that,
like
the
case
in
which,
like
we
think
it's
open
data
public
data
like
referenceable,
so
that's
one.
A
A
If
you
have
any
questions
that
you
want
the
client
to
answer,
if
you're
a
notary
that
is
interested
in
supporting
but
wants
to
understand
what
they're
doing,
please
please
please
feel
free.
Ask
any
questions
completely
open
forum.
Go
to
the
issue.
Write,
write
your
thoughts
down,
get
your
opinions,
it's
important
for
us
to
hear
what
you
have
to
say
and
important
for
the
community
to
support
these
things
together.
A
A
Exactly
I
mean
phase
here,
that's
right
and
riba
is
here
as
well
for
discover
if
there's
any
questions
actually
right
now
for
discover
or
3000
rise
of
genome,
charles,
especially
if
you're
reading.
If
you
have
any
questions
like,
I
would
happily
like
to
take
the
next
two
minutes
to
give
these
guys
a
forum
to
address
them,
and
then
we
can
go
to
the
next
section
of
the
conversation.
C
A
A
So
I
think
that's
that's
an
interesting
thing,
because
the
way
we
provision
this
thing
is
that
a
notary
needs
to
have
data
cap
to
be
a
notary,
and
then
you
need
to
have
some
data
cap
to
be
able
to
participate
in
the
large
data
set
notary.
A
A
Speaking
of
not
as
many
notaries
notary
elections
are
ongoing.
As
you're
aware
many
of
you
have
applied,
many
have
reapplied.
So
congratulations
for
all
of
the
of
all
the
time
that
was
being
spent
on
that.
I
really
appreciate
it.
We
are
excited
to
share
that.
You
know
all
the
scoring
happened.
The
first
pass
was
shared.
A
Lots
of
feedback
went
over
many
people,
you
know
have
already
reacted
to
the
feedback
if
you
haven't
or
if
you
have
questions,
I
want
to
keep
the
last
few
minutes
of
this
call
to
address
that,
but
I
think
the
way
you
should
perceive
this
is
basically
we.
We
should
wrap
up
this
week.
A
C
C
A
Yeah,
so
I
think
the
there's
a
lot
of
entities
that
apply
that
are
in
multiple
regions
and
I
think
the
the
best
practice
that
we
were
basically
following
was,
if
you
do
like
the
way
you
should
be
calculating.
Your
collateral
is
like
accounts
on
which
you
have
access
to
the
private
keys
and
that
that
collateral
can
include
staked
unstaked
vested
unvested
future
unvested.
And
so,
if
you
hold
the
private
keys
and
the
miners
in
a
different
region,
then
that's
fine,
because
many
notaries
that
are
serving
as
well
operate
in
different
regions.
A
And
one
of
the
questions
I
had
for
making
was:
please
pick
a
region
because
you
can't
keep
floating
and,
and
so
that's
either
you're
effectively
picking
a
region,
because
you
specifically
want
to
be
a
resource
for
clients
in
that
region,
because
you
understand
their
needs
as
a
client.
You
understand
the
kinds
of
questions
you
need
to
ask
them
for
you
to
believe
that
you
can
vet
them
because
you're
a
major
stakeholder
of
the
falcon
network.
A
The
point
of
the
that
question
in
the
application
is
that
that's
the
incentive
you
have
as
a
notary
right,
the
more
you
have
at
stake,
the
more
likely
you
are
to
care
about
the
success
of
the
network
and
therefore
the
more
you
have
to
lose,
and
therefore
the
more
you're
likely
to
have
your
interests
aligned
with
this
community.
That's
the
sort
of
the
the
spirit
behind
that
question.
C
Okay,
so
if
I
have
I'm
a
bit
bigger
company,
I
have
lots
of
collaborations
in
china.
Now
I
open
branch
all
across
the
world
in
all
the
continent,
with
one
person
or
two
person
stand
up
company
and
I
use
my
character
to
assign
to
each
of
them,
so
they
can
take
a
seat,
all
the
candidates
right
and
then,
when
I
vote,
we
can
have
the
voting
right
in
all
the
continents.
A
Yeah,
I
think
the
I
think
that
that's
that's:
okay,
okay,
okay,
good
yeah!
I
think
that
until
we
reach
a
point
where
that
doesn't
scale,
I
genuinely-
I
genuinely
think-
and
this
is
just
one
opinion,
so
we
should
all
discuss
it
if
we
don't,
but
I
think
we
care
more
about
ensuring
that
we're
able
to
unblock
clients
than
we
care
about
this
regional
based
thing.
C
I
don't
know
I'm
yeah,
I'm
not
so
rich
and
I'm
maybe
not
even
be
able
to
take
a
city
in
north
america.
So
I'm
not
thinking
about
south
america.
I
just
think
about
over
centralized
of
yeah
representative.
C
A
C
A
C
Same
amount
of
in
china,
there
are
a
lot
of
bigger
big
companies.
They
have
help
set
up
lots
of
miners.
Each
miner
has
one
bb
or
two
people
through
pd.
They
kind
of
have
some
control
of.
If
you
ask
them
to
sign
a
message
through,
they
have
yet
no
problem.
Even
the
subsidized,
if
you
ask
a
separate
site
to
sign,
a
message
proves
really
heavy:
it's
not
a
problem,
just
send
the
email
to
their
parent
company.
So
please
sign
for
me
right.
C
C
Well,
you
can
have
different
subsidized
and
each
subsidizer
applied
in
your
region.
Yeah.
A
A
C
A
And
you're
going
to
sign
up
a
company
in
canada.
Well,
conveniently
I
don't
know
to
what
extent
that's
happened
yet,
but
maybe
we
should
wisen
up.
I
think
this
round
of
elections
is
relatively
clean.
I
might
be
wrong
if
I'm
wrong,
please
reach
out
to
me,
because
I'm
still
doing
all
the
re-scoring
or
please
flag
it.
I
think
this
should
be
an
open
conversation.
This
should
function
like
a
dispute,
but
I
think
that
as
long
as
we
as
long
as
one
parent
company
currently
has
one
notary
seat,
I
think
we're
okay.
C
A
Happening
yeah,
then,
I
think
please,
please
do
raise
that
as
a
flag,
yeah,
okay,
folks,
I
think
we're
we're
at
the
hour
the
like
I
mentioned,
you
know
we
we're
gonna
focus
on
wrapping
these
up
this
week.
So
if
you
have
any
questions,
please
feel
free
to
reach
out
to
me.
If
not
I'm
gonna
start
rescoring,
because
I
think
many
people
have
already
responded
to
the
feedback
that
we
left,
and
so
we
should
be
able
to
lock
this
in
by
the
end
of
the
week
really
excited.
A
This
is
a
very
big
milestone
because
together
it
means
we've
made.
You
know,
major
progress,
the
point
where
we're
doing
the
next
set
of
notes.
So
congratulations
to
all
of
you
and
I'm
excited
to
see
how
this
plays
out
once
again
lost
plug
if
you're
a
community
member
or
nobody
that
has
any
interest
in
the
large
data
set
notaries.
A
Please
go
ask
your
questions,
nominate
yourself
to
be
a
multi-signer
or
a
signer
on
the
multi-seg,
so
that
we
can
proceed
with
those
as
well
and
continue
to
increase
the
scope
of
the
program
thanks
again
for
your
time.
Take
care
have
a
good
rest
of
your
days
or
evenings
wherever
you
are
and
yeah
good
to
see
everybody
and
see
you.