►
From YouTube: Leap Weekly Meeting #31 (Sept 7th) 2022
Description
This week the Leap huddle group updates the community with progress on Leap software development, communications strategy for upgrading to Leap and when to activate the mandel features.
00:00:06 Recap and this weeks topics by Daniel
00:02:40 Leap software development update by Stephen
00:04:10 Communication strategy for upgrades by Daniel, Randall
00:15:46 Block producer upgrades by Daniel
00:18:22 Testing on Jungle and Kylin by Daniel, Michael
00:24:28 Activate Mandel features by Daniel, Denis, Michael, Yves
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://www.eosnetework.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #EOSIO #ENF
A
All
right
welcome
everybody.
It
is
september
the
7th-
and
this
is
our
31st
week
meeting
to
plan
for
the
leap
upgrade
three
meetings
left.
Well,
I'm
not
quite
three
meeting
three
weeks
left
we're
going
to
be
doing
some
more
meetings,
we'll
be
adding
some
to
the
to
the
calendar
starting
next
week,
but
today
is
the
seventh
exactly
three
weeks
to
go
until
the
planned
consensus
upgrade
so
time
to
raise
the
the
heat
level
a
little
bit
quick,
quick
recap.
From
last
week
we
looked
in
on
software
development
progress.
A
A
A
I'm
not
sure.
Last
last
we
checked
there
were
not
any
responses
to
the
survey,
yet
I'm
not
sure
whether
that
has
changed
so
again.
That's
something
else,
we'll
check
in
on
testing
on
jungle.
We
already
had
pretty
much
everyone
on
on
jungle,
upgraded
to
the
final
release.
Last
we
checked,
crypto
lions
was
preparing
to
update
the
system
contracts.
They
had
run
into
some
more
questions
and
issues.
They
were
getting
the
same
hashes.
A
I
saw
that
that
was
clarified
in
the
jungle
chat,
although
I
do
believe,
there's
still
still
need
to
propose
that
msig
test
net
strategy
again
where
we
checked
in
on
kyle
and
things
were
going
well
and
we've
got
some
more
tracking
on
how
our
block
producers
are
going
with
the
upgrade.
So
we
can
check
in
there
again.
Last
week
we
already
had
some
pretty
good
engagement
from
the
from
the
top
21,
as
well
as
some
standbys.
A
B
I
I
think
that
you
covered
the
main
update,
which
was
the
release
of
the
latest
dune
rc.
I
I
think
that
going
final
on
both
cdt
and
dune
is
imminent.
I
would
assume
that,
before
the
close
of
the
week
that
will
likely
have
made
that
call
just
because
nothing's
really
come
up,
but
everything
seems
to
be
looking
good
in
on
target
for
the
timeline
that
we're
working
against.
A
A
A
We
can
see,
we've
got
the
the
top
97
of
the
folks
on
the
on
this
tracker
here
that
have
at
least
acknowledged
they've
received
the
information
quite
a
few
here
that
we
that
have
we
we're
not
sure
whether
or
not
they've
received
it
is
it.
Is
it
sitting
in
their
junk
mail,
inbox
or
or
what
nice
thing,
though,
is
we've
also
got
the
24
hour
volume
here
and
the
both
for
eos
trading
pairs
and
and
across
the
whole
exchange.
A
So
we
can
prioritize
how
we
reach
out,
I'm
not
sure
randall.
Do
you
have
anything
you
want
to
share
about
about
this
status
here?
What
you
guys
been
working
on
one
question
I
have
is
is
how
confident
you
are
in
these.
I
was
actually
when
I
just
sorted
by
volume.
I
was
a
little
surprised
by
some
of
the
ones
near
the
top
here.
A
C
Yeah,
so
what
are
doing
now
is
we
are
sending
we
are
sending
out
the
survey
by
itself,
that's
another
way
of
trying
to
reach
out
to
people,
and
we
actually
also
go
into
the
their
platforms
directly
and
some
of
them.
We
are
trying
to
reach
out
to
them
on
telegrams
and
telegram
groups
and
other
things.
So
you
see
the
ones
who
are
not
responding.
C
A
If,
if
we
don't
have
the
contacts,
some
of
our
dp
and
exchange
contacts
that
we're
talking
to
may
have
a
way
of
of
reaching
some
of
these
folks
as
well,
especially
in
the
in
the
exchange
area-
and
you
know,
one
of
the
ones
I
saw
you
were
missing
was
bit
hum
actually
genie
who,
I
believe
is
on
this
call,
is,
is
going
to
thank
you.
She
is
she's
she's,
going
to
be
reaching
out
to
them
and
letting
us
know,
for
example.
A
D
D
E
A
D
A
A
A
E
D
The
the
actual
outreach
rate
might
be
hotter
simply
because
some
some
of
these
people
shouldn't
be
there
or
they're
they're
somebody
relevant
right.
So
if
you
only
go
on,
I
guess
I'm
not
sure
where
this
list
was
populated
from,
but
if
it's
populated
from
coin
market
cap
or
coin
gecko-
and
you
just
filter
through
a
lot
of
that
data
is
wash
trading
and
there
is
not
real
accurate
data.
D
Gecko
is
definitely
better
than
point
market
cap,
but
even
that
it's
it's
not
necessarily
accurate
right.
I
think
I
think
the
approach
at
this
stage
other
than
those
that
we
know,
for
example,
like
we
know
hit
bcc,
is
a
real
exchange.
We
should
try
and
get
in
touch
with
them.
That
is
a
real
exchange,
others
that
we're
not
too
sure
the
other
approach
can
be.
We
continuously
push
the
message,
especially
in
top
tier
media,
that
the
fork
is
coming
that
way.
D
D
A
Cool
and
and
yeah
one
thing
I
asked
our
team
to
do
this
week
on
the
social
media
side
is
yeah
crank
up
our
public.
You
know
just
from
our
twitter
account
from
basically
all
of
our
public
things
really
start
promoting
heavily
that
hey
september
21st
is
coming
so
you
know
maybe
we'll
get
a
few
that
see
on
social
media
and
then
again
the
targeting
directly,
the
the
real
ones
we
need
to
make
sure
are
upgraded.
We'll
again
we
can.
A
We
can
help
with
that
and
it
sounds
like
eos
support
is
already
adjusting
the
strategy
going
into
telegram
things
like
that.
It's
all
all
good
good
stuff,
okay,
anything
else,
randall
from
you
or
anyone
else
on
this
topic,
and
I'm
not
sure,
is
who
like
going
through
here
myself,
I
wouldn't
know
who
to
remove
and
who
to
keep.
Is
that
something
that
randall,
your
team
has
the
expertise
to
be
able
to
do,
or
do
you
guys
need
help
to
be
able
to
do?
That?
Is
that
a
reasonable
ask.
C
Pretty
much,
I
think,
for
the
top
tiers,
we
just
went
through
it
and
we
basically
came
up
with
a
list
of
the
top
notch
exchanges
that
we
all
know
about
and
pretty
much.
I
think.
Actually,
I
sent
it
to
eve
as
well,
so
that
we
he
can
help
us
with
the
content
that
he
knew
and
pretty
much
we
just
going
with
the
the
exchanges
that
we
know
that
people
are
very
familiar
with
pretty
much
that's
what
we're
trying
to
do.
D
And
leverage
the
so
the
people
that
you're
speaking
with
us
some
of
these
exchange
daniel
so
of
these
exchanges,
oftentimes
the
infrastructure,
people
move
from
one
exchange
to
another,
or
they
know
the
people
from
the
other
exchanges,
and
so
you
can
just
put
your
list
of
these
ones.
We
really
need
to
reach
out
to
we
haven't
been
able
to
get
confirmation,
send
them
to
your
contacts
and
ask:
do
you
know
of
anybody
here?
D
A
D
A
But
we've
again,
everyone
has
acknowledged,
there's
a
couple
that
we're
still
haven't
heard
any
status
from
infinity
stones
and
rapid.
I
I
heard
from
whalex
this
morning.
They
were
one
of
the
ones
that
we
were.
We
were
having
a
hard
time
getting
an
update
from,
and
they've
now
acknowledged.
Yes,
they
will
be
ready
for
september.
21St
no
concerns,
so
things
are
progressing
nicely
with
the
bp
upgrade
we'll
continue
to
keep
this
updated.
A
A
A
A
A
A
F
A
F
A
A
A
B
Yeah
it'll
just
be
bumping
the
version.
The
only
thing
I
want
to
reiterate
is
that
there
were
some
naming
changes
that
took
place
inside
of
the
transition
from
the
previous
rc
to
the
current
one
for
eos
system
contracts,
as
well
as
some
stuff
related
to
ricardian
just
wanted
to
call
that
out.
But
I
don't
think
that
any
of
that
is
going
to
introduce
any
high
level
of
risk,
assuming
that
we
can
get
that
final
out
within
this
week
and
having
that
actually
get
upgraded
inside
of
jungle.
B
A
A
G
G
B
As
far
as
I
understand
the
way
that
the
contract
compiled
between
the
previous
rc
and
the
latest
rc,
there
was
no
change.
That
was
like
the
whole
debacle
that
we
had
just
discussed
previously
and
my
assumption
at
this
time.
I
can
provide
an
update
if
it's
otherwise
is
that
there
will
still
be
no
substantive
change
in
how
the
contract
is
compiled.
E
A
F
E
A
A
A
A
G
Yeah,
so
we
would
what
we
would
do.
Is
we
just
got
up?
You
know
another.
You
know.
Third
party
smart
contract
make
a
little
action
called.
You
know,
check
date,
and
the
only
thing
that
that
smart
contract
would
do
is
if
it
is
not
past
that
date
fail,
which
means
that
when
we
do
the
m-sig-
and
we
include
that
in
the
protocol
upgrade
whenever
we
achieve
the
15
edit
21,
it
would
do
two
things
it
would
do.
A
G
And
I
guess,
is
it
even
yeah?
The
test
can
be
done
with
any
msig,
so
we
can
technically
just
do
do
an
msig
with
a
token
transfer
and
say
this
token
transfer
has
to
happen
tomorrow.
You
know
and
then,
if
it
happens
and
then
you
can
execute
it
not
today,
but
only
tomorrow,
then
it's
the
same
behavior
as
the
protocol
upgrades,
except
instead
of
a
token
transfer.
G
A
Test
yeah,
could
we
do
that,
like
this
this
week
on
thailand?
That's
that
way
do
that
test,
as
you
know,
as
soon
as
possible
this
week
and
then,
as
soon
as
we're
happy
with
the
results
of
that
test,
we
can.
We
can
propose
it
on
main
net
with
the
real
with
the
activation,
and
then
we
can
start
you
know,
or
at
least
by
maybe
by
next
week.
A
F
I
do
have
a
question
on
the
check
on
that
which
we
can
definitely
test
with
any
m
sig
and
that's
an
interesting
you
know
mechanic
to
add,
but
is
it
going
to
cause
the
first
step
of
the
inline
actions
to
fade?
Well,
it's
going
to
allow
somebody
to
still
execute
the
msig
it's
going
to
fail
from
preventing
the
protocol
activation,
but
ultimately
flush
the
m-sig
out,
which
means
we've
got
to
go
and
re-circle
back
around.
I
don't
know
if
there's
any
way
around
that.
G
G
Yeah-
and
this
is
only
possible
because
it's
the
msig
execution
is
no
longer
using
the
deferred
transactions,
so
deferred
transactions
did
end
up
having
this
weird,
like
you
can
execute
it.
Would
it
would
push
a
delay
and
then
the
delayed
transaction
would
then
fail
after
it's
been
executed,
but
now
that
msig,
like
the
os
and
m6,
are
now
using
inline
actions
to
do
the
execution,
the
execution
is
in
the
same
stack
as
the
all
the
other
transactions.
So
as
long
as
one
fails,
it
just
rolls
back
everything
and
never
and
nothing
have
ever
happened.
F
A
G
G
G
D
F
F
G
F
The
system
contract
wasn't
marked
as
a
system
or
something
crazy
ram.
Yes
and
all
sorts
anyway.
I
was
just
curious
on
that.
I
am
curious,
you
know
I
mean
that's,
that's
a
protocol
activation.
It
should
just
be
activate,
but
we
can
probably
test
it
with
like
system
contract
actions
just
to
make
sure
I'm
curious.
A
A
A
E
D
30
minutes
is
too
short,
I
would
say
you
need
the
hour,
so
it
would
be
1300
to
1400
yeah
at
a
minimum
yeah.
It
could
also
be
that
you
collect
the
signatures
for
a
period
of
24
hours,
people
test.
Basically,
the
msg
is
just
pending
and
it
gets
activated
the
following
day.
So
you
still,
the
network
is
still
ready
to
upgrade.
Everything
is
good.
D
A
Okay,
so
from
your
perspective,
you're
not
picky
on
whether
the
activation
is
actually
executed
on
the
21st
or
the
next
day.
As
long
as
we've
got
everyone
signed
by
then
correct,
okay-
and
I
guess,
is
there
marketing
value
in
having
it
executed
on
that
call
like
ooh,
you
know
we're
live
streaming.
We
got
all
the
signatures.
Let's
do
it.
D
Well,
there's
value
in
whatever
you're
going
to
execute.
So
if
you
do
that
the
next
day,
then
you
should
have
the
live.
Call
the
next
day
as
well,
when
it's
going
to
execute
right,
so
everybody's
waiting
around
the
timer
is
coming.
No
more
signatures
are
needing
to
be
collected.
Essentially
it's
going
to
execute
on
its
own
or
somebody
will
go
and
execute,
but
then
everybody's
waiting
and
yes,
then
you
can
do
your
woo,
but
then,
more
importantly,
you
can
do
the
is
everything
working,
fine
yeah,
some.
B
F
D
E
D
D
So
you
know
what's
going
to
happen,
but
it's
my
opinion,
so
you
like
the
signatures
for
a
period
of
time,
and
then
you
get
so
actually
you
can
start
the
nc
before
the
1300
utc
on
the
21st
start.
Collecting
signatures.
Have
that
call
where
everybody's
discussing
this,
whatever
let
that
go
through
for
24
hours,
it
can't
be
executed.
A
E
A
F
If
it's
got
the
execution
prevention
by
all
means,
I
would
say
yeah
as
for
when
we
execute.
I
do
think
that
coordinating
that
and
timing
it
and
and
lining
everybody
up
and
as
much
as
I'll
joke
about
wanting
to
have
ross
being
bad.
I
do
think
geographically,
you
know
when
you
look
at
probably
the
nodes,
and
I
don't
know
where
all
the
bp
nodes
actually
are,
but
there
may
be
some
value
from
executing
it,
not
whenever
I
am
awake
and
staring
at
the
computers
as
much
but
yeah.
F
F
D
F
C
F
D
F
D
D
F
A
F
D
Anyway,
oh
it
is
the
best
we've
been
through
this.
It
is
the
best
that
is
the
best.
There
are
nodes
in
europe.
There
are
operators
in
europe.
If
you
do
the
opposite,
they
are
literally
in
the
middle
of
the
night.
If
you
do
the
current
time
slot
everybody's
awake
during
that
time,
we've
been
through
this
over.
F
A
D
But
then,
like
you,
suggest,
put
the
nsig
up
next
week:
slowly,
connect
signatures
over
time
as
people
are
upgrading
as
they're,
confident
that
their
nodes
are
now
stable
and
they're
good
and
that
might
be
the
trigger,
for
them
is
hey
if
you've
been
running
now
for
a
couple
days
a
week,
whatever
once
you're
comfortable.
But
your
nodes
are
good.
You
sign
this
ensign
type
of
thing
so
that
by
that,
maybe
even
by
the
18
17
or
something
like
that,
we
might
have
you
know
12
13
signatures.
A
Exactly
yeah,
so
I
think,
given
that
the
21st
is
the
date,
we've
been
communicating,
let's
aim
to
actually
execute
it
on
the
21st
and
so
we'll
aim
to
have
all
signatures
collected.
You
know
at
least
24
hours
ahead
of
that,
maybe
even
even
ahead
of
that,
but
we'll
leave
the
next
day
as
an
option.
As
you
know
we're
going
to
be
meeting
daily.
If
we,
if
we.
A
D
A
D
Which,
but
so
for
the
west
coast,
then
it's
5
a.m.
The
meeting
starts.
6
a.m.
The
execution.
Having
said
that,
I
do
not
there's
grey
mass,
that's
on
the
west
coast,
potentially
for
some
of
their
people.
I
know
the
data
center
is
located
west
coast,
but
the
people
are
east
coast.
Who's
gonna
push
the
button,
I
think
they're
east
coast.
No
one
is
so.
We
should
actually
ask
your
amass.
They
might
be
the
odd
the
outlier.
D
A
For
now,
I'm
gonna,
we'll
say
1400
we'll
follow
up,
and
I
think
it
makes
sense
like
we're
used
to
always
meeting
at
this
time,
so
keeping
that
the
same
we'll
meet
again
at
this
time
and
then
we'll
all
get
on
the
call
and
we'll
execute
an
hour
into
the
call.
I
think
that's
a
a
good
approach
or
again
we'll,
depending
on
how
well
we're
gonna
need
to
decide
before
we
propose
the
mc
by
monday.
So
we'll
have
we'll
have
a
decision
here
by
monday,
when
we
propose
that
mcgee.
A
G
D
C
A
D
Okay,
correct
so
just
looking
at
the
list
of
bps,
I
know
the
node
operators
there's
none
in
in
on
the
west
coast.
There
are
some
in
australia,
so
generals,
so
the
1300.
So
I
guess
meeting
at
1200
utc,
which
would
be
8
a.m.
Eastern
executing
at
9
a.m.
Eastern,
which
would
be
1300
utc,
will
actually
cover
more
people.
Okay
and
it
will.
It
will
be
even
less
it
will
be
even
earlier
in
asia,
so
8
p.m,
9
p.m.
It'll
be
easy
right
before.