►
From YouTube: EOS MANDEL Meeting #7 (March 23rd 2022)
Description
All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues/37
#eos #mandel
Everything EOS is the official media channel of the EOS Network Foundation (ENF). The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
https://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF
A
Welcome
everybody:
it's
march,
23rd,
it's
our!
I
think
this
is
our
seventh
week
now
meeting
on
the
agenda,
we'll
check
in
on
the
code
situation,
how
testing's
going
how
our
collection
of
contacts
and
assembly
educational
materials
going
and
we
can
check
in
on
kailin
as
well.
Is
there
anything
else
to
add
to
the
agenda
anything
new
come
up
in
the
last
week
that
that's
worth
adding
to
the
agenda
today?
Okay,
let's
get
into
it,
then,
starting
with
this
one.
I
eve:
do
you
have
anything
to
report
on?
B
Somebody
could
go
and
double
check
other
than
that
the
work
should
be
there
and
it's
just
a
question
now
continuing
the
review
testing
to
see
whether
or
not
there
are
any
issues
with
that,
so
that
we
can
ideally
address
before
we
start
the
the
work,
the
remaining
work
to
get
it
to
3.1,
so,
ideally
in
the
next
next.
I
guess
this
week
next
week
and
the
following
week,
so
it
gives
us,
let's
say
two
and
a
half
weeks
from
today
to
find
any
bugs
with
that,
so
that
we
can
address.
A
B
Really
the
vps
are
going
to
be
able
to
deploy
this
on
jungle
asap
so
3.0
it
was
any.
Has
anyone
been
able
to
confirm
if
there's
an
extra
dot
in
there
or
not?
I'm
gonna
go
check
right
now,
so
it
was
six
days
ago
that
it
was
merged
on
on
the
17th.
Yes,
it
was
last
thursday
it
was
after
our
call,
and
somebody
wants
to
go
here.
I
thought.
C
A
A
B
You
have
a
specific
tag.
This
pr
shows
the
merge
where
we
included
the
diffuse
changes
and
what
I'll
do
is
I'll,
post
that
in
mandel
just
so
that
you
have
great
as
well,
it's
a
pull
38
and
it
would
be
if
we
were
to
name
it,
it
would
be
3.0.5.
So
I
guess
there
would
be
a
second
period
all
right
under
the
current
structure.
I
guess
cool.
A
D
D
C
D
B
C
Bill
did
they
put
a
build
in
the
in
wherever
the
repos
are
then
yeah.
Just
like
the
latest
code,
you
can
easily
build
yeah.
I
mean
that
they
know
a
docker
container
of
305.
I
don't
believe
so.
There's
nothing
to
just
take,
there's
no
binary
to
take
and
just
use.
You
would
have
to
build
your
binary
unless
dan
or
brian
or
kevin
or
somebody
that
knows
how
to
do
that
could
do
that.
For
us.
I
don't
think
dan
ben
and
todd
and
steven
are
not
working
on
it
any
longer.
D
C
C
C
We
can
tag
this
and
then
do
a
build
and
then
start
testing
it
on
a
jungle,
but
we
don't
like.
I
can't
do
that.
I've
never
built
you
know
usao
before
so
we
would
need
either
you
know,
stan
or
brian
or
kevin
someone.
That's
willing
to
do
that.
That
can
that
actually
can
build
the
software
and
then
make
it
where
we've
got
a
docker
container
or
whatever
sitting
in
the
repo,
and
then
people
can
use
that.
D
D
C
B
F
Mean
if
we're
ready,
I
think
it's
probably
a
good
place,
but
I
think
we
need
just
a
bit
of
cleanup
and
then
we
can
tag
it.
The
some
of
the
sub
modules
don't
actually
point
to
their
corresponding
mains.
I
don't
think
right
at
this
moment,
so
we
probably
should
just
clean
that
up
a
bit
and
then
at
that
point
I
think
it
would
be
a
good
point
to
tag
it.
If
you
just
want
to.
Let
me
know
what
you
want
to
tag
it
we
can.
I
can
make
that
happen.
That
would
be
awesome,
maybe
kevin.
F
F
Do
you
need
right
access
to
the
no
I've
got
right
access,
so
you
guys
make
the
call
I'll
get
a
pr
up
to
update
the
remaining
sub
modules.
I
think
that
hasn't
been
done.
Stephen
done
a
little
bit
of
that
work,
but
I
think
there's
a
little
bit
left
there
to
do
and
then
yeah
and
then
a
pr
up
to
update
the
the
cmake
file
for
the
given
release
and
we'll
call
it.
I
guess
three:
zero
five
rc
one
is
that
one
3.0.5
rc1
okay.
G
A
C
C
List
of
the
files
at
that
specific
version
level
of
every
one
of
the
files,
so
you
could
go
back.
If
we
then
built
more
stuff,
you
could
go
back
and
still
grab
the
3.0.5
rc1,
because
each
one
of
the
files
got
tagged
with
that.
So
it's
just
a
way
of
you
know
snapshotting
and
saying
this
is
what
this
code
is.
C
This
is
what
we
have
in
it
and
the
other
stuff
that
came
after
it's
not
in
it,
but
there
still
would
need
to
be
a
build,
but
we
I've
noticed
that
there
have
been
some
people
building
dockers
and
then
leaving
them
in
the
repo,
and
I
just
don't
have
my
screen
up
to
remind
myself
what
the
heck
that
that
part
of
it's
called
if
kevin
or
stan
or
someone
wanted
to
build
an
ubuntu
1804
and
an
ubuntu
2004
or
whatever
1604.
I
don't
know
what
jungle
is
running,
then
you'd
be
closer.
D
F
You
know
one
thing
we
should
do
is
we
should?
There
are
release
notes
for
the
for
the
previous
release
for
three
zeros,
and
so
we
should
do
a.
We
should
do
some
release
notes
for
this
as
well.
If
we're
going
to
do
a
tag,
release
but
steven
is
that
something
you
could
put
together
for
your
portion
of
what
you
guys
did
yeah?
F
Okay,
if
you
could
start
that,
then
I
could
add
the
you
would
do
a
draft
of
it
and
let
me
know-
and
then
I
can
jump
on
there
and
add
what
what
we
did.
Oh,
which
is
very
minor
stuff.
Just
just
some
minor
cleanup
is
all
we've
done
so
far
in
the
repo
all
right
did.
A
A
All
right
anything
else
on
this
topic
all
right.
Moving
back
to
the
jungle,
do
we
have
costa
rica
yet
forgot
to
ask
them,
but
I
can
ask
them
if
they're
going
to
rejoin
cool-
and
I
had
I
haven't
reached
out
to
argentina-
so
that's
my
bad
too
and
I
see
attic
lab
is
just
waiting
to
get
voted
in
so
good
we're
making
progress
there.
What's
next,
I
don't
know
randall.
If
you
have
anything
to
update
on
the
collection
of
contact
information
for
our
exchanges
and
dapps.
A
I
think
I
saw
randall
join,
not
sure
if
he
can
speak,
not
really.
Okay,
no
problem.
I
know
last
time
we
checked,
we
were
well
on
our
way.
We
have
the
majority
of
our
targeted
contacts.
We
have
contacts
for
them,
so
I
think
we're
in
pretty
good
shape.
There
stan
any
progress
on
the
documentation
stuff
that
you've
been
working
on.
D
A
So
that's
something
I
think
you
and
I
maybe
can
partner
on
like
I'll
need
your
help
on
the
technical
stuff,
and
I
can
help
craft
something
write
an
article
and
maybe
get
the
enf.
Maybe
zach
can
help
us
spread
it
when,
when
it's
ready,
what
else
any
was
the
platform
support
that
we
were
waiting
for
some
documentation?
Any
progress.
E
There
ted
no
we're
waiting
for
now,
since
we've
released
the
names
bucky,
it
will
start.
C
E
A
C
C
Yeah,
so
that
should
come
out
that
I
mean
if
it
had
been
brought
over,
but
we
didn't
bring
it
over.
Stephen
and
todd
didn't
bring
it
over.
So
you
should
delete
that
line
off
it's
up
above
it's
the
third
one
up
yeah
from
the
bottom
of
that
list.
Roxdb
yeah!
Well,
it's
listed
twice.
So
it's
there!
It's
in
the
pull
that
out.
We
don't
even
have
it
in
the
manual
repository
at
all,
so
you
could
remove
it
out
of
both
lists
and
then
I
think
we
do
have
soft
float
in
both
lists.
C
F
G
F
C
F
C
F
C
Think
we
could
get
it
done
before
3.1.
If
we
decide
we
want
it,
we
should
do
it
before
3.1
and
then
we've
got
the
release.
That
goes
out
to
all
the
block
producers
and
everything
is
done.
The
way
it's
going
to
be
done
in
the
future.
I
wouldn't
want
to
release
to
the
block
producers
and
then
change
the
structure
that
would
we
have
a
chance
to
kind
of
start.
F
I
think
that's
really
yeah
this
point
that
it's
supposed
to
be
before
3.1.
I
think
that's
really
an
important
point,
because
once
you
do
this,
like
you,
don't
want
to
go
back
and
that's
through
a
problem.
You
don't
want
to
support
like
both,
so
you
want
to
do
it
before.
3-1
officially
is
cut
that
way
you
don't
ever
have
to
like
have
because
supporting
it
both
ways.
It's
a
real
there's,
a
real
problem.
If
you
have
to
do
like
some
patch
and
something
in
fc,
then
you'd
have
to
like,
but
you
have
to
go.
F
A
B
Yeah,
so
that
would
be
at
the
very
latest.
It
would
be
great
to
have
to
be
able
to
time
it
with
alongside
the
oci.
But
it's
going
to
be
hard
to
say
when
that's
even
possible
until
the
engineers
start
and
for
them
to
give
us
a
better
estimate
and
then
to
work
alongside
the
oci
guys
to
see
if
we
can
freaking
canada
and
what
that
looks
like,
ideally
again
yeah
whether
or
not
we
even
have
something
before
that.
Yeah
I'm
not
too
sure,
but
that
would
be
yeah.
A
A
C
Work
but
it's
doable,
it's
not
going
to
be
the
hard
part,
the
hard
part's
going
to
be
all
the
history
and
state
log
splitting
and
all
the
stuff,
the
code-
that's
just
not
done,
and
bringing
that
code
in
and
that's
what
the
engineers
will
be
spending
more
time
on
in
creating
what
will
eventually
be
3-1
and
deprecating.
All
the
old
code
out
that's
found
and
said
this
should
be
removed.
They'll
be
busier
with
that.
Then
this.
This
will
be
a
simple
task.
B
If
they
decide
they
want
yeah,
and
this
is
again
this
is,
I
would
say
this
is
a
lower
priority
and
it's
if
we
want
to
do
it
right.
So
I'd
wait
before
the
engineers
start
and
get
their
feedback
and
continue
having
these
discussions
weekly
here
and
then
they'll
join
once
they
start.
We've
got
kevin,
is
here
seeing
this
here
as
well?
If
this
starts
picking
up
and
other
people
start
joining
as
well
get
their
feedback,
we
can
make
that
decision
later
on.
Moving.
A
A
B
A
B
B
Nation
is
going
to
be
running
it
like
the
week
later
on
after
they
do
their
tests
right
and
then
the
full
transition
over
always
takes
about
two
months
or
so
everybody
does
it
at
their
own
pace
they
coordinate.
So
I
wouldn't
talk
about
the
minute
right
away.
Just
talk
about
the
final
release
in
early
august
on
june
and
then
in
june.
Sorry
in
august
sorry-
and
then
we
talked
about
having
the
hard
four
september
still
aiming
towards
center.
I
think
it
was
23rd
where.
H
A
B
A
A
B
B
Probably
never
heard
of
that
are
they
is
it
real
volume?
I
have
no
idea
so
I'd
say
anything
more
than
five
million.
At
first
glance,
I
just
don't
even
actually
no,
these
are
pairs,
so
it's
not
even
the
same
hold
on
the
majority
of
the
volume
is
found
in
the
same
exchange.
It's
just
different
payers
right.
So,
for
example,
binance
has
pairs
with
the
eos
for
multiple
things.
Well,
then,
binance
also
has
a
pair
for
like
eos
in
euro,
which
is
under
a
million
dollars,
but
it's
still
binance.
It's
still
the
same
exchange.
B
Applications
more
than
two
percent
yeah,
I
would
put
like
more
than
two
percent-
maybe
basically
you're
reaching
out
to
ten
exchanges,
because
the
majority
of
the
trading
pairs
are
found
on
very
few
exchanges
right.
So,
but
two
percent
of
all
of
the
eos
trading
volume
is
that
yeah
of
all-
and
that
fluctuates
obviously.
But
yes,
you
could
even
say
like
the
top.
I
don't
know
15
exchanges
and
it
depends
which
metrics
you
want
to
use.
B
B
And,
to
be
honest
as
well,
the
most
of
the
exchanges
are
getting
their
liquidity
from
the
main
exchanges
and
they're
just
looking
into
the
ipis,
and
so
it's
not
necessarily
that
there's
actual
trading
volume
as
many
as
much
as
their
bots
when
those
bops
don't
work
and
that's
where
their
money
is
just
switch
over.
It's
relatively
simple.
A
Cool,
so
one
thing
I'm
going
to
work
on
over
the
next
week
is
consolidating
all
of
the
notes,
and
we've
got
all
of
our
meeting
notes
over
the
last
seven
weeks.
Things
have
changed,
I
think
there's
some
people
out
in
the
community
who
still
think
we're
targeting
a
consensus
upgrade
in
may,
for
example,
so
I'm
going
to
put
together
a
one-page
summary
of
all
the
latest
information
and
we
can-
and
maybe
we
can
communicate
that
in
the
short
term
and
then
obviously
we'll
need
to
add
a
much
more
of
the
technical
details.
B
A
B
Experience
of
last
time
is,
the
majority
did
switch
over.
They
switched
over
at
the
last
minute
because
they
needed
to,
but
they
didn't
do
it
beforehand,
which
is
normal
and
the
very
few
that
didn't
update.
They
quickly
updated
there
after
and
there
was
really
no
disruption
of
service
like
we
didn't
hear,
because,
because
it's
all
volume
we
really
didn't
hear
of
anything,
there
was
literally
no
exchange
that
contacted
the
1.84.
B
That
said,
oh
my
god,
my
services
are
down
the
times
that
that
has
occurred
had
nothing
to
do
with
with
a
fork.
It
had
to
do
with
the
network,
either
being
congested
and
too
much
transaction
volume
and
their
own
history
solutions,
for
example,
just
compute
buffs.
It's
never
had
to
do
with
before
right.
A
C
C
B
C
B
E
A
Yeah
my
intention
there
was
not
necessarily
quarterly
consensus
upgrades
it's
just
quarterly
and
that
was
kind
of
coming
from
feedback
eve
that
you
guys
were
talking
about
getting
into
a
pattern
eventually,
so
not
all
at
once,
but
we
will
be
increasing
the
frequency
of
releases
and
making
sure
that
the
work
that
we
do
here
is
preparing
us
for
that.
But.
C
Would
you
even
expect
and
I'm
not
saying
a
hard
fork?
Would
you
even
expect
exchanges
say
we
put
out
four
releases
a
year?
There's
minor,
there
are
no
hard
forks
in
them.
Do
you
expect
the
exchanges
to
pick
them
up
and
run
them
every
one
of
them
within
a
short
amount
of
time
that
we
release
them?
I
just
feel.
B
Like
no
people
skip,
but
it
doesn't
really
matter
right,
so
we
have
at
any
given
time
we
have
all
the
block
producers
running
different
versions,
that's
pretty
standard
until
they
catch
up,
and
so
I'm
really
referring
like
one
block
producer
would
be
running
like
a
good
example.
Be
eos.
Nation
is
typically
the
first
block
producer
to
upgrade
to
everything.
B
Then
other
people
start
winging
in,
but
by
the
time
let's
say
the
last
person's
coming
in
there's
a
new
release
again
and
eos
nation
is
on
another
version
again,
but
the
extra
functionality
or
the
extra
performance
and
stuff
is
not
a
hard
forks.
It
doesn't
really
matter
if
everybody's
cascading
in
different
versions,
plus
some
block
producers,
run
their
own
versions
as
well.
They
modify
them.
B
So
I
in
that
regard,
I
would
think
that
yeah,
if
we
were
to
do
let's
say
non-breaking
non-hard-fought
changes
four
times
per
year,
where
we
have
extra
features
extra
little
things
where
it
improves
some
apis
or
improves
some
performance
or
it
improves
certain
pieces
of
the
code.
I
would
say:
that's
a
pretty
aggressive
but
really
good
goal
that
we've
seen
to
manage
in
the
past
and
once
we
get
into
a
group,
the
exchanges
were
really
responsive
to
upgrades,
probably.
C
Once
they
had
that
group
yep,
we
just
have
a
smaller
team
now
and
we
just
don't
quite
have
the
throughput,
even
though
we
have,
and
even
though
in
at
the
other
blockchain
company.
Besides
the
ogs,
which
there
were
five
or
six,
there
were
four
kind
of
second
tier
players
that
would
do
a
lot
of
these
lower
level
tasks
and
stuff.
We
have
none
of
those,
so
there's
just
we're
just
the
really
skinny
cat
right
now,
all
right.
A
In
the
background
and
my
goal
here
is
everything
that
we're
doing
here,
we
should
try
to
do
it,
make
it
so
that
it's
repeatable
we're
we're,
let's
not
throw
away
the
work
we're
doing
here.
Let's
build
the
processes
and
the
systems
and
the
habit
that
make
it
easier
to
do
again,
the
next
time
cool,
I'm
good.
With
that
anything
else.
I
just.
C
Wanted
to
say-
and
I
don't
have
the
exact
data
and
brian,
if
you
do
know
please
chime
in
I,
I
was
trying
to
give
some
buffer.
You
know
when
we
had
discussed
kind
of
end
of
june.
I
think
into
june
is
very
it's
kind
of
a
you
know.
A
lay
up.
It's
really,
you
know
it's
buffered,
because
I
think
the
oci
work
is
targeting
mid-may
or
end
of
may.
C
So
if
the
engineers
can
come
on
board
and
get
the
history
and
states
log
splitting
and
stuff
like
that
in
the
time
we
might
actually
be
in
a
month
sooner
than
we
put
there,
I
just
want
you
to
know
that
really
is.
It
should
be
the
outside
edge
and
it
should
have
buffer
and,
as
we
know,
a
little
more
and
we'll
meet
with
alice
and
I'll,
let
brian
speak
and
he
can
say
if
he
knows
the
actual
target
right
now,
but
I
thought
it
was
in
may
sometimes
we.
H
C
B
As
we
go
yeah
actually
one
of
the
things
that
could
be
that
we
could
control
or
that
we
could
communicate
is,
we
could
put
let's
say,
end
of
june
mid-july
type
of
thing.
So
that's
what
the
communication
is
at
this
time
and
as
we
get
closer
to
the
day,
if
we're
able
to
actually
beat
that
and
get
faster,
we
can
shoot
that
as
a
good
news
story
like
we're
so
on
track
that
we're
even
to
go,
let's
say
mid-june
or
something
like
that
instead
and
then
that
communication
could
change.