►
From YouTube: Mina Community Node Working Group Meeting | 05.17.22
Description
The weekly Node Working Group session serves as a platform for the community, ecosystem partners, and the Mina Foundation to interact.
This meeting is a time to discuss the latest core protocol releases and for members to propose suggestions, raise issues, and provide and get feedback.
Issues discussed can be found on GitHub: https://bit.ly/NWG-issues
Chapters
0:00 — Intro & Preamble
1:33 — O(1) Labs - Andrew - Updates
9:10 — O(1) Labs - Prithvi & Nathan - Node Triage Issues (updates)
15:53 — New #archive-node Discord channel
19:28 — Q&A, Discussion - Delegation Program
Mina Protocol – the world's lightest blockchain
B
A
C
Yeah
I
have
a
few,
the,
as
many
of
you
know,
the
1.3.1
release
has
now
been
upgraded
to
stable,
it's
identical
to
the
previous
1.3.1
beta
1.,
so
many
of
you
should
be
running
one
of
one
of
those
versions.
Yeah,
please
upgrade
at
your
at
your
earliest
convenience,
and
I
would
love
to
hear
any
thoughts
in
this
meeting
about
how
the
experience
with
1.3.1
has
been
for
folks.
C
D
C
D
C
We're
able
to
get
more
of
that
information
now
because
of
the
node
status
collection
system.
So
if
you
enable
node
status,
we
will
be
able
to
know
what
version
that
node
is
running
and
be
able
to
track
those,
but
that's
an
opt-in
sort
of
interface
and
that's
how
we
would
prefer
that
it
is
kept.
So
no,
otherwise
we
don't
really
have
a
good
breakdown.
A
C
C
C
Me,
yes,
basically,
this
interface
will
give
us,
give
us
a
regular
sort
of
ping,
a
regular
push
of
information
about.
You
know
what
block
you're
currently
looking
at
as
the
best
tip,
what
version
of
the
software
you're
running
and
other
little
statistics
like
that
to
to
help
us
keep
track
of
how
well
the
network
is
running
at
any
given
time.
C
I
believe
the
ip
address
is
the
only
thing
that
we
were
sort
of
worried
about
in
that
regard,
and
I
don't
think
we
provide
public
keys.
So
it's
it's
really
not
about
tracking
your
key
or
your
funds,
or
anything
like
that.
We're
just
trying
to
track
that
node
and
software
that
it's
running
so
yeah
and.
C
C
A
F
F
The
screen
just
a
quick
overview.
We
went
over
this
last
week
as
well.
There
have
not
been
any
significant
updates
in
our
issues
in
our
low
priority
column,
apart
from
including
this
issue,
which
is
with
respect
to
some
of
the
discussions
that
we
had
previously
in
the
networking
group
about
the
snark
work,
inclusion
rate
and
so
nathan
had
created
this
issue
some
time
ago,
and
I
think
this
was
mentioned
in
the
google
document.
F
So
I
added
this
at
the
top
of
our
low
priority
column,
and
so,
as
I
mentioned,
I
mean,
there's
there's
not
really
been
any
significant
progress.
I
think
you
know
we're
we're
deferring
some
of
this
work
to
you
know
deliver
some
of
the
things
that
we
need
for
the
incentivized
test
net,
and
so,
if
there
is
any
change
in
status,
you
know
I'll
be
updating
these
tickets
and
letting
you
guys
know.
F
Apart
from
that,
there
are
two
issues
that
are
still
in
the
needs:
triage
column,
the
first
one.
You
know
I've.
I've
responded
to
this
community
member
and
tried
to
see
if
they
still
see
this
issue
and
I'll
ping
them
once
once
more.
But
I'd
like
to
ask
any
of
you
guys:
are
you
seeing
any
of
this
restart
issue
with
the
latest
releases
and
and
we
have
the
the
new
stable
release?
That's
that's
also
out.
F
B
F
Okay
yeah,
so
you
know
I'll
I'll
reply
to
metric
and
see
if
there's
anything
any
logs
that
he
can
share.
But
if
you
guys
aren't
seeing
it
in
your
in
in
the
newer
beta
and
stable
releases,
then
it
might
be
something
that's
specific
to
his
environment
and
if
he
can
provide
us
logs
that
allow
us
to
reproduce
it.
That
would
be
great,
if
not,
there's
not
really
much
more
investigation
that
we
can
do
really
without
that
information.
D
Yeah,
it's
jonathan.
I
just
I
just
wanted
to
ask
about
10
786.
I
know
you
popped
that
into
low
priority
thanks
for
adding
it
to
the
board.
I
wondered
how
much
discussion
there's
been
internally
just
about
the
priority
of
that.
My
thinking
is
that
it's
a
pretty
big
contributor
to
the
to
the
way
that
this
marketplace
works
and
if
we
were
buying
those
snarks
more
often
you'd
have
a
lot
more
inclusion
of
snark
work
from
people
not
producing
at
zero.
D
B
F
There's
just
there's
just
competing
interests
in
terms
of
priority
of
like
getting
some
of
the
features
that
we
want
to
deliver
for,
z,
caps,
ready
yeah.
I
understand
that
and
so
it's
just
a
little
bit
of
a
trade-off,
so
we're
kind
of
in
a
in
in
a
crunch
mode
right
now,
and
we're
definitely
going
to
try
to
address
this
as
soon
as
possible.
F
F
D
F
I
also
want
to
call
out
to
anybody
else
like
if,
if
there
are
issues
that
you
feel
like,
we
need
to
discuss
as
a
community
and
need
to
be
represented
here
on
the
board.
That's
one
way
to
do
it.
You
can
add
into
the
google
doc
of
the
meeting
minutes
here
or
let
me
know
on
discord
or
you
know,
post
in
any
of
the
channels
and
we'll
make
sure
to
at
least
talk
about
it
a
little
bit
but
yeah.
That's
pretty
much
it
guys.
No,
no
other!
F
A
F
Yeah
definitely
so
yes
was
it
yesterday
or
day
before
we
created
a
new
archive
note
channel
in
discord,
and
so
what
I'd
really
like
to
do
is
get
the
community
of
users
who
run
the
archive
node
service
together.
There
are
a
few
things
that
we'd
like
to
discuss
with
you
regarding
changes
to
the
database,
schema
migration
of
the
archive
database
and
really
get
a
get
your
opinion.
It's
it's.
G
C
Yeah
it's
about
how
we
can
sort
of
engage
with
the
community
of
folks
who
are
actively
volunteering
to
run
archive
nodes,
and
you
know
make
sure
that
the
direction
that
we
have
in
mind
for
the
archive
node
matches
up
with
what
you
all
are
expecting
and
looking
for.
And
you
know
that
we're
building
tools
that
you
will
make
use
of.
F
Yeah
and
to
piggy
back
off
of
that,
I
don't
think
we
have
a
central
place
on
discord
to
talk
specifically
about
archived
node
related
issues.
So
it's
just
a
good
place
to
just
you
know
have
that
discussion,
because
sometimes
it
happens
on
qa
task
force
or
on
mainnet
block
producers
just
in
different
places,
and
so
hopefully
you
know
we
can
gather
all
of
you
guys,
even
if
you're
not
running
an
archive
node
and
you
want
to
participate
in
the
discussion
please
join
in
you
know
your
opinion
is
very
valuable,
so.
D
I
decided
a
while
ago
to
stop
running
sidecar
and
I've
just
been
running
the
new
uptime
service.
I'm
not
the
latest
announcement
that
went
out
really
ask
that
you're
running
both.
I'm
I'm
wondering
if
there's
any
reason
that
I
would
really
care
about
that.
I've
decided
I'll.
Just
wait
till
the
new
service
is
in
use.
A
A
A
G
C
A
C
A
A
B
A
B
H
A
B
A
And
let
everyone
know
when
they
come
into
effect.
For
example,
we
mentioned
the
kyc,
something
that
was
coming
into
effect
and
there
will
be
other
ones
and,
as
as
we
implement,
those
they'll
also
be
we'll,
have
further
information
and
thanks
a
lot
questions
and
if
anyone
else
watching
the
recording.
After
has
any
questions,
you
can
ask
in
the
description
program
channel
and
let's
see
this
quite
a
bit
each
time,
but
we'll
have
maybe
one
more
question
and
kelly's
asked.
A
A
I
don't,
I
don't
really
know
what
I
can
say
about
that.
That's
something
that's
kind
of
up
to
them.
They
do
that
or
we
automatically
kicked
from
the
delegation
program.
So
we
do
have
a
post
coming
out
with
that
shortly
supposed
to
come
up
today,
but
just
waiting
for
a
couple
more
people
to
have
a
forget
it
before
we
post,
I
will
have
specific
information
on
how
that
will
be
handled.