►
From YouTube: Mina Ecosystem Updates – Meeting #4 | September 3, 2021
Description
Mina Protocol's Ecosystem Updates sessions take place every few weeks and involve short updates and a Q&A with Mina's ecosystem contributors to share details on core protocol development, tools, wallets, and more.
Timestamps
0:00 - Welcome – Mina Foundation
1:27 - Core Protocol and Snapps – O(1) Labs
3:20 - Rust Implementation – Chainsafe
5:20 - Tooling// Delegation Program Uptime Tracker – Ontab
10:40 - Mina VRF-rs tool – Zero Knowledge Validator
17:30 - Community Website – MinaCrypto.com
22:20 - Q&A
Slide deck:
https://docs.google.com/presentation/d/1W92UjRT99B93l_4jD_-nX-e0Jfhrb6hXievi0-CIU74/edit?usp=sharing
If you're contributing to Mina's ecosystem and would like to share your updates at the next meeting, please fill out this form: https://bit.ly/EcosystemContributors
Mina is the world's lightest blockchain, powered by participants. Rather than apply brute computing force, Mina uses advanced cryptography and recursive zk-SNARKs to design an entire blockchain that is about 22kb, the size of a couple tweets, ushering in a new era of blockchain accessibility. With its unique privacy features and ability to connect to any website, Mina is building a private gateway between the real world and crypto—and the secure, democratic future we all deserve. Find out more at minaprotocol.com.
A
Okay,
well
again
welcome
everyone.
Thank
you
for
joining
this
nez
ecosystem
update
session.
My
name
is
christine
yip.
I
lead
the
community
efforts
at
nina
foundation
and
every
few
weeks
we
organize
a
call
where
everyone
can
get
updated
about
the
things
that
has
been
happening
in
the
last
weeks.
It's
very
exciting.
So
this
time
we
have
five
speakers.
A
B
A
A
C
Great,
thank
you
very
much
christine,
so
the
o1
labs
team
has
been
working
on
on
a
variety
of
different
work
streams.
Here
we
we've
been
chugging
with
snaps
and
snarky
js.
We
held
an
initial
sort
of
workshop
to
share
our
design
and
and
our
initial
implementation
with
some
community
members
and
some
people
from
other
zero
knowledge
proof
projects,
and
we
got
a
lot
of
awesome
feedback
and
we're
iterating
on
that.
A
D
Well,
hello,
yeah,
so
yeah,
so
yeah,
I'm
from
chainsaw
for
working
on
the
rust
implementation
of
minna,
if
you've
never
heard
about
it,
so
yeah
so
yeah.
So
since
last
time
we've
completed
our
first
milestone
completely,
which
is
the
surte
implementation,
so
the
our
rust
port
of
the
bin
library
used
by
oak
camels,
so
we're
now
able
to
fully
de-serialize
a
block
which
is
great
so
yeah.
D
So
that's
fully
done
for
now,
which
is
good
and
then,
since
that
we've
also
been
currently
working
on
our
second
milestone,
which
is
the
chain
selection
algorithm.
So
we're
continuing
implementing
the
parts
from
the
spec
for
that.
We've
also
been
working
on
auxiliary
data
structures
that
are
needed
for
that
that
aren't
explicitly
spec'd
but
are
used,
such
as
the
block
tree,
which
is
essentially
a
tree
of
all
the
forks
on
the
network
and
then
also
starting
to
look
a
little
bit
into
the
databases
that
we
could
use
so
yeah.
D
B
You're
you're
excited
to
be
here
it's
my
first
time
doing
any
of
these
community
updates.
So
thanks
for
having
us
and
very
quickly,
we
are
working
on
the
the
litigation
program
for
the
foundation
and
overlap,
so
we're
building
tools
for
the
foundation
mainly
to
be
able
to
keep
track
of
the
uptime
data
and
also
keep
track
of
the
human
obligation
for
the
delegation
program
and
follow
up
with
the
balances
and
keep
track
of
the
payments
received.
B
B
Or
christine,
do
I
need
you
to
yeah
click?
Next?
Okay,
thank
you!
So,
basically
high
level,
the
side,
sidecar
data,
we
can
do
a
search
based
on
the
state
hashes
received
from
the
block
producer
keys,
and
we
do
a
bit
of
that
filtering
for
removing
the
duplicates
making
sure
the
the
validity
of
the
data,
mainly
by
the
block
heights
and
the
state
hashes.
B
And
then
we
started
scoring
the
the
site
card
data
for
the
uptime
and
calculation
and
based
on
this
score,
we
are
gonna
list
out
the
the
positions
in
the
leaderboard
and
the
foundation
would
as
well
as
the
overlap,
would
go
ahead
with
the
delegation
to
the
top
120
nodes
and
based
on
the
top
120
notes.
We
start
basically
our
notification
system.
B
Next,
so
we
have
two
notifications
that
are
going
out,
so
the
first
notification
based
on
the
legated
accounts
on
addresses,
is
triggered
at
t
plus
100
in
the
new
epoch.
We
are
looking
at
the
number
of
blocks
produced
the
amount
delegated
to
a
node
and
we
do
the
calculation
one
for
foundation
and
one
for
overlap.
B
B
And
yeah
so
and
right
now
the
delegations
are
one
two
one,
and
so
we
basically
look
at
the
payments
received
from
the
delegating
addresses
from
one
labs
and
the
foundation.
So
that's
one
key
point
to
highlight
and
since
we
have
the
full
amount
delegation,
that's
basically
what
we
are
tracking
for
everybody's
information.
So
we
need
to
receive
the
payments
back
to
the
same
order.
B
And
one
point
to
highlight
here:
if
I
forgot
to
mention,
is
yeah:
we
do
keep
a
balance
per
epoch
too,
so
yeah
we
we
have
that
balance
behind
the
scene
that
we
keep
track
of
with
the
payments
that
we
have
received.
So
if
any
node
falls
behind,
we
have
that
balance
and
can
go
up
or
down
if
there's
overpayment.
We
also
know
that
and
can
keep
track
of
that
and
we
can
adjust
in
the
next
epoch.
A
E
E
E
E
So
that's
not
going
to
be
the
focus
of
the
tool
to
consider
the
cases
shown
in
yellow
but
to
focus
more
on
the
orange
and
red
ones
or
if
you
had
an
opportunity
to
use
the
block,
but
you
didn't
have
a
block
produced
in
in
the
slot.
It
could
be
because
your
producer
was
offline,
so
the
second
decision
tree
is
showing
the
case
where
a
block
is
added
to
the
slot.
E
E
So
this
is
something
you
could
improve
on
or
if
the
block
you
produced
was
the
right
height
and
you
had
a
better
vrf
than
other
block
produces,
but
the
block
you
produced
was
produced
too
late.
You
could
also
improve
upon
that,
but
then
there's
also
the
case
where
your
block
producer
wasn't
online
for
that
slot
and
you
just
didn't
produce
a
block
evenly.
Your
viera
gave
you
the
opportunity
to
produce
a
block
in
that
slot.
E
So
here
you
can
see
that
we
had
72
opportunities
to
produce
a
block
in
this
epoch
and
we
won
38
of
those
those
blocks.
So
that's
the
case
that
was
in
green
in
two
previous
slides
and
we
lost
33
blocks,
but
this
was
the
case
as
shown
in
yellow
which
it's
not
always
clear,
exactly
why
you
lost
the
block,
and
there
was
one
case
where
we
missed
a
slot
and
the
reason
we
missed
it
is
because
we
produced
a
block
too
late.
E
A
And
thank
you
for
your
team
for
building
this.
We
get
this
question
so
often
from
also
you
users
who
are
trying
to
select
a
validator
in
a
community.
We
have
over
200,
so
people
are
like
how
is
everyone
performing,
and
how
do
I
pick
the
right
validator
and
I'm?
I
believe
that
this
tool
would
be
very
helpful
in
that
yeah.
Definitely,
I
think.
E
A
F
F
It's
where
people
could
get
all
the
latest
news,
videos
all
those
kinds
of
things,
technical
analysis,
we've
also
got
competitions
on
there.
There's
information
on
staking
one
of
the
things
we
really
want
to
do
is
make
it
easy
to
understand.
So
I
noticed
before
a
lot
of
crypto
websites
are
quite
difficult
to
understand.
So
one
of
the
things
important
to
us
is
try
to
make
it
as
clear
as
possible,
and
you
know
try
and
get
rid
of
the
job
as
much
jargon
as
we
can.
F
F
F
F
F
We
also
want
to
try
and
set
up
some
kind
of
review
section.
So
we
can,
you
know,
prioritize
the
ones
working
really
well
and
if
we
can
also
help
the
community
testing
these
apps
as
well.
That
could
be
a
really
good
thing
if
we
can
debug
them
and
try
and
try
and
get
them
get
the
community
involved
with
we're
testing
them.
That
would
be
great
as
we've
got.
We've
got
lots
of
guest
writers,
who's
going
to
be
working
on
the
website.
F
Regular
contributors.
We've
got
lots
of
interviews
on
there.
I'm
sure
everybody
here
today
will
be
hopefully
at
some
point
happy
to
talk
to
us
and
give
share
their
knowledge
to
the
community,
so
yeah,
there's
we've
got
lots
of
more
things
to
come,
but
that's
but
that's
about
it
for
now.
If
you
want
to
go
to
the
last
slide,
this
is
just
a
bit
of
information.
F
F
A
F
A
A
C
Yeah,
I
I
I
will
say,
as
as
mentioned
in
the
o1
labs
update,
the
the
test
net
launch
will
be
in
november,
and
I
will
say
that
the
complexity
of
launching
snaps
without
impacting
the
stability
of
mainnet
is,
is
what
we're
trying
to
mitigate
and
so
it's
it
could
potentially
take
quite
a
long
time
to
get
to
that
state
through
that
stabilization
phase
on
the
test
net
before
we
move
into
maintenance.
So
there's
no,
no
clear
timeline
on
it.
A
Thanks
andrew
and
that's
that
was
a
great
question.
Pepman
event,
I'm
sure
when
the
time
comes,
we'll
also
share
some
more
detailed
updates
about
it,
and
also
you
know
if
you
would
be
part
of
this
test
net
being
part
of
making
snaps
possible
on
mainnet
yeah
you're
also
very
welcome
to
join
a
test
net.
A
C
A
G
I
just
had
to
rejoin
as
a
panelist,
so
so
that
I
could
answer
that
too.
The
snaps
tools
are
are
going
great,
so
as
part
of
building
snaps,
there
are
a
whole
bunch
of
different
tools
to
be
built
like
many
many
separate
ones,
but
we
have
a
very
clear
idea
of
what
those
are
and
a
pretty
clear
road
map
of
what
we
need
to
do.
So
now,
it's
just
a
matter
of
taking
some
time
to
execute
and,
like
andrew
said,
we're
kind
of
we
we're
really
hesitant
to
give
a
timeline.
C
G
Possibly
this
is
tbd,
yes,
so
we're
also
working
on
a
revamp
of
our
docs,
because
we
think
that's
gonna
be
really
important.
We
know
we
can
do
much
better
with
their
docs
and
and
so
we'll.
We
want
to
launch
with
really
good
docs
regarding
snaps,
so
yeah,
let's,
let's
just
say,
tbd
but
but
yeah,
and
we're
working
on
a
lot
of
that.
I
don't
wanna,
make
promises
on
that
at
the
moment.
G
I
haven't
really
planned
to
do
that,
but
we
could-
and
we
did.
We
did
do
a
workshop
recently
with
some
participants
to
get
some
feedback
on
our
tools
and
we
have
a
very
clear
idea
of
what
we
need
to
execute
on
so
right
now,
it's
just
a
matter
of
taking
some
time
to
get
back
to
the
code
and
start
advancing
what
we
know
and
then
further
on
to
like
maybe
a
month
out,
you
know
we're.
A
Oh
amazing,
thank
you,
andrew
and
jason
for
sharing
the
updates.
I
see
also
a
lot
of
excitement
in
the
chat
about
snaps
and
I
think
we're
at
time,
so
I
want
to
thank
everyone
again
for
joining,
and
especially
the
speakers
for
sharing
their
updates,
so
really
appreciate
andrew
elizabeth
bizzot,
susanna
and
pete
for
joining
today
and
speaking
and
jason
too,
for
sharing
his
update.
A
So
if
you've
built
something-
and
you
would
like
to
share
it
during
this
mina
ecosystem
update
session
too
and
then
feel
free
to
fill
out
the
survey
that
should
be
in
the
description
of
the
youtube,
video
and
yeah,
and
hopefully
we'll
have
you
speak
here
in
this
session
next
time,
all
right.
Well,
I
want
to
wish
everyone
a
great
day.
Thank
you
for
joining
and
for
the
zoom
participants.
When
you
leave
the
session,
there
will
be
a
survey
that
can
give
us
some
feedback.