►
From YouTube: Filecoin Plus - July 6 Notary Governance Call
Description
Filecoin Plus governance call, in which we discuss recent DataCap allocation trends, clients applications for Large Dataset Notaries, and the open topics for governance community discussion.
A
All
right,
folks,
welcome
to
notary
governance,
call
for
the
day
of
july
6th
excited
to
have
you
all
here,
as
usual,
lots
to
chat
about
so
we're
gonna
get
started
right
away.
Thank
you
for
those
of
you
that
were
able
to
make
it
live,
and
for
those
of
you
that
are
catching
the
recording,
don't
forget
to
join
the
slack
channel
and
participate
in
any
conversations
there
or
in
github
that
you're
interested
in
so
we'll
start
off
with
our
sort
of
usual
and
I'll.
A
Try
to
make
this
part
quicker
this
time,
because
I
think
there's
a
lot
more
interesting
conversation
to
be
had,
but
quick
updates
on
general
state
of
data
cap
and
flow,
and
then
we
have
some
interesting
topics
in
each
of
the
remaining
sort
of
topics
or
topic
areas
largely
said,
notaries
closing
out
for
the
elections
and
then
a
couple
of
open
issues
that
have
been
filed
are
relevant
to
our
community,
to
cover
and
and
before
we
dive
into
this,
actually
extending
a
warm
welcome
to
the
new
notaries
that
are
slowly
starting
to
get
confirmed
on
chain.
A
A
First
up,
some
updates
on
the
data
cap
side
of
things.
Only
three
allocations
went
through
from
manual
applications
on
github.
I
think
in
general,
like
the
rate
of
application,
creation,
submission
and
and
acceptance
is
just
a
lot
slower
on
github
right
now,
or
was
at
least
for
the
last
four
to
six
weeks.
A
We've
seen
that
pattern
where,
like
during
the
elections,
I
think
it
just
went
down
and
then
also
in
general,
like
the
net
new
clients
are
still
growing,
but
many
of
them
are
coming
through
the
automated
verifier
and
even
now,
there's
only
like
eight
sort
of
pending
applications,
whereas
prior
to
the
elections,
that
number
was
much
bigger.
A
The
number
for
the
amount
of
data
cap
that's
been
given
to
clients
has
gone
up
correspondingly
by
about
10
tabi
bytes
in
the
last
two
weeks,
where
across
the
435
or
so
verified
clients
in
our
ecosystem.
A
Just
shy
of
300
are
automatically
verified
today
and
all
of
those
allocations,
the
utilization
of
the
data
cap
is
going
up
quite
a
bit
quicker
actually,
and
so
that
number
has
climbed
a
fair
amount
over
the
last
month
where
we
were
hovering.
A
You
know
around
the
10
mark
of
used
data
cap
and
now
it's
climbing
past
14,
so
it's
great
to
see
that
clients
are
actually
able
to
leverage
the
data
capture
receiving
and
so
excited
to
think
about
ways
with
you
as
well
to
make
that
easier
to
ensure
that
the
data
cap
that's
been
handed
out
is
being
leveraged
and
clients
continue
to
make
the
best
use
of
this
network
as
possible.
A
Average
time
to
data
cap
continues
to
go
down
literally
every
time
I
edit
this
slide.
It
goes
down.
You
know
three
to
four
hours.
I
suspect
that
that's
because
the
ratio
of
the
clients
that
are
using
automated
verification
is
higher
and
continues
to
increase
relative
to
those
that
are
coming
in
through
github.
As
you
can
see
the
table
below
the
time
tier.
A
The
first
response
from
a
notary
is
about
ten
and
a
half
days
and
then
the
time
to
getting
data
caps
from
that
notice
about
four
days
after
that-
and
that's
somewhat
relative
to
the
fact
that
also
you
know
automated
verification
happens
in
one
epoch
or
two
epochs
like
30
seconds
to
a
minute,
and
so
as
long
as
a
lot
of
those
applications
keep
coming
from
there.
A
Our
average
time
to
data
cap
will
look
relatively
lower,
but
we
should
start
thinking
about
ways
in
which
we
want
to
pull
these
numbers
down,
to
ensure
that,
as
a
community,
clients
are
being
served
like
the
the
clients,
are
deserving
of
having
a
frictionless
experience
on
falco
and
continue
to
get
that
quick
screenshot
from
textiles,
phil
plus
notary
stats.
Not
not
really
substantive
changes
here
other
than
you
know
clearly,
like
the
amount
of
days
that
things
are
open,
are
starting
to
drop.
A
My
hypothesis
for
this
is
that
our
auto
close
bot
is
doing
a
good
job.
So
thanks
all
to
those
of
you
that
helped
shape
that
in
conversations
over
the
last
couple
of
months,
but
that
thing
basically
takes
care
of
issues
that
have
been
laden
for
too
long,
and
so
that's
certainly
bringing
the
latency
and
the
median
sort
of
open
days
down
just
because
issues
that
aren't
getting
any
traction
are
getting
closer
automatically,
which
is
good.
It's
also
helping
signal
to
clients
that
they
shouldn't
just
wait.
A
Infinitely
to
hear
back
from
entertaining
can
proceed
with
either
reaching
out
to
another
node
or
your
next
steps,
but
this
does
lead
me
to
believe
that
we
probably
need
to
make
it
a
little
easier
for
notaries
to
trade.
Clients
are
to
basically,
you
know,
transition
clients
over
when
they
don't
necessarily
have
the
time
to
handle
it
or
the
data
cap
or
the
desire,
maybe
to
ground
the
data
gap.
A
To
that
specific
client
cool,
I
guess
before
we
jump
into
this
any
general
thoughts
or
anybody
want
to
express
anything
regarding
data
cap
or
data
cap
flow,
any
immediate
reactions
to
anything
that
I've
said.
B
We,
I
guess
it's
maybe
two
questions.
Is
there
going
to
be
a
notary,
onboarding
or
something
where,
where
you
can
run
us
through?
I
suppose
we
observe
these
meetings
and
we
see
that
applications
are
happening
and
we're
going
to
run
an
experiment
with
a
client,
but
we
we're
facing
some
issues.
So
maybe
some
someone
that
could
guide
us
through
how
to
do
this
or
some
onboarding
would
really
help.
A
Yeah,
yes
to
that,
that's
on
the
agenda.
We
will
discuss
that
as
when
we
hit
the
sort
of
nerdy
elections
like
close
out
section,
and
you
mentioned
there
were
two
things:
is
there
anything
else
that
you
wanted
to
find.
B
A
Sure
yeah,
so
I
think
for
the
client
side
of
things
that
we
should
talk
about
now,
because
that
is
very
relevant
to
this
framing.
So
there's
this
repo,
which
is
the
client
onboarding
reaper
falcon
plus,
where,
if
you
go
to
github.com
dash
project,
slash,
I
think
it's
file
going
plus
client
onboarding
with
hyphens
across
the
words
that's
where
there's
some
amount
of
minimal
documentation,
much
of
which
has
also
been
ported
over
to
the
official
file
coin.
Docs
gilan.
A
A
That
says
like
write
a
message
of
this
format
and
based
on
that,
the
bot
will
effectively
acknowledge
that.
Oh,
like
this
data
cap
allocation,
needs
to
happen
and
well
actually,
in
your
case,
it's
not
even
that
you
would
sign
into
the
registry
app
once
you
have
your
ledger
and
you're
approved
for
for
signing
into
the
app,
and
you
just
be
able
to
it's,
like
a
click
on
the
application
that
you
want
to
approve
as
a
notary
and
then
press
an
approve
button
kind
of
thing.
Yeah.
B
I
think
that
all
makes
sense,
but
it's
more
than
logistics,
like
literally
talking
about
from
small
data
onboarding
to
large
data
like.
C
B
Are
others
doing
that
managing
risk?
You
know
and
retrieval
at
this
early
stage.
So
it's
more
that
kind
of
stuff
and.
C
B
Think,
maybe
I'll
take
it
offline
with
you,
and
you
can
direct
me
to
some
of
the
businesses
who
are
doing
it
and-
and
I
can
pick
it
up
with
those
guys
just
to
learn
from
their
lessons.
A
B
A
Yeah
so
sorry,
my
my
internet
was
giving
out
briefly,
but
I
think
I
can't
catch
what
you're
talking
about
yeah.
We
can
definitely
take
it
offline,
but
I
would
almost
say
if
you
don't
mind:
let's
talk
about
it
for
another
30
seconds
of
circus,
I'm
sure
somebody
will
watch
this
recording
and
gain
something
from
it
as
well.
So
the
first
thing
I
would
suggest
is
the
filecoin
plus
channel
in
slack,
has
a
ton
of
really
active
clients
and
notaries,
many
of
whom
are
in
the
call
right
now
that
participate
in
various
data.
A
There's
plenty
of
folks
here
that
have
participated
in
deal
making
at
scale
deal
testing
at
scale
participating
in
competitions
like
slingshot,
specifically
onboarding
data
at
a
large
scale,
either
with
miners
they
directly
correspond
with
their
own
or
just
strangers,
and
then
some
of
the
folks
in
this
call
as
well,
are
like
minor
ex
fellows
that
are
actively
working
day
to
day
on
like
deal
testing,
and
so
I
would
almost
say
like
a
hey
like
do
you
have
any
guidance
for
my
first
deal
kind
of
thing.
A
That's
a
completely
reasonable
thread
to
start
in
the
falcon
plus
channel,
there's
also
a
phil
deal-making
channel
that
I
think
jennifer
kicked
off
was
also
in
the
call
at
the
moment
in
falcon
sack
where
that's
where
we
see
some
like
offline
coordination
happening.
I
think
field
deal
market,
maybe
what
it
is,
what
it's
called
yeah
filled
deal
market.
She
just
dropped
in
the
chat,
and
so
there
there's
like
advertisements,
negotiation
and
things
like
that
between,
like
the
two
sides
of
the
marketplace.
A
That
could
be
interesting
and
then
I
would
say
the
remainder
of
it
is
sort
of
captured
in
the
doc
in
like
the
respective
docs
for
the
client
that
you're
using
so
in
the
case
of
using
lotus,
which
many
people
are
right
now,
just
because
it's
the
the
interpretation
that's
available
at
the
moment,
others
are
coming
on
and
and
obviously
we
expect
the
network
to
diversify.
A
But
at
this
point
in
time,
where
most
people
using
lotus,
there
was
a
big
sort
of
effort
in
the
last
several
months
to
improve
the
onboarding
path
to
falcon
when
using
the
so
there's
now
like
a
tutorial
that
goes
end-to-end
for
a
client
who
goes
and
gets
data
cap
from
the
automated
notary
and
learns
how
to
make
their
first
deal.
Of
course,
just
at
a
smaller
scale.
A
A
So,
like
data
transfer
doesn't
happen
on
the
network,
which
would
be
applicable
to
much
larger
scale
like
data
onboarding,
so
cases
in
which
you
need
to
make
deals
that
are
at
like
the
multi
100
debi
by
or
the
pepe
byte
range,
where
you
need
to
have
that
coordination,
where
you
don't
want
to
pick
an
alliance
on
the
bandwidth
or
the
network
itself,
but
would
rather
coordinate
in
some
way
with
the
different
storage
providers
to
get
that
data
over
to
them,
whether
that's
through
using
cloud-based
storage
options
using
non-cloud-based,
but
still
software-based
storage
options
or
dumping,
something
on
a
hard
disk
and
putting
it
on
a
truck
and
shipping
several
hard
disks
to
people.
A
There
are
a
few
ways
you
can
do
that,
and
so
just
improving
the
guidance
around.
That
is
something
that
I'm
specifically
addressing
and
so
I'd
love
to
chat
about
ways
in
which
we
can
make
it
easier
to
understand
cool
all
right
with
that.
I
think
I'm
going
to
move
on
to
the
next
topic
just
an
interesting
time
and
then
meg.
Let's
definitely
chat
about
it,
either,
happily
in
one
of
those
slack
channels
as
well.
A
If
that
would
be
preferred,
yeah
thanks
dave
sweet,
of
course,
so
on
the
large
data
set
notary
front,
quick
refresher,
we're
looking
at
several
applications,
so
I
think
we're
at
14
in
total,
which
requires
seven
notaries
to
sign
on
so
many
of
you
that
are
just
becoming
notaries.
I
know
some
of
you
are
already
involved
so
like
emma
and
a
few
others
were
already
signing
on,
I
think
bypasses,
then
a
few
others
already
like
signing
on
to
or
being
willing
to
be
participating
in
the
multisig.
So
that's
awesome.
A
Thank
you
so
much
for
that
and
for
those
of
you
that
are
just
getting
elected
as
notaries
feel
free
to
check
out
the
list,
issues.
That's
a
place
where
you
can
have
like
a
disproportionate,
highly
leveraged
impact
on
file
coin,
as
a
notary
where,
even
though
your
allocation
individually,
because
of
the
rubric
might
be
much
smaller,
like
10
heavy
bytes,
100
heavy
bytes
through
the
large
dataset
notary,
multisig
setup,
you
can
influence
a
client,
that's
looking
at
five
baby
bytes
of
data
cap
and
severely
improve
the
rate
at
which
they
can
onboard
onto
the
network.
A
There's
some
there's
a
lot
of
like
interesting
applications.
There
we've
had
a
few
of
them
come
present,
and
so
I
I'd
like
to
just
spend
a
second
on
just
highlighting
that
this
is
something
that
everybody
should
be
doing.
Even
if
you're,
not
a
notary,
helping
the
community
or
helping
the
notaries
do.
The
due
diligence
is
awesome.
A
The
deal
strategy
and
things
like
that,
and
so
if
you
are
just
a
community
member
and
a
stakeholder
of
any
kind
in
the
falcon
network,
which
you
could
be
a
minor,
a
different
client,
ensuring
that
this
process
works
for
us
and
and
by
works
I
mean
not
just
that
the
clients
get
data
cap,
but
rather
the
right
clients
get
the
right
amount
of
data
cap
and
we
do
it
in
a
way
that
we
can
continue
to
scale
up
and
build
trust
with
these
clients
and
generally
scale
up
the
operations
of
falcon
plus.
A
This
is
a
phenomenal
opportunity
to
influence
the
way
in
which
this
program
will
shape
data
onboarding
onto
the
network,
and
so
I
would
highly
suggest
that
you
take
a
second
to
review
the
applications
there.
Perhaps
after
this
call,
I
have
a
little
prompt
on
the
next
slide
anyway
to
talk
about
some
feedback
on
how
we
can
make
that
easier,
and
so
I'll
ask
you
to
hold
your
comments
for
that.
But
before
we
dive
into
that,
a
couple
of
things
that
have
come
up
in
past
calls.
So
the
first
one
thanks
to
julian.
A
What
are
the
expectations
of
actually
being
a
notary
on
this
multi-stake?
How
much
time
should
like?
Would
you
expect
this
to
take,
and
what
does
it
mean
to
be
a
lead
notary
and
is
it
difficult,
etc?
And
so
just
want
to?
We
chatted
about
this
in
the
last
call
briefly-
and
I
just
wanted
to
drop
this
here
as
guidance
for
those
of
you
that
are
becoming
new
notaries.
So,
for
each
of
these
large
data
sets
that
we
choose
to
support.
A
There
are
seven
notaries
that
will
sign
on
to
a
multisig,
and
then
one
of
those
should
elect
or
be
elected
as
like
a
lead
notary
and
the
responsibility
of
the
leader
needs
that
you
are
like
the
dri
for
ensuring
that
the
client
is
actually
compliant
with
their
application.
So
that
could
mean
weekly
you
just
check
in
on
the
various
dashboards
that
are
being
built
and
the
dashboards
themselves
are
being
built
in
a
way.
They
should
be
as
easy
as
possible,
but
you're
just
checking
things
like.
Are
they
actually
using
the
data
cap?
A
Are
they
actually
using
it
with
the
pool
of
miners
that
they
suggested
that
they
would
or
in
a
fair
way
and
distributing
it
across
the
large
set
of
miners?
Are
there
deals
that
are
actually
happening
at
the
rate
that
was
expected
and
are
these
deals
valid,
which
is
as
simple
as
just
going
to
for
fox
and
just
looking
at
some
of
the
messages?
And
so
I
would
suggest
that
you
know
the
the
work
of
the
lead
notary
here
is
not
substantively
more
than
a
few
minutes
a
week.
A
So
that's
just
like
copy
pasting,
the
raw
like
a
comment
in
a
specific
format
that
basically
prompts
the
bot
to
kick
off
the
proposal
process
to
the
multi-sig
for
a
data
cap
allocation
go
through
and
then,
if
you're,
a
notary,
that's
on
the
multi-stick,
but
not
the
so-called
lead
notary,
then
you're
effectively
doing
the
same
things
other
than
you're,
not
creating
you're,
not
actually
responsible
for
adding
in
that
comment,
but
other
than
that
you
should
be
checking
in
on
the
client
actions
and
client
behavior
as
well
sort
of
intermittently
or
on
a
weekly
basis.
D
Who
is
supposed
to
trigger
audit.
A
I
would
say
the
lead
notary
probably
would
trigger
in
the
case
that
something
wasn't
working,
you
would
just
flag
it
and
that
that
would
be
as
simple
as
either
creating
an
issue
in
the
notary,
governance
thing
or
just
posting
a
comment
that
says:
hey.
Something
looks
off
here:
let's
hold
off
on
on
sort
of
giving
additional
data
cap
grounds
for
now,
and
we
can
talk
about
it
in
the
issue
itself
or
in
the
next
governance
call
in
the
when.
D
We
were
managing
like
individual
client,
I
mean
clients
individually,
like
smaller
clients.
Usually
we
ask
the
question,
I
mean
we
ask
the
client
to
comply
with
the
fact
that
we
may
audit
them
and
they
may
share
their
data
content
with
us.
So
we
can
just
look
at
what
they
are
storing
on
the
network
when
we
do
this
large
data
set.
D
D
D
A
Okay,
so
what
would
be
a
good
way
in
which
maybe
maybe
one
option
is
like,
if
asked
they
should
be
able
to
produce
a
sample
of
some
of
the
content
and
maybe
share
it
privately
either
like
google
drive
or
some
some
solution,
whereby
notre
can
actually
see
like
what
some
of
the
content
might
be?
Okay,
yeah.
I
think
it
makes
sense
to
make
that
a
policy.
A
I
think
one
of
the
things
we
talked
about
julian
extensively
before
even
extending
and
creating
this
program
was
to
ensure
that
nothing
was
stored
through
this
program
that
couldn't
be
publicly
verified
right.
We
talked
about
it
being
for
public
data
sets
or
for
clients
that
weren't
going
to
encrypt
the
info,
and
I
think
for
the
first
iteration
of
this,
like
the
first
set
of
clients
that
we
do
from
the
50
peppy
bites.
We
set
aside
for
this
yeah.
I
think
that
makes
perfect
sense
and
so
putting
it
in
the
guidance
makes
sense
to
me.
A
A
D
Have
another
one:
sorry:
do
you
plan
to
explain
the
multisig
process
to
to
us
so
how
we
can
like
sign
this?
So
could
we
have
a
quick
demo
or
something
like
this?
Yes,.
A
A
I
was
wondering
if
the
right
forum
to
do
that
would
be
in
a
governance
call
or
in
like
and-
and
this
is
something
we're
I
was
going
to
discuss
at
the
last
slide,
but
we
were
planning
to
or
we
were
hoping
to
do,
some
sort
of
like
notary
office
hours
type
thing
where
we
like
help
some
of
the
new
notaries
on
board
and
get
set
up
with
the
app
and
the
ledger
and
in
that
they're
learning
the
flow
of
how
the
issue
comments,
influence
things
and
doing
the
same
for
like
how
to
participate
in
the
multisig.
A
So
we're
hoping
to
do
that
sometime
in
the
coming
weeks,
to
enable
I
also
have
documentation
that
I've
been
drafting
that
I'm
planning
to
just
put
on
the
repo
that
should
just
show
you
easily.
Like
here's
the
exact
comment
structure.
A
Here's
how
you
message,
because
it's
it's
as
simple
as
like
the
lead
notary,
dropping
a
comment
in
the
actual
issue
that
says
like
here's,
the
client
address
and
then
here's
the
amount
of
data
cap
and
that's
literally
it,
and
so
when
that
happens,
everything
else
happens
at
the
back
end,
where
it
looks
like
it
it,
it
actually
looks
the
same
as
a
client
application
when
they
come
in
where,
if
you
log
into
the
app
you
see
a
row
so
there's
like
a
new
table
that
says
large
data
sets
and
then
there's
a
row
for
that
application
and
all
the
notaries
on
the
multisite
get
prompted
to
approve
it.
D
A
Yeah,
but
I
think
it's
definitely
worth
covering
in
in
like
an
office
hour
session.
Thank
you
sweet
and
then
the
second
topic
that
sort
of
has
been
around
in
these
conversations
regarding
the
ldn
support
has
been
support
for
slingshot,
so
this
was
flagged
because
of
the
rice,
genomes
or
3000
rush
genomes
project.
That
was
looking
for
lots
of
data
cap.
I
think
there's
been
a
decent
amount
of
back
and
forth
and
I
I
don't
think,
there's
like
a
broad
community
consensus.
Some
notaries
were
supportive.
A
Some
notaries
were
supportive
if
and
only
if,
it's
like
a
client
that
isn't
doing
any
self-dealing
and
then
some
notaries
were
against
supporting
data
cap
for
a
slingshot
because
slingshot's
already
an
incentivized
program
where
clients
are
getting
rewards.
I
think
at
this
point
like
it's
still
open
for
discussion.
It
would
be
great
to
hear
some
opinions
from
new
notaries.
A
It
doesn't
have
to
be
today,
but
this
is
something
you
should
think
about
and
and
definitely
like
see
if
you'd
like
to
support
or
generally
believe
that
falcon
plus
should
be
supporting
initiatives
like
this.
If
there's
any
immediate
opinions
feel
free
to
drop
something
in
the
chat
or
unmute
and
discuss
I'll,
give
it
a
minute
just
to
see
if
there's
anyone
that
has
any.
A
So
with
that
wanted
to
flag
that
three
applications
have
had
seven
notaries
that
are
that
have
elected
themselves
to
serve
on
the
on
the
client
application
on
the
multisig.
I
think
a
lot
of
this
was
wrangling
on
behalf
of
the
clients
directly.
I
know
jv
was
definitely
going
around
and
seeing
if
people
would
be
willing
to
support
his
applications
to
ensure
he
got
the
data
gap,
but
I
do
want
to
remind
the
notaries
that
are
participating
that
there's
11
additional
open
applications.
A
Some
of
these
have
been
opened
up
for
a
while.
Definitely
some
really
cool
and
interesting
use
cases.
I
would
recommend
taking
a
look
and
and
seeing
if
you
have
any
any
thoughts
on
this
thanksgiving
for
dropping
the
link
in
the
chat
so
yeah
I
mean
we
have.
We
have
50
and
review
even
if
these
top
three
go
through.
A
I
think
each
of
those
requested
between
three
and
five
so
say
it's
five
that
still
leaves
us
with
35
period,
bytes
that
we
want
to
go
and
support
and
yeah
lots
of
really
cool
use
cases.
So
I
would
highly
recommend
you
know
notary
stuff
and
go
check
this
out,
but
also
everybody
else,
as
I
mentioned.
So
with
that.
That
sort
of
leads
me
to
a
little
bit
of
a
discussion.
A
I
I
want
to
suggest
that
we
have
today
on
what
are
ways
in
which
we
can
make
the
review
process
easier
and
more
efficient
and
also
maybe
encourage
people
in
the
community
to
help
because
effectively,
the
ones
that
got
to
action
got
a
lot
of
traction
very
quickly
or
it
was
like
forced
by
like
prompting
on
slack
through,
like
client
directly
interacting
with
notaries,
but
the
ones
that
didn't
get
as
much
traction
are
just
sort
of
sitting
open,
and
so
I
wanted
to
throw
up
some
bullets
on
like
maybe
like
what
do
we
think
about
success
for
this
program
and
then
based
on
that,
like
how
can
we
shape
better
engagement
on
the
open
applications?
A
So
if,
if
we
were
to
define
success
for
this
iteration
of
like
large
data
set
notary
support
like
in
my
in
at
least
in
the
initial
opinion,
I
would
propose
basically
that
we
want
to
get
50
bytes
out.
We
probably
want
to
do
it
across
at
least
10
projects,
because
we
put
a
cap
of
5
per
project
anyway,
but
also
that
we
want
diversity
of
projects.
A
That
means
that
the
data
cap
available
to
clients
will
increase
almost
20
x.
If
you
look
at
the
numbers
today,
especially
when
we're
setting
up
the
program,
it
was
like
500
w
by
600
tabby
bytes
of
data
cap
available
to
clients.
A
So
that's
going
to
go
up
massively
and
then
the
data
can
be
used
by
clients
should
go
up,
but
the
data
cap
used
should
be
more
than
proportional,
because
I
would
expect
that
clients
that
are
participating
in
this
program
are
doing
things
at
scale
and
once
they
overcome
that
initial
friction
of
making
deals
that
like
meg
was
referring
to
going
beyond
your
first
year,
should
be
substantially
easier
than
doing
your
first
deal,
and
so
that
could
be
interesting.
A
And
then
I
think
the
biggest
thing
for
us
is:
we
learn
about
how
we
interacted
with
clients
whether
or
not
it
was
efficient
and
effective
in
line
with
the
goals
of
falcon
plus.
Did
we
actually
make
it
easier
for
clients
to
get
the
data
cap
they
needed?
Did
we
actually
enable
deal
making
on
file
coin
at
scale,
and
so
with
those
sort
of
principles
in
mind
or
any
others
that
you
might
want
to
share?
A
I
would
love
to
have
like
a
few
minute
discussion
on
things
that
we
can
do
to
make
the
the
application
review
process
better.
I
see
some
things
in
chat
already
so
jennifer
is
proposing.
Maybe
we
have
one
monthly
call
where
notre
is
gathered
together
and
just
goes
through
the
applications
yeah.
I
think
it's
a
great
idea
to
review
some
of
the
apps
together
jennifer
we
actually
had
for
the
first
like
five
or
six.
A
We
actually
had
the
clients
come
and
present
so
like
topi
and
a
few
others
like
the
clients
came
to
the
call
and
talked
for
a
few
minutes.
I
would
love
to
hear
what
people
thought
of
that
like
if
that
was
efficient
or
a
good
use
of
time,
and
if
that's
like
one
way
in
which
we'd
like
like
to
review
applications,
there
was
a
initial
part
of
the
proposal.
A
I
think
and
julian
I
don't
know
if
you
remember
this,
but
one
of
the
things
we
talked
about
was
giving
each
of
these,
like
large
data,
set
applications
like
two
weeks
to
get
data
cap,
but
obviously
these
have
been
open
for
much
longer
and
like
no
one's
actually
like
policing
or
saying
that
they
shouldn't
be
open
and
theoretically
we
could,
but
I
feel,
like
that's,
not
really
useful
at
the
moment,
because
we're
still
trying
to
figure
out
like
how
to
make
the
friction
of
engagement,
lower
and
we'd
like
to
ensure
people
talk
so
yeah,
maybe
yeah.
A
Maybe
you
know,
notary
governance
clause
include
that
there's
steven
is
proposing
I'd
like
to
see
apps
along
with
the
large
data
cap
requests,
which
means
the
data
is
storing.
The
function
is
retrievable
and
useful.
A
Does
that
mean
it
means
oh
yeah,
like
applications
like
actually
like
the
web
use
cases
or
the
use
cases
of
the
info
right
yeah,
it
looks
like
there's
chats
further
below
stephen
feel
free
to
unmute
as
well.
If
you're,
comfortable
and
share
yeah.
E
Yeah,
okay
and
yeah.
Thank
you
yeah,
because
I
also
granted
some
data
caps
for
for
some
clients,
but
I
really
would
to
say
the
data
have
been
stored
in
falcon.
It
could
be
youtube.
E
Especially
if
the
data
is
it
yeah,
it's
private
data
for
me,
it's
very
hard
to
to
verify
or
you
have
to
validate
it
and
yeah
yeah.
If
the
data
cap
is
used
properly,.
A
Yeah
yeah,
I
think
that's
a
really
good
point.
So
a
few
of
the
apps,
like
the
one
that
jv
did
for
nft
storage.
I
think
there
was
a
top
5
i1.
There
were
a
few
that,
like
actually
linked
to
a
website,
and
it
was
like
hey,
you
can
go
look
at
the
website
and
once
the
data
cap
is
being
used,
you'll
be
able
to
access
it.
A
I
think
the
estuary
one
said
that
everything
would
be
available,
at
least
on
ipfs,
as
well
as
through
filecoin
for
retrievals,
so
some
of
them
are
like
supporting
web
pages
where
you
can
go
and
prove
it,
but
not
all
of
them
are,
and
so
I
think
that
should
be
a
question
that
we
should
just
ask
the
clients
like:
where
is
this
info
actually
going
to
be
useful?
How
do
you
show
that,
like
the
community
at
scale
will
benefit
from
it?
A
So
I
really
like
that,
like
I
think,
a
good
first
step
there,
stephen
could
be
just
asking
the
question
on
the
app
and
then
maybe
we
just
make
that
part
of
the
application
template
as
well
like
more
officially,
we
say,
like
we
add,
like
a
field
that
says:
where
will
this
info
be
visible,
because
I
don't
think
that's
a
field
right
now,
so
some
some
of
them
are
sharing
that
info,
but
not
all
of
them
are
which
is
interesting.
C
Hey,
can
you
hear
me.
C
Yeah
so
like
so
from
our
like
previous
experience,
I
feel
like
jv
is
like
doing
quite
well
job
on
the
application.
So
I'm
wondering
like
for
for
new
applicants.
Are
they
like
able
to
access
to
us
like
through
the
slide,
because,
like
jb
clearly
know
our
names
on
slack,
and
so
they
they
can
like
contact
me
yeah
like
directly.
So
I'm
not
sure,
like
these
new
applicants
like
have
had
a
way
to
like
reach
out
to
us
through
stuff.
A
A
So,
regardless
of
like
being
able
to
dm
you
and
then
the
second
would
be
seeing
if
people
are
comfortable
like
how
did
you
feel
about
like
a
client
dming
you
on
slack
was
that
was
that,
okay
with
you
or
do
you
think,
that's
too
much?
Or
would
you
prefer
it
because
it
helps
you
engage
with
these
applications.
C
A
Okay,
what
about
other
notaries?
Are
you
generally
comfortable
with
that
because
well
I
mean
in
the
past,
we've
talked
about
like
publishing,
like
not
just
your
slack,
their
github
ids,
but
also
slack,
but
then
we
went
back
and
forth
and
then
we
didn't
do
it
after
the
first
round
of
elections,
but
maybe
we
just
add
to
the
table
where
all
of
your
github
handles
are
listed
with
your
application
ids,
you
could
just
add
slack.
Do
if
you're
comfortable.
A
Thanks,
I
think
it's
something
to
think
about.
I.
I
also
think
it's
hard
to
say
no
to
this
because
of
the
way
in
which
this
question
is
being
asked
of
you,
because
it's
all
recorded
and
now
everybody
will
know
when
you
said
no,
don't
share
my
slack.
So
I
I
don't
think
this
is
a
fair,
fair
way
to
ask
this.
Maybe
we
have
this
conversation
in
the
notre
dame
channel
and
just
make
sure
people
are
okay
with
it.
F
Yeah
to
to
present
you
know
the
alternative
opinion
here
like
I
think
that
there's
something
great
about
having
the
asks
and
the
posts
and
things
like
all
in
the
public
fill
plus
channel
and
our
reactions
to
them.
Because
then
I
do
think
that
it
will
allow
new
people
to
see
maybe
how
much
work
it
takes
like
how
much
shepherding
they
a
client
needs
to
do
to
get
a
large
data
set
approved,
whereas
if
it
starts
happening
more
and
more
in
dms,
we're
just
hiding
kind
of
how
much
work.
F
That
is,
for
you
know
longevity
for
a
new
client
to
look
back
and
say
well,
how
did
estuary
get
approved
right?
They
can
go
search,
all
those
different
messages
and
see
so
just
just
some
thoughts
on
you
know,
keeping
things
in
the
open
and
but
creating
like
an
open
channel
that
maybe
is
a
little
more
filtered
rather
than
just
the
parent
full
plus
channel
yeah
versus
going
in
the
direction
of
let's
just
see
who's
comfortable,
getting
dm.
A
Yeah
one
thing
we
could
do
is
you
know
how,
in
slack
you
can
create
like
notification.
Tags
like
we
could
do
like
an
ad
notaries,
where
everyone's
slack
handle
is
taggable
and
create
a
thread
for
each
application,
because
I
think
that
in
general,
slack
notifications
are
easier
for
people
than
github
notifications,
but
I
don't
know
if
that's
true,
I
would
love
to
hear
from
the
notaries
in
the
room
right
now
like.
Would
you
rather
be
notified?
A
A
G
A
Yeah,
I
guess
julian
your
github,
creates
an
email
and
sends
it
to
you
right,
yeah,
yes,
yeah.
I
think
it's
interesting.
Maybe
we
try.
Maybe
we
try
going
back
to
like
actively
engaging
the
clients
in
these
calls
to
begin
with
and
then
see
what
the
traction
looks
like
and
then
based
on
that
we
can
get
better
about
engaging
on
slack
and
and
more
public
slack
channels
yeah.
So
I've
got
a
few
clients.
D
That
came
to
me
directly,
yeah
and
each
time
I
was
proposing
them
just
to
reach
out
to
you
and
see
if
they
can
have
like
a
five
minute
slot
to
present
something
to
all
the
notaries
yeah
more
impact
than
just
trying
to
to
negotiate
with
each
notaries
and
explaining
the
project.
Yeah.
A
Let's
do
that,
let's
do
that.
I
I
don't
think
many
of
them
reached
out,
but
also
julian.
You
know
how
good
I
am
about
looking
at
my
dm,
sometimes
so,
let's
yeah,
I
think
we
should
proceed
with
that
for
sure.
I
think
there
is
hundreds
of
them
actually
that
reach
out
to
you,
but
hundreds.
D
A
D
A
Cool
yeah,
I
think
we
should
definitely
like
bring
in
the
clients
the
calls
we
tried
that
it
was
pretty
effective
the
first
time,
so
that
might
be
good
for
sure
and
then
yeah.
I
think,
if
notaries
are
comfortable
with
publishing
the
slack
handles,
we
can
start
adding
that
to
the
repo
at
least
so
some
clients
know
where
to
go
and
then
based
on
that,
we
can
start
looking
at
like
more
efficient
methods
and
notification
sounds
good
to
me
cool.
A
If
that's,
if
that's
good,
then
I
would
say
the
the
action
item
for
those
of
you
here,
regardless
of
whether
or
not
your
notaries
check
out
these
apps
drop.
Some
comments,
see
if
you
have
any
questions
for
them,
see
if
there's
something
you'd
like
to
support
as
a
notary
or
if
you
think
they
should
or
should
not
receive
support.
A
A
So
an
example
of
this
is
estuary
made
the
case
that
all
the
data
is
public,
but
they
don't
always
necessarily
know
what
the
data
is,
because
it's
clients
of
estuary
that
want
to
do
deal
testing
with
it,
but
all
of
it
will
be
open
and
accessible
same
with,
like
some,
I
think,
one
of
the
ones
where
we
had
towel
pipe.
I
come.
A
They
explained
that,
like
the
photos
themselves
had
open
rights,
so
anybody
could
access
the
photos
that
were
being
stored,
but
it
could
be
photographers
who
are
uploading
new
photos,
and
so
that's,
I
think,
that's
the
point
of
differentiation
between
like
having
public
data
sets
that
are
like
open
curated
sets
of
data
from,
like,
I
don't
know,
nasa
internet
archive
versus
data
itself
that
is
inherently
open
and
accessible
to
the
public.
A
A
This
is
a
table
of
what
the
state
was
yesterday.
So
if
anybody
has
since
responded
between
yesterday
and
today,
I
have
not
updated
this
yet,
but
basically
we
have
addresses
on
chain
for
every
notary,
except
for
four.
So
if
you're
here
falcon
foundation,
we
need
you
to
affirm
stuff
by
base
we're
waiting
for
the
ledger
based
address
to
come
in
wayne.
We
need
you
to
affirm
stuff
and
then
hold
on
once
you
have.
The
ledger
set
up
happy
to
help.
A
You
walk
through
like
getting
the
address,
but
those
are
the
the
outstanding
ones.
I
think
everybody
else
was
able
to
get
an
address.
All
the
notaries
that
previously
had
grounds
have
opted
to
go
with
their
previous
addresses,
which
I
think
should
be
easier,
and
so
hopefully,
barring
any
random
issues
in
the
bot
and
the
interaction
of
the
chain
should
be
smooth
and
the
same
address
that
you're
using
should
automatically
get
topped
up
to
the
limit.
That
also
means
we
don't
need
to
do
any
funky
mathematics,
because
we
don't
have
to
go
and
subtract.
A
You
know
max
eligible
data
cap
from
existing
sorry
existing
data
cap
from
the
max
eligible
one.
We
can
just
top
it
back
up
to
what
you
qualified
for
and
choose
to
take,
which
I
think
is
good
yeah
and
so
from
an
onboarding
perspective.
Here
are
the
following
steps.
So
one
is
there's
a
doc
that
was
drafted
up
for
the
previous
round
of
notary
elections.
That
was
like
the
notary
on
boarding
dock
to
the
falcon
app.
A
I'm
working
on
updating
that
briefly
before
I
link
it
out,
but
I
will
be
sending
it
out
to
all
the
notaries
in
the
file
coin
plus
notaries
channel,
which
is
a
separate
channel
than
the
generic
falcon
plus
channel
on
slack,
and
so
that
way
you
have
all
the
instructions
for
getting
set
up.
If,
for
whatever
reason
you
are
not
in
that
channel
by
the
end
of
the
week,
please
let
me
know,
because
I
think
I
should
be
able
to
get
all
of
you
there
and
share
the
instructions.
A
But
the
more
interesting
topic
that
we
we
want
to
talk
about
was
like
you
know:
we've
had
a
lot
of
new
notaries
expressed
that
they
want
to
speak
with
existing
notaries
to
help
learn
more
about
experiences.
Onboarding
understand
how
to
do
some
things,
and
so
that
plus
the
addition
of
what
julian
was
suggesting
earlier
in
the
call
on
like
how
do
these
things
actually
happen,
whether
it's
for
just
new
client
applications
or
multi-sig
applications
wanted
to
propose
gilan.
A
And
so,
with
that
in
mind,
I
think
it
would
be
awesome
to
host
something
like
this
any
sort
of
immediate
reactions
in
the
chat
on
whether
or
not
this
is
something
you'd
want
to
come
to
or
would
be
useful
or
would
be
interesting
or
if
you're,
an
existing
notary.
Would
you
be
open
to
sharing
your
experiences
and
your
processes?
That
would
be
awesome.
A
Maybe
we
can
do
it
at
a
similar
time
slot
as
one
of
the
notary
governance
calls,
or
maybe
we
do
two
of
them
to
you
know,
handle
all
the
time
zones,
something
like
that
can
be
achieved
to
ensure
that
everybody
can
be
there.
We
could
probably
also
do
something
like
you
know
the
half
an
hour
before
the
next
notary
government.
Next,
two
notary
governance
calls
or
something
like
that,
like
some
solution
where
it
doesn't
disrupt
your
daily
schedules
too
much.
If
anybody
has
any
suggestions
on
that
too,
I
would
absolutely
love
to
hear
them.
D
D
So
no,
I
I
think
that
when
I
I
mean
I
look
at
the
the
scores
of
the
different
notaries.
You
know
the
scorecard
that
we
used.
I
mean
to
elect
the
different
notaries
and
do
you
think
it
could
be.
I
think
it
could
be
great
if
the
the
top
rated
one
for
some
items
can
explain
and
the
process
they
want
to.
They
have
in
place
for
us,
so
we
can
improve
our
own
way
of
of
managing
these
different
items.
A
That's
awesome.
That's
a
really!
I
really
like
that
suggestion.
Thank
you
for
sharing
that
yeah.
I
think
that'd
be
great
that
one.
I
think
I
would
suggest
that
we
do
that,
like
maybe
in
a
few
weeks
in
preparation
for
the
next
round
of
elections,
or
something
like
that,
but
I
think
that's
a
really
really
good
idea.
A
A
Thank
you.
Thank
you
great
suggestion.
Okay,
so
it
looks
like
we.
We
should
definitely
do
this
like
office
hours
type
type
format.
I
see
some
support
for
it
or
enough
support,
at
least
in
the
chat
would
well.
I
think
what
we
need
to
do
is
just
figure
out
what
time
zone
and
like
where
to
make
this
work,
so
I
can
just
quickly
pull
folks
on
the
on
slack
and
then
we
can
take
it
from
there.
B
Deep
australia,
because
we're
all
the
way
down
the
bottom,
we
don't
mind
starting
at
7
a.m,
like
we
don't
mind
an
earlier
slot,
which
makes
it
better
for
the
northern
hemisphere.
A
Okay,
so
I
think
the
tricky
thing
is
always
balancing
west
coast,
plus
europe
plus
china,
and
it
not
being
like
absurdly
late
at
night
for
you
or.
C
A
Earlier
and
so
what
we
may
need
to
do
is
do
two
sessions
which
I
think
is
fine
like
if
we
did
two
times
45
minutes
or
two
times,
30
minutes
that
might
be,
and
we
could
just
do
it
at
like.
You
know
reasonable
slot
for
australia
and
north
america
and
then
reasonable
assault
for
china
and
europe
kind
of
thing.
That
might
be
like
the
way
we
do.
Nerdy
governance
calls.
A
Basically
it
might
be
worth
just
investing
in
that
time,
because
I
think
this
is
something
that
they're,
it's
probably
valuable,
to
be
their
life
more
so
than
like,
watching
the
recording
for,
like
a
governance,
call
like
we
yeah,
and
so
let's
chat
about
it
on
slack
and
see
what
the
easiest
way
would
be
to
do.
But
yeah.
Thank
you
for
being
flexible,
really
appreciate
it.
Let's
see
how
we
can
make
this
work.
A
Awesome,
oh
there's
something
in
the
chat
yeah
before
the
governor's
call
could
be
yeah.
We
could
do
like
30
minutes
before
the
next
two
calls
or
something
jonathan,
as
I
mentioned
that
one
thing
that
came
to
mind,
though,
is
like
I
don't
know.
If
we
we
want
to
wait
four
weeks,
though
right,
because
the
next
notary
governance
called
this
slot
is
four
weeks
away,
which
feels
like
a
lot.
A
I
would
almost
be
like,
let's
just
see
if
we
can
find
a
saw
in
the
next
two
weeks
for
everybody
to
be
able
to
attend,
and
so
that's
that's
the
sort
of
trade-off
to
ensure
that
we're
not
generating
too
much
lag
in
activating
new
notaries
that
you
currently
have
the
energy
and
the
excitement
to
get
going.
A
Yeah,
I
think
the
the
general
like
lift
for
doing
something
like
this
is
not
too
high
right,
because
the
a
lot
of
the
content
already
exists.
It's
about
pulling
people
into
the
room
and
making
sure
that
people
are
able
to
make
it
from
a
scheduling
perspective,
and
so
I
don't
yeah,
I'm
not
too
worried
and
then
julian's
already
nominated
himself
to
run
the
sessions
in
the
chat.
So
I
think
we're
in
really
good
shape.
Julian.
B
I
think
you're
you're
you've
got
a
lot
more
stamina
than
us,
I'm
not
sure
how
how
smart
we'll
be
at
one
in
the
morning
then
we
can
do
early,
though.
A
A
No
worries,
nice.
Okay,
so
with
that,
I
think
we
should.
We
should
head
off
to
the
next
topic.
We
have
about
10
minutes
left,
so
I
think
we're
making
good
good
time.
A
So,
there's
two
there's
two
issues
to
discuss.
Based
on
what
I
saw
in
github,
the
first
one
is
around
issue
number
195
that
I
think
stephen
started.
If
you
want
to
talk
about
it
or
if
anybody's
who
participate
on
the
issue
wants
to
talk
about,
it
feel
free
to
unmute
and
take
over.
A
A
Okay,
maybe
I'll
do
that,
and
then
we
can
talk.
I
see
something
in
the
chat.
Okay
for
those
of
you
watching
the
recording,
there's
a
bunch
of
trip
planning,
apparently
to
hawaii
happening
regardless
for
issue
195..
So
this
this
issue
is
around.
How
do
we
validate
private
data,
that's
being
stored
by
verified
clients
or
what
are
ways
in
which
we
can
verify
clients
that
need
to
store
private
data
and
ensure
that
they're
following
through,
and
so
one
thing
I
want
to
flag?
A
Is
that
like
the
way
in
which
file
client
plus
has
been
set
up
is
at
least
in
the
short
term,
definitely
more
focused
on
public
data,
but
that
doesn't
mean
we
shouldn't
start
thinking
about
this
again.
In
many
cases,
it's
clients
that
cannot
even
onboard
onto
the
network
until
we
have
a
path
like
this,
and
so
at
least
starting
to
think
about
it
and
coming
up
with
ways
makes
a
lot
of
sense
to
me.
A
I
wanted
to
divide
the
conversation
into
two
parts
where
I
was
like
hey
what?
What
can
we
do
before
verifying
the
client
or
before,
like
the
data
cap
has
been
allocated
and
then
what
can
we
do
once
the
data
cap
has
been
allocated
and
so
for
the
before
part?
Like
specifically,
I
guess
the
prompt
for
the
room
is
like
what
are
ways
in
which
we
can
build
trust
about
the
client
that
don't
necessarily
require
access
to
encrypted
data.
A
I
know
femboshi
has
has
come
up
with
a
way
in
which
they
see
access
or
access,
like
some
limited
amount
of
the
data.
Maybe
you
have
something
to
share
from
your
processes,
other
notaries,
that
I've
worked
with
clients
in
the
past
or
those
of
you
that
are
clients
or
are
familiar
with
client
requirements.
Here
I
would
love
to
hear
about
ways
in
which
we,
as
a
community
can
build
trust
for
these
kinds
of
clients
before
we
even
give
them
the
data
cap.
So
let's
spend
a
few
minutes
talking
about
that.
A
If
anybody
has
thoughts
to
share
and
then
we
can
talk
about
like
looking
at
post
data
cap
allocation
as
well,
I
know
some
of
you
who
participated
in
the
github
issue
because
there
were
already
a
few
comments
are
in.
The
call
right
now
feel
free
to
share
your
thoughts
in
chat
or
unmute.
If
you're
comfortable.
C
Yeah
so
like
so
like
for
fambushi
for
us,
like
we
first
of
all,
like
it
check
the
data
like
their
description
on
their
data
and
to
see
like
what,
if
there's
like
any
problem
with
that
and
then
like,
if
necessary,
we
will
ask
them
to
like
provide
a
deck
of
their
like
business
itself
to
see
like
if
there
will
be
like
some
potential
following
on
that.
So
like.
Basically,
we
we
just
need
to
let
the
clients
deprive
more
materials
about
their
like
data
to
prove
that
and
their
data
is
like
a
legit.
C
They
won't
be.
Like
you
know,
I
mean
involving
some
like
illegal
data
such
as
porn
or
something
like
that
and
to
see
like
they
have
like
legit
process
to
to
filtering
this
data
or
like
pre-process
their
data,
so
that
their
data
won't
be
like
having
like
problems
to
be
saved
on
the
network
and
also
like.
We
did
like
check
on
their
all
kinds
of
license
official
license
issued
by
the
government,
something
like
that
to
see
like
they're,
actually
running
this
business.
C
E
Yeah,
okay,
I
also
also
received
some
applications
from
some
clients
and
to
save
yeah,
private
and
data,
and
they
claimed
and
all
their
data
are
private
and
they
how
to
encrypt
all
the
data
into
the
system.
So
yeah
ask
their
your
business
license
and
we
have
some
deals
and
also
yeah.
I
check
the
samples
yeah,
but,
okay,
I
think
yeah.
This
is
good.
This
is,
and
I
start
but
well
the
as
I
start,
I
think,
yeah
it's
okay.
E
Well
and
after
the
first
data
gap
and
use
user
app,
they
will
ask
more
right
yeah.
For
example,
they
will
have
much
larger
and
difficult
yeah.
But
but
the
question
is
we
yeah?
We
could
make
sure
that
to
have
a
and
contract
and
to
to
and
make
sure
the
miner,
and
also
the
client
to
guarantee
that
they
have
the
obligation
to
make
sure
their
data
are
needed
and
their
complaints
with
the
local
governance
or
regulation.
E
But
how
to
avoid
your
self
dealing,
and
I
think
that
is
also
the
question
right
yeah,
because
okay
and
the
minor
can
work
with
a
client
together
to
make
to
just,
for
example,
to
to
to
save
them
and
grab
the
data
to
give
the
ten
times
power.
That
is
a
hard
part.
A
Yeah
yeah,
I
think,
like
in
general,
that's
been
a
massive
challenge.
Right,
like
you,
never
know
what
the
association
is
between
a
client
and
a
minor,
because
minors
can
be
invented
every
day
and
so
yeah.
We
should
talk
about
that.
I
I
have
some
suggestions,
but
I'd
love
to
hear
more
before
we
dive
into
that
two
hands
went
up,
jonathan
want
to
go
for
it
and
then
galen.
I
Yeah,
so
we've
been
chatting
chatting
to
a
university
about
storing
their
data
on
the
network
now,
as
we've
been
chatting
to
them,
and
we've
chat
to
other
people
that
you
can
really
drop
people
into
kind
of
social
trust
layers.
I
if
we
take
university
data,
you
can
trust
that
a
lot
more
than
if
we
went
to
a
small
reseller
that
sells
date
would
reset
that
would
use
that
data
storage
for
their
needs
right.
I
I
just
feel
like
we
could
rank
them
in
a
kind
of
social
hierarchy,
because
you,
because
you're
not
you're,
not
gonna
a
university
is
not
gonna.
Allow
you
to
see
lots
of
their
data
because
it's
quite
sensitive,
so
you
know
they
need.
They
just
need
to
be
some
kind
of
ranking
system.
I
think
from
you
know,
for
for
the
sla,
depending
on
the
client.
A
I
A
I
A
I
And
and
just
another
one
they
they
do
have
to
stay
on
australian
soil,
and
they
also
do
have
to
be
with
miners
that
are
they
can't
be
with
miners
that
don't
show
who
they
are
in
australia,
because
you
know
university
is
not
going
to
put
their
data
with
any
random
people.
A
Yeah,
I
think,
there's
like
there's
an
element
I
what
I'm
hearing
from
what
you're
saying
is
that
there
are
certain
like
end-to-end
flows
that
exist
where
all
the
hands
are
trustable
enough,
that,
like
not
having
all
the
data,
is,
makes
it
more
okay
for
us
to
support
as
a
community
right.
That's
like
my
interpretation,
a
little
bit
where
you're
saying
it's
university.
A
They
can
share
their
entire
methodology
for
how
they're
processing
the
data
they
have
a
very
clear
set
of
requirements
and
where
the
data
can
end
up
they've
got
contracts
that
show
who
the
miners
are.
Our
miners
themselves
are
willing
to
share
info
about
themselves
like
publicly
to
the
point
where,
like
everyone's
like
comfortable
with
like
this
equation,
so
in
those
cases
like
does
that
make
it
okay
for
us
to
give
like
a
massive
data
capcom,
because
they're
willing
to
talk
about
it
or
there's
like
an
academic
paper
published
on
like
how
this
info
is
stored.
A
Yeah,
like
maybe
maybe
that's
good
enough,
like
I,
I
don't
know,
but
that
certainly
feels
like
a
fair
proposal.
I
Yeah
and
what
I've
looking
at
the
technical
side
there's
actually
only
very
few
miners
in
this
region
that
can
facilitate
what
they
the
the
data
that
they
want
to
store
as
well.
So
in
the
network
governance,
it
would
be
kind
of
you
know
it.
Might.
The
data
might
only
go
to
two
or
three
miners.
So
then,
let's
think
there's
a
cap
at
20,
so
there
would
be
breaking
that
rule
as
well
yeah.
But
you
know
if
you
want
to
move
forward
as
a
network
and
take
you
know,
get
bigger.
I
A
A
I'm
not
saying
these
are
efficient
ways
to
do
it,
but
processes
like
this
do
exist
in
real
life
as
well,
and
so
that's
yeah
we're
thinking
about
a
little
more
yeah.
I
Yeah,
I
think
if
we
just
if
we
take
an
australian
client
that
has
one
petabyte
and
they're
gonna,
basically
put
that
on
two
miners.
They
need
to
go
to
a
us
notary,
get
it
signed
off
and
then
it
can
happen
over
here.
I
think
that's
the
the
most
transparent
way
to
happen.
Yeah,
I
think
that's,
probably
the
best
solution,
yeah.
A
Yeah,
bringing
in
the
regional
sort
of
unbiased
input
as
well
that
makes
sense
galen
you
had
a
hand
up.
F
Yeah,
it's
okay.
F
So
the
question
is
like
what?
How
much
do
we
need
to
write
out
like
these
risk
profiles,
so
that
it
could
be
like
that?
I
think
that
could
be
like
a
conversation.
Another.
A
Time,
yeah,
that
makes
sense.
I
think
that
was
also
sort
of
what
stephen
was
alluding
to
sorry
to
call
on
you
directly
stephen.
But
one
of
the
things
that
you
were
talking
about
was
like
it's
very
hard
to
validate
the
actions
of
somebody
in
a
completely
trustless
peer-to-peer
network.
But
what
are
like
patterns
that
we
can
find
or
what
are
like
usage
indicators
that
we
can
see
in
the
way
deals
are
being
made.
A
Minors
are
being
corresponded
with,
or
contracts
are
being
signed
that
allow
us
to
build
that
trust
with
that
client,
both
prior
to
an
application
and
after
like
giving
somebody
data
cap
because,
based
on
how
we
agree
on
or
align
on,
like
as
you're
saying,
give
them
as
we
as
a
community.
If
we're
aligned
on
the
things
that
we
consider
to
be
anti-patterns
or
patterns,
we
don't
want
to
support.
A
Then
we
can
use
that
to
specifically
come
up
with
pattern
matching
or
processes
that
allows
us
to
ensure
that
the
clients
that
are
doing
like
what
we
believe
is
the
right
thing,
are
the
ones
receiving
the
support
to
continue
doing
it
at
scale
and
then
bringing
in
ways
of
like
reducing
bias
like
jonathan's
talking
about
could
be
could
be
interesting,
too
yeah.
There's
an
interesting
suggestion
in
the
chat
from
galen
might
be
worth
following
an
issue
about
that
one
again
higher
risk
data
cap,
so
less
multiplier
with
less
trust
from
a
client.
A
It
could
be
interesting,
we're
almost
at
the
hour
and
so
actually
we're
past
the
hour
now.
So
I
know
we're
we're
running
out
of
time.
I
did
want
to
highlight
this
one
too,
because
we
didn't
get
a
chance
to
talk
about
this
as
much
because
of
the
same
reason
it
was
at
the
end
of
the
day.
I
can
be
done
another
time
so
for
those
of
you
that
can
stick
around
for
a
few
minutes.
I
would
greatly
appreciate
it.
A
This
one
is
a
fip
that
was
filed
a
few
weeks
ago,
where
the
consideration
was
make
a
deal
with
a
client
or
a
client
can
make
a
deal
on
the
network
that
isn't
verified
to
begin
with,
but
may
become
verified
at
some
point
and
at
that
point
the
sector
can
be
upgraded
and
so
that's
beneficial
for
clients,
because
even
if
they
have
data
cap
applications
pending
they're
not
like
stuck
or
blocked
on
this
actually
happening
like
they
can
go
and
get
the
data
cab
application
at
some
point
in
the
future.
A
Of
course,
there's
feedback
for
us
as
stakeholders
of
falcon
plus,
where
you
know
people
are
thinking
about
ways
in
which
we
might
be
blocking
them
as
a
community.
So
of
course
we
should
figure
out
our
own
processes
and
become
more
efficient.
But
regardless
of
that,
you
know
looking
at
ways
in
which
clients
can
become
unblocked
as
soon
as
possible,
whether
that's
testing
or
starting
to
onboard,
because
onboarding
is
expensive
and
takes
time.
So
I'm
blocking
them
from
starting
to
do
that
and
then
once
the
client
receives
data
cap
in
the
future.
A
Upgrading
that
deal
state
effectively
to
say
that
this
is
actually
now
a
verified
deal
and
upgrading
the
sector
to
ensure
that
the
miner
is
being
rewarded
for
storing
verified
deals
and
then
the
client
is
being
rewarded
for
going
through
the
process
of
getting
verified.
So
this
is
fip.
It's
a
fib
that
was
filed
to
allow
upgrading
of
these
of
these
deals,
even
though
they've
already
been
sealed,
and
so
there
was
a
couple
of
considerations
on.
They
were
already
flagged
in
the
discussion.
The
first
was
like
you
know.
A
I
think
it
was
steven,
actually
that,
like
this,
which
is
like
how
do
we
check
for
the
data
that's
being
stored
over
time
and
whether
or
not
it's
compliant
over
the
duration
or
like
what
happens
before
they
get
data
cap
versus
after
other
methods
that
we
could
use
for
verifying
data.
So
I
think
charles,
if
you're
still
here,
you
were
also
participating
in
this
and
then
a
couple
other
folks.
I
don't
remember
off
the
top
of
my
head,
but
I
think
some
folks
on
the
call
as
well.
A
There
are
some
interesting
questions
around
what
happens
to
pricing
where
a
client
could
effectively.
You
know,
lie
to
a
minor
and
say:
hey
I'll,
get
data
cap
for
this
and
then
never
get
data
cap,
and
so
I
end
up
getting
a
cheaper
deal.
The
interesting
implications
are
at
what
point
that
upgrade
happens,
because,
obviously
you
know
minor
rewards
go
up
substantively,
but
what
about
the
le?
A
You
know,
like
the
ratio
of
like
say,
epochs
left
in
the
duration
of
the
deal
once
it
becomes
verified
versus
not,
and
so
there's
still
you
know
lots
to
talk
about
here.
I
want
to
make
sure
that
people
that
are
in
the
room
right
now
and
those
watching
the
recording
understand
like
what
the
context
is
behind
this,
and
so
I
think
we
shared
a
little
bit
of
that.
A
I'd
also
love
to
see,
if
there's
any
immediate
opinions
and
give
you
a
chance
to
share
either
in
chat
or
and
voiced,
and
then
let's
continue
the
conversation
in
github
at
the
link
or
in
slack
in
the
falcon
plus
channel
or
at
the
next
noted,
governance
call
but
yeah
any
immediate
thoughts
on
this
like
how
what
are
your
reactions,
especially
if
you're
a
notary,
a
client
or
a
minor?
What
are
your,
what
are
your
thoughts.
H
D
Do
we
have
any
existing
use
case
for
this?
One.
A
I
don't
know
if
there's
an
explicit
client
use
case.
This
is
more
proactive.
I
think
in
that
there's
a
it
came
from
folks
that
felt
that
either
their
clients
or
they
themselves
as
clients,
were
blocked
on
getting
like
data
cap
before
they
could
start
with
proceeding
to
onboard
data
onto
falcon.
So
it
was
more
that
hey
like
because
onboarding
rate
can
only
be
so
high
and
if
data
cap
is
delayed
like
14
days,
15
days,
why
not
start
onboarding
right
away
and
then
upgrade
the
sector
in
the
future?.
G
A
lot
of
like
clients
have
a
good
public
data
set
and
also
a
lot
of
them.
Having
like
enterprise
and
data
sets
like
private
data
sets
right
now,
which
file
coin
plus
doesn't
support
just
that.
So
what
they're
thinking
is
like
that
logic.
That
mechanism
may
happen
coming
in
later,
as
the
file
cleaner
will
grow
the
ecosystem
grows.
However,
they
don't
want
to
get
blocked
by
that,
so
they
want
to
get
the
the
data
stored
first
and
then
have
the
possibility
to
upgrade
the
deals
later.
G
Another
thing
is,
I
think,
it's
fib
16,
which
is
already
a
dropped
in
the
fifth
ripple.
Everyone
can
take
a
look
later
as
well.
It's
about
pacquiao
data
in
cc
sectors.
So,
as
many
of
you
here
already
know
that
population
storage
deal
right
now,
the
cost
is
pretty
high.
G
Of
course,
like
core
devs
are
working
on
like
optimizations.
However,
it
can
take
some
like
longer
time
to
do
that,
so
a
minor
some
minors
has
proposed
the
other
fib.
It's
like
right
now.
I
can
pack
everything
as
like
cc
sector,
so
I
don't
have
to
pay
for
the
private
storage
deal,
however,
in
the
future
like
but
like
they
want
to
pack
verified
data
instead
of
just
you
know,
random
data,
like
basically
all
cells
right
now
like
for
the
cc
factors
so
in
the
future
they
can,
like
those
trades,
can
verify.
G
D
Yes,
so,
okay
do
we
do
I
mean
so
so
we
just
discussed
previously
just
about
slingshot.
We
know
that
for
slingshot
there
is
huge
amount
of
did
that
have
been
done
and
many
of
them
have
been
done
like
by
self
dealing.
D
I
was
just
wondering
if
this
type
of
flip
could
not
be
used
by
people
just
to
allocate
data
cap
on
their
own
deals
later.
On
I
mean
I
will
think
that
this
could
come.
This
type
of
flip
should
be
linked
to
the
fip
that
we
discussed
previously
to
that.
We
have
some
ways
to
slash
data
cap
if
they
are
not
allocated
properly.
G
Yeah
that
would
be
really
cool.
I
was
actually
like
thinking
about
the
first
point
here
under
the
consideration,
so
stephen
brought
up
like
tracks
for
client
data
being
stored
over
time,
so
I
was
thinking
like
so
you
know
you
guys
know
how
we
have
this
builder
for
window
post.
Maybe
maybe
you
can
have
something
for
similar
for,
like
you
know,
unverified
deals
like
firefight
clients,
something
like
that.
A
There's
the
other
angle
to
this
as
well,
where
your
data
cap,
in
and
of
itself,
like
we've
thought
about
putting
in
like
a
lot
of
notaries,
are
already
doing
this
thing,
where
the
first
allocation
is
a
small
amount
of
what
the
client
asks
for
and
then
they're
happy
to
give
repeat
allocations.
And
then,
when
we
built
the
multisig
thing,
we
did
the
same
thing
where
the
first
allocation
is
like.
You
know,
five
percent
or
whatever
of
the
total
allocation.
A
Then
that
number
goes
up
over
time,
and
so
we
could
also
start
standardizing
practices
like
this
across
more
notaries
and
more
client
experiences
with
those
notaries
that
add
in,
like
checkpoints,
for
a
client
to
prove
that
they're
doing
the
right
thing
or
using
the
data
cap
in
the
right
way
or
whatever
yeah
yeah.
D
We
also
highlight
during
the
last
last
time
you
know
the
the
ceremony
or
the
the
file
plus
day
that
we
had
yeah.
C
A
That's
true,
I
did
some
around
the
elections
actually,
and
so
at
least
three
or
four
notaries
had
to
provide
a
bunch
of
info
for
for
for
this
round
of
elections,
and
so
all
of
that
is
actually
tracked
in
there
in
their
applications.
A
A
It
should
be
me
it
should
be
multiple
people
that
are
participating
in
that,
but
just
because
it
was
during
the
election
cycle.
It
just
happened
that
way,
but
yes,
disputes
are
starting
to
did
show
up
quote
unquote
from
me,
as
I
was
like
checking
through
some
of
the
applications
and
the
tooling
that
was
used.
There
was,
like
you
know,
checking
the
dashboards
to
see
what
was
happening,
what
what
were
the
percentages
of
dealing
between
clients
and
minors
and
notaries
and
clients,
and
then
how
much?
A
What
was
the
concentration
of
data
cap
from
a
notary
across
all
the
minor
ids
that
are
participating?
Were
there
any
disproportionate
numbers
there?
How
many
allocations
directly
had
issues
that
we
could
look
at
in
github,
where
all
the
conversation
happened
in
github
versus
happened
in
email?
You
in
what
cases
where
the
application
disappeared
did
like?
Where
was
the
documentation
for
every
single
application
that
was
approved
by
a
notary
like
things
like
that?
Like
that
level
of
investigation,
we
were
able
to
do
for
this
round
of
elections,
which
yielded
some
good
takeaways.
A
A
D
I
think
that
not
having
any
way
to
slash
the
when
the
data
cap
is
not
used
properly
is
just
slowing
down.
Maybe
other
thing
we
want
to
put
in
place
because
we
are
just
maybe
like
slowing
down,
because
we
don't
know
how
we
need
to
add
additional
control,
and
so
on
I
mean
when,
when
you
have
some
ways
to
just
you
know,
remove
what
has
been
allocated.
A
Yeah
it'd
be
great
julian
if
you
could
actually
link
your
proposal
flip
as
well
into
this
one
to
just
tag
those
two
together,
because
it
it
makes
sense
to
me
for
the
discussion
to
happen
on
both
of
them,
and
I
have
a
last
one,
because.
A
D
Yeah
yeah,
I
I
think
we
should
talk
about
like
renewing
data
cap,
not
that
sorry
renewing
the
deals
they
verified
this
when
they
expired.
D
G
Renew
deals
shouldn't
be
different
for
regular
deals
and
verified
deals,
and
that's
my
got
like
you
know
initially
yeah,
but
definitely
we
should
be
talking
about
radio
deals
sometime
soon
or
yeah.
A
A
D
My
point
is
like
when
you
have
clients
like
starling:
they
want
to
store
data
for
for
dozens
of
years
if
they
have
to
to
just
to
renew
all
the
deals
every
year
and
a
half
and
and
just
like
need
to
reallocate
to
get
new
data
cap
and
so
on,
just
to
renew
the
deal
for
me,
it's
it's
like
a
very
heavy
process.
D
Instead
of
just
renewing
the
deal
they
have
to
ask
for
new
data
cap
and
just
you
know,
reapply
up
to
the
renewal
and
so
on.
I
I'm
not
sure
we
should
go
on
this
on
this
road,
but
I'm
happy
to
discuss
about
it.
A
A
All
right,
I
think
I
think
you
know,
really
appreciate
the
folks
that
were
able
to
stay
later
thanks
so
much
sorry,
it
was
a
little
long
today,
but
hopefully
productive,
interesting
lots
of
good
topics,
lots
more
to
follow
up
on
so
yeah
thanks
so
much
for
being
here
for
those
of
you
that
are
watching
the
recording,
try
and
join
the
next
one.
When
you
can
looking
forward
to
seeing
you
in
one
of
these
calls,
can
I
just.
A
Yes
like
how,
how
is
my
application
is
processing,
it's
that
do.
I
need
to
manually
grab
enough
notaries
to
support
my
application-
hey
great
question,
so
we
we
chatted
about
this.
I
think,
right
before
you
joined
the
call
where
we
were
talking
about.
You
know
ways
in
which
we
can
get
additional
traction
for
the
large
data
set
notary
applications,
because
some
of
the
apps
that
I've
gone
through,
like
literally
the
the
client
like
dm.
The
note
reason,
was
like
hey:
what
do
you
think?
A
What
do
you
think
and
we
were
able
to
get
like
traction
like
that,
but
that's
not
necessarily
like
systematic,
systematically
feasible
every
single
time.
So
there's
a
couple
of
proposals
that
came
up
in
this
call
where,
like
for
all
the
open
applications,
we
should
have
the
clients
come
in
and
present
and
start
making
more
active
decisions
in
the
notary
governance
calls
so
we'll
start
dividing
like
a
portion
of
the
nerdy
governance
call
for
just
this.
A
In
your
case,
I
think
it's
very
reasonable
for
you
to
choose
to
dm
notaries.
I
think
the
better
option
would
be
if
you
just
make
a
thread
in
falco
and
plus
channel
and
just
say:
hey.
You
know
trying
to
find
some
notification
support
on
this
and
feel
free
to
tag
folks
and
just
share
any
additional
information
on
your
application.
I
think
that's
a
good
way
to
go.