►
From YouTube: EOS MANDEL Meeting #2 (Feb 16th 2022)
Description
UNCUT FULL Version: https://youtu.be/7K0VZmouuaA
All EOS Mandel Meetings : https://github.com/EOS-Nation/mandel/issues/37
#eos #eosio
A
Welcome
everyone
to
the
second
weekly
call
for
the
mandel
kickoff.
Thank
you.
Everyone
for
joining
we've
got
a
nice
large
group
of
people
here,
presentation
from
block
producers,
software
development
team,
the
frackily
team,
enf
eos
support
all
across
the
board.
We've
got
some
some
representatives,
so
thank
you.
Everybody
where
we
left
off
on
last
week
was
there's
still
some
questions
on
the
code
strategy,
whether
it's
going
to
be
a
3.2
and
3.0
or
3.1,
and
what
are
the
dates
jungle
reset
is
is
a
big
priority.
A
B
A
B
With
the
for
the
api
transaction
lifecycle
feature
that
I
mentioned
last
week,
which
could
be
added
and
the
timelines
do
line
up
with
what
we
were
looking
for,
and
so
we
would
still
be
able
to
have,
let's
say
the
release
out
roughly
a
month
later
than
what
we
expected,
which
is
quite
acceptable.
So.
A
B
Sometime
in
june,
but
it'll
depend
as
well,
because
if
we're
not
enabling
the
hard
fork
functions,
let's
say
we
merge
and
we
go
to
3.1
and
we
have
this
api
transaction
lifecycle
function
added.
We
don't
necessarily
need
to
enable
the
hard
fork
functions
right
away
to
showcase
that
we're
not
running
the
block
one
repo,
okay,
because
that
function
in
itself
would
not
be
found
in
the
block
one
repo.
B
So
by
default
you
know
if,
if
that
function
works
on
the
main
net,
then
that
means
that
we're
not
pointing
to
block
one
repo,
because
that
function
would
not
be
in
the
block
one
repo,
and
so
it
would
actually
be
a
somewhat
simpler
from
a
from
that
consensus
upgrade
function
which
then
could
occur
later
on.
Okay,.
A
B
B
B
B
Able
to
coordinate
the
process
and
refine
our
strategy
so
that
in
the
future,
when
it
is
useful
and
when
we
do
want
to
do
so,
we've
got
a
much
smoother
process
that
we've
tested
out
and
that
we're
comfortable
with.
So
it
would
buy
us
a
little
bit
of
time
it
would.
We
would
still
be
able
to
signal
that
we're
not
running
the
block
one
repo
without
necessarily
having
to
do
that,
and
so
it
it
makes
a
little
bit
more
flexible.
C
B
B
B
A
B
B
Use
the
functions
like
block
logging
block
trimmings
are
would
continue
using
2.3
and
or
not
upgrade
at
all,
but
some
would,
but
in
order
to
signal
that
we're
no
longer
using
the
block,
one
repo
then
likely
the
enabling
of
those
functions
so
that
it
does
become
a
consensus.
Upgrade
would
now
become
a
greater
priority,
and
so,
if
you
didn't
upgrade,
then
you'd
be
falling
behind,
you
would
no
longer
be
in
line
with
the
main
eos.
A
A
E
E
So
we
will
start
from
the
two
zero
launch
that
that
chained,
the
jungle,
four
on
the
two
zero
version
and
with
all
features
that
was
available
to
the
on
2.0
also,
I
think
we
will
start
jungle
4
without
initial
taking
distribution
because
it
looks
like
it
was
not
required
the
previous
time
and
it
just
take
a
time
and
use
resources
which
is
not
needed.
Yeah,
I'm
working
on
the
bootstrap,
we'll
prepare
them.
E
We
will
start
the
bios
node
and
launch
everything
and
then
share
information
for
everyone
to
connect
how
to
connect
like
genesis
file,
probably
the
same
as
we
did
for
jungle
tree.
We
will
try
to
do
this
during
finish
preparing
through
this
week
and
be
ready
for
the
next
week.
I
think
okay,
yes,
I
know
yeah.
So,
as
I
know,
the
next
week
should
be
when
the
repository
will
be
available
yeah,
but.
A
A
And
then
yeah
go
through
the
upgrade
process
for
the
1.8
upgrade.
We
distributed
a
survey
to
basically
developers
and
exchanges
to
get
feedback
on
what
they're
running,
and
it
was
a
good
opportunity
for
us
to
kind
of
keep
on
top
of
the
status
that
you
know
are.
Are
people
aware
of
this
upgrade
their
requirements
and
working
on
getting
their
nodes
updated
in
time?
For
the
the
consensus
upgrade,
we
didn't
have
a
terribly
large
response.
Actually,
we
only
had
17
people
actually
respond
to
this
survey.
D
I
need
to
review
it.
Basically,
we
need
to
ask
questions
which,
where
we
break
compatibility
right
like
state
history,
for
example,
state
history
of
mandel
is
adding
a
few
new
fields,
so
all
the
state
history
readers
might
not
work.
So
these
these
topics
are
important.
Also,
if
someone
is
running
2.1,
we
need
to
have
some
transition
strategy
for
those
who
are
using
latin
use
nation
using
two
to
one.
But
the
good
thing
is
that
u.s
nation
is
running
that
so
traditional
strategy
will
be
delivered
by
them.
A
Pay
attention
to
it
and
ask
people
again
similar
in
addition
to
the
survey
in
1.8,
we
had
an
article
that
basically
pulled
together
all
of
the
resources
for
any
any
node
operator
or
developer.
This
is
a
summary
of
the
resources
we
provided
for.
1.8
stan
is
working
on
doing
the
documentation.
You
know
what
are
the
impacts
of
the
mandel
release,
target
high
volume,
applications
and
exchanges
directly.
So
again,
this
is
something
that
randall
and
I
have
been
discussing.
Thank
you.
Randall
the
eos
nation.
A
We've
got
a
a
database
of
apps
and
and
exchanges,
and
I
believe,
randall
you
said
you.
You've
got
also
your
own
database
and
a
crm
tool.
We've
got
an
intern
on
our
team
who's
in
the
process
of
going
through
the
database
of
all
of
the
apps
and
exchanges
and
getting
a
contact
information
we're
trying
to
get
an
email
address.
You
know
when
you
want
to
submit
a
ticket
to
an
exchange.
A
What's
the
email
address,
get
it
get
those
all
kind
of
in
our
crm
and
when
we're
ready
to
commute
when
we
have
all
of
our
resources
assembled,
we
can
reach
out.
In
addition
to
that,
there's
going
to
be
a
lot
of
just
boots
on
the
ground.
You
know
I'll,
I'm
I'll
coordinate
with
all
of
the
top
21s
and
and
all
the
exchanges,
but
what's
happening
now
is-
is
we're
just
basically
building
that
list
randall?
Maybe
you
and
I
can
talk
more
offline
about
coordinating,
so
we're
not
duplicating
efforts.
A
Maybe
we
can
share
what
information
we
have
and
what
information
kind
of
combine
those
resources.
Ideally,
what
I'd
like
at
the
end
of
this
is
that
we
have
some
public
resource
that
anyone
can
access.
You
know
it's
a
it's
a
public
good
for
the
community
like
a
a
contact
list.
Do
we
make
we
only
make
public
what
we're
able
to
make
public?
A
What
I
have
in
mind
for
most
you
know,
there's
most
exchanges
have
both
public
and
private
channels
of
communication,
so
yeah,
whatever
this
public
document
would
be,
would
be
the
public
channels
of
communication
so
that
there
may
be
our
internal
crm
system.
That
includes
both
public
and
private
information
and
then
maybe
there's
a
separate
document.
That's
public,
for
you
know
with
just
the
bare
minimum.
We
don't
want
the
all
of
the
knowledge
lost
in
the
event
that
you
know
something
happens.
A
We
have
someone
in
the
future
no
longer
able
to
participate
that
contact
information
will
be
will
be
useful.
Okay.
So
that's
everything
that
kind
of
was
in
progress
from
the
last
call.
There
are
some
other
items
in
our
to-do
list
that
I
want
to
discuss
today.
There
are
a
few
things
that
we
identified
that
we're
going
to
need
on
the
kailin
test
net
power
up
we're
going
to
need
to
do
the
binary
update,
we're
going
to
do
the
kind
of
highland
feature
activation
and
nate.
A
C
So
basically
there's
two
things
that
I
noted
that
can
be
improved.
The
first
is
that
kylan.blox.io
was
taken
down
because
there
is
no
hyperion
or
history
provided
to
them.
I
spoke
with
saeed
he's
happy
to
reset
it
up
to
where
you
can
do
historical
searches,
that's
one,
the
other
one
is
the
faucet.
I
was
doing
a
little
bit
of
research
before
the
call
it
looks
like
eos.
Laumau
was
really
in
charge
of
that.
I
don't
know
if
they
really
exist
anymore.
Argentina
has
the
faucet,
but
it
only
gives
you
10
tokens.