►
From YouTube: Mina Ecosystem Updates – Meeting #3 | August 13, 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, wallets, and more.
Timestamps
0:00 - Welcome – Mina Foundation
1:55 - Core Protocol and Snapps – O(1) Labs
3:44 - Rust Implementation – Chainsafe
6:50 - GraphQL API Endpoint – Mina Explorer
14:02 - Auro Wallet – Niuniu/Bit Cat
17:50 - PodSNARK – Mina Development Group
20:12 - Q&A
Slide deck: https://docs.google.com/presentation/d/1Ce8J5FGF1X_z4TanDfcMmrNfs1W98yPuT2G6z-g1f2s/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
All
right
well,
we're
also
recording
the
session,
so
hello,
boston,
mike
so
people
who
couldn't
make
it
in
time
they
can
always
watch
it
back.
I
know
we
have
a
full
agenda,
so
I'd
like
to
start
so
hello.
Everyone
welcome
to
the
mina
ecosystem
update
session.
My
name
is
christine
yip
and
I
lead
the
community
efforts
at
mina
foundation.
A
A
C
D
C
Threaded
process
and
we're
testing
some
potential
solutions
until
a
rust
solution
is
available
for
the
long
term.
We're
also
looking
at
certain
network
performance
improvements
regarding
the
pdp
layer.
This
should
be
really
pretty
great.
Instead
of
fetching
blocks
that
have
already
been
received
when
that
header
is
is,
has
already
been
been
seen
by
the
node.
It
won't
fetch
that
full
block
again,
so
this
will
greatly
reduce
bandwidth
usage
and
should
really
help
stability
issues.
D
D
So
first
is
the
last
bit
of
serialization,
so
this
is
actually
the
first
thing
we
start
to
work
on
when
we
first
start
the
project.
So
we
have
two
pieces
left.
The
first
one
is
the
layout
parser,
so
it's
basically
the
rest
library
to
read
and
traverse
the
type
layout
files
that
can
be
generated
by
the
ocam
types.
The
second
piece
is
the
loosely
type
deserialization
so
before
we
have
actually
replicated
every
type
that
makes
up
a
mina
block.
We
are
developing
a
loosely
type
improv
deserializer.
D
D
It
also
helps
us
to
write
tests
until
the
strongly
typed
implementation
is
completed
next
up,
there's
block
selection
logic,
so
this
is
the
main
focus
for
us
right
now,
and
the
block
selection
logic
is
what
we
would
need
to
decide
which
block
to
include
in
a
collection
of
blocks.
That's
received
from
the
network.
D
D
Lastly,
there's
the
checkpointing
algorithms,
so
the
checkpointing
api
is
how
the
mina
blockchain
decides
whether
a
fork
in
the
chain
is
long
or
short.
So
we're
also
in
the
process
of
implementing
this
as
the
specs
are
getting
updated,
and
this
would
help
us
decide
or
figure
out
which
chain
is
the
honest
chain
or
the
correct
chain.
D
E
Okay,
hey
everybody!
I'm
gareth,
I'm
going
to
give
a
quick
overview
of
the
mena
explorer
graphql
api.
Can
we
go
to
the
next
slide?
Yeah
perfect?
So
what
is
it?
It's?
A
it's
a
custom
archive
node
that
works
by
persisting
graphql
block
subscriptions
from
the
daemon
and
exposing
all
of
this
historical
data.
What
it's
not
is
it's
not
a
proxy
to
the
meena
daemon
graphql
api
itself.
There
are
some
really
good
public
endpoints
out
there
like
minograph.
E
E
So
what
problem
are
we
trying
to
solve
as
you're
probably
aware,
mina
ships
with
a
graphql
api
as
part
of
the
daemon,
but
as
mena
is
a
succinct
blockchain?
This
means
we
don't
actually
have
access
to
any
of
the
prior
history
in
mina.
Finality
is
290
blocks.
So
once
we
get
past
that
point,
the
consensus
nodes
who
require
this
information
actually
drop
the
blocks
as
they're
no
longer
needed,
so
the
demon,
graphql
node
is
actually
limited
in
only
returning
data
from
the
last
290
blocks.
E
E
You
either
need
to
write
your
own
wrapper
on
top
of
it
or
use
some
some
of
the
hostess
services
like
figment's
data
hub
that
expose
an
api,
but
what
the
amino
explorer
graphql
api
does
is
to
basically
provide
a
very
similar
interface
via
graphql
to
the
block
data,
but
instead
of
being
limited
to
290
blocks.
It
actually
does
this
for
the
for
the
entire
chain.
E
You
can
also
get
the
individual
snark
work
because
in
the
archive
note,
these
are
actually
grouped
together
as
fee
transfers
if
there
are
multiple
in
a
single
block
and
it's
also
actually
easier
to
get
the
canonical
block
information
without
the
use
of
some
fancy,
postgres
recursive
queries
and
then
just
the
last
one
on
that
list
do
is
it's
highly
queryable,
so
you
can
write
some
custom
queries
to
retrieve
any
data.
You
want
basically
to
incorporate
into
your
tooling
pretty
easily
next
slide.
Please.
E
So,
just
to
quickly
demonstrate
this
on
the
left.
We
have
the
the
daemon
graphql
api
and
on
the
right
we
have
the
the
amino
explorer
graphql
api.
As
you
can
see,
they
take
a
very,
very
similar
format
and
while
these
two
queries
will
turn
the
exact
same
data,
this
only
works
if
your
node
is
within
290
blocks
of
50
697,
as
I
have
it
there.
So
next
slide,
please!
E
I
think
one
more.
Oh
there
we
go
so
if
you
kind
of,
if
you
needed
some
more
inspiration
to
to
build
something
here,
are
some
projects
already
in
the
mina
ecosystem
that
are
using
this.
So,
firstly,
there
are
a
number
of
pool
payout
scripts,
which
many
of
the
delegators
will
have
already
used.
They
used
to
calculate
rewards,
so
these
typically
make
use
of
the
staking
data
information,
as
well
as
getting
all
the
block
winner
and
transaction
and
snarfy
data
from
each
block.
E
The
next
one
is
similar
to
the
earlier
example
I
showed,
but
it's
used
to
find
transactions
with
abnormally
high
fees
and
then
display
them
on
a
real-time
dashboard.
So
this
is
a
common
mistake.
We've
seen
when,
when
delegating
is
setting
the
fee
too
high
and
thinking
that's
the
amount
you're
delegating
and
this
dashboard
actually
allows
easy
tracking
of
the
block
producer
who
got
the
fee.
So
hopefully
they
can
actually
then
return
that
I
should
note
the
creator
of
this
sushi.
E
Validator
also
has
a
number
of
other,
really
interesting
dashboards
that
are
worth
checking
out.
Next.
There
I've
linked
a
github
repo
that
allows
block
producers
to
provably
demonstrate
which
slots
they
won
for
an
epoch
after
the
fact,
and
then
using
the
graphql
api,
it's
possible
to
determine
their
performance
based
on
the
slots
they
actually
produced,
rather
than
basing
their
performance
on
simply
winning
canonical
blocks,
which
has
a
large
luck
factor
in
it.
E
The
next
one
is
an
interesting
one.
It's
a
simple
bash
script,
but
it's
really
useful
in
that
it
determines
the
median
snark
fee
for
the
last
100
blocks
or
whatever
look
back
period.
You
set
it
to
so
this
kind
of
simple
one
liner.
This
can
be
used
to
set
your
snart
fees
dynamically.
Based
on
what
the
recent
blocks
seen
and
then.
Finally,
I
recently
built
a
prototype
exporting
tool.
E
This
allows
you
to
export
all
of
your
transactions.
Block
production
snark
work,
all
your
history,
basically
into
formats
that
are
suitable
for
importing
into
popular
tracking
software.
This
is
typically
a
pain
point
for
many
when
you
have
thousands
of
say
incoming,
staking,
rewards
and
the
tools
tool
here.
E
Does
this
kind
of
in
a
format
that
can
be
simply
imported
with
the
intention
with
the
community
support
to
get
many
more
of
the
most
popular
software
supported
and
then
finally,
last
slide
yeah
and
that's
everything
from
me,
you
can
access
the
api
at
that
link
where
you'll
also
find
a
graphical
gui.
So
it's
quite
easy
to
get
started
and
playing
around,
and
I
guess
I
look
forward
to
seeing
what
you
built
so
cheers.
Thanks.
A
F
All
right,
hi
everyone,
I'm
luigi
from
bitcast
and
my
discord
name
is
nuno
yeah.
You
know
it's
my
nickname,
I'm
the
pm
of
our
wallet
and
let
me
share
the
reasoning:
complete
works,
yeah
first,
second,
yes,
we
we
have
completed
the
audit,
which
is
only
the
audit
of
of
the
browser
extension
for
the
always
mobile
app.
F
We
will
open
source
it
at
the
next
week
and
second,
the
other
wallet
app
store
version
has
been
launched
there.
You
also
can
go
to
the
app
store
search
it
and
third,
we
have
make
some
user
experience
improvement
in
in
the
our
wallet,
for
example,
before
many
users,
and
have
faith
to
execute
the
delegate.
F
F
F
Second
will
display
the
currency
in
the
wallet
for
the
usd
cny
and
the
rob
third,
so
our
wallet
has
has
many
russian
users,
so
we
will
support
russian
and
actually,
we
also
has
already
helped
us
translate
english
to
russian
and
because
some
format
reason
we
still
have
a
lot
of
worker
to
do
next
slide.
Please,
and
in
the
end,
the
work
come
download
and
use
our
wallet.
A
simple
and
circular
wallet
support,
android,
iphone,
chrome,
firefox.
A
Thank
you.
Thank
you,
nunu.
I'm,
I'm
very
excited
about
auro
as
well,
especially
because
you're
the
you've
just
concluded
the
audit,
congratulations
and
yeah.
I
think
it's
really
convenient
to
have
an
in-browser
wallet.
So
thank
you
for
this
work.
Nunu
all
right
next
up
is
moody
from
the
mena
development
group
he's
starting
a
very
exciting
project
as
well.
It's
called
pot
snark.
B
Nice
to
meet
you,
I'm
moody,
I'm
from
the
amina
development
group
we've
been
recently
working
on
on
an
idea
called
podsnark.
It's
basically
going
to
be
a
podcast
live
on
our
telegram
community.
We
have
an
unofficial,
mina
community
on
the
telegram
and
we're
going
to
be
planning
to
do
like
a
collaboration
with
the
mina
foundation
on
hosting
monthly
episodes
on
telegram.
B
It's
going
to
be
basically
a
q,
a
with
our
host
and
we're
thinking
about
crowdsourcing
the
questions
to
the
community.
So
we're
really
trying
to
use
the
spot
stock
event
in
a
way
to
bridge
the
gap
between
the
the
team,
the
community,
in
a
way
that
we're
going
to
the
community
and
all
to
giving
the
community
the
possibility
to
ask
and
then
afterwards
all
of
those
recording
will
be
recorded
and
posted
on
spotify
and
our
on
our
youtube
channel.
So
christine
can
you
go
to
the
next
slide?
Please.
B
Thank
you.
These
are
our
social
channels,
so
we
have
a
telegram
community
and
the
television
telegram
development
group
as
well.
Usually
the
telegram
development
group
consists
of
I
mean
people
that
really
project
and
would
like
to
help
the
project.
So
if
you
guys
want
to
hop
in
sometime,
chat,
have
a
discussion
with
us.
You
can
hop
in.
We
also
have
a
community
back
twitter,
a
community-backed
website
and
our
partners
youtube
channel,
so
it's
gonna
be
next
week
on
the
18th
and
our
first
guest
is
going
to
be
with.
A
A
F
A
Got
it?
I
hope
that
answers
your
question
carlins
and
if
not,
I
know
that
there
are
a
lot
of
guys
out
there
and
I
also
see
another
community
member.
Is
it
austin
mike?
He
said
he's
saying:
there's
a
wallace
channel
on
our
discord
and
both
carbonara
and
bitcat.
They
are
both
very
responsive
there
to
help
the
users
yeah.
So
I
also
see
another
question
that
was
already
answered
but
might
be
interesting
for
others
as
well.
B
Yeah,
basically,
that's
the
link
for
the
questions.
So
if
you
go
on
it,
you
can
pick
any
question
you
want
decide
and
then
submit
it
and
we
also
have
the
option
if
you
want
to
directly
ask
even
for
the
question
as
well.
So
please
we're
we're
very
excited
to
hear
what
kind
of
questions
the
community
wants
to
ask.
A
Okay,
well,
it
seems
that
they're
not
that
many
questions
during
this
session,
all
right.
Well,
thanks
everyone
for
attending,
and
thank
you
to
the
speakers
for
taking
the
time
to
share
your
updates
with
us.
If
any
of
you
have
some
updates
to
share
with
the
brother
community,
we
have
a
sign
up
form
that
we
will
post
in
the
description
on
youtube,
and
we
also
have
a
survey
that
we'd
like
to
ask
you
to
fill
out.