►
From YouTube: Fil+June 14, 2022 Notary Governance Call
Description
The community governance calls to discuss the Filecoin Plus program.
Topics Covered
- Links to Application presentations: https://drive.google.com/drive/folders/1Q05bJ-YtRF1PBwS_Wi85OLG26oPRfZIf?usp=sharing
- Meeting times for future sessions
- LDNv3 Rollout Timelines
Github:
https://github.com/filecoin-project/notary-governance/issues/549
Slide Deck:
https://docs.google.com/presentation/d/1EW2OnnKlpOTjIjwmJKRxld8B2c5LyQcaLx2Cv4rLqW8/edit?usp=sharing
Slack:
filecoinproject.slack.com
If you would like to attend these meetings LIVE, the Fil+ Notary Governance calendar is available at
https://calendar.google.com/calendar/u/0/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0@group.calendar.google.com&ctz=America/Los_Angeles
A
All
right
well
we'll
go
ahead
and
launch
good
morning.
Everybody
today
is
the
june
14th
first
portion
of
the
notary
governance.
Call
I'd
like
to
welcome
you
all.
If
you're
looking
for
the
high
level
agenda,
this
is
kind
of
how
we
structure
these
calls
the
first
couple
moments
we
dedicate
to
introductions
housekeeping
participation.
A
Then
we
jump
into
metrics.
We
take
a
look
at
how
our
time
to
data
cap
is
doing
the
overall
network
storage.
Then
we
bring
up
issues
that
are
relevant
to
the
community,
so
these
are
things
that
we
should
flag.
You
should
flag.
Then
we
save
time
for
any
issues
that
you'd
like
to
discuss
and
at
the
very
end,
if
there's
time
we
have
a
q,
a
with
any
of
the
applications
that
have
been
submitted
with
videos.
So
with
that
going
forward.
A
A
Oh,
my
goodness,
he's
not
on
the
call
yet
so
when
he
comes
on,
I
might
call
him
out
by
me
and
have
him
introduce
himself
uses
protocol
labs.
This
is
his
second
week
at
the
company
and
he'll
be
looking
at
how
we
can
do
monitoring
how
we
can
incorporate
some
of
the
different
tools
that
are
in
development
to
make
those
processes
work
a
little
bit
better
for
you.
So
it's
not
such
a
manual
process
and
then
we
could
actually
start
to
build
out
a
lot
more
trust.
A
When
we
have
all
these
reports
like
hey,
I
saw
self-dealing
or
hey.
I
saw
this
thing
happen.
How
do
we
have
tools
in
place
that
actually
help
the
community
so
once
he
joins
the
call
we'll
make
sure
to
save
some
time
at
the
end,
for
him
to
say
a
proper
intro,
but
you
should
see
his
name,
the
addition
distribution
channel
so
he's
one
of
us.
A
He
works
at
pl,
very
friendly,
very
sweet
and
when
he
joins
bob
sam
proper,
if
you're
on
the
call
right
now,
if
you're
able
to
making
sure
that
your
name
matches
your
organization
makes
it
a
whole
lot
simpler
to
help
you
if
you
have
questions
or
need
help
in
the
future.
So
right
now
I'm
a
bad
example.
But
galen
is
a
great
example
and
that
right
now
kevin.
You
have
no
idea
what
organization
I'm
with.
But
if
you
look
at
galen's
name,
it
actually
says
galen
file,
point
foundation
so
to
make
that
change.
A
A
It's
really
easy
for
us
to
come
back
and
be
like
who
were
you?
How
can
we
help
you
if
we
know
who
you
are
so
taking
that
moment
will
make
it
a
lot
easier
for
us
to
get
you
back
all
right?
So
if
you
are
a
notary
and
on
the
call,
we're
still
doing
this
kind
of
check-in
model
right
here,
jalen
will
be
posting
a
link
in
chat
just
go
ahead
and
fill
out
that
you're
here
on
this
survey
and
we'll
be
diving
it
forward.
A
This
is
just
a
quick
way
that
we
can
give
you
points
towards
your
sla
and
your
participation
on
the
program,
so
nothing
new.
This
is
only
for
notaries.
If
you
are
on
the
call
and
you're
a
new
storage
provider
or
a
new
applicant,
you
just
want
to
kind
of
start
logging
these
ahead
of
time.
It's
also
valuable.
If
you
decide
to
apply
to
be
a
notary
in
the
future,
you
can
call
back
hey.
A
I
was
on
50
of
the
notary
calls
last
year,
and
this
would
be
your
record
of
proof
to
kind
of
show
that
so
with
that,
let's
jump
into
metrics.
Now
we
show
this
slide.
I
think
every
other
time,
every
time
and
one
thing
that
I'd
like
to
point
out
are
two
big
changes
that
we've
seen
since
the
last
cycle.
A
Now
you
can
see
this
is
an
average
time.
So
that
means
that
somebody
might
have
been
waiting
two
three
weeks
or
somebody
might
have
been
waiting
like
20
minutes,
but
when
we
average
it
together
right
now,
we're
still
at
that
three
day
mark.
But
what
we're
looking
to
do
is
bring
that
back
to
the
day.
Now
that
we
have
all
the
data
cap
being
distributed
to
your
notaries,
now
that
we
have
v3
launching
to
make
that
more
effective.
A
Now,
as
we
take
a
look
at
the
data
cap,
that's
coming
in,
we
also
have
network
increasing,
so
we
showed
this
slide
about
every
other
time,
just
to
kind
of
check
in
on
it.
If
you
look
at
the
size
and
scale
that
we
have
for
the
biocoin
plus
program,
it's
just
monumental
amount
of
storage
that
we're
bringing
in.
A
So
that's
why
we
invest
a
lot
of
time
in
making
sure
that
we're
doing
right
and
making
sure
that
we're
getting
your
feedback
as
members
of
the
community
that
this
is
a
program,
that's
working
for
you
and
so
a
lot
of
the
slides
that
we
have
on
here.
They're,
not
statements,
they're
questions
like
how
do
you
think
we
should
proceed
and
so
always
feel
like
you,
have
a
voice,
a
vote
and
that
your
opinion
matters
and
we'll
talk
about
some
of
the
ways
that
you
could
document
as
we
go
through
now.
A
Here's
the
first
question,
where
we're
going
to
ask
for
that
opinion:
for
you:
notaries,
you'll
notice
that
every
day
in
the
notary
channel
in
slack
there'll,
be
a
posting
from
the
filter
bot.
The
point
of
this
posting
is
to
flag
the
issues
that
need
diligence
either.
Applications
ldns
whatever
it
may
be,
and
the
way
it
currently
stands
right
now
is
that
it
will
say
hey.
We
have
a
client
request,
it's
coming
from
this
and
it's
assigned
the
way
that
it's
set
up.
A
A
So
what
I'm
going
to
do
is
I'm
going
to
let
you
guys
comment
chat,
feel
free
to
give
like
a
unmute,
but
what
we're
looking
for
is
input
from
the
notaries
on.
Essentially,
would
you
like
to
pilot
a
program
where
your
name
is
tagged?
Where
if
you
have
an
application,
it
will
tag
you
and
then
you'll
see
that,
but
you
will
get
much
more
spam,
so
unmute.
If
you
have
thoughts
or
discussion
looking
for
from
the
notaries.
B
D
C
Think
is
it
weekly
or
is
it
daily
it's
daily
it's
daily,
okay,
because
we
can
also
experiment
with
that
too.
I
think
when
we
had
initially
designed
it,
it
was
going
to
be
weekly,
but
I
think
just
with
the
volume
of
issues
and
how
quickly
they
changed,
we
were
not
tracking
them,
but
if
it
becomes
too
noisy,
even
every
other
day,
like
might
might
make.
A
Sense,
that's
a
great
point,
so
I
put
this
out
james
thanks
for
the
feedback,
batman
plus
kid
jackie
for
your
thumbs
up.
What
we'll
do
is
consider
this,
like
jurassic
park,
we're
still
tinkering
with
the
dna
on
this
one
to
get
the
perfect
dinosaur.
So
if
we
post
this
up
and
you're
like
man
guys,
this
is
way
too
much.
Let
us
know.
I
think
that
what
we're
trying
to
communicate
in
this
is
we're
trying
to
get
it
right.
A
C
So
from
the
system
status
we'll
be
implementing
ldn
v3
we're
going
to
talk
about
more
of
that
later
in
the
call
parts
of
that
are
live,
but
across
the
next
six
weeks
like
we
want
to
have
some
more
tooling
and
training
and
make
sure
that
it
is
working.
We
have
a
target
of
200
pibs,
sealed
in
data
cap
and
175
active
ldns.
I
think
that
we
can
maybe
hit
both
of
those.
In
six
weeks.
C
We
are
going
to
hopefully
hear
from
some
working
group
proposals
and
be
launching
those
in
github
and
testing
the
implementation
of
them.
You
heard
about
some
of
those
at
fieldplus
day
as
well,
and
we
have
a
target
of
getting
a
job
description
out
for
some
increased
head
count
and
hopefully
starting
some
interviewing.
I
don't
know
how
quickly
we
will
be
able
to
select
a
candidate
and
onboard
it
may
take
more
than
six
weeks.
So
a
conservative
objective
is
to
at
least
have
the
job
description
and
some
interviews
going.
C
E
Yes,
putting
him
back
on
the
spot,
it's
what
he's
gotten
for
the
last
week.
Hey
everybody
good
to
see
you
all
here
really
great,
to
see
many
of
you
at
falcon
plus
day,
though,
unfortunately
I
wasn't
able
to
be
there
in
person.
I
did
see
a
lot
of
you
join
in
in
person
and
not
zoom
rough
and
quick
introduction.
Faraga,
who
just
joined
the
team
from
the
pl
side,
he's
going
to
be
spending
his
time
working
and
being
more
focused
on
trust
and
transparency.
E
So
you'll
see
him
in
and
out
of
conversations
regarding
dashboards
apis
as
well
as
a
lot
of
the
work
around
the
systems,
we're
designing
for
risk
analysis.
I'm
really
excited
to
have
him
on
board.
He
brings
the
wealth
of
experience
that
is
in
many
ways
related
to
the
work
that
I'm
excited
to
do
with
him,
and
so
please
give
him
a
warm
welcome.
If
you
see
him
anywhere
in
slack
or
github,
I
hope
that
you
can
engage
with
them,
as
you
would
engage
with
any
of
us
so
appreciate
your
time
and
your
efforts.
F
F
A
Just
to
have
youtube
davin
is
there
anything
else
you
wanted
to
add
on
this
before
we
go
on
all
right.
Okay,
here
are
the
open
issues
that
we've
had
flagged
from
slack
from
github
and
discussion
at
the
day.
So
let's
talk
about
these
four
and
these
four
are
meant
to
be
discussions
so
I'll
always
pause
before
we
go
on
to
get
your
feedback.
A
If
you
don't
want
to
unmute,
feel
free
to
comment
in
the
chat
and
we'll
be
in
there
as
well,
so
the
first
one
is
just
like
a
huzzah
falcon
plus
day
took
place
this
time.
Last
week
we
had
hundreds
of
viewers
that
came
in
live
and
we're
gonna
have
the
videos
up
shortly,
and
this
will
be
a
nice
way
if
you
were
curious
to
see
some
of
the
different
points
about
the
community,
but
don't
always
have
time
to
like
read
a
big
repo
or
dive
into
it.
A
The
goal
of
the
file
coin
plus
day
was
that
we
could
engage
with
everyone
live
and
in
person
on
the
chats,
but
also
have
this
historical
resource
that
we
could
come
back
to.
So
if
you
look
at
some
of
the
talks,
they
jump
by
crypto
economics
or
legal
issues
or
galen
just
gave
like
a
30
000
foot
view
of
like
the
program.
A
So
if
you
have
someone
new
to
your
team
and
you're
trying
to
onboard
them,
you
could
have
them
watch
the
videos
we're
currently
going
through
post-production,
it's
kind
of
a
lengthy
process
to
make
sure
the
cameras
are
lined
up
and
just
like
last
time,
we'll
invest
in
making
sure
that
these
are
translated
with
subtitles
on
the
very
bottom
mandarin
speakers
to
come
through.
So
as
these
release,
we'll
post
these
online
I'll,
keep
you
updated
in
the
film
plus
channel
the
build
plus
notaries
when
these
go
live.
So
that
way
you
can
come
back.
A
C
Yeah,
I
you
know,
I
thought
that
it
was
amazing
I
loved
like
seeing
the
different
community
presentations
and
getting
all
the
conversations.
I
think
that
huge
kudos
to
k-ray
for
really
spearheading
this
five-point
plus
day.
I
was
there
for
a
lot
of
the
first
one
and
I
just
think
that
the
program
has
grown
exponentially.
C
Our
footprint
has
grown
and
the
kind
of
community
engagement
and
participation
is
phenomenal,
so
really
looking
forward
to
what
we
kind
of
generate
with
all
that
hype,
but
then
also
like
where
we're
going
to
go
with
falcon
plus
day
next
year.
I
do
think
that
it's
going
to
need
to
be
five
or
six
hours
and
we're
going
to
have
some
really
great
kind
of
working
group
sessions
so
stoked
to
hear
more
feedback
from
other
people
as
well.
E
Yeah
plus
one
I
got
to
also
view
it
from
the
isaac,
somebody
not
there
in
person
which
honestly
the
majority
of
attendees
are
not
in
that
room
and
are
participating
online,
and
it
was
really
great
to
be
able
to
participate
and
engage
in
the
way
that
at
least
I
felt
like
I
was
able
to,
and
so
I
really
appreciate
the
creation
of
the
space
kerry
for,
like
everybody
that
wasn't
able
to
be
there
in
person.
My
biggest
takeaway
was.
It
was
a
freaking
blast.
E
It
needs
to
be
longer,
there's
too
much
stuff
that
we
have
to
talk
about
and
there's
a
lot
of
awesome
things
to
share
and
we
need
more
of
these
one.
A
year
is
too
little,
and
so
I'm
really
excited
for
a
tour
of
phil
plus
days
to
come,
where
we
get
to
meet
many
of
you
more
in
person
as
well,
and
now
I'm
just
volunteering
carey
for
more
work
and
so
dropped.
E
We
have,
we
had
a
photographer
in
the
room,
so
I'm
assuming
we'll
get
some
photos
from
that
soon,
but
yeah.
Thank
you
all
so
much
for
participating,
whether
it
was
in
person
or
virtual.
You
know,
please
give
us
your
honest
feedback
like,
as
I
mentioned.
I
do
think
we
need
to
do
more
of
these,
and
so
I'd
love
to
get
your
feedback.
They
either
support,
disagree
or
you
know,
even
modify
the
way
we
think
about
them.
A
All
right,
everybody,
the
next
topic
is
ledger
verification,
and
this
has
been
something
that
we've
kind
of
talked
about
in
the
last
couple
calls.
So
thanks
for
your
patience,
those
of
you
that
have
verified
your
ledger.
This
is
that
point
of
the
conversation
where
you
can
just
kick
back
say
and
let
us
go
through
it.
We
have
three
slides
to
talk
about
this
I'll,
take
the
first
one
again
and
we'll
take
the
next
two.
So
here's
the
thing
with
the
ledger:
verification
for
new
notaries
that
are
coming
on
board.
A
This
is
a
new
process
and
essentially
what
this
ledger
verification
does.
Is
it
says
that
you
physically
have
the
ledger
that
you're
signing
on?
That's
all.
It
is
doing
it's
doing
that
physical
handover
for
it.
This
is
a
requirement
and
the
reason
for
the
requirement
is
it's
part
of
that
trust
and
safety
that
we're
building
into
the
network.
A
So
some
of
you
have
had
technical
blockers
for
this,
and
for
that
I
am
so
sorry
and
we're
working
to
get
through
it.
The
thing
that
I
will
say
is
sometimes,
if
you
send
a
dm
or
a
group
message
between
certain
individuals,
just
with
the
sheer
volume
of
communication
that's
coming
through
slack,
you
may
receive
a
delayed
response,
so
one
of
the
things
I'm
asking
is:
if
you
have
any
kind
of
blockers
with
your
ledger:
either
you
get
an
error
message
or
it
doesn't
work
or
something's
going
on
with
your
ledger.
A
Please
share
that
in
the
field
plus
notary
slack
channel
and
the
reason
for
this
is
one
we
can
make
a
public
record
and
share
that
solution
with
other
individuals,
but
two.
It
will
make
sure
that
it
doesn't
fall
off,
it
might
get
overlooked
or
it
might
get
stepped
on
with
other
messages,
and
we
don't
know
that
we've
overlooked
it.
So
I'm
going
to
shift
any
kind
of
direct
messages
that
you
might
send
me.
Like.
A
C
Yep,
so,
as
you
mentioned,
there
might
be
a
number
of
reasons
as
to
like
why
you
have
not
completed
this
step
for
some
of
you
for
some
of
the
notaries.
If
you
have
not
completed
this
step,
you
also
have
not
received
any
data
cap
and
been
ratified,
and
that
might
be
a
situation
where
you
don't
have
a
physical
ledger
device
and
you
let
us
know
we
get
it.
These
are
like
unprecedented
times
like
shipping
delays
are
a
big
thing.
C
We
really
want
to
add
more
tooling
support,
but
currently
this
is
the
tooling
support
that
we
have
our
ask
to
to
notaries
in
that
position
is,
please
continue
to
participate.
You
can
continue
to
do
diligence
in
github
issues.
You
continue
to
ask
questions
continue
to
come
to
these
calls
make
discussion,
topics
and
also
keep
us
updated
when
you
do
get
your
device
we'll
ratify
you,
and
we
understand
you
know
as
we
look
to
forward
election
cycles,
just
be
transparent.
That's
all!
That's!
C
That's
what
we
ask
all
the
time
for
some
notaries,
you
may
have
a
ledger,
but
you
have
not
done
the
verification
part
in
this
case
like
it
is
possible
that
we
have
already
ratified
you
sent
you
the
data
cap
to
the
address
that
you
provided.
We
need
you
to
go
complete
those
steps
to
actually
verify
your
ledger
in
order
to
then
start
making
allocations.
So
kind
of
you
know
do
that
step,
that's
on
you
and
then
for
some
of
you.
C
You
may
have
a
ledger,
but
the
address
that
you
gave
us
on
one
part
of
your
application
doesn't
match
the
address
on
your
ledger.
So
we
may
have
two
competing
addresses
on
hand
for
you
and
in
that
situation
you're
going
to
hit
that
technical
blocker,
because
those
addresses
don't
match
for
a
lot
of
you.
We
have
sent
you
requests
in
your
github
issue,
asking
to
kind
of
confirm
which
one
so
that
we
can
have
one
source
of
truth.
We're
only
going
to
send
that
data
cap
allocation
to
one
address.
C
C
There
may
have
been
some
updates
that
I've
missed,
but
if
you
see
your
name
on
this
list,
it
is,
it
is
possible
or
probable
that
you
have
not
completed
the
ledger
verification
process
and
you
may
or
may
not
have
been
ratified
yet,
and
you
may
or
may
not
be
on
things
like
the
ldn
v3.
So
as
we
mentioned,
please
talk
to
us
in
slack
check.
Your
github
issue
check
your
ledger
that
the
address
matches
on
your
ledger
device
as
what
is
in
your
github
issue,
attempt
to
verify
message
us.
C
You
know
in
slack
when
you
have
completed
that
process
or
to
let
us
know
wherever
you
are,
if
we've
already
communicated
to
you
directly
in
your
github
application
to
say
we
hear
you
that
you
don't
have
a
ledger.
Thanks
for
letting
us
know,
you
don't
need
to
do
anything
more
right
now,
just
keep
participating
and
let
us
know
when
you
get
one.
So
I'm
gonna
pause
here
and
just
see
if
there
are
any
quick
questions,
but
I
don't
see
any
hands.
A
A
The
second
what's
happening
is
with
time
zone
shifts
and
changes
in
schedules
that
some
of
these
calls
might
not
be
conducive
for
everybody,
as
we
can
see
on
this
call
right
now
we
have
around
30
of
us
in
the
afternoon,
call
we
might
have
around
10
or
15..
Now,
that's
fine
if
it
works,
but
sometimes
it's
always
good
to
come
back
to
our
roots
and
evaluate
if
we
have
any
sacred
cows
or
if
we
have
something
that
should
be
evaluated,
and
this
we
have
for
evaluation
is
the
time
that
we
have
these
calls
together.
A
So
there
was
an
issue
that
was
made
538.
It
was
just
essentially
asking:
is
this
time
a
conducive
time,
or
could
we
do
better?
So
what
we
did
was
we
pulled
the
applications
who's,
a
notary
where
they
are
in
the
world
and
we're
essentially
split
between
north
america,
china
and
then
those
of
you
that
are
calling
in
from
like
oceana
eu,
you
populate
the
outlying
perimeters,
so
the
intent
is
that
we
maximize
this
time
for
everyone.
A
What
we're
seeing
is
that
we
have
a
lot
of
you
come
to
this
morning
session
and
fewer
come
to
the
second.
So
the
question
that
we're
going
to
propose
right
now
is
some
of
the
ideas
floated
was
delay
the
second
session
by
one
hour,
which
would
push
it
back
to
5
pm
or
make
it
a
different
time
zone
for
the
asian
audiences.
A
I
have
a
link
here.
I'm
going
to
drop
this
into
chat
just
to
make
it
a
little
bit
easier
for
everyone
to
see
as
far
as
time
zones
go.
But
if
you
have
thoughts,
this
would
be
a
good
time
to
post
it
in
chat.
If
you
want
to
come
directly
to
this
issue,
this
538
feel
free
to
actually
reply
right
back
on
this
proposal.
But,
like
hey,
I
think,
that's
a
wonderful
idea.
Can
we
see
this
time
zone
that
time
zone,
and
this
is
nice
if
you're
going
to
be
commuting
in
a
certain
hour?
A
I
think
we're
going
to
do
this
straight
by
representative
democracy,
where
we
don't
have
the
overwhelming
number,
but
we
have
what
number
works
best
with
the
most
people,
so
I'm
going
to
unmute.
Excuse
me
mute
and
if
you
want
to
mute
talk
about
times,
why
you
come
to
the
first,
why
you
might
not
come
to
the
second.
This
is
our
discussion
time
on
what
to
do.
E
E
E
A
Batman,
what
we'll
do
is,
if
you
want
to
play
around
with
your
mic.
It
comes
back
up
we'll
save
time.
At
the
end
of
this
call
for
any
kind
of
like
circling
back
on
okay,
then
we
will
keep
this
issue
open.
If
you
have
thoughts
times,
please
post
it
in
538,
please
post
it
in
slack,
we'll
collect
some
more
signal
again.
This
is
never
a
done
issue.
We'll
always
look
at
like
how
we
can
maximize
time.
So
that
meant,
if
you
get
that
mic
I'd
love
to
hear
from
you
and
yeah
all
right,
galen
b3.
C
Apparel
d3
roll
out
roll
over
roll
tide,
any
any
football
fans
out
there.
No
just
all
right,
we
got
we
got
someone,
so
we
are
rolling
with
v3
we've
been
talking
about
this
for
a
while.
I've
been
building
the
tooling.
In
the
background.
I
know
that
there's
not
always
like
transparency
into
like
the
timelines
on
these
things,
but
we
we
have
to
do
a
lot
of
testing
with
our
various
dev
teams
before
we
can
make
these
implementation
changes.
So
at
this
point
in
time
this
tooling
has
started
to
launch.
C
We
will
be
rolling
over
existing
issues.
So
a
note
here
for
clients
and
notaries.
The
existing
approved
github
issue
will
remain
open.
The
next
allocation
is
just
going
to
come
from
a
new
notary
source,
so
you
as
a
as
a
client
shouldn't
necessarily
need
to
try
and
create
a
new
issue
or
anything
like
that.
If
your
issue
has
not
yet
been
approved,
we're
still
going
to
be
going
through
those
and
making
those
approvals
excuse
me
and
that
you
will
get
your
first
allocation
from
the
v3
notary.
C
This
should
decrease
some
of
that
time
for
the
root
key
holder
delay,
because
now
we
don't
need
the
root
key
holders
to
stand
up
a
new
notary
for
every
client.
So
this
is
a
place
where
we're
trying
to
to
decrease
that
time
to
data
cap,
calling
this
out
for
everybody,
an
important
label
for
you
to
watch
for
if
you're,
a
notary
and
you're
like
hey,
I
tried
to
do
a
thing.
C
It
didn't
work
if
you're,
a
client
and
you're
like
what's
going
on,
what's
happening
once
you
have
been
approved,
you
should
see
this
state
approved
label
that
should
persist
and
remain
on
for
all
of
the
clients
that
have
been
approved
by
the
governance
team.
To
then
start
getting
those
allocations,
we're
still
going
to
follow
the
allocation
schedule
where
they
receive
an
allocate.
The
next
allocation
after
they've
used
75
of
their
previous
allocation
and
those
allocation
volumes
ramp
up.
All
of
that
is
the
same.
C
C
Your
expectations
are
still
basically
the
same
under
this
vc
v3
process,
when
an
app
has
state
approved
and
ready
to
sign.
That
means
that
you
should
see
it
in
the
front
end.
It
still
needs
two
signatures.
Before
you
jump
in
and
sign
it,
you
should
still
go.
Do
the
diligence
review
their
application
review
their
past
deal,
making
behavior
the
bot
will
still
post
stats
for
previous
allocation
behavior
and
ask
more
questions
in
the
github
issue
and
then
use
the
front
end
to
sign
it
so
notaries.
C
For
you
guys,
the
process
is
the
same,
pretty
much
exactly
the
same
as
it
was
we're
just
we're
just
changing
that
root,
key
holder
step
and
we're
changing
where
that
data
cap
comes
from
next
slide,
please
k-ray
so
community
expectations,
so
this
is
for
the
notaries,
as
well
as
the
broader
community,
as
well
as
the
governance
team
raise
a
flag.
If
you
have
questions
about
something
notaries,
if
you
jump
in
and
you
see
that
an
application
has
the
ready
to
sign
label,
but
then
you
start
reading
it
and
you're
like
wait
a
minute.
C
This
is
there's
we're
missing
something
here:
there's
a
flag
for
some
additional
question.
Ask
your
question
and
what
we're
going
to
be
doing
is
we're
going
to
create
a
template
comment
that
the
bot
is
going
to
be
watching
out,
for
that
will
basically
pause
subsequent
allocations
and
so
we'll,
let
you
know
when
that's
ready,
we'll
have
a
tutorial
like
a
recorded
screencast
tutorial
on
how
to
save
that
template
and
we'll
put
that
stuff
in
the
readme.
But
this
is
for
notaries
and
just
community
members.
C
If
you
see
something
like
you
know,
this
client
is
doing
a
thing
that
they
said
they
were
going
to
do
something
else.
But
right
now
their
allocation
rate
is,
you
know,
85
percent,
and
I
want
to
like
pause
them
getting
their
next
allocation
until
they
can
kind
of
give
us
some
more
explanation
as
to
why
use
the
comment?
Ask
the
question
it'll
pause
allocations.
C
C
C
We
have
a
new
subsection
for
large
data
sets,
and
so
because
all
of
these
allocations
are
going
to
come
from
a
single
multisig
notary,
we
had
to
kind
of
restructure
how
we
track,
basically,
the
interaction
between
a
group
of
notaries
working
with
a
group
of
clients.
So
in
this
situation,
because
it's
every
two
signatures
leads
to
an
allocation,
we
essentially
have
these
dye
ads
where
two
notaries
working
together
send
out
data
cap.
C
C
You
know,
prioritizing
certain
types
of
clients
or
things
like
that?
What
clients
are
not
getting
enough
attention,
so
this
dashboard
is
now
live
and
again
we
encourage
community
members
to
lean
on
this
dashboard
and
help
us
investigate
what
is
happening
in
community,
and
if
you
start
to
see
that
this
dashboard
is
missing
a
certain
piece
of
information,
let
us
know
or
be
empowered
to
build
your
own
dashboard
as
well
pulling
this
data.
So
thank
you
to
all
of
our
our
dashboard
teams.
C
It
really
helps,
I
think,
there's
some
questions
happening
in
chat
around
a
different
topic
that
deep
is
addressing,
but
at
this
point
in
time,
v3
is
launching.
We
are
rolling
that
out
and
github
issues
will
be
getting
updated
and
data
cap
will
continue
to
flow
once
we
are
confident
that
v3
is
working
and
we
have
connected
all
of
the
existing
clients
to
that
new
notary.
C
We
have
a
number
of
projects
that
are
different
proof
of
concepts
that
are
sort
of
operating
out
of
the
traditional
flow
of
v2,
for
example
the
seal
storage
projects,
those
have
a
different
subset
of
notaries.
Those
multi-sigs
will
continue
to
operate.
We
will
continue
to
track
those
proof
of
concepts
and
we
may
still
have
other
new
large
data
set
things
that
we
test,
for
example,
things
coming
out
of
the
enterprise
working
group.
Those
may
follow
a
different
pattern,
so
while
we
have
almost
all
of
our
ldns,
probably
95
percent
of
them
will
go
through
v3.
C
C
C
Okay,
great
so
the
v3
proposal
issue
is
also
still
up
in
github
as
we
roll
this
out
and
test
it.
If
you
see
problems
or
issues,
if
the
tooling
is
missing
something
go
to
the
notary
governance,
repo
jump
in
that
issue,
and
let
us
know
what's
working
and
what's
not
so
thank
you
for
your
your
patience
and
support.
I
think,
there's
a
chat
question.
E
A
All
right
so
we're
going
to
share
the
link
one
more
time.
This
is
just
for
sla
if
you
want
to
get
quote
unquote
credit
for
being
here,
we've
got
count
this
to
you
existing
notaries
or
you
that
might
want
to
come
in
the
future
and
if
you
join
the
callway
galen,
just
posted
the
link
there.
Thank
you
for
that.
A
Okay,
we're
gonna
turn
the
floor
over
to
any
kind
of
community
discussion
before
we
get
into
applicant
q,
a
so
if
you're
on
the
line-
and
you
have
some
topic
that
you'd
like
to
flag
that
we
talked
about
this-
would
be
the
time
to
do
it
and
then
what
we're
going
to
do
after
this
is
save
time
for
any
of
the
questions
that
may
have
come
from
any
of
the
applicants
so
notaries
on
the
line.
Storage
providers
open
forum
for
anything
we
want
to
talk
about.
E
I
I've
got
a
question
I
guess
for
folks
regarding
these
topics.
Does
anybody
here
have
any
questions
about
anything
regarding
anything
that
was
discussed
at
falcon
plus
day,
if
you
were
there
or
even
ldnv3,
that
you
feel
like
you
haven't,
had
the
opportunity
to
discuss
yet
because
you
know
we
shared
a
lot
of
updates.
A
lot
of
things
have
changed.
E
E
Yeah,
so
it's
actually,
the
number
that
was
shared
at
phil
plaste
by
galen
was
400,
bibs
and
so
yeah.
I
think
it's
a
really
good
question.
I
think
that,
like
looking
at
the
use
cases
that
we
enable
today
versus
the
use
cases
we
may
enable
the
in
the
future
does
definitely
play
like
a
role
in
like
how
we
get
to
this
number
or
how
we
feel
like
we
want
to.
E
I
think,
a
couple
of
thoughts
for
me
and
again,
please
feel
free
to
jump
in
one
I'm
sort
of
looking
at
roughly
like
wanting
to
get
to
that
number
first,
regardless
of
whether
or
not
that
data
is
unique
right.
So,
if
we're
looking
at
like
5x
replication
on
average,
that
number
looks
a
lot
easier
to
reach.
E
I
know
that
there's
several
different
teams
in
the
ecosystem
that
are
working
on
different
forms
of
business
development
and
bringing
on
substantively
different
types
of
clients
in
the
near
future.
So
I'm
really
excited
to
see
what
they
bring
on,
because
I'm
pretty
confident
we'll
see
a
significant
amount
of
throughput
from
those
and
then
last
and
definitely
not
least,
is
oh
sorry,
you're
talking
about
the
sprint
specifically,
I
was
thinking
about
like
the
october
goals.
Sorry
for
thanks
for
clarifying,
I
think,
for
one
thing
that
I
do
want
to
add
to.
E
To
bring
on
like
a
magnitude
of
additional
data
cap
and
so
part
of
this
means
we
need
to
improve
our
processes
to
move
quickly
enough
to
not
block
clients
that
are
interested
in
making
the
progress
that
they
claim
they
are.
And
then
part
of
this
is
also
just
you
know,
as
a
software
as
a
network
as
an
onboarding
process,
of
which
falcon
plus
is
just
a
piece
of
the
whole
thing,
still
needs
to
work,
but
yeah
sorry
ramble
a
little
bit,
please
feel
free
to
add.
C
I
agree
with
deep
that
I
think
the
answer
is
yes.
I
think
that
the
storage
providers
are
able
to
get
us
there
with
the
speed
that
they
can
onboard
it,
and
I
think
that
the
the
question
kind
of
becomes
what
type
of
data,
how
many
replications,
where
is
it
coming
from
and
how
distributed?
Is
it
and
that's
what
we
want
to
learn?
C
Oh
it's
eight
pids
and
we
think
that
weekly
we
can
do
250..
Then
we
don't
need
to
put
eight
pids
on
on
chain
at
that
notary
multisig.
We
just
still
have
the
two
weeks
of
actual
usage
at
the
notary
level,
but
we
now
have
a
better
estimate
of
how
much
are
all
of
our
ldns,
anticipating
they're
gonna
need,
and
so
then,
when
an
ldn
comes
in,
we
don't
need
to
say
well.
The
max
that
you
can
request
right
now
is
five.
We
could
just
ask
them
what
they
actually
want
and
then
work
towards
that
number.
C
But
it
is
a
good
question
because
there
will
always
be
the
thing
of
how
how
quickly
can
one
part
of
this
funnel
move
when
everything
has
to
like
flow
in
sequence,
if
the
data
isn't
there,
the
onboarding
rate
isn't
gonna,
you
know,
keep
ramping.
If
the
onboarding
rate
isn't
ramping,
then
the
tooling,
to
you
know,
make
the
onboarding
smoother
isn't
going
to
be
prioritized
right,
so
so
it
will
always
be
sort
of
a
balancing
factor.
Jay.
I
don't
know
if
that
answers
your
question
but
happy
to
to
talk
more
to
it.
C
A
Well,
yeah,
just
to
kind
of
like
check
in
with
everybody
who's
on
the
line.
What
we
found
was
there
were
a
lot
of
fabulous
applications
coming
through
and
a
lot
of
those
organizations
wanted
to
share
their
projects.
But
the
dilemma
was
so
many
projects
to
share
that.
We
wouldn't
have
time
for
any
kind
of
community
discussion.
It
would
just
be
demos,
so
in
the
governance
call
repo,
you
can
request
an
item
like
that
man
suggesting
we
talk
about
the
time
zones
as
well
as
anybody
who
submitted
an
application
that
wants
to
share
it.
A
So
what
they've
been
doing
for
everybody's
transparency?
Is
they
post
a
thread
on
the
github
issue
that
says
hey
I'd
like
to
be
a
part
or
be
on
the
call?
They
provide
a
brief
information
about
their
company
where
they
are,
and
then
they
record
a
five-minute
video
which
comes
from
this
folder,
and
then
I
put
it
here
and
then
I
share
that
in
slack
with
all
of
your
notaries,
as
well
as
public
in
the
applications.
A
So
that
way,
you
could
see
these
five
videos
watch
these
ahead
of
time
and
then,
when
we
come
to
this
call,
we
can
now
have
this
set
up.
So
rather
than
having
to
invest,
you
know
20
30,
35
minutes
to
watch
these.
We
could
spend
time
to
ask
specific
questions
like
hey.
I
see
that
you
have
private
data
on
yours
or
you
could
flag
like
hey.
I
don't
know
why
you
would
need
police
video
surveillance,
so
we're
going
to
kind
of
open
this
up,
maybe
go
one
at
a
time.
A
If
notaries
have
watched
this,
I'm
going
to
give
you
the
floor
first,
so
any
notaries
that
are
on
the
call
that
would
like
to
ask
an
application
question.
The
floor
is
yours
after
the
notaries
have
finished
their
calls.
If
any
of
you
applicants
are
on
the
line,
you
want
to
provide
any
additional
contacts.
You'll
be
second,
so
all
mute,
any
notaries
that
have
any
questions
on
these
the
floor
is
yours.
E
C
A
C
A
There
are
some
common
questions
that
seem
to
come
up
again
and
again,
and
I
kind
of
put
those
as
prompts
for
like
what
you
should
address
and
some
of
the
common
questions
are
like.
Who
is
your
organization
like?
How
do
you
verify
that
so
providing
details
about
who
you
are?
Why
are
you
trusted
and
then
what
are
you
doing
with
the
data
and
then
addressing
some
of
the
questions
that
you
might
hear
like?
Is
it
open?
Is
it
public?
Does
it
benefit?
A
So
if
your
request
has
like
large
private
enterprise
data-
yes,
it's
going
to
hang
it's
going
to
require
a
lot
of
additional
steps
and
if
you
are
asking
for
these
large
data
sets,
if
you
are
asking
for
this
grant,
essentially
what's
going
to
be
is
the
onus
is
on
you
to
go
back
and
address
these
questions
to
provide
this
additional
information?
So
what
I
highly
recommend
you
do
is
that
you
look
at
other
examples
of
other
applications
that
have
been
processed.
A
A
So
maybe
that's
your
cue
to
say:
look,
I'm
going
to
look
at
a
few
other
applications
that
are
similar
to
mine
that
have
been
approved,
see
what
questions
have
come
up
and
then
answer
those
myself
as
I
go
through
there,
and
I
guarantee
you
you're
going
to
see
a
lot
faster
traction
if
you
come
back
to
the
application
review
and
be
like
hey,
you
might
be
curious
about
these
questions.
I've
addressed
them.
Here's
my
video,
I'm
waiting
for
a
data
and
then
I
could
help
fast
track
it,
but
that
seems
to
be
the
biggest
slowdown.
H
Yeah,
can
everybody
hear
my
voice
now
about
the
police
data?
I
want
to
mention
that,
as
present,
the
data
we
plan
to
store
in
fireclone
are
many
on
social
governance
and
have
been
stormed
on
our
own
platform,
so
this
data
can
be
made
public
and
assisted
by
anyone,
and
our
data
have
different
different
categories.
We
are
planning
to
store
in
five
coins.
H
H
H
H
So
we
we
want
to
put
some
of
our
data
that
can
everyone
to
allow
the
to
to
see
this
part
of
data
to
pull
down
the
file
coin,
to
have
a
fair
cover
like
a
a
truck
a
test
project,
some
something
like
that.
So
we
have
a
lot
of
huge
numbers
of
data,
but
even
5
5
pv
is
very
small
to
us,
but
we
want
to
have
a
try
to
to
have
a
good
start.
H
H
A
Yeah,
it's
a
good
point
about
the
public
and
private
data,
so
we're
not
I'm
going
to
mute
and
we're
going
to
kind
of
put
a
cap
on
this
one.
I
think
the
closing
thought
on
this
one
is.
Hopefully
this
system
is
going
to
start
to
improve
and
get
a
little
bit
better,
and
that
system
is
if
you're
an
applicant
and
it's
been
longer
than
a
week
and
you
haven't
seen
traction
a
good
way
to
kind
of
address.
It
is
look
at
past
issues
see
what
kind
of
questions
those
of
you
on
the
call
you're.
A
Seeing
that
a
lot
of
the
questions
are
like,
is
this
public
already?
How
are
we
doing
it
so
hunan?
I
know
that
you
have
more
questions.
This
is
great
to
take
it
to
that
application.
Review
slack
channel
that
way.
It's
a
public
record
is
going
forward.
Also,
remember
that
your
github
ticket
is
a
public
record,
so
addressing
linking
and
commenting
that
public
forum
is
what
we're
looking
for
and
that
will
take
it
back.
There's
going
to
be
another
call
taking
place
at
4
o'clock,
pacific
I'll,
be
posting
that
time.
A
So
if
you
want
to
come
back
to
share
more
details
or
just
make
sure
that
you
get
more
traction,
we
invite
everyone
to
that
call
so
with
that
I'll
stay
on
the
line
for
just
a
minute,
but
I
just
want
to
thank
everyone
for
dialing
into
the
june
14th
governance,
sync
and
respectful
of
schedules.
Thank
you
for
your
time.
I
keep
you
late.
Thank
you
again.
Everybody
welcome
to
the
second
notary
governance
meeting
of
june
14th,
2022
and
high
level
topics
for
agenda.
This
will
probably
be
a
faster
call.
A
We
did
this
morning.
We
took
a
lot
of
time
just
to
kind
of
flush
out
since
there's
substantially
less
of
us
on
the
line
just
to
kind
of
prep
you,
this
might
be
a
faster
one.
We're
gonna
introduce
you
to
some
new
friendly
faces
on
the
pl
side.
That
would
be
helping
with
the
governance
team
we're
going
to
take
some
time,
just
as
a
quick
check
in
on
metrics
to
keep
you
updated
on
where
the
performance
stands.
A
We're
going
to
highlight
three
community
issues
that
were
flagged
and
galen's,
going
to
give
an
overview
on
some
of
the
updates
with
ldvm,
we'll
update
that,
and
then
we
save
time
for
anything.
You
want
to
talk
about,
as
well
as
any
applicants
that
want
to
be
on
the
line
for
q,
a
so
the
high
level.
Those
will
be
the
main
agenda
points
and
subcategories
as
we
go
through
it.
A
So
with
that,
a
very
friendly
hello
from
deep
galen
and
myself,
who
you've
probably
seen
many
times
if
you're
on
the
line
for
the
first
time,
we're
going
to
ask
a
chance
for
you
to
kind
of
check
in
and
say
it,
but
you're
going
to
recognize.
This
slide
went
from
three
faces
to
fourth,
so
I'm
going
to
turn
the
floor
over
to
our
fourth
mystery
participant
who's.
Now
running
trust
and
transparency
for
the
network.
F
Hi
everyone,
my
name
is
ragev.
I
it's
my
second
week
here
at
pl
and
I'll,
be
as
kevin
mentioned,
I'll,
be
helping
out
with
trust
and
transparency.
So
what
that
looks
like
in
the
coming
few
months
is
thinking
about
the
risk
scoring
system
with
infill,
plus
also
thinking
about
client
onboarding
and
the
ux
side
of
things.
On
that
I
had
a
chance
to
meet
some
of
you
last
week
in
austin.
A
Very
happy
to
have
you
perfect
timing.
We
have
a
lot
of
these
questions
coming
up.
So
welcome
glad
to
have
you
if
you're
on
the
line
right
now.
The
next
slide
we're
going
to
ask
for
participation.
Consider
this
just
optional,
but
just
as
we
start
to
work
together
as
a
community
dialing
in
sometimes
it
gets
really
tricky
to
field
these
questions
that
come
in
from
slack
or
may
come
in
after
someone
who's
watching
it.
A
So
if
you're
on
this
line-
and
you
want
to
make
it
just
a
little
bit
easier
on
comms
for
yourself,
ours
and
the
community
take
a
moment
and
just
make
sure
that
your
name
is
something
that
we
would
match
so
make
it.
Your
slack
name,
make
it
your
github
handle.
But
sometimes
we
come
back.
We're
trying
to
field
questions
after
the
fact
and
it's
like
cool
power,
guy
number
27
and
we're
like.
I
have
no
idea
who
this
is.
A
So
if
you
set
your
name,
it
makes
it
a
lot
easier
for
us
to
help
you
out.
If
you
need
it
and
with
that,
we're
going
to
post
the
slack
for
the
sla
check
in
just
as
a
quick
heads
up,
we've
been
doing
this
for
the
last
four
notary
governance
calls.
Thank
you
galen.
I've
now
collected
all
of
that
data
and
in
the
notary
channel
tonight
and
tomorrow,
I'm
in
a
post
like
hey
notary
x,
I've
got
you
as
attending
the
last
four
out
of
five
governance
sessions.
A
Does
this
jive
with
your
schedule
as
well,
and
if
this
works
for
everybody
else
we're
going
to
switch
to
a
model
where
we
post
that
check
in
ahead
of
the
call?
So
we
don't
take
time
on
the
call
in
the
future
to
go
forward
and
it
will
auto
populate
into
the
leaderboard
that
alexandria
is
building
for
us.
So
this
is
kind
of
one
of
the
last
times
that
we'll
be
asking
for
this.
We'll
move
to
a
model
where
this
is
more
automated
and
then
pick
that
up
all
right.
A
A
We
are
rolling
out
the
data
cap
for
all
the
new
notaries.
We
went
from
20
to
50,
so
that's
taking
quite
a
significant
batch
of
time
and
then
a
lot
of
the
delay
is
also
from
our
waiting
for
ldn,
v3
and
so
dalen's
got
a
lot
of
great
news
when
we
get
to
that.
But
the
big
highlight
to
call
this
slide
right
now.
A
Is
that
that
time,
the
data
cap
we're
still
around
that
one
week
and
we're
going
to
call
this
out
with
any
applicants
that
are
on
the
line
and
you
might
submit
an
application
and
you
say:
hey
it's
been
a
week,
I
haven't
heard
back:
that's
pretty
normal.
If
you
go
longer
than
a
week,
something
might
be
off
and
we'll
talk
about
tips
for
applicants
to
make
their
their
data
cap
requests
go
a
little
bit
faster.
A
It
kind
of
looks
like
business
as
usual
over
the
last
two
weeks,
so
nothing
substantial
to
call
out
no
drastic
reduction
in
storage
capacity,
no
drastic
increase
in
storage
capacity,
the
big
takeaway
from
that
is
we're
still
just
kind
of
chugging
along
we're,
still
kind
of
like
no
big
drastic
changes.
We'll
highlight
this.
If
anything
should
change
now.
A
Here
is
the
first
thing
where
we're
looking
for
input
from
you
on
the
call,
so
I
realize
that
majority
of
us
are
screens
off
muted,
so
feel
free
to
type
into
chat
or
type
into
slack
or
to
unmute.
But
what
we're?
Looking
for
right
now
is
every
day
in
the
notary
slab
channel.
This
filter
bot
will
post
and
it
will
say
something
like
hey.
There's:
five
ldns
15
applications,
whatever
the
number
is
and
right
now
it
is
not
tagging
individuals.
A
So
we
got
some
feedback.
It's
like
yeah,
I'm
not
checking
it
because
I
don't
know
that
that
was
directed
to
me
and
so
one
of
the
feedbacks
we
got
was.
Can
we
make
that
filterbot
tag
each
individual
person?
We
brought
this
up
on
the
last
call
and
now
we're
going
to
put
it
to
a
vote,
and
so,
if
masaki
or
danny
or
anybody
actually
had
an
application
from
a
client
or
request
for
data
you'll
get
a
tag
and
it
will
say
hey.
A
This
is
waiting
for
you
and
it's
meant
to
be
a
friendly
ping
to
let
you
go
into
your
registry
and
clear
it
out.
Quick,
it's
not
meant
to
be
a
spam,
so
this
is
that
moment
where
you
come
to
chat.
You
say:
please
don't
tag
me.
I
think
the
slack
would
be
overwhelming
or
you
say
yeah,
let's
give
it
a
shot,
let's
test
it
out.
Galen
had
a
great
point
this
morning
and
it
was
this
filter
box
running
every
day.
A
If
we
test
out
the
tagging
in
slack
and
it
gets
to
be
too
much,
you
could
give
us
that
feedback
and
say
hey
dial
it
back
from
posting
every
day
to
maybe
twice
a
week,
so
I'm
going
to
pause
unmute.
If
anybody
has
thoughts,
galen
danny
anybody
in
the
community
feel
free
to
share
them
now
or
you
can
put
them
in
chat.
A
C
Yeah,
I
think
jesse
is
asking
if
we
could
put
maybe
something
like
using
the
example
on
the
screen.
My
client
allocation
request
for
yoshihito
photography,
issue
number
1718
assigned
to
the
sake.
It
may
be
something
like
opened
for
x
number
of
days
so
that
maybe
the
request
there
is
to
say
in
addition
to
tagging,
if
directly
in
the
issue,
we
could
have
prioritization
schema
so
that
people,
the
notary,
could
glance
at
this
and
say
of
the
five
that
my
name
is
showing
up.
Next
to
you
know,
one
of
them
is
much
older.
C
I
think
it's
an
interesting
idea.
I
don't
think
it's
impossible.
I
think
it
would
require
a
little
bit
more
tech
just
to
figure
out
how
we
would
calculate
it,
but
we
could
ask
the
team
to
see
how
hard
that
would
be.
I
think
my
my
gut
reaction
is
what
I
would
rather
is
when
the
notary
like
signed
on
and
saw
their
name
next
to
five.
C
They
just
did
all
five
and
if
it
took
like
too
long
to
do
that,
many
that
that's
a
different,
that's
a
different
issue
compared
to
like.
Oh,
I've
only
got
time
to
do.
You
know
one
of
these
allocations,
because
my
so
that's
just
my
like
hot
gut
take,
but
I
think
that
that
is
a
very
interesting
idea.
Definitely
something
that
we
could
ask
if
there
are
other
people
that
have
sort
of
similar
thoughts
on
how
useful
that
would
be.
K
Hello,
this
is
the
demon
yeah.
I
say
my
name
is
here
for
three
times
and
unstable
yeah.
I
have
a
suggestion
here.
I
believe
that
these
three
applications
I
had
some
questions
yeah
for
them
and
but
I
didn't
get
any
response
for
a
few
days
so
yeah.
If
they
yes
reminder
what
like
this,
I
will
give
this
kind
of
reminder
day
by
day,
but
and
actually
I'm
waiting
for
response
from
the
clients.
K
So
yeah
could
have
have
some
intelligence
to
say
that
yeah,
if
the
load
hurry
get
respawn
and
yeah.
If,
if
the
loader
response
is
a
last
comment
and
actually
yeah,
the
boy
is
on
the
client
side,
so
yeah
actually
yeah
for
the
three
items.
I
just
closed
the
issues
because
I
waited
for
10
days
yeah,
but
no
response.
C
Yeah
yeah,
I
think
it's
that's
a
really
good
point.
I
think
that
makes
a
lot
of
sense
in
a
in
a
perfect
world.
We
would
have
some
additional
tooling
to
change
the
labels,
because
what
we
would
want,
basically,
is
for
the
notary
to
post
a
question
and
to
then
change
the
label
to
say
you
know,
waiting
for
client
or
further
info
needed
and
then
for
the
client
when
they
replied
for
it
to
switch
the
label
back
to
you
know,
needs
diligence
so
again,
like
that's
a
really
interesting
idea.
C
That
makes
a
lot
of
sense.
It
would
require
a
little
bit
more.
You
know
tech
work
on
the
back
end,
because
right
now,
the
this
bot
that
posts
this
is
just
looking
for.
Is
it
open?
Does
it
have?
The
label
needs
diligence,
so
we
would
need
to
kind
of
manipulate
those
labels,
but
yeah.
I
think
that's
a
really
good,
really
good
idea
too.
We
couldn't.
We
could
look
at
that.
I
think
what
we're
really
trying
to
get
here
to
fundamentally
is
like:
how
can
we
notify?
C
C
L
Many
two,
so
the
first
one
is
like
is
it's
just
this
looks.
This
looks
fine.
I
do
kind
of
like
the
idea
of
the
two
days
or
the
twice
a
week
rather
than
every
day,
but
I
I'm
just
putting
a
vote
into
that.
The
other
question
I
have
is
have
we
what's
the
status
of
us
thinking
about
building
a
system
that
isn't
kind
of
hanging
off
github
for
all
of
this,
because
it
feels
like
a
lot
of
these
user
interface
and
notification.
L
C
You
know
danny
it's
it's
funny.
You
mentioned
that
and
it's
almost
as
if
we
work
together-
and
I
I
I
feed
you
these
questions,
but
I
really
genuinely
we
I
genuinely.
We
don't
but
deep-
and
I
have
been
have
been
dreaming
about
that
for
a
long
time
and
we
are
actually
in
talks
with
a
dev
shop.
We
have
some
exploration,
calls
with
a
dev
shop
this
week
to
build
some
client-facing
tools
and
this
kind
of
thing.
C
We
will
probably
continue
using
the
notary,
tooling
that
kiko's
built,
but
that
we
will
we
will
kind
of
disambiguate
the
client
part
of
it
off
of
github
potentially,
and
so
with
that
these
kinds
of
back
and
forth
conversations
where
you
know
stephen
asks
a
question.
It
needs
to
say
it
has
gone
back
to
the
client
we
can
track
when
the
client
replies
like
that
back
and
forth.
Could
theoretically,
sometime
in
you
know
this
this
year,
come
off
of
github
and
happen
in
another
platform.
C
So
that
is
a
dream
state
and
it
is
the
thing
that
we
are
in
investigation
because
there's
been
a
number
of
issues
where
people
are
like.
I
don't
have
access
to
github
github
doesn't
fit
into
my
workflow
github
deleted
my
account.
You
know,
there's
just
a
lot
of
when,
when
we
don't
own
that
surface
area
in
that
infrastructure,
it
is
really
hard
to
like
make
it
do
what
we
need
it
to
do
and
that
leads
to
lots
of
different
pain
points
across
the
program,
so
yeah
great
ideas.
C
A
This
one
so
jesse
what
I've
written
down
in
my
notes
is
that
having
some
kind
of
prioritization
schema
where
you
can
see
how
long
it's
been
open,
I'll,
explore
and
I'll,
let
the
notary
channel
know
on
that
and
stephen.
I
also
appreciate
that,
seeing
if
we
could
have
some
type
of
label
that
the
bots
pulling
from
that
will
tell
you,
you
have
immediate
action
that
way:
you're
not
getting
spammed
and
having
to
check
things,
that's
the
kind
of
feedback.
It
really
appreciates
just
wanted
to
drive
that
home.
Thank
you,
sweet
all
right!
Galen!
C
Yes,
happy
too,
so,
if
you
tuned
in
to
some
of
our
state
of
the
program
last
week
at
phil
plus
day,
we
talked
about
some
of
our
objectives,
kind
of
through
from
now
through
october,
for
the
entire
program
for
the
governance
team.
One
of
the
things
that
we
talked
about
doing
was
sort
of
organizing
ourselves
into
some
sprints.
C
As
far
as
the
system
status
goes
this
week,
we
will
be
starting.
The
implementation
for
ldnv3
has
already
kicked
off,
but
in
addition
to
that,
across
the
next
six
weeks,
we
want
to
add
some
additional
tooling
and
some
additional
training
resources
to
kind
of
make
sure
that
that
ldnv3
is
up
and
running.
So
it's
kind
of
a
high
level
system
status
goal
in
the
sprint
volume
wise
we're
trying
to
target
200
pips
sealed
in
data
cap
we're
at
a
hundred.
C
C
We
want
to
get
the
from
from
approval
by
the
gov
team
to
first
allocation.
We
want
to
get
that
to
less
than
three
days
and
we
want
to
consistently
get
to
days
without
data
cap,
for
you
know,
unpaused
applications
to
zero,
and
so
that
means
that
once
a
ldn
client
has
gotten
their
first
allocation,
we
want
the
subscription
top
up
subsequent
allocation
bot
kind
of
process
to
work
such
that
they
don't
run
out.
We've
gotten
pretty
close
to
this
we've
gotten
down
to
the
wire
on
a
few.
C
I
think
that
we're
doing
well
but
being
able
to
publish
that
as
a
win
will
be
great
from
the
engagement
side.
We
have
some
readme
documentation
updates
that
are
going
to
be
coming
out
across
our
different
github
repos.
From
the
governance
side,
we
are
looking
forward
to
seeing
some
working
group
proposals
for
some
proof
of
concept
in
the
six
week
sprint
and
from
the
risk
side
the
foundation
will
be
working
on
getting
a
job
description.
C
C
A
I'll,
just
kick
off
the
big
note
of
gratitude
to
those
of
you
that
came
in
person
just
big.
Thank
you.
It's
nice
to
have
your
company
get
to
meet
you
and
kick
off
to
those
of
you
that
smoked
spoke
meg.
Thank
you
for
coming,
giving
an
enterprise
proposal
meeting
the
communities
and
those
of
you
that
watched
it
was
kind
of
cool
to
be
able
to
like
tune
in
see
the
live,
viewership
and
then
go
forward
on
that.
Just
to
kind
of
keep
you
updated.
A
The
things
that
are
happening
right
now
is
we're
reviewing
all
the
videos
in
post-production
we're
making
sure
that
the
cameras
line
up
with
the
screen
share
with
the
audio
and
making
sure
that
they
have
appropriate
subtitles
for
mandarin
and
we're
going
to
be
handling
these
hanging.
These
on
youtube
in
the
coming
days.
A
So
everything
from
the
field
plus
day
will
be
posted,
live
and
we'll
have
that
back
up
as
we
watch
it,
one
of
the
big
takeaways
was,
it
would
have
been
nice
if
we
would
have
had
more
time
to
stretch
out
sessions
and
have
longer
q
a's.
So
we
might
be
talking
about
having
another
phil
plus
day,
maybe
like
scale
down
from
being
in
a
hotel
with
like
live
participants
to
strictly
online,
and
that
way
we
can
afford
some
more
time
to
it.
C
I
was
just
going
to
give
another
big
shout
out
appreciation
to
k-ray.
He
really
led
the
charge
on
this
and
wrangled
a
bunch
of
cats,
and
you
know
it
takes.
It
takes
a
massive
team
and,
as
you
guys
know,
anytime
you're
trying
to
organize
a
massive
team
with
different
stakeholders
and
different
competing
priorities.
Getting
them
to
pull
in
the
same
directions
are
difficult,
so
k
ray
the
success
of
this
event
like
doing
hybrid
events,
is
really
difficult.
Doing.
Hybrid
events
where
you
have
multiple
rooms
with
very
different
stakeholders.
C
You
know
it
even
events
are
complicated
and
so
to
for
us
to
pull
one
off
that,
I
think,
went
pretty
much
without
a
hitch
and
had
very
top
class
like
video
production,
the
the
we're
gonna
see
some
like
great
photos
from
it.
You
know,
I
think
that
the
room
setup
went
really
well
and
I
think
that
it
clearly
shows
that
we
have
invest.
We
invested
a
lot
of
time
into
running
so
props
to
k-ray.
C
A
Tbd
all
right
next
item
on
the
agenda
just
to
kind
of
check
in
it's
the
ledger
verification,
so
when
we
did
the
onboarding
with
all
the
new
notaries.
Thank
you
for
your
patience.
I
wanted
to
check
in
because
this
has
been
like
one
of
those
questions
that
we've
got
a
lot
of
dms,
so
two
points
to
this
and
I'll
hand
it
over
to
galen
for
two
additional
facts.
Point
number
one:
the
ledger:
verification
is
a
required
step
and
for
the
program.
A
The
reason
for
that
is
with
this
verification
step,
we
can
verify
that
the
notary
who
is
physically
the
kyc
on
this
is
the
same
notary
that
controls
the
signature
address
line.
Without
this
step,
we
truly
don't
have
any
kind
of
physical
kyc,
so
I
know
that
some
existing
notaries
have
been
using
other
scripts
and
different
ways
around
this.
Some
of
you
might
have
ordered
a
ledger
and
had
some
issue
galen
we'll
talk
about
that.
A
But
the
big
thing
that
I
wanted
to
drive
home
on
this
call
is
that
this
ledger
step
for
verification
is
a
requirement
for
signing
data
and
we'll
get
into
some
other
things
you
can
do
in
the
meantime.
What
I'm
asking
is
that
if
you
have
any
kind
of
technical
blockers
complications,
I
very
much
appreciate
the
group
threads,
the
dms.
I
think
what
may
be
happening
is
that
we're
overlooking
some
of
those
because
of
the
sheer
volume
of
dms
that
come
through.
A
This
way,
we
get
the
benefit
of
answering
your
question
in
a
public
record,
but
then
it's
also
a
lot
easier
to
unblock
you
same
day
next
day
to
those
of
you
that
might
have
had
to
wait
a
couple
of
days.
My
apologies.
Hopefully,
we've
got
you
all
squared
away.
We
have
a
very
short
list
of
those
that
you
haven't
registered,
but
the
big
takeaway
is.
This
is
a
required
step.
I'm
going
to
hand
it
over
to
galen
for
a
little
bit
more
on
that.
C
Yeah
so,
as
we
said,
some
notaries
have
not
completed
this
part.
I
do
know
that
there
are
subnetters
that
do
not
want
to
use
a
ledger
device
and
do
not
want
to
use
some
of
the
tooling
that
is
built.
That
is,
it
is
an
open
system,
and
that
generally
we
understand-
and
that
makes
sense,
but
for
the
tools
that
we
have
they're
currently
just
we
are
not
able
to
support
all
of
the
different
implementations
or
all
of
the
different
hardware
wallets,
and
so
we
have.
We
are
currently
using.
C
You
know
a
ledger
device
on
our
tooling,
so
for
the
notaries
that
do
not
have
a
physical
ledger
device,
for
you
know,
maybe
a
shipping
issue.
We
understand,
we
ask
that
you
continue
to
participate
and
keep
us
updated
and
we
can
ratify
you
once
you
get
that
device
and
then
we
can
onboard
you
to
the
different
tooling
services
that
we
have
for
summaries.
You
may
have
a
ledger,
but
you
haven't
done
the
verification
in
plus.fill.org.
C
C
So
please
jump
in
or
you
may
have
a
ledger,
but
the
address
on
the
device
does
not
match
what's
in
your
github
application,
and
this
is
leading
to
some
of
those
tech
issues
that
carrie
was
talking
about.
So
your
addresses
those
two
addresses
need
to
match.
If
you
are
having
an
issue
message
us
in
slack,
so
those
are
some
of
the
kind
of
scenarios
that
we're
talking
about
and
then
care
if
you
could
advance
for
me,
please
thank
you.
So
this
was
the
list
that
I
have
it
may
be
outdated.
C
We
may
have
already
gotten
a
few
updates.
I
haven't
gone
through
and
refreshed
all
of
this
list,
but
these
are
people
for
one
reason
or
another
that
I
have
in
my
big
ugly
spreadsheet
as
not
yet
verifying
their
ledger
device.
That
doesn't
necessarily
mean
that
these
people
have
not
been
ratified
as
notaries.
It
just
means
that
they
have
not
yet
verified
their
device.
A
A
All
right
proposal,
538,
was
floated
by
fat
man
during
the
week,
and
this
comes
down
to
the
time
of
this
call
so
essentially
we'll
post
the
link
here,
if
you're
keen
to
see
it
in
538.
What
the
proposal
was
talking
about
is
just
reviewing
the
times
that
we
do.
These
calls
as
a
quick
flashback
on
the
program
when
it
kicked
off.
There
was
one
call
a
day.
A
lot
of
the
feedback
was.
It
was
unable.
I
A
Make
the
call
so
we
split
it
into
two.
We
have
one
in
the
morning
one
in
the
afternoon,
and
the
goal
of
that
is
to
overlap.
So
our
afternoon's
your
morning,
vice
versa,
and
the
feedback
was
that
this
time
is
tricky
for
some
people
in
parts
of
the
world.
So
we're
kind
of
seeking
community
discussion
right
now
on.
A
Does
this
time
work
we're
going
to
kind
of
prioritize
those
of
you
that
are
on
the
call
right
now
for
feedback
and
then
we're
going
to
post
this
one
more
time
to
see
if
we
could
kind
of
get
some
additional
thoughts.
So
those
of
you
that
are
on
the
call
would
this
be
better
if
it
was
an
hour
sooner
an
hour
later,
keep
it
how
it
is
or
any
additional
thoughts.
C
A
For
transparency,
how
we
think
about
this
so
right
now,
it's
california,
it's
4
p.m!
Pacific
time
zone.
I
think
the
feedback
was
in
shanghai,
definitely
fact-checked
me,
but
it's
like
somewhere
around
6
7
a.m
and
the
feedback
was
if
it
was
a
little
bit
later.
You
could
get
there
in
the
office.
One
of
the
concerns
was
for
anybody
who
was
north
america,
then
you're
starting
to
push
it
to
like
five
six
seven
o'clock
or
you
might
see
twinkling,
there's
no
right
answer.
A
A
I
think
my
worry
is
that
we
move
it
an
hour
or
two,
and
then
we
drop
50
of
our
participation,
so
we'll
probably
be
pulling
this
I'll
try
to
make
it
as
low
lift
as
possible,
but
the
goal
is
to
make
this
as
easy
for
you
to
attend
as
we
go
forward.
So
any
other
thoughts.
Thank
you
for
posting.
That
link.
C
C
Okay,
so
talking
about
v3
rollout
rollover,
roll
up
roll
preposition,
we
some
news
for
all
you,
notaries
and
clients
that
are
on
the
call.
As
we
launch
this,
the
existing
approved
github
issues
will
remain
open.
So
if
you
are
a
client
or
you
are
notary
working
with
a
large
dataset
issue,
that
issue
will
remain
open.
The
subsequent
allocation,
the
next
allocation
that
it
is
ready
for,
is
just
going
to
come
from
the
new
v3
notary.
So
for
all
of
you,
new
notaries.
You
are
now
on
this
multi-sig.
C
Once
you
sign
into
the
tooling
and
see
a
new
ldn
request.
That's
coming
from
this
v3
notary
you'll
be
able
to
sign
that
if
you
were
to
sign
on
right
now
today,
I
think
you'll
see
something
like
I
can't
remember,
20
or
30
that
are
currently
ready
to
sign,
but
those
are
still
being
listed
as
coming
from
their
old
address.
C
We're
still
going
to
have
to
do
some
work
to
roll
over
those
allocations
that
are
already
either
in
process,
because
they
already
have
one
proposal
and
are
waiting
for
the
approval
or
because
they
are
marked
as
ready
to
sign
but
are
still
pointing
at
their
previous
multi-sig.
So
we'll
be
working
on
that
process.
If
you're
a
brand
new
client,
then
your
first
allocation
will
be
coming
from
the
v3
notary.
C
So
the
important
thing
to
kind
of
watch
out
for
as
both
clients
and
notaries
in
this
process
is
we're
going
to
be
using
this
label
that
is
state
approved.
This
label
should
be
going
on
and
only
coming
off
when
there
is
an
issue,
and
it
should
be
on
there,
so
that
all
of
the
clients
that
have
been
approved
and
are
ready
to
be
receiving
allocations
and
then
being
watched
by
the
subsequent
allocation
bot
should
have
this
label.
C
So
what
that
label
means
is
that
a
client
application
has
been
approved
by
the
governance
team
and
that
it
is
then
ready
for
diligence
and
signatures
by
the
notaries.
So
one
of
the
things
that
we're
really
trying
to
cut
down
with
this
step
is
the
delay
of
sending
it
to
the
root
key
holders
and
then
needing
the
root
key
holders
to
take
action
for
every
ldn
in
order
to
create
a
new
multi-sig
entity,
and
so
in
this
process,
the
root
key
holders
do
not
need
to
approve
every
ldn.
C
C
You
can
go
either
path
and
see,
which
ones
have
the
state
approved
and
ready
to
sign
when
it
has
those
two
labels.
That
means
that
it
is
on
the
notaries
to
do
that.
Diligence.
Look
at
the
past
deal-making
behavior,
we're
still
going
to
have
the
stats
bot
that
posts
that
deal
behavior
and
review
the
client
details.
Are
they
you
know
behaving
the
way
they
said
they
would
is
all
the
information
there
you
know.
Does
additional
diligence
need
to
happen
and
we're
encouraging
you
to
still
ask
more
questions
in
that
github
issue.
C
C
C
F
C
C
All
right,
hopefully,
you
can
see
these
slides.
Can
I
get
a
thumbs
up?
If
you
can
see
my
v3
rollout,
slides,
sweet
all
right,
so
notary
expectations
are
essentially
the
same
community
expectations.
This
is
for
the
governance,
team,
notaries
and
just
a
general
community
member.
If
you
see
something
say
something,
we
expect
you
to
raise
a
flag
for
a
large
dataset
issue.
If
you
have
a
question
about
it
and
you
would
like
to
pause
the
allocations
for
one
reason
or
another,
so
we're
going
to
come
up
with
a
comment
template
that
you'll
use.
C
We
will
have
some
tutorial
steps
and
we'll
be
putting
it
in
the
readme
where
notaries
can
create
a
saved
reply
or
anyone
can
just
go
and
copy
paste
that
template
and
the
bot
will
basically
go
in
and
put
the
label
state
paused
instead
of
approved,
and
what
this
does
is.
It
will
pull
it
off
of
the
front
end
so
that
it
doesn't
show
up.
So
if
you're,
a
notary-
and
you
know
you
come
look
at
an
ldn
and
you
think
I
can't
open
this
link,
their
sample
data
isn't
working.
C
I
you
know
want
to
ask
a
question:
while
you're
asking
that
question
you
may
think,
I
don't
think
that
it
is
safe
for
them
to
get
a
next
allocation.
I
don't
want
two
other
notaries
to
jump
in
and
sign
this,
because
it's
missing
some
really
critical
information.
So
you're
going
to
put
that
comment
on
and
you're
going
to
say
you
know
missing
this
waiting
for
this.
Ask
the
question:
wait
for
the
client
to
reply.
This
is
kind
of
similar
to
what
steven
was
talking
about
earlier
with
the
back
and
forth.
C
You
know
the
ball
is
then
in
the
court
of
the
client,
and
so
we
get
that
this
is
a
baked
in
slow
down
and
that
this
could
come
from
any
community
member.
So
that
may
be
a
thing
that
we
need
to
really
design
for
it
may
become
abused.
A
community
member
may
jump
in
and
selectively
pause
large
data
set
clients
for
some
reason
or
another.
C
A
Okay,
then,
what
we're
gonna
do
to
keep
with
our
promise
of
giving
you
a
few
extra
minutes
back
on.
This
call
is
gala.
Would
you
mind
going
to
the
second
to
last
slide
in
this
deck?
Please
I
see
that
we
have
some
application
applicants
on
the
line.
Thank
you
for
coming
just
for
essay
across
the
board
about
three
two
governance
calls
ago.
We
realized
that
we
had
more
applicants
who
wish
to
present
their
projects
than
we
had
realistic
time.
A
So
what
we
did
was
we
set
up
a
proposal
where
the
applicants
could
record
a
short
video
of
their
organization
and
their
data
request
and
then
make
that
available
video
available
to
notaries
for
review.
The
hope
is
to
not
have
to
spend
hours
on
demos
and
that
you
could
see
this
ahead
of
the
call
and
come
with
any
questions
as
we
roll
this
process
out.
A
The
intended
goal
is
that
I'll
share
in
slack
on
the
application
channel
and
the
private
notary
channel
the
video,
as
well
as
the
application,
and
that
way
during
the
call
you
might
come
with
questions
like
hey.
I
saw
that
application,
but
I
don't
want
to
get
involved
because
it's
private
data-
or
it
has
x,
y
and
z,
to
those
of
you
that
are
on
the
call
as
an
applicant
here
is
my
feedback
and
advice
number
one.
A
Number
two
is
that
if
it's
been
longer
than
a
week
or
two
and
you
have
not
gotten
a
response,
what
that
should
be
telling
you
is
that
the
notaries
who
are
looking
at
your
application
have
so
many
questions,
or
they
see
so
many
sticky
issues
that
they
may
not
want
to
dip
a
toe
into
really
kind
of
integrating
into
those
questions.
So
number
2.1.
A
My
advice
is:
if
you're
an
applicant-
and
it's
been
two
weeks
and
you've
had
no
notary
interactions,
is
to
look
at
previous
applications
that
have
been
approved
going
to
github
sort
by
approved
and
see
somebody
with
a
very
similar
data
set
if
you're
doing
vacation
photos
find
somebody
else.
If
you're
doing
like
home
security
find
somebody
else
in
that
workflow
and
then
look
at
what
questions
those
notaries
have
asked
them
and
try
to
address
that
in
your
github
application,
either
make
your
own
issue
and
say
that
or
then
come
back.
A
A
If
it's
clear-cut,
if
it's
standard,
if
the
website
use
case
all
makes
sense,
you'll
see
it
go
faster
if
you're
hitting
those
delays.
That
might
be
the
reason
why
I
would
happily
put
my
time
on
the
board
ping
me
in
the
application
review,
like
hey
kevin,
why
do
you
think
I'm
not
getting
any
traction
on
this
and
I'll?
Tell
you
hey.
I
have
20
questions
about
your
website.
Your
organization
maybe
address
these
and
then
that
will
make
it
a
little
bit
faster.
So
with
that
the
screenshot,
the
deep
excuse
me
that
galen
is
sharing
right.
A
There
were
some
of
the
applications
that
came
back.
I
posted
these
in
slack
if
you
want
to
grab
them
along
with
their
video
but
notaries.
On
the
call,
I
will
say
that
the
people
that
took
the
time
to
put
this
together
are
the
people
that
are
putting
in
that
extra
plus
one
they're,
not
just
like
phoning
it
in.
A
So,
if
you
were
keen
to
look
at
an
application
and
get
involved
and
have
somebody
that
is
a
willing
participant,
these
people
have
shown
that
they
are
willing
to
spend
that
extra
minute
to
get
you
the
information
that
you
need.
So
with
that
I'll
open
it
up
if
any
applicant
or
any
notary
has
questions
about
these
the
floor
is
yours,.