►
From YouTube: Leap Weekly Meeting #34 (Oct 5th) 2022
Description
This week the Leap Upgrade Working Group updates the community with blocks.log survey results, future upgrades, three strike rule, and more!
00:00:00 Start
00:00:03 Recap and this week's topics
00:01:13 Block.log survey
00:02:10 Leap 3.1 upgrade issues
00:03:04 Future upgrades
00:07:15 Block.log survey review
00:10:53 Three strike rule
00:12:03 System contracts and Msigs
00:13:04 End
Antelope Leap 3.1 upgrade working group 10/5 Github meeting summary:
https://github.com/EOS-Nation/leap/issues/101
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's
October
5th.
This
is
our
second
week
now
meeting
I
guess
in
the
new
series
of
events
post
EOS,
Independence
Day
as
we
work
towards
the
next
consensus,
upgrade
quick
recap
from
last
week.
We
we
did
it
just
quick
check
in
on
how
things
are
going,
since
the
upgrade
seems
that
upgrade
was
a
big
success
all
around.
A
We
shared
that
the
enf
has
released
some
patch
releases
leap,
CDT
system
contracts,
software
development,
progress,
the
work
on
3.2,
rc1
and
leak.
Util
is
in
progress
and
we
are
expecting
perhaps
we'll
have
a
Target
date
today.
So
we
can
talk
about
that
later
and
we're
right
now.
High
level
enf
is
working
towards
possible
March,
April
timeline
for
the
next
consensus
of
upgrade
and
as
of
last
week,
EOS
support
Was
preparing
to
send
out
a
survey
to
talk
about
the
block
logs
files.
A
B
A
A
And
and
that's
it
any
I,
don't
know
if
there's
any
other
agenda
items
anyone
wants
to
add,
but
maybe
we
can
start
by
re
rechecking
in
on
how
we're
doing
post
launch
again.
Last
last,
we
heard
all
the
top
tiers
are
back
in
business.
Are
you
hearing
anything
otherwise
Randall
since
last
week,
as
far
as
you
guys
are
seeing
on
the
EO
support
side
of
things.
B
A
And
then
from
anyone
else,
anyone
hearing
anything
from
either
node
operators,
dap
developers,
exchanges
or
yourselves
with
the
with
the
latest
or
the
the
upgrade
that
we've
been
running
for
a
couple
weeks
now,
foreign
I'll
take
that
as
good
sign.
In
that
case,
let's
get
into
the
future
upgrades
how?
How
are
we
looking
Steven?
Do
we
have
any
any
I
any
sense
on
timelines
for
the
next
upgrade.
C
C
D
I
was
gonna,
say
there
was
one
thing
that
did
actually
come
up
in
some
of
the
upgrades
on
other
chains
about
some
confusion
around
the
eosio
nsig
system
contract
in
some
of
the
repos,
and
they
were
trying
to
get
things
nailed
down
on
exactly
which
version
was
published
on
the
new
repo
and
maybe
pulling
in
I.
Don't
know,
I,
don't
remember
what
channel
it
was
in,
but
does
that
ring
a
bell
that
it
was
something
about
the
the
old
the
old
msig
used
to
use,
deferred
transactions
and
the
new
one
does
not.
D
But
it
also
had
to
be
adjusted
for
a
delay
seconds
or
something
like
that.
But
there
were
some
iterations
of
that
instant
contract,
and
then
there
was
confusion
finding
it
in
the
repos.
We
can
catch
back
up
in
the
channels,
but
I
think
it
was
one
of
the
antelope
channels
that
that
msig
contract
there
was
some
and
I
think
it
what's
on.
Eos
was
kind
of
a
combination
of
what
got
scattered
in
some
of
those
different
ports
over
the
is.
D
What,
ultimately,
you
can't
use
the
time
contract
because
that
uses
new
imsa?
Well,
they
still
have
the
old
msig,
so
they
went
to
go
update
the
imsa
pull
the
new
in-sig
contract,
and
then
there
was
some
discussion
about
the
version
they
found
didn't
have
like
a
delayed
seconds
param,
or
something
that
there
was
some
confusion
about
the
path
and
I
think
they
got
it
narrowed
down.
They
were
showing
the
commits
and
everything.
But
if
y'all
are
you
know,
doing
a
system
contract
and
all
of
that
I
don't
know
that
might
be
included.
A
A
D
A
A
B
Hello,
can
you
hear
me
we
can
okay
yeah,
so
the
the
Google
Docs
is
at
Excel.
That
has
each
question
okay
answered,
so
you
know
how,
like
the
the
charts
has,
let's
say
like
a
graph
there
to
see
who
answered
yes
or
no.
The
Google
documents
actually
break
it
down
so
that
you
can
see
what
each
respondent
said
and
what
their
follow-up
answer
was.
B
Got
it
right.
So
is
there
a
need
for
chunk
block
that
log
file
right
so
respondent
number
one
for
example,
said
no
right
and
they
didn't
answer
a
follow-up
right
because
they
said
no,
but
respondent
number
three
said
yes
and
they
said
that
it
will
be
easier
to
manage
than
one
large
file
right.
So
that's
how
we
have
it
on
the
Google
Docs.
A
B
C
A
B
A
B
A
C
I
think
that
it
just
had
to
do
with
people
who
had
loads
and
loads
of
CPU
and
where
I
think
there
was
like
a
three
strike
rule
related
to
the
building
that
he's
introduced
that
helped
significantly
with
the
performance
on
wax
I
can
share
a
link
to
that
PR
specifically
to
the
group,
but
outside
of
that
I.
Don't
think
that
there's
anything
too
critical.
A
lot
of
what
this
release
is
just
for
everybody's
context
and
you'll,
see
in
the
release
notes.
C
A
Thank
you.
Well
one
thing
we
didn't
talk
about,
I
guess
so
system
contracts
is
going
to
require
an
msig,
so
we
haven't
not
yet
deployed
that.
Will
you
know
we'll
we'll
I
guess
get
an
MC
up
to
do
that?
There's
nothing
pressing
with
this
3.1.1
in
the
system
contract.
Is
there
anything
that
we
need
to
be
rushing
to
get
an
msig
up
to
deploy.