►
From YouTube: Filecoin Plus - April 11 Notary Governance Calls
Description
The seventh set of Notary Governance calls of 2023 April 11th to discuss the Filecoin Plus program.
Slides and Links: https://docs.google.com/presentation/d/1Wqgf9KVwn5Bv3ood0OGADtmdHu0bRRrNJ3UBviUfdE0/edit?usp=sharing
Agenda
Notary
Notary - Leaderboard participation
Registry - Updated URL address (https://filplus.fil.org) (no longer - plus.fil.org)
Governance
Mission Statement
Road Map Updates
FIP 0056
Update + Discussion w/ @Kaitlin_FF
Proposals
850: Diligence Flow
851: Increasing Datacap requests
821: Removal of Datacap
Working Group Updates
E-Fil+ 853: Upfront checks
T&T - Dispute Resolution Approach
T&T - Resolution Tracker
Community Discussions
Open Forum
All LDN application presentations are a-sync will be discussed in #fil-plus-application-review SLACK
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
Follow Filecoin!
Website: https://bit.ly/3ndAg44
Twitter: https://bit.ly/3ObND0x
Slack: https://bit.ly/3HKfFy7
Blog: https://bit.ly/3HFZFNv
Reddit: https://bit.ly/39N4Jmv
Telegram: https://bit.ly/3bkP8Ly
Subscribe to our newsletter! https://bit.ly/3Oy8J9j
#filecoin #ipfs #libp2p #web3 #nft
A
B
B
We
have
a
special
guest
speaker
joining
us
Caitlin,
beagle
coming
from
the
filecoin
foundation,
she's,
going
to
speak
a
little
bit
about
56
and
answer
any
questions
that
you
guys
might
have
about
that
process
or
how
it
closed
out
or
any
kind
of
next
steps
that
goes
along
with
it.
Then
we
have
an
update
as
far
as
number
five
zero.
This
was
the
due
diligence.
B
It's
been
on
our
schedule
for
two
weeks,
so
this
will
be
the
last
time
that
we're
talking
about
it
as
well
as
2-1,
which
is
the
removal
process
that
Simon
will
be
walking
us
through
and
lastly,
another
return
to
increasing
the
data
cap,
application
to
15
petabytes
one
last
round
of
discussions
before
we
close
that
out
and
move
it
offline.
We
have
working
group
updates.
Casey
will
be
joining
us
to
talk
about
853,
which
is
a
full
upfront.
B
Disclosure
for
the
Enterprise
field
plus
program
RG
will
be
unable
to
make
the
call
so
I'll
speak
on
his
behalf
about
the
resolution
process.
The
trust
and
transparency
put
together
as
well
as
how
that
process
works
for
having
a
public
repository
both
named
and
Anonymous
any
questions,
and
we
should
have
lots
of
time
at
the
end
of
the
call,
if
there's
anything
on
your
mind
that
you
wanted
to
bring
up.
B
As
always,
if
you'd
like
to
mention
anything
or
have
it
discussed,
please
post
it
in
chat
and
we'll
make
sure
that
we
can
kind
of
triage
that
question
we'll
say
it
out
loud.
So
anybody
watching
on
YouTube
can
answer
so
with
that.
If
you're
joining
this
governance
call
today
is
April
11th
per
California
time,
the
next
call
will
be
taking
place
on
April
25th
in
the
slide.
Deck
is
the
invite
to
this
link?
B
If
you
want
to
add
this
to
your
shared
calendar
and
keep
up,
but
just
a
friendly
reminder,
the
next
call
will
take
place
two
weeks
and
the
calls
take
place
at
zero,
eight
hundred
Pacific
and
1500
UTC,
as
well
as
1800
Pacific
and
zero
one.
The
next
day
as
we
go
forward,
we
post
the
agenda
in
the
governance
repo.
So
if
you
have
any
topics
that
you
wanted
to
ensure
were
included
whether
it
was
slides
or
a
talking
point,
please
see
that
agenda
add
a
comment.
Just
like
Hey
Kevin
can
I.
B
Please
have
a
few
moments
to
talk
about
X,
we'll
build
it
in
give
you
access
to
insert
slides
and
go
forward
and
as
a
friendly
reminder.
If
you
are
a
data
applicant,
if
you
would
like
to
prepare
a
video
we'll
make
sure
that
that
gets
shared
in
the
notary
channels,
but
we're
no
longer
dedicating
time
for
an
application
summary
as
we
go
forward
on
that.
So
with
that
notary,
SLA
again
big.
Thank
you
to
Catalin
and
spill
for
putting
together
the
leaderboard
Dash.
This
is
what
we're
looking
at
right.
Now,
it's
the
notaries
leaderboard.
B
With
this.
We
can
now
see
the
number
of
unique
clients,
time
to
data
cap
number
of
issues
created,
and
this
has
kind
of
a
stack
ranking.
This
is
the
second
week
that
we've
kind
of
rolled
this
out
we'll
talk
more
about
how
the
participation
works,
but
if
you
would
like
to
manage
and
show
your
participation
for
meeting
I'm
going
to
drop
this
very
unique
code
in
chat
right
now,
if
you
copy
that
code
out
of
chat,
you
can
then
sign
into
the
leaderboard
enter
that
chat
as
your
participation
name.
B
B
If
you
have
any
problems,
any
issues,
please
let
me
know
in
chat
and
I'll,
be
happy
to
come
through
and
help
you
after
the
call
or
triage
you
to
get
you
set
up
if
you're,
not
a
notary,
you're,
a
storage
provider
you're
a
data
applicant
you're,
an
interested
Community
member
and
you're
on
this
call
or
you're
watching
it.
I
highly
suggest
that
you
do
fill
out
this
form
when
we
have
the
elections
for
notaries.
One
of
the
questions
we
ask
is:
what's
been
your
past
experience
with
the
program.
B
How
have
you
contributed
and
participated
and
being
able
to
point
to
the
fact
that
you've
attended
these
governance
meetings
is
a
great
way
to
show
that
you've
been
active
and
a
member?
So
even
if
you're,
not
a
notary
you're
on
this
call
highly
recommend
filling
that
out
and
just
kind
of
connecting
yourself
to
these
links.
That
way,
we
can
kind
of
show
your
participation
in
the
program
with
that
all
right
notaries.
This
is
a
big
one:
we've
updated
the
URL
for
the
registry
page.
So
previously
we
were
using
plus.fill.org.
B
That
is
mean
Sunset,
so
you
might
have
seen
the
post
come
through
in
the
public
repos
of
slack.
This
is
just
one
of
those
friendly
reminders
to
please
update
your
bookmark
to
the
registry.
It's
now
fill
excuse
me
philplus.fill.org
and
when
you
follow
that
link,
this
is
the
new
registration
page,
no
other
changes,
but
if
you
have
the
old
one
bookmarked
and
it
doesn't
work,
this
is
the
reason
why
we've
updated
this
URL
so
make
sure
that
you've
update
your
bookmark.
B
That
way,
it
comes
through
hello
Chandra,
thanks
for
putting
that
in
chat,
I
appreciate
that
and
that'll
go
through,
and
then
why
didn't
I
see
your
question
in
chat?
I
tried
to
register
this
uuid.
It
says
empty
I'm,
going
to
assume
that
that's
for
the
leaderboard
that
unique
ID
for
the
meeting
was
coming
through
empty.
If
anybody
else
is
getting
a
problem
with
that
ID
that
I
posted,
let
me
know
and
I'll
come
through
otherwise
wine
and
what
I'll
do
after
the
call
is
I'll
manually
help
and
get
that
added
for
you.
B
If
it's
just
a
you
issue,
I'll
help
you
out.
If
anybody
else
has
that,
let
me
know
and
I'll
troubleshoot
when
it's
not
my
turn
to
talk
and
make
sure
you
guys
are
set
thanks
for
raising
that
all
right,
quick
friendly
check
in
on
governance.
So
you
know
the
governance
team.
There's
seven
of
us
here
to
help
you
with
whatever
you
have
set
up
across
the
program.
B
So
again,
we
have
a
very
specific
governance
team
here
to
help
you,
if
you
don't
know
who
to
reach
out
to
feel
free
to
tag
me
and
I
can
put
you
in
the
connection
with
the
right
member
of
the
team,
Galen
posted
in
the
public
Channel
a
couple
of
days
ago
about
a
very
public
road
map
that
we've
shared
and
the
highlights
on
this.
One
is
essentially
that
filecoin
plus
for
the
last
year
and
a
half
has
been
really
focused
on
bringing
that
data
in
meaning
large
quantities
of
data
growing
the
network.
B
B
If
anybody
wants
to
see
it,
and
essentially
what
this
will
allow
you
to
do
is
pull
back
and
see
what
we're
working
on
what's
currently
in
Flight,
what's
coming
on
the
pipeline
next
and
what
you'll
see
in
the
coming
months
of
2023.
So
this
master
plan
is
all
public
we're
going
to
be
releasing
a
lot
more
articles
on
medium
talking
about
the
work
that's
being
created,
because
sometimes
this
happens
behind
the
scene
and
you
might
not
be
able
to
see
it.
B
So
one
of
our
goals
and
2023
is
to
make
it
much
more
transparent
as
we
go
through
and
make
that
all
set
up
for
you
just
a
quick
reminder
on
our
mission
statement,
we're
looking
for
use
cases
on
data
onboarding
that
support
like
the
storage
through
a
governance
process.
So,
as
you
know,
fill
plus
is
putting
that
application
through
with
an
additional
level
of
diligence
by
members
of
the
community
that
have
a
vested
interest
in
the
stake
of
the
program.
B
So
with
that,
we
have
again
I'm
going
to
turn
the
floor
over
to
Caitlyn
and
she's,
going
to
talk
briefly
about
the
56.
What
was
going
on
where
the
status
was
and
any
notaries
on
the
call
that
wanted
to
ask
questions.
Caitlyn
is
a
subject
matter.
Expert
really
happy
to
have
her
on
the
call
so
Caitlin
thanks
for
joining
us
floor
is
yours.
C
If
we
haven't
met
previously,
my
name
is
Caitlin
and
I
work
as
the
governance
technical
program
lead
at
the
filecoin
foundation,
where
we
have
been
working
through
fit
56,
which
proposed
a
sector
duration
multiplier
for
the
file
coin.
Network
for
the
past
several
months.
Just
this
last
week
we
asked
for
core
devs
to
review
all
Community
feedback.
Receipts
dates
to
help
us
decide
whether
the
FIP
ought
to
be
accepted
or
rejected,
and
it
was
quite
unanimous
that
this
step
did
not
have
enough
Community
consensus
to
move
forward,
so
the
sector
duration.
C
Multiple
proposal
has
been
rejected.
It
is
not
eligible
for
inclusion
in
the
pending
Network
version,
19
upgrade
or
any
future
network
upgrades,
and
although
anyone,
including
the
authors
of
fit56,
are
welcome
to
author
new,
similar
fips
at
any
time
as
of
right
now,
I
have
no
knowledge
of
any
plans
to
reopen
any
future
proposals
for
a
segregation
multiplier
or
any
sort
of
similar
type
proposal.
C
Share
we're
moving
forward,
including
four
new
fips
in
again
Network
version
19,
which
is
going
to
land
on
the
network
mid-may.
Most
of
these
are
sort
of
technical
enhancements
and
upgrades
to
existing
protocol
components,
things
related
to
window,
post,
processing
and
and
cron
regulation.
Also,
nothing
too
flashier
too
exciting,
though
happy
to
provide
more
information
about
those
as
well
and
just
wanted
to
be
here
to
perhaps
answer
any
questions
that
anyone
in
the
notary
community
may
have
about
fit.
56
specifically.
C
C
But
ultimately,
it
was
according
a
really
group
decision
that,
because
storage
providers
themselves
were
the
ones
who
would
be
responsible
for
actually
implementing
this
policy
by
investing
and
upgrading
sectors
that
their
concerns
ought
to
be
heated
and
that
it
wouldn't
be
appropriate
to
decide
to
move
forward
with
this
tip.
Given
the
concerns
that
that
Community
had
raised
so
consistently
over
the
last
several
months
back.
A
C
Yeah,
of
course,
and
as
a
result
of
fit
56,
also
this
type
of
crypto
economic,
except
when
the
real
challenge,
to
the
way
that
we
process
protocol
governance
proposals
and
as
a
result,
we
are
actually
working
really
hard
to
shift
our
Focus
now
on
introducing
new
processes,
tools
and
mechanisms
to
help
ensure
that
governance,
as
it
scales,
is,
in
fact,
increasingly
decentralized.
Also.
C
So,
if
you're
interested
in
sort
of
these
broader
or
meta
governance,
questions
that
we're
trying
to
answer,
we
have
a
community
space
for
this
also,
and
you
all
are
more
than
welcome
to
participate
in
that
again.
Governance
of
the
filecoin
plus
program
remains
separate
from
protocol
governance
at
large,
but
we
do
want
to
respect
the
fact
that
all
of
you
are
filed
when
community
members,
even
as
notaries,
and
if
you
want
to
talk
about
FIP
one
changes.
C
Do
you
want
to
talk
about
potential
ramps
for
including
on
chain
more
governance
decisions
if
you're
really
curious
about
the
fit
56
process
or
want
to
understand
the
impacts
for
file
coin
plus?
More
deeply.
You're
welcome
to
register
to
join
us
at
our
next
Community
protocol
governance.
Call
they
happen.
Monthly,
but
the
next
one
will
be
on
April
24th.
So
just
a
few
weeks
from
now
and
as
mentioned,
Alexandria
I'll
pull
up
those
links
for
you
to
some
of
the
meeting
notes
and
documentation
from
the
56
discussion
specifically.
C
B
C
Yeah
great
question,
so
we
actually
just
launched
these
meetings
previously.
Protocol
governance
was
not
a
super
Popular
Community
topic,
since
it
tends
to
be
pretty
technically
dense,
but
we
will
be
setting
up
a
new
slack
Channel
just
this
week.
So
if
you
are
interested
in
that,
you
can
keep
your
eyes
on
the
Phil
Phipps
Channel
and
filecoin
public
slack.
That's
currently,
where
we
share
all
of
our
updates
and
information.
C
But
we're
going
to
be
breaking
that
out
so
that
fips
discussions
Etc
can
stay
separate
from
some
of
the
other
governance
discussions
we
want
to
have.
In
addition,
in
the
Phil
Phipps
GitHub
channel
in
the
discussions
Forum,
we
also
have
weekly
updates
that
we
post
with
all
of
the
necessary
information
that
anyone
may
need.
We
welcome
any
community
members
to
open
discussions
there
just
like
they
do,
for
filecoin
plus
governance
issues
and
again
in
the
interim,
the
Phil,
Phipps,
Channel
and
filecoin
public
slack
is
usually
the
best
place
to
reach
us.
B
Wonderful
I
appreciate
that
everyone
I'll
link
that
in
the
notaries
channel,
so
that
we
have
access
to
that
and
I'll
make
sure
that
it
goes
into
the
the
slide
deck
for
this
call
Caitlin.
Thank
you
so
much
for
the
time
to
come
and
explain
that
and
just
kind
of
outline
that
process
grateful
for
your
time.
Thank
you
again.
Yeah.
B
All
right,
so
with
that
we're
going
to
move
into
a
little
bit
more
of
a
tactical
slant,
we
have
three
proposals
that
are
currently
working
their
way
through
GitHub.
Consider
this
just
updates.
Some
of
these
have
been
on
past
calls.
This
is
a
chance
to
kind
of
re-emphasize.
What's
going
on
on
that
roadmap,
as
well
as
give
you
and
the
community
a
chance
to
ask
any
discussion,
questions
with
the
authors
themselves,
so
with
that
I'm
going
to
turn
it
over
to
Phil
for
the
talk
on
what's
going
on
with
the
diligence
flow.
D
Hey
guys,
so,
just
as
a
recap,
this
is
the
new.
This
is
going
to
be
the
new
notary
due
diligence
flow.
The
purpose
of
this
is
to
give
notrees
more
of
a
voice,
so
you
can
signal
to
other
notaries
if
you
approve
disapprove
or
are
waiting
for
evidence
from
the
clients
on
a
specific
LDN
application.
So
let's
say
you
want
to
you
think
an
application
looks
nice.
D
As
current
updates,
we
are
done
making
all
the
technical
functionality
and
we
are
testing
testing
different
ways
to
go
about
this,
because
we
don't
want
it
to
break
if
it
breaks
it
will
mess
up
a
bunch
of
labels
for
LDN
applications
and
that
will
slow
down
everyone.
So
we're
just
careful
now
to
not
push
something
that
breaks
and
yeah.
D
B
I
appreciate
that
Phil
Phil,
one
of
the
questions
that
I
saw
come
through
on
slack,
was,
is
this
a
process
that
has
to
be
followed
or
if
a
notary
wanted
to
take
a
separate
path
to
performing
their
own
diligence?
Will
they
still
have
that
creative
freedom,
or
will
this
be
like
a
mandatory
process
that
must
be
followed.
D
D
So
you
do
your
diligence
offline,
and
you
put
this
template
comment
on
the
on
GitHub
to
show
that
hey
I've
done
my
due
diligence
and
to
signal
to
everyone
else
that
you
have
done
your
due
diligence,
which
is
useful
for
other
notaries,
because
now
they
don't
have
to
redo
due
diligence
again,
if
they
trust
you
right.
So
it
will
make
all
your
lives
easier.
If
you
found
this.
D
B
E
Yeah
thanks
Kerry,
so
just
want
to
be
revisiting
this
proposal
to
just
give
some
background
due
to
The
Ledger
filecoin
app.
We
currently
cannot
support
the
ability
to
sign
messages
that
don't
end
up
on
change
and,
since
all
notaries
are
using,
the
ledger-based
addresses
we're
currently
blocked
from
building
the
original
data
cab
removal
feature.
E
A
lot
of
the
technical
blocks
have
been
noted
in
The
Proposal,
but
I.
Just
I
won't
go
too
much
into
it
right
now,
but
more
into
like
the
temporary
workaround
that
we're
working
on,
and
so
the
governance
team
started
to
take
action
on
this,
especially
with
the
program
moving
into
the
quality
phase,
so
we'll
be
using
two
new
notaries,
one
acting
as
a
proposer
and
the
other
as
an
approver.
E
E
Once
the
issue
is
live,
notaries
will
have
the
opportunity
to
provide
their
input
by
commenting
on
the
proposal
and
then
following
a
two-week
period
of
discussion
and
careful
consideration
of
like
all
the
comments,
if
there
is
a
consensus
or
majority
support
of
at
least
two
two
notaries
to
remove
the
data
cap
from
the
client
address,
the
TNT
working
group
or
the
governance
team
will
essentially
take
action
to
remove
data
cap
again.
This
is
just
a
temporary
workaround
until
we
are
unblocked
with
the
original
way
of
going
with
this
process.
B
B
E
B
E
Yeah
so
I
know
we
talked
about
this
in
the
last
notary,
governance
call
and
I
intentionally
tried
to
start
with
the
the
remove
data
cap
feature,
but
I
know
this
proposal
got
a
good
amount
of
comments
and
I
think
just
some
concern.
There
was
a
lot
of
people
who
raised
some
concerns,
but
I
guess
for
the
for
those
who
weren't
on
the
last
governance
call
or
did
not
see
this
proposal.
B
That's
great
Simon,
so
then
I
know
that
you
have
it
on
your
slide
there
about
the
current
allocation
process
that
in
the
first
allocation,
it's
the
lesser
of
five
percent,
so
that
won't
change
off
the
first
cycle.
This
just
means
that
if
you
have
that
larger
data
set,
you
can
still
use
the
program
great
update.
Does
anybody
on
the
call
have
any
questions
or
comments
or
any
discussions
on
this
proposal?.
E
E
Just
one
thing
forgot
to
mention:
yeah:
please
would
love
some
more
feedback.
The
governance
team
decided
to
basically
take
action
on
this
and
like
try
to
close
this
by
Friday.
This
coming
I
believe
that's
the
14th
and
we'd
start.
We
would
start
working
on
this,
so
please
we
really
do
appreciate
all
the
feedback
and
comments
and
even
just
ideas
on
maybe
how
we
can
improve
this,
because
these
concerns
are
great,
but
I
know
also
deep
made
a
good
comment
on
this.
B
F
Sure,
thanks
thanks
Kate
Ray,
so
hello,
everyone,
a
quick
update
on
the
e-fill
bus
pilot
I,
put
together
a
proposal.
It's
number
853,
there's
a
link
here
and
basically,
what
we're
looking
to
do
is
within
the
pilot
we're
going
to
iterate
on
what
we've
accomplished,
thus
far
towards
more
efficient
initial
allocation
approval
processes.
F
But
we've
learned
that
with
the
e-fill
requirements,
the
kyckyb,
not
as
many
questions
are
being
asked
to
get
to
that
point
of
trust.
So
we
want
to
implement
a
what
I'm
calling
a
full
upfront
check
so
based
on
a
lot
of
the
feedback
and
questions
that
notaries
would
ask
that
would
delay
sort
of
this
approval
process.
We
want
to
collect
all
that
information
up
front
to
alleviate
notaries
from
having
to
really
go
through
any
more
back
and
forth.
F
Essentially
what
they
need
is
listed
on
this
page
here
right,
we're
going
to
collect
data
owner
information
and
business
information
through
kyckyb
we're
going
to
collect
information
about
the
STS
involved
in
the
project
based
on
their
locations,
proof
of
data
centers
Etc,
and
then
we're
also
going
to
collect
more
information
about
the
data
set
itself.
The
size,
all
the
information
about
the
copies
where
they're
being
stored,
with
whom
proof
of
the
data
set
sample
data
sets.
So
this
this
is
the
basic
information
that
notaries
asked
for.
F
They're
expecting
you
know,
sort
of
a
quicker
turnaround
in
review
time,
so
I'd
like
to
enable
everyone
in
the
group
to
be
able,
you
know,
depending
if
you're
awake
in
the
west
coast
of
the
USA
or,
if
you're
in
Asia
in
China
and
you're
available
to
review
something
that's
been
submitted.
It
just
makes
things
a
bit
smoother
for
clients
who
are
looking
for
that
quick
turnaround
time
and
so
I
would
I
would
estimate
over
the
next
probably
two
months.
B
Kevin,
that's
really
exciting.
One
of
the
questions
that
I
could
see
coming
up
from
some
of
the
notaries
is
once
the
kyc
KYB
check
is
done
at
the
initial
upfront.
Is
there
a
goal
you're
looking
for
for
signing
like
sign
within
12
hours,
24
hours?
Is
there
like
a
Target
that
we're
hoping
to
get
to
after?
This
is
up
front.
F
I
I
the
initial
guidelines
that
I
I
reviewed
and
again
historically
as
full
plus,
has
evolved.
You
know
things
have
changed,
but
I
saw
three
days
was
sort
of
the
average
time
the
expectation
for
notaries
to
be
able
to
get
to
these
things.
I
mean
these
are
volunteers
who
have
other
items.
Let's
say
that
they
have
to
be
responsible
for
in
their
own
lives
and
they
don't
necessarily
have
all
the
time
and
energy
too,
address
a
lot
of
these
applications,
but
our
clients
are
becoming.
F
You
know
as
they're,
providing
more
and
more
information
and
being
more
transparent
and
providing
as
much
trust
as
as
needed.
The
expectations
for
approval
times
are
faster.
So
imagine
if
you
were
applying
for
kyc
on
you
know
a
web
3
company
site
you
would,
you
would
want
immediate
results
right,
you'd
want
the
check
to
take
place
and
you'd
want
to
be
approved
as
soon
as
possible,
so
that
that's
where
this
is
going.
It
can't
be
that
immediate,
obviously,
there's
a
lot
to
review
with
these
applications
and
finding
notaries
that
are
available
still
takes
time.
B
We
had
a
question
come
through
from
Chad
just
saying
this
out
loud
for
anybody
watching
the
recording
or
not
watching
chat.
It's
what's
currently
like
the
step
in
the
process.
That's
most
time
consuming.
So
if
a
notary
didn't
have
this
full
upfront
check,
where
have
you
seen,
delays
in
that
notary
due
diligence
process
so
far,.
F
One
is
just
because
we
were
assigning
notaries,
so
my
ability
to
have
a
notary
engaged
was
limited
and
I
might
have
to
reassign,
so
there
was
potentially
a
delay
there,
but
more
so
it's
the
back
and
forth.
So
if
a
client
does
not
provide
all
this
information
that
I
had
listed
on
the
screen,
notaries
are
going
to
ask.
F
So
let's
say
it
takes
a
day
to
send
a
message
and
then
a
client
takes
a
day
to
send
a
message
back
in
the
notary
if
they
respond
or
are
aware
that
they
got
a
message
back,
takes
them
another
day
right.
So
these
async
messages
over
different
time
zones
over
different
response
rates
can
take
days
weeks
and
that's
very
inefficient
using
GitHub.
F
B
That's
awesome,
Kevin.
Perhaps
it's
gonna
be
really
impressive.
Thanks
for
spearheading
that
sweet
RG,
as
I
mentioned,
isn't
on
the
call.
So
I'll
speak
on
his
behalf.
Anybody
feel
free
to
interrupt
me.
Simon
Phil
Casey,
if
I
say
something
or
you
have
any
more
additional
context.
So,
a
few
months
ago
we
got
the
flags,
it
was
really
good
flags
and
it
was
hey
I'm
noticing
some
violations
of
the
community
standards
either
the
way
that
the
data
cap
is
being
claimed
to
be
stored,
or
it's
duplicative.
You
know,
fill
in
the
blanks.
B
So
we've
had
a
lot
of
conversation
on
the
trust
and
transparency
side
on
how
to
bring
this
into
a
transparent
process
without
making
it
so
burdensome
on
the
community
to
respond,
or
those
of
you
that
are
finding
these
things.
So
there
was
a
Tracker
that
was
put
together
was
dispute.
Resolution
tracker,
I'm,
sharing
screen
with
it.
Now
this
is
a
public
tracker,
it's
linked
in
the
slides
and
what
you
can
do
with
this
is
see
specifically
what
the
trust
and
transparency
is
team
is
looking
on
and
what
their
status
is
as
they
go
through
this.
B
So
again,
this
is
is
meant
to
be
more
of
a
public.
Hey
is
this
on
the
road
map
for
trust
and
transparency?
Is
anybody
even
looking
at
this
data
right
now
to
kind
of
address
this
and
get
an
answer
on
why
this
is
taking
place
in
the
meantime,
RG
put
together
a
very
well
written
approach
to
how
that
dispute
resolution
is
taking
place.
It's
a
medium
article
it
published
just
recently
and
he
spells
out
the
steps
on
it
specifically.
What
are
they
looking
at?
B
So
again,
this
dispute
resolution
tracker
is
public
I'm
just
going
to
copy
the
link
here
and
put
it
in
chat,
so
everyone
can
see
it
again,
and
here
is
the
article
that
RG
published
the
medium
article
that
was
shared
online
just
in
case
you
don't
have
it
or
how
that
process
is
taking
place.
So
again,
this
is
meant
to
be
much
more
transparent,
also
a
much
more
abbreviated
process
rather
than
things
taking
months.
B
The
goal
is
to
get
these
down
to
a
few
days,
if
not
weeks,
for
that
abuse
process
to
be
brought
out
to
the
light
flagged
and
then
corrected
as
we
go
forward
so
I'm
going
to
pause
and
see.
If
anybody
has
any
questions
about
this
tracker,
the
article
or
anything
the
TNT
working
group
is
currently
focused
on.
B
Well,
all
right
I
will
have
one
Alibi
to
this.
Is
you
can
see
on
this
flag
on
this
dispute
resolution
tracker
dispute
raised
by
if
there
was
ever
an
issue
that
you
came
across
and
you
just
didn't
feel
comfortable,
putting
your
name
on
something
and
then
having
to
be
out
in
the
community?
You
can
always
flag
these
things
anonymously,
so
you
can
see
like
this
one
right
here.
This
violation
when
self-dealing
this
was
flagged
by
an
anonymous
member
which
is
just
totally
fine.
Okay,
I
want
to
stress
that
again.
B
Sometimes
it
could
be
a
little
bit
daunting
to
put
together
all
that
information.
Put
your
name
on
that.
So
big
big,
thank
you
to
those
of
you
that
have
done
that
have
taken
that
step
to
say,
look
I,
believe
in
the
program
I'm
willing
to
stand
behind
my
my
diligence
and
I
just
want
to
flag
this
for
others,
but
if
there
ever
is
a
case
where
you
see
something
and
you
wanted
to
flag
this
anonymously,
that
is
always
an
option
and
just
reach
out
to
RG.
B
He'll
obviously
know
who
you
are,
but
none
of
that
information
will
be
shared
outside
of
RG.
Specifically
that
way,
you
can
raise
these
issues
in
a
private,
more
Anonymous
manner.
Dylan
not
to
to
put
you
out.
We
have
a
few
moments.
Is
there
anything
that
you
wanted
to
kind
of
speak
to
or
call
back,
I
tried
to
talk
to
the
road
map
and
the
blog
post
that
you
had
recently
put
together,
but
if
you
have
any
thoughts
any
open
time,
no
pressure
just
wanted
to
make
sure
I
gave
you
an
opportunity.
G
G
So
you
can
check
it
out
in
both
places.
Go
check
it
out
on
medium.
First
give
it
claps,
because
that's
one
of
the
places
where
we're
tracking
metrics
more
closely
so
read
it
there
we'll
be
posting
things
on
that
Medium
page
more
frequently.
They
won't
all
be
kind
of
full
long
form.
Blog
posts
like
this
one
there'll
be
more
just
sort
of
updates
and
some
shorter
things.
But
if
you
wanted
to
just
go
ahead
and
follow
that
Medium
space,
but
then
speaking
specifically
about
it,
there's
some
information
about
mission
and
vision.
G
We've
talked
about
it
in
previous
governance.
Call.
The
mission
sort
of
wording
changed
a
little
bit
from
that
previous
governance
call,
but
you
can
go
see
it
and
then
there's
a
couple.
Call
outs
on
there
around
sort
of
how
we
are
trying
to
Define
sort
of
the
scope
of
the
programs
has
been
sort
of
an
ongoing
question
about
what
should
or
shouldn't
get
data
cap.
G
You
know
how
do
we
determine
these
different
stakeholder
groups
and
who's
eligible,
so
we
we
unpack
that
a
little
bit
in
the
blog
post
I
would
encourage
everyone
to
go.
Read
it
and
let
us
know
if
you
have
questions
if
something
isn't
clear,
this
is
the
definition
we're
going
to
work
with
for
now,
and
the
notaries
will
help
us
sort
of
unpack
it
into
specific
examples.
G
But
there's
been
a
lot
about
you
know:
should
certain
types
of
data
be
eligible
for
data
cap
or
not
that's
where
we
really
want
to
try
and
get
a
little
bit
more
clarity
for
everyone
in
the
community
so
check
that
out
specifically
about
the
com,
the
quality
phase
you'll
see
the
road
map.
There's
some
big
items
we'll
be
updating
that
public
roadmap
as
we
go.
G
We
have
some
things
getting
checked
off,
we'll
be
adding
new
things
to
it
and
we'll
be
adding
a
lot
more
metrics
and
dashboards
to
track
how
we're
doing
for
those
roadmap
items
so
I'm
excited
I.
Think
it'll
be
a
lot
more
transparency
and
accountability
both
for
the
governance
team
and
for
the
notaries
and
for
the
footprint
of
the
project.
Overall,
so
I'm
sure
that's
exactly
what
k-ray
said
when
he
pitched
it
earlier.
Sorry
I
couldn't
make
it
but
yeah
happy
to
answer
any
questions.
G
H
B
B
B
As
always,
if
there's
anything
that
you
wanted
to
add,
we'll
have
plenty
of
time
at
the
end
of
this
call
for
any
Community
discussions
and
always
feel
free
to
link
in
this
is
the
second
call
of
March
11.
Excuse
me,
April
11th
next
call
will
take
place,
April
25th,
and
you
can
see
the
schedule
for
the
year
remaining.
B
If
you
don't
have
this
on
your
calendar,
the
link
will
be
right
there
and
I
just
put
the
deck
to
tonight's
presentation
right
here
in
our
chat
as
we
go
along,
you'll
also
find
in
the
YouTube
link
as
well
as
in
slack.
If
you
want
to
see
any
of
the
slides
that
we
mentioned
in
this
presentation,
if
you
are
Keen
to
add
an
item
to
an
agenda,
feel
free
to
come
to
the
repository
and
just
say,
Hey
Kevin
can
I.
B
Please
have
three
minutes
to
talk
about
this
and
whatever
this
is
we'll
put
on
the
agenda
and
make
sure
that
it's
part
of
the
issues
that
we're
tracking
so
at
any
time
you
wish
to
discuss
flag
or
raise
an
issue.
Just
come
to
the
repository.
This
kid's
made
two
weeks
before
the
call
and
just
add
any
topics
that
you'd
like
to
share
and
I
could
reach
out
to
you
to
make
sure
that
any
slides
or
time
is
allocated
for
that
presentation.
As
you
go
for
you,
notaries,
on
the
call.
B
F
B
If
you
log
into
the
leaderboard
page
with
this
login
that
I'm
posting
now
that's
how
you
can
log
your
participation
in
and
I'm
just
going
to
grab
this
link
one
more
time
if
you
haven't
bookmarked
this-
and
this
is
the
leaderboard
that's
being
built
out-
that
will
actually
track
all
the
stats.
Ttds
participation
in
GitHub
repos
time
to
data
cap
analysis,
the
slas.
All
of
it
will
be
in
this
leaderboard.
So
again,
if
you're
on
the
call
and
you're
a
notary,
you'll
need
to
sign
in
using
the
GitHub
that
you
created
your
application
with.
B
So,
even
if
you're,
not
a
notary,
I
highly
encourage
you
to
follow
those
two
links.
That
link
will
be
open
for
a
while
for
you
to
sign
in
and
go
through
it.
If,
at
any
time
you
have
any
technical
questions,
feel
free
to
comment
and
chat
on
this
call
or
you
can
send
a
DM
to
Phil
and
I
in
the
public
slack
and
we'll
be
helping
to
troubleshoot
anything
that
you
may
have
as
you
go
through
it.
So
with
that,
let's
talk
about
notary
updates.
For
you
first
big
one
is
the
registry.
B
B
The
plus.fill.org
has
been
Sunset
so
just
to
shift
in
how
that's
phrased.
This
is
just
a
friendly
reminder
to
update
your
bookmarks,
because
if
you
follow
that
old
URL,
it
will
no
longer
work
and
that
new
philplus.fill.org
is
how
you
can
sign
into
the
registry
if
you
have
any
issues
as
always
feel
free
to
reach
out
and
I'll
link
you
into
the
right
pocs
to
get
that
fixed
for
you.
So
with
that,
let's
talk
about.
What's
going
on
in
the
government
side
of
the
house,
the
seven
members
of
us
make
up
the
fill
plus
team.
B
Our
titles
are
listed
right
below
us,
so
if
you
ever
need
help
in
any
aspect
feel
free
to
reach
out
to
any
member
of
our
team
responsible
for
that,
if
you're
not
quite
sure
who
to
go
to
for
a
question
where
you're
looking
for
a
friendly
ping,
always
feel
free
to
reach
out
to
me,
Kevin,
Dash,
FF
and
I
can
happily
route
you
to
the
place.
You
need
to
go
the
slack
Channel
or
the
POC.
That
would
be
able
to
help
you
the
most
so
again
reach
out
anything
you
may
need.
B
We
spoke
last
governance,
call
about
the
road
map
that
we're
working
on
one
of
the
goals
that
we're
kicking
off
here
in
the
first
part
of
2023
is
trying
to
make
the
fill
Plus
work.
That's
happening
much
more
transparent,
so
Galen
put
together
a
blog
post
in
medium
he
and
deep
outlined.
Essentially,
what
are
the
six
phases
for
fill
plus
taking
place?
B
Galen
spoke
at
length
about
these
for
how
to
find
out
about
them
how
to
kind
of
articulate
that
and
how
we're
transitioning
from
bringing
data
onto
the
file
coin
Network
and
in
2023
shifting
that
from
just
quantity
to
Quality.
So
a
lot
of
the
road
maps
that
we're
working
on
and
a
lot
of
the
tooling
are
focused
on
making
sure
that
the
data
is
onboarded.
Is
quality
data
to
add
to
the
betterment
of
human.
B
So,
as
you
look
at
these
as
you
look
at
this
blog
post,
that's
where
the
slant
is
going
and
a
lot
of
the
work
that
we're
talking
about
whether
it's
in
these
proposals
already
or
in
the
roadmap
that
we're
going
to
share
the
work
that
comes
out
is
really
focused
again
on
quality
of
data
that
we're
pulling
in.
So,
if
you
have
any
question
about
these
posts,
if
you
have
any
issues
feel
free
to
reach
out
in
either
the
slack
channel
for
notaries,
The,
Fill,
Plus
or
message
Galen.
B
Who
is
the
author
of
this
and
deserves
the
credit
and
props
for
putting
this
together?
It's
really
well
structured.
We
have
a
role
roadmap
with
engineering
Sprints
that
you'll
see
coming
down
the
pipeline
and,
as
always,
looking
for
your
feedback
and
input
to
make
sure
that
we're
serving
you
as
this
network
continues
to
grow.
B
Think
that
that's
probably
the
big
stress
point
that
I
would
say
that
we're
seeing
from
our
roles
on
governance
is
how
do
we
support
you
as
a
community,
especially
you
notaries
that
are
taking
your
time
to
look
at
this
data
on
board
this
data
and
make
sure
that
it's
benefiting
all
that
come
through
so
really
driving
home?
That
Community
governance
aspect
is
what
we're
working
on
and
making
sure
that
you
have
a
voice.
You
have
a
saying
that
this
is
built
in
a
way
that
benefits
You
by
you
for
you.
B
So
if
you
have
any
questions
on
this
again
feel
free
to
reach
out
and
we'll
have
plenty
of
time
to
Circle
back
to
this
on
the
end
of
the
call,
if
you
have
any
thoughts
room
for
improvement
or
any
discussion,
as
that
goes
forward,
the
broader
ecosystem
governance,
an
update
for
you,
if
you're
following
this
so
essentially
fit
56,
did
not
pass
lots
of
discussion.
Lots
of
ongoing
and
Caitlyn
joined
us
on
the
morning
session
to
kind
of
outline
where
we
can
find
some
more
resources
about
this
and
really
how
this
process
was
driven
forward.
B
So
I
put
two
of
those
links
these
weren't
included
in
the
morning
session.
These
are
just
now
added
so
I'll
make
sure
that
those
get
added
to
the
links
in
slack,
but
essentially
there
is
a
channel
in
slack
called
Phil
Phipps
in.
There
is
a
lot
of
the
links,
discussion
and
chatter
that
might
happen
offline
of
a
GitHub
repository.
What's
coming
down
the
pipe,
when
are
they
meeting?
What
are
they
talking
about?
There's
also
a
governance,
repo,
that's
linked
here
in
the
slide
deck
and
inside
of
that
governance
repo.
B
You
can
then
see
all
of
the
issues
that
they're
Tracking,
not
just
56,
but
what's
currently
in
progress,
I
took
a
quick
screenshot
and
put
that
in
this
slide
deck.
So
you
can
see
the
five
fips
that
are
ongoing
again,
these
Improvement
plans
are
really
built
off
the
community
and
the
input
that
gets
added.
So
if
you
were
a
notary,
please
speak
up.
Your
voice
is
counted
and
heard.
If
you
have
input
in
these
add
them
as
they
go
forward
and
in
this
community
tracking
board.
There's
also
discussions
that
you
can
take
part
in.
B
B
So
with
that
I'm
going
to
turn
the
floor
over
to
Simon
or
excuse
me
Phil,
and
to
walk
us
through
that
I
see
some
questions
in
chat
before
I
go
on,
I
will
re-post
the
code
here
and
then
I'll
repost
at
the
end,
just
like
an
air
table,
I
think
that
if
you
join
a
slack
or
a
yes,
a
zoom
call
after
I've
posted
it,
you
won't
see
it.
So
those
of
you
in
chat
I'll
post
that
link
one
more
time
if
you're
a
late,
Joiner
and
I'll.
B
And
awkward
Phil's,
not
on
the
call,
so
you
know
what
I'm
just
going
to
speak
to
it
and
Phil.
If
you
jump
in,
you
cut
me
right
off,
here's
what's
going
on
with
H50,
if
you're
a
notary,
you
realize
something,
it's
really
difficult
to
tease
out
a
lot
of
the
diligence
in
these
applications.
There's
a
message:
there's
a
back
and
forth
and
in
those
back
and
forth,
there's
lots
of
room
for
like
things
to
get
lost,
there's
not
always
a
script
on
what
to
do
so.
B
Phil's
been
working
really
hard
to
put
together
essentially
like
a
diligence
pathway.
So
it's
essentially
a
check
box.
So
if
a
person
asks
for
an
application,
they
would
then
be
prompted
to
provide
information.
Then
the
notaries
can
look
at.
Those
prompts
follow
these
scripts
and
then,
rather
than
having
guesswork
into
what
articulate
diligence
looks
like
this
script.
This
due
diligence
prompts
will
have
labels
and,
as
those
labels
Progressive
will
advance
that
LDN
through
the
system.
B
The
goal
of
this
is
to
make
the
lives
of
you
notaries
a
little
bit
simpler
when
you're
going
through
this
process-
and
this
is
just
one
of
those
small
steps
that
you'll
see
in
trying
to
make
this
process
as
easy
as
possible
for
you
to
make
quality
decisions
as
your
onboarding
quality
data
to
it.
So
the
issue
is
eight
five.
Zero
I'll
link
it
here
in
the
chat
as
soon
as
I'm
done
talking
and
it's
a
great
way.
If
you
want
to
share
any
comments,
this
is
the
third
time
we've
talked
about
it.
B
E
E
Sounds
good
thanks,
Carey
yeah,
so
right,
two
one
I
know
we
talked
about
this
a
few
weeks
back
and
a
few
notary
calls
back,
but
we'll
be
basically
revisiting
this
proposal
and
to
just
give
you
some
background.
Yeah
due
to
The
Ledger
file
coin
application,
we
are
unable
to
support
signing
messages
that
do
not
end
up
on
chain
addition.
E
Nationally,
all
notaries
are
using
the
ledger-based
addresses
which
is
currently
preventing
us
from
building
the
data
cap
removal
feature.
A
lot
of
the
technical
blocks
have
been
noted
in
The
Proposal,
which
I
commented.
I
won't
go
too
much
into
it
right
now,
but
you
can
definitely
check
it
out
again.
It's
the
latest
comment
in
The
Proposal,
but
I
do
want
to
go
more
into
the
temporary
workaround.
E
So,
given
that
the
program
is
moving
into
the
quality
phase,
the
governance
team
decided
to
take
action
to
get
this
going.
So
the
new
workflow
would
be
that
two
new
notary
addresses
will
be
used
one
as
a
proposer
and
the
other
as
an
approver.
These
notaries
will
act
on
behalf
of
actual
notaries
and
will
be
able
to
produce
these
signed
bytes
required
to
either
modify
or
remove
data
cap
balances
from
client
addresses
on
chain.
Again,
the
solution
is
intended
to
be
temporary.
E
Once
the
issue
is
live,
notaries
will
have
the
opportunity
to
comment
on
the
proposal
after
a
two-week
discussion
period
and
careful
consideration
of
all
the
comments.
If
there
is
a
consensus
or
majority
support
by
at
least
two
notaries,
the
TNT
working
group
or
the
governance
team
will
take
action
to
remove
datacab,
that's
kind
of
the
summary
of
the
new
workaround.
Again,
please
take
a
look
at
the
latest
comment
on
the
proposal
would
love
any
feedback
and
just
yeah.
E
Sounds
good
again,
yeah
I
know
we
talked
about
this.
One
I
think
the
last
Governor's
call
as
well,
but
for
those
of
you
who
weren't
there
or
did
not
see
the
proposal
just
to
give
you
the
short
summary.
Essentially,
this
idea
is
proposing
to
increase
data
cap
requests
for
all
DNS
to
a
limit
of
15
PID
per
applications.
B
That's
great
Simon,
thank
you,
so
I'd
like
to
pause
and
see
if
anybody
has
any
thoughts
or
comments
or
questions
on
851,
which
is
increasing
the
allocation
from
5
up
to
15
or
the
data
cap.
Removal
request
how
this
workflow
would
look
and
how
it
would
take
place
or
the
due
diligence
plan
that
Phil
is
working
on.
So
if
you
have
any
thoughts,
comments
or
questions
on
the
call,
this
is
your
chance,
just
shoot
a
hand
up
and
we'll
be
happy
to
turn
the
floor
over
to
you.
B
F
You
know
SP
locations
about
some
other
things,
so
I'm
attempting
to
to
put
together
a
list
that
will
require
all
this
information
to
be
produced
by
the
client
up
front,
and
then
we
want
to
test
to
see
if
this
is
really
enough
for
notaries
to
say.
Okay,
you
know
this
looks
good.
This
is
a
good
that's.
This
is
the
essence
of
what
we
need
to
to
essentially
produce
that
first
allocation,
so
over
the
next
10
15
data
data
set
allocations.
F
The
other
thing
that
we're
doing
here
as
well
for
those
of
it
following
along,
we
were
assigning
notaries
to
allocation
reviews
and
just
based
on
some
feedback,
we've
gotten
and
again,
just
in
the
in
the
essence
of
testing
continuing
to
iterate.
We
found
that
some
of
our
clients,
because
they're
open
and
straightforward
with
this
information,
they're
expecting
sort
of
reviews
and
and
checks
on
on
the
allocation
and
in
a
more
timely
manner.
F
So
we
found
by
by
assigning
there
were
issues
with
notifications
going
out,
and
there
were
issues
with
you
know:
notary's,
just
not
available,
which
is
understandable,
so
I
I
have
a
I,
have
a
full
working
group
of
35
notaries
that
are
that
can
be
available
to
do
these
checks.
So
we
just
want
to
open
it
back
up
to
all
of
them
to
enable
the
the
notaries
to
be
eligible
to
review
as
requests
come
in
whether
you're
in
a
different
time
zone.
F
So
this
is
this
is
what
we're
looking
at
moving
forward
like
I
said
we'll
look
to
test
this
over
the
next,
probably
two
months
or
so,
to
see
how
this
looks
with
the
ultimate
goal:
to
move
closer
and
closer
towards
automating
that
initial
allocation,
as
as
much
as
we
can
yeah
so
I'll
pause
there.
Okay,
ray.
B
Oh,
that
was
great
Casey
opening
it
up.
If
anybody
on
the
call
has
questions
about
this,
if,
if
I'm
hearing
this
is
like
a
somebody
who's
with
the
notaries,
the
big
change
is
trying
to
make
this
easier
for
you
as
notaries,
so
you're
not
always
having
to
check
GitHub
for
those
application
questions
and
then
also
removing
that
notaries
on
the
call
that
are
participating.
If
you
have
any
feedback
or
thoughts.
This
would
be
great
to
hear,
hear
your
input.
B
All
right
well,
if
anything,
should
come
up
we'll
have
time
at
the
end.
This
is
always
thanks
for
putting
the
comments.
Eight
three,
eight
five
three
is
in
the
chat.
If
you
want
to
add
any
input,
Casey
Man
props
can't
wait
to
see
this
and
awesome
stuff
that
you're
doing
there
rg's
not
on
the
call
so
filling
big
shoes
for
him
tonight,
speaking
to
what's
going
on
with
the
TNT.
So
ever
since
we've
really
started
to
take
a
look
at
the
Quality
data,
a
lot
has
been
asked
of
the
trust
and
transparency
working
group.
B
B
It's
called
The
Resolution
tracker
I,
just
put
the
link
in
chat
if
you
were
Keen
to
see
it
or
follow
along,
but
essentially
what
this
is
meant
to
be
is
a
public
transparency,
auditable
readable
for
anybody
who's
curious
to
see
what
the
trends
and
transparency
team
is
looking
at
and
what
kind
of
issues
they're
discussing
I'd
call
out
if
you're
a
notary
looking
at
this
for
the
first
time?
Is
it
there's
the
option
to
flag
things
anonymous?
B
Some
of
the
feedback
we
got
was
hey.
I
noticed
something,
but
I
don't
really
want
to
start
any
kind
of
discussion
or
have
my
name
be
involved
in
that,
but
I
wanted
to
be
able
to
flag
that
for
review.
So
RG
took
that
feedback
and,
as
you
can
see
some
of
the
lines
that
I
have
highlighted
on
the
slide,
if
there's
a
violation
that
you'd
like
to
Flag
by
messaging
RG
directly,
you
can
raise
that
without
having
to
ever
give
your
name
and
really
step
forward.
B
So
if
there
was
an
issue
that
you
saw
as
a
notary
that
you
wanted
to
flag,
but
you
were
fearful
or
just
didn't
want
to
deal
with,
whatever
might
come
from
that
discussion,
RG
will
take
that
and
make
sure
that
that
flag
is
raised
anonymously.
So
we'll
just
be
between
you
and
RG.
It
doesn't
go
out
to
the
working
group
and
it's
a
great
way
if
you
want
to
stay
transparent
and
stay.
Have
your
identity,
just
kind
of
not
shared
with
this
RG,
also
put
together
a
Blog
that
talked
about.
B
How,
essentially,
are
they
looking
at
this
approach
to
having
that
communication?
I'll
put
that
blog
here
in
chat
as
well,
and
essentially
what
this
is
is
just
a
medium
article
or
he
just
essentially
spells
out
that
every
week
on
Friday
they're
going
to
be
collecting
this
and
surface
these
voices
surface.
This
concern
in
that
spreadsheet
tracker
and
then
making
sure
that
that's
a
priority.
That's
going
along
with
the
tooling
that
Simon
and
filler,
putting
together
with
the
enhancements
that
Casey,
is
doing
on
the
Enterprise
side
of
the
house.
B
So
that
not
only
is
this
process
is
simplified,
transparent
and
easy
to
use
for
you,
notaries,
but
also
to
make
sure
that
that
data
application
is
going
out
to
the
right
intended
applications
and
being
signed
and
stored
in
an
effective
way,
so
that
blog
article
talks
a
lot
about
that.
It's
a
short,
probably
two
minute,
read
I
just
linked
it
here
in
chat,
it's
in
the
slide
deck.
B
If
you
have
any
questions,
so
this
notary
resolution
tracker
is
up
if
you'd
like
to
see
anything,
feel
free
to
click
on
that
as
you
go
forward,
quick
updates
from
our
side-
and
we
have
a
full
30
minutes
left
so
either
lots
of
conversations
coming
or
happening
online.
But
with
that
the
floor
is
yours.
If
you're
on
this
call-
and
there
is
literally
anything
you'd
like
to
talk
about-
stick
a
hand
unmute
the
floor
is
yours,.
H
B
It's
a
good
flag,
Danny
I,
apologize
that
RG
isn't
here
to
answer
that
and
since
I
don't
have
an
answer,
I
won't
make
up.
One
I
will
find
out
with
RG
and
I'll
make
sure
that
we
Post
in
slack
to
get
that
answered
thanks
for
flagging
that
and
we'll
get
an
answer
published
shortly
for
you
go
if
there's
anything
that
comes
up
as
always
feel
free
to
slack
us
or
mention
in
GitHub.
Otherwise,
thank
you
all
for
your
time
to
dial
into
this
call.