►
From YouTube: Mina Community Node Working Group Meeting | 03.29.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.
If any community members have questions or feedback on the latest 1.3.0 beta 5 release, please visit the #mainnet-block-producers channel on the Mina Discord: https://bit.ly/MinaDiscord
The issues discussed can be found on GitHub: https://bit.ly/NWG-issues
Chapters
0:00 - 1:16 Intro & Preamble
1:17 - 3+04 O(1) Labs - GitHub issues updates and overview
3:05 - 21:38 Q&A / Discussion
Transition to the new Delegation Program SNARK-work-based uptime tracking system
Berkeley QA testnet
Process for announcing Delegation Program scoring system
Mina Protocol – the world's lightest blockchain
A
All
right,
hello,
everybody
welcome
to
the
no
working
group
session
for
today,
we'll
start
off
with
the
preamble
and
we'll
go
through
a
few
updates,
and
then
we
can
get
on
to
questions.
Here's
the
preamble,
the
node
working
group
is
sessions
are
a
time
when
members
come
together
and
discuss
and
collaborate
with
ecosystem
partners
in
the
meena
foundation.
A
Topics
discussed
generally
include
latest
releases,
node
operations
and
other
technical
matters
related
to
the
protocol.
Although
this
is
at
the
discretion
of
the
node
working
group,
my
name
is
john
robinson
and
I'm
the
community
operations
manager
at
the
amina
foundation,
I'm
here
to
support
and
facilitate
these
meetings.
So
if
there's
anything
you'd
like
to
talk
about
or
anything,
I
can
do
to
help
out.
A
Please
just
let
me
know
the
meeting
will
be
recorded
and
posted
on
youtube
and
so
it'll
be
accessible
for
everyone
to
see,
and
if
you
have
any
questions
during
the
meeting,
it's
a
pretty
small
meeting
again.
So
just
you
can
just
shout
them
out.
If
a
lot
of
people
show
up,
please
use
the
button
down
below
to
raise
your
hand
and
there's
no
little
on
the
agenda
today.
So
we'll
start
off
with
updates,
as
usual
andrew
do
you
have
any
updates.
B
Yes,
a
little
bit,
I
think
we
talked
in
the
meeting
last
week
about
an
upcoming
alpha
and
that's
still
in
the
works.
I
should
have
the
time
to
put
it
together.
This
afternoon,
we've
been
doing
some
testing
on
the
side
and
just
trying
to
make
sure
that
everything
is
up
to
the
standard
that
we
that
we
intend
and
I
think,
we're
getting
there
so
yeah.
So
it's
in
good
shape.
A
C
I
don't
have
any
particular
updates.
I
have
been
looking
into
the
snark
work,
inclusion
inconsistency
that
has
been
discussed
at
some
recent
meetings
currently
planning
to
deploy
a
custom,
build
to
devnet,
to
help
give
us
more
information
on
this
and
try
and
recreate
the
scenario
there
so
that
we
have
more
information
to
develop
a
fix.
A
Oh
great
thanks
nathan,
so
if
anyone
out
there
is
interested
on
the
devnets
and
open
test
net
channel,
we
have
so
if
you're
watching
the
recording
later
on,
please
feel
free
to
join
in
there
and
you
can
check
out
the
information
in
the
pinned.
Messages
also
just
ask
questions
in
there,
and
people
will
be
able
to
help
you
out
so
yeah
a
good
chance
to
test
out
some
of
this
stuff
that
we're
building
here.
A
A
B
This
setup
now
funnels
everything
through
a
central
sort
of
load,
balancer
for
all
of
the
requests,
and
it
seems
to
not
be
handling
the
amount
of
traffic
with
everybody
signing
on
in
the
announcement
and
everything
that's
going
on
right
now,
so
we're
working
on
getting
sort
of
the
back
end
scaled
up
to
the
point
where
it
can
handle
everyone's
requests.
At
the
same
time,
I
think
we're
also
discovering
potential
other
bugs
that
will
need
to
get
resolved
here.
I
think
I
know
gareth
reported
one
that
seems
to
be
a
different
sort
of
crash.
B
Ideally
they
each
failure
for
the
uptime
system
will
have
a
much
better
message
that
actually
gives
the
failure,
reason
and
the
like
http
error
code,
and
that
will
be
a
lot
more
helpful
to
us
at
least
a
couple
of
those
so
that
we
can
identify
if
you're
all
experiencing
exactly
the
same
sort
of
failure
or
if
it's
potentially
a
couple
of
issues
that
that
will
need
to
be
resolved.
Yeah,
I
think
right
now.
B
B
I,
I
think,
that's
a
coincidence.
I
mean
I
think
I
think,
like
I
said
I
think,
there's
lots
of
people
coming
well
again.
I
would
love
to
hear
if
we
have.
You
know
I
I
need
to
see
logs
in
order
to
better
understand
if
everyone's
in
exactly
the
same
bucket,
but
the
experience
that
I've
been
seeing
on
my
own
notes
and
and
from
what
I've
been
seeing
reported
in
the
discord.
B
D
D
B
Yeah,
so
so,
there's
some
right,
there's
some
errors
that
it
that
it
will
always
give
during
catch-up
or
during
bootstrap
there's
an
error
that
I
think
is
is
potentially
deeper
and
and
maybe
related
to
something
else
that
we're
going
to
investigate
further
an
actual
like
failure
to
snark
the
transaction
is.
It
is
an
issue
that
we
want
to
investigate
and,
like
I
said,
we're
already
digging
into
what's
going
on
on
the
back
end
side,
to
make
sure
that
we
can
handle
the
request
volume
that
we're
getting
yeah.
B
Into
that
and
figure
out
what's
going
on,
that
is
the
new
part
of
what's
going
on
like
that
is
the
new
thing
with
this
ips
or
you
know,
with
this
change,
and
that
is
not
accepting
your
requests
as
efficiently
as
the
previous
like
direct
ip
system
was
so
that's
what
we
need
to
figure
out,
but
it's
a
service
that
has
been
scaled
successfully
by
many
people
many
times
before,
so
we
will
figure
it
out.
This
is
not
scaling
a
blockchain.
This
is
scaling
nginx.
I
think
we'll
be
okay,
but
yeah.
D
I
don't
know
if
it's
a
coincidence,
but
in
the
in
the
endpoint
that
we
were
sending
the
stats
to.
I
haven't
seen
those
retries
in
the
past.
I
don't
know
if
that
retrying
thing
is
like
new
in
the
latest
stable
version,
and
that
might
be
the
thing
that
we
see
in
the
new
locks
that
we
didn't
see
before,
but
I
I
see
timeouts
with
with
the
previous
end
point
as
well,
and
I
see
errors
as
well
there
with
the
previous
end
point.
D
A
D
B
Yeah,
so
I
think
the
other
thing
that
has
changed
really
is
that
nginx
returns
a
different
error
code
when
it
times
out
and
as
a
result,
the
the
client
actually
has
different
logic.
So
it
retries
because
it
returns
a
500
and
so
there's
something
wrong
with
the
back
end.
So
I
think
that's
the
main
thing
that's
happening
and
yeah.
B
In
any
case,
we
need
to
make
sure
that
and-
and
we
now
have
a
much
closer
to
the
real
user
base
for
the
number
of
nodes
trying
to
use
this
system
and
we
need
to
match
the
system
to
to
that
scale.
And
hopefully
a
lot
of
these
issues
will
ease
and
then
we'll
get
a
better
signal
about.
You
know
what's
really
still
wrong
and
what
we
can,
what
we
can
fix
from.
E
E
A
There
there's
quite
a
few
people
involved
in
that
too.
So
I'm
not
sure
if
andrew
could
answer
that
just
by
himself.
So
we
will
have
to
talk
about
that,
but
from
what
we,
what
we
heard
from
our
ecosystem
partner
on
tab
and
the
others
that
things
were
pretty
solid
so,
like
andrew
says
it
seems
to
be
just
the
server
in
the
middle
there.
The
web
server
so.
B
I
mean
I,
I
think
I
think,
in
terms
of
trying
to
get
the
bug
address
like
I
think
I
think
we're
it's.
You
know
high
priority
for
us
and
for
and
for
ontab.
I
think
it's
it's
going
to
get
addressed
as
soon
as
we
can
the
question,
but
you
know
I
I'm
not
even
really
involved
in
the
decision
making
process
for
how
the
how
the
program
operates.
So
that
is
a
whole
nother
question.
You
know
really.
I
think
we
need
to
gain
confidence
as
a
as
a
an
operating
group.
B
The
mina
foundation
needs
to
gain
confidence,
and
then
you
all
should
be
confident.
You
know.
Clearly
the
the
level
of
concern
in
the
discord
right
now
is
too
high
to
be
considering
this
the
production
system.
So
we'll
we'll
we'll
be
working
to
address
that
and
then
I
I
think
the
the
mina
foundation
can
reevaluate
that
that
decision.
E
E
D
B
B
Yeah
I
mean
I,
I
was
involved
in
a
lot
of
the
discussions
in
in
terms
of
trying
to
make
this,
because
I
you
know
I
I
wasn't
yeah
I've
been
involved
in
a
lot
of
the
design
and
some
chunks
of
the
implementation,
but
we're
really
trying
also
to
hand
this
project
off
to
folks
who
have
more
bandwidth
to
maintain
it
full
time.
It's
part
of
the
reasons
it
sat
for
so
long
was
because
I
didn't
really
have
the
time
to
be
working
on
it
and
it's
it's
just.
B
You
know,
on
top
of
all
the
other
day-to-day
responsibilities,
so
we're
still
trying
to
work
out
some
of
those
things
I
think
in
in
in
the
process
of
fixing
each
of
these
bugs
and
moving
forward
on
the
process,
we're
trying
to
figure
out.
You
know
who
can
maintain
these
things?
How
can
we
yeah?
How
can
we
have
a
high
level
of
confidence
in
in
all
of
these
services?.
A
D
A
B
D
B
There's
lots
to
your
point:
there's
there's,
there's
lots
of
other
work
that
has
gone
into
making
this
a
complete
and
and
useful
system
for
you
all,
and
that's
that's
really
the
thing
that
we've
been
building
towards
in
all
of
this
time.
You
know,
there's
the
the
client
side
that
we
wanted
to
get
out
into
your
hands
and
start
testing
as
soon
as
possible
because
it
is
incorporated
in
the
daemon
and
our
release
process
is
slow.
But
while
that
was
happening
you
know,
we've
been
developing
the
back
end.
B
The
ontap
has
been
working
on
a
front
end
and
a
leaderboard
and-
and
you
know
incorporating
that
into
what
we're
going
to
be
doing
in
the
future.
So
yeah
lots
of
hands-on
on
this
and
and
making
it
a
complete
product
to
make
sure
that
that
you
know
the
delegations
are
fair
and,
and
the
program
is
operated
efficiently.
B
A
D
B
Not
in
the
stable
version,
so
in
the
qa
task
force
channel,
there's
discussions
around
the
berkeley,
qa
net
versions,
there's
also
a
github
discussion
topic
around
berkeley
qa
that
will
allow
you
to
connect
to
the
current
network.
That
network
has
a
a
variety
of
tests
associated.
I
think
the
discussion
even
dictates
what
those
tests
are.
D
A
Natalia
also
has
a
question
here:
it
says:
do
we
have
an
update
about
the
criteria
that
will
be
used?
After
almost
all
the
block
producers
will
have
close
to
100
percent
uptime,
so
things
related
to
scoring
natalia
and
and
everyone
there'll
be
a
follow-up
coming
out
about
that.
How
the
scoring
will
be
determined,
also
related
to
some
of
the
other
things
that
we've
been
discussing
in
here,
like
related
to
the
the
community
suggestions
that
have
been
raised
above
the
delegation
program.
A
So
there's
still
quite
a
bit
of
things
coming
out.
We
we
really
wanted
to
get
this
and
people
to
start
upgrading
as
soon
as
possible,
because
it
will
take
quite
a
while
there's
there's
over
a
thousand
applicants
in
the
in
the
delegation
program
and
so
far,
there's
about
200
that
have
been
using
the
old
system
and
some
of
those
people
may
or
may
not
be
on
discord
or
easily
contactable.
A
B
Yeah,
I
just
want
to
say,
from
from
the
implementation
perspective,
we're
just
trying
to
figure
out
how
to
get
to
the
point
where
we
have
many
many
people
who
have
100
uptime
and
because
that
means
a
lot
of
things
are
working.
Well,
it's
a
good
problem
to
have,
and
then
I
think
the
community
immune
foundation
are
gonna.
Continue
this
these
discussions
on
on
on
what
you
know
what
happens
next,
once
we
get
there.
E
A
So
these
are
things
that
are
all
very
new
to
us
and
still
developing,
and
it's
it's
a
learning
experience
for
everyone.
But
what
we're
building
up
to
is,
you
know,
practicing
the
skills
and
building
up
the
tools
and
finding
the
best
way
to
reach
these
decisions
amongst
the
community
and
everyone
so
yeah.
There
will
be
a
kind
of
open,
open
discussion
on
these
kind
of
things.