►
From YouTube: Mina Community Node Working Group Meeting | 05.10.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.
The issues discussed can be found on GitHub: https://bit.ly/NWG-issues
Chapters
0:00 — Intro & Preamble
1:33 — O(1) Labs - Andrew - Updates (1.3.1-beta)
5:36 — O(1) Labs - Prithvi & Nathan - Node Triage Issues (updates)
15:31 — Q&A and Discussion
Mina Protocol – the world's lightest blockchain
A
Hello,
everyone
welcome
to
the
note
working
group
session
today,
we'll
start
off
with
a
preamble,
and
we
have
some
updates
to
go
through
and
I
see
we
have
some
questions
on
the
agenda
so
welcome
and
here's
the
preamble.
B
A
Foundation
topics
discussed
generally
include
latest
releases,
node
operations
and
other
technical
matters
related
to
protocol.
Although
this
is
the
discretion
of
the
node
working
group,
my
name
is
john
robinson
and
I'm
the
community
operation
manager
at
the
amina
foundation,
I'm
here
to
support
and
facilitate
these
meeting
sessions.
So
if
there's
anything,
I
can
do
to
help
just.
Let
me
know
if
you
have
a
question,
please
put
up
your
hand
and
we
can
get
to
the
order
and
you're
also
welcome
to
speak
out
too.
A
It's
not
like
there's
too
many
people,
so
yeah,
please
feel
free
to
speak
out.
This
meeting
will
be
recorded
and
posted
to
youtube
in
an
effort
to
increase
our
transparency
and
to
get
the
information
we
discuss
here
available
to
as
many
people
as
possible.
A
So
thanks
thanks
a
lot
for
adding
the
topics
to
the
agenda
today
and
what
we'll
do
to
start
off
we'll
hand
it
over
to
andrew
our
ecosystem,
partner,
owen,
labs
and
he'll
give
some
updates
for
us
andrew.
C
Yeah,
hello,
everyone,
as
you
may
or
may
not
have
heard,
there's
a
a
new
beta
release
out
on
maynet
1.3.1
beta
1..
That
includes
some
cleanup
to
the
docker
entry
point
that
should
make
it
a
lot
easier
to
use
a
mina
and
environment
file
that
works
for
for
debian
and
have
it
directly
work
in
in
docker,
as
well
as
some
new
little
bits
of
features
there
for
the
script,
and
it
should
improve
the
reliability
of
the
new
snark
based
uptime
delegation
client
the
front
end
of
that
that
new
system.
C
So
it's
recommended
to
update
that
as
soon
as
possible,
and
let
us
know
how
your
your
experience
has
been.
I
would
love
to
hear
from
anyone
here.
Who's
been
running
it
over
the
weekend.
D
Yeah,
in
my
case,
no
differences
at
all
between
the
cases
where
the
old
person
I
mean
the
stable
one
is
running
and
where
the
beta
one
is
running
it.
It
is
just
running
on
a
note
and
I
didn't
see
any
differences.
D
I
have
to
say
that
I
do
not
see
any
problem
in
the
other
run
in
the
other
nodes
running
the
stable
one.
So
probably
when
I
see
that
I
don't
see
any
differences,
the
fact
is
that
I
didn't
have
a
problem
with
a
stable
one.
So
that's
the
reason
why
my
case
has
you
know
differences
yeah.
I
understood.
C
C
It
should
not
infinitely
store
logs
anymore
into
a
into
a
file
and
therefore
eventually
run
out
of
disk
space
and
crash.
I
am
an
anti-docker
man,
okay
yeah.
So
then
the
debian
side
has
changed
less,
but
I'm
glad
that
yeah,
your
experiences
are
comfortable.
D
A
Okay
sounds
good,
then,
if
anyone
watching
the
recording
after
has
any
feedback
on
this
also
it'd
be
really
appreciated
and
you
can
post
that
in
the
mainnet
block
producers
channel
and
if
you
tag
linuscrom
you'll,
be
able
to
check
it
out
quite
quickly
and
I'd
like
to
say
thanks
a
lot
to
everyone.
A
Also,
who's
been
testing,
not
only
in
our
group
here,
but
people
watching
the
recording
for
all
the
testing
we're
doing
this
release,
as
andrew
mentioned,
has
some
features
aimed
at
the
delegation
program
and
I've
done
start
working,
and
so
many
people
out
there
updated
very
quickly
to
get
on
to
that.
So
we
can
continue
testing
and
it's
really
really
appreciated
and
that
kind
of
feedback
and
that
fast
response
and
everything
really
makes
it
a
lot
easier
for
everyone
working
on
it.
So
yeah
thanks
a
lot
for
that.
A
All
right,
do
you
have
anything
else,
andrew
any
other
updates
or
anything
like
that.
C
A
Great
thanks
senator
all
right
next
up
also
from
our
equal
assistant
partner,
11,
knives
prithvi.
I
believe
you're
gonna
go
through
some
of
the
no
triage
issues.
A
I
will
yeah
would.
A
B
So,
hey
folks,
this
is
one
of
the
boards
we're
using
to
track
some
issues
that
are
reported
by
yourselves
or
other
community
members.
We
did
a
little
bit
of
cleanup
of
it
earlier
this
week,
and
so
what
I'm
showing
you
here
today
is
kind
of.
What
we
understand
are
the
some
of
the
open
items
and
we'll
kind
of
discuss
like
our
strategy
in
terms
of
addressing
some
of
them.
B
If
you
feel
like
there
are
some
issues
that
you
are
seeing,
that's
not
represented
on
here
feel
free
to
send
any
of
the
github
issues
my
way
or,
if
they're
not
logged
in
github.
Yet
you
can
inform
me
about
them
either
on
discord
on
on
any
one
of
the
channels,
or
you
can
dm
me
and
we'll
make
sure
that
you
know
we
kind
of
try
to
triage
them
and
get
them
addressed
in
upcoming
releases.
B
But
for
now
this
is
what
we
have
displayed
is
kind
of
representative
of
some
of
the
issues
that
we're
kind
of
tracking
and
I'll
go
over
some
of
these
one
by
one.
I
think
nathan
is
here
as
well,
so
I'll
differ
to
him
on
some
of
the
specifics
on
on
on
other
ones,
so
without
if
there's
no
questions
I'll
kind
of
go
over
the
needs
triage
section.
B
So
the
first
issue
here
is
that
one
of
the
users
reported
that
in
this
version
the
node
was
often
restarting
it's
still
in
the
needs
triad
section,
because
you
know
we've
had
releases
since
then.
You
know
andrew
just
mentioned
we're
even
promoting
something
to
stable
fairly
soon.
So
what
I
did
was
I
asked
this
person
if
it's
reproducible,
if
it's
not
reproducible
in
the
latest
releases,
we'll
probably
go
ahead
and
close
this
one,
the
the
next
one
generated
blocks,
not
gossip
well
enough
to
appear
on
the
network.
B
I
think
this
is
an
old
historical
issue,
so
I
think
emory
are
you?
Are
you
online
here.
B
E
E
B
Okay,
great
and
once
you
get
that
yeah
just
do
let
us
know
yep.
E
B
So
I'll
move
on
to
the
next
one,
this
one
is
more
concerned
with
the
delegation
back
end.
We
were
seeing
some
errors
about
the
uptime
service,
not
getting
a
block
in
in
the
three
minute
schedule
window.
So
what
I've
done
is
I've
asked
the
members
of
the
delegation
program
channel
to
see
if
they
still
see
this
error
log
and
we'll
we'll
use
that
to
determine
whether
or
not
we
want
to,
I
guess,
continue
investigation
or
close
this
issue.
D
Yeah
question
the
question:
there
is,
if
you
don't
have
the
response
of
many
folks
at
the
time,
you
can't
be
sure
that
not
anybody's
getting
it.
So
I
mean
it's
just
a
couple
of
folks
who
responded
directly
to
me
and
the
question
there
is.
D
We
can't
know
if
anybody's
getting
it,
for
example,
with
the
logs
it's
the
same
happening.
We've
been
sharing
locks
there
of
the
new
open
system,
but
I
think
it's
a
10
of
us
or
maybe
15,
who
have
shared
the
logs
and
the
only
comment
here
is
yeah.
We
have
to
be
cash
there.
E
About
the
log
parts,
can
we
get
a
proper
documentation
on
maybe
the
main
website
and
somewhere
else,
because
we
are
not
in
it?
We
we
were
planning
to
get
integrated
and
I
left-
and
I
left
it
for
our
guys
and
they
couldn't
find
proper
place
to
getting
opt
into
the
lock
system
and
didn't
get.
Is
it
working
or
not?
So
can
we
have
a
documentation
on
that
more
clear
stuff?
That
will
probably
be
helpful
in
the
future.
C
B
Thanks
and
back
to
eisen's
point
yeah.
Definitely
we're.
B
I
think
we'll
need
to
continue
to
monitor
the
issue
regarding
the
the
error
log
in
there,
and
what
we
really
want
to
do
is
evaluate
whether
or
not
this
error
like
what
what
sort
of
effect
this
has
on
the
uptime
score
as
well,
and
so
I
do
need
more
people
to
check
their
logs
and
reply
back,
but
for
now
we're
probably
just
going
to
leave
this
in
the
needs,
triage
column
and
based
on
other
people's
reports,
we'll
make
them
determine
the
determination
of
whether
to
keep
it
open
or
close
it
so
going
on
to
the
lower
priority
section.
B
So
we
have
three
issues
here
and
I
was
wondering
maybe
nathan,
since
you're
here
you
might
be
able
to
just
say
a
few
words
about
some
of
the
investigation
that
you
and
the
team
has
done
on
the
undies.
B
I
know
I've
actually
gone
and
updated
this
one
specifically
about
the
transactions
rumor
from
mempool,
but
yeah.
If
you'd
like
to
say
something
before
is
yours.
F
F
F
B
Great
thanks
a
lot
nathan
yeah,
thank
you.
So
this
is
the
current
state
of
the
board.
Today
again,
I
am
monitoring
the
different
channels
on
discord
and,
if
you
see
anything,
you
know
definitely
feel
free
to
let
any
one
of
us
know
and
we'll
we'll
try
to
track
it
on
here.
It
just
helps
us
get
a
little
bit
organized
and
we'll
be
giving
updates
on
this.
So
there's,
no,
not
any
more
questions
yeah
feel
free
to
dm
me
or
post
in
any
one
of
the
public
channels.
A
B
The
other
thing
I
want
to
mention
is
just
thank
you.
Everybody
who's
been
participating
in
the
qa
net.
We
really
do
value
your
activity,
and
you
know
helping
us
like
find.
A
lot
of
the
issues
that
you
guys
have
been
raising
recently
helps
out
a
whole
lot
and
john.
Maybe
you
can
kind
of
mention
how
people,
if
they
want
to
get
act
active
in
the
qa
task
force.
How
would
you
ask
them
to
do
that.
A
Yeah,
absolutely
if
anyone's
interested
in
joining
the
qa
task
force,
you
can
ping
chris
f,
that's
me
or
post
in
one
of
the
channels
and
ask
if
you,
if
you
think
you
think
chris
f,
then
you'll
probably
get
a
faster
response,
but
otherwise
someone
will
be
able
to
direct
you
yeah.
It's
really
great
thanks
for
all
the
participation
there
too.
All
right
thanks
a
lot
for
the
update
stupid.
We
do
have
a
couple
of
questions
on
the
agenda.
A
I'll
just
share
the
screen
for
that
the
first
one
there
it
says
the
status
of
snarky
dapps,
dev
kit.
It
was
expected
some
time
ago
again
we
we
can't.
We
can't
comment
too
much
on
timelines
or
anything
that
hasn't
been
public
released
so
far.
But
if
anyone
could
comment
on
that,
that
would
be
really
great.
A
So,
okay,
let's
put
this
one
down
into
the
parking
lot
and
we
can
answer
that
in
the
channel
or
bring
that
up
next
time
and
get
some
more
information
on
that.
One
number
three
says
bridging
with
other
chains.
Some
announcements
were
made
too.
How
does
the
situation
look
like
implications
for
the
snark
worker
and
node
running
so
also,
probably
for
this
one?
We
can't
comment
too
much
on
anything
that
hasn't
been
public
released.
A
Yet
there
there
are
quite
a
few
things
in
progress.
Some
communications
will
be
coming
out
related
to
the
snark
worker
and
node
node
running
in
that
also
with
a
delegation
program,
there
will
be
some
announcements
very
shortly,
bridging
with
other
chains.
That's
also
something
for
these
kind
of
things.
Please
follow
this
announcements
channel
or
the
news
and
updates
channel
in
discord
and
as
soon
as
the
information's
there
we'll
put
it
up
for
you
guys.
A
Also
you
can
follow
on
the
website
as
well
or
the
blog,
I'm
not
sure.
If
there's
is,
does
anyone
else
have
anything
to
comment
about
these
ones.
B
C
There
was
a,
I
think,
the
big
news
regarding
bridging
is
that
the
nil
foundation
put
out
a
demo
of
verifying
the
mena
proofs,
which
is
one
of
the
prerequisites
to
building
a
bridge
and
we're
we're
working
through
all
of
those
prerequisites
or
some
folks
are
working
towards
satisfying
all
of
those
prerequisites
over
time
and
we'll
we'll
be
building
more
and
more
of
those
pieces
but
yeah
so
far.
That's
that's
the
exciting
piece
to
start
playing
with.
A
Yeah
yeah
do
do,
please
keep
your
eyes
open
on
the
announcement
channel
and
that
there
will
be
stuff
coming
out
over
the
next
couple
of
weeks.
So
all
right
great.
So
we're
basically
finished
the
questions
and
items
on
the
agenda.
Sorry,
some
of
them
didn't
have
much
that
we
can
actually
answer
here
at
the
moment,
but
that
information
will
come
out.
Does
anyone
else
have
any
questions
or
anything
they'd
like
to
discuss.
A
So
what
we
can
do,
then
I'll
stop
the
recording
here
and
if
you
could
stay
on
for
a
moment
or
two
after
we
can
just
have
a
chat
until
the
end
of
the
into
the
session.
A
All
right
everyone
well,
thank
you
very
much
for
that.
Thanks
for
the
updates,
andrew
nathan
and
griffey
very
much
appreciated,
and
thanks
a
lot
for
everyone
for
the
questions.
A
If
anyone
watching
would
like
to
participate
in
a
qa
task
force
or
any
of
the
other
testing,
that's
going
on
please,
post
in
one
of
the
discord
channels,
probably
mainnet
block
producers
or
the
devnet
channel,
and
if
you
ping
chris
f
you'll,
be
able
to
get
added
to
some
of
those
channels
all
right
everyone.
Well.
Thank
you
very
much
really
appreciate
your
time
and
we'll
see
you
next
week.