►
Description
This week the huddle group updates the community with progress on Leap 3.1 RC4, Kylin updates, Rebranding to Antelope, ramping up communications and more!
Timestamps
00:00:03 This weeks recap and topics by Daniel
00:01:22 Leap 3.1 RC4 and CDT 3.0 RC2 by Stephen
00:03:53 Testing on Jungle 4 by Daniel
00:04:51 Kylin updates by Daniel, Michael
00:07:54 Rebrand update and code repos by Daniel, Stephen
00:10:35 D.U.N.E 1.0 RC2 and survey feedback by Daniel, Stephen
00:17:31 Antelope is born by Yves, Ted
00:25:10 Ramping up communication for Sept 21st by Yves
00:35:43 End
Summary
🟢 In progress action items are on track:
Communicate upgrade plan broadly #50
EOSIO has been rebranded to Antelope. Mandel has been rebranded to Leap.
The Mandel 3.1 Upgrade Guide is being updated with the new branding.
EOS Support will be sharing the upgrade guide with exchanges and developers once the changes are published.
We'll continue to promote the September 21 upgrade and resources heavily this week.
Mandel software development #41
Leap 3.1 RC4 and CDT 3.0 RC2 will be released today
Small system contracts update is coming tomorrow
We should have a confident timeline on Leap 3.1 final release next week
Test Mandel on Jungle 4 #44
BPs on Jungle will be asked to upgrade to Leap 3.1 RC4 once it's released.
Testnet strategy #40
EOS Nation has proposed the following MSIGs on Kylin:
🔑 #1 MSIG configure PowerUp
🔑 #2 MSIG system contract set code (v3.1.0-rc1)
🔑 #3 MSIG activate latest protocol features
🔑 EOS Nation #4 MSIG system contract set ABI
Waiting for latest PR to be merged
Platform Support #55
DUNE 1.0 RC2 will be coming on Thursday with fixes for Windows 10 issues
ENF is requesting a survey for chainbase utilization and will provide more context.
https://techgaun.github.io/active-forks/index.html#eosnetworkfoundation/mandel-chainbase
https://techgaun.github.io/active-forks/index.html#eosio/chainbase
Participants (15)
Host: Daniel Keyes | EOS Nation
Yves La Rose
Ross (EOSphere)
Kevin Heifner
EOSUSA Michael
Max_Cho :: KOREOS Owner-South Korea
Matt Witherspoon
Zack Gall
Stephen Diesel
Vlad
Ted Cahall
Andri Cryptolions (Andri Bobrovych)
Jeff Werner
junhank | NodeONE
Genie Kim - EOSeoul
Luis Paris | ENF (Luis Paris)
Randall Roland
Virginia Glass
Alysha Mims
Denis Carriere
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://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
A
We
have
we've,
have
it
deployed
the
system
contracts,
so
we
can
see
if
there's
any
anything,
coming
out
of
testing
in
the
last
week,
we
as
a
last
call
we're
preparing
to
activate
power
up
on
kyle,
and
we've
made
some
progress
there.
We
can
report
on
that,
in
particular
with
in
the
context
of
the
rebrand
happening
today.
I
want
to
talk
about
our
communication
plan
and
the
progress
we're
making
there
and
we
had
received
some
feedback
on
dune
which
I've
shared.
A
A
A
B
B
A
B
I
think
there's
a
high
level
of
confidence
in
the
stability
of
this
release,
since
there
were
really
just
some
minor
bug
fixes
that
went
in.
However,
we've
we've
not
nailed
down
an
official
timeline.
I
think
we
should
be
able
to
provide
a
confident
update
next
week
around
where
we're
at
but
everything's
looking
really
great
so
far,.
A
A
A
Last
week
we
had
michael
mentioned,
there
was
some
issues
with
hyperion
and
older
versions,
but
as
far
as
I
can
tell
it,
things
seem
to
be
along
smoothly
on
jungle,
so
we'll
chris,
just
ready
ready
to
yeah.
Once
rc4
comes
out,
we'll
we'll
get
everyone
to
upgrade
and
run
it
through
its
paces,
and
hopefully
we
can
yeah
get
that
final
release
soon.
A
On
the
kylin
stuff,
making
good
progress
there,
so
the
we've
we've
put
out
the
a
few
m
sigs
denny
has
put
on
kyle
in
just
a
couple
days
ago.
One
is
to
activate
power
up.
The
other
is
to
deploy
the
system
contract
set
code,
and
then
we
have
the
up
activate
the
protocol
features
and
also
actually
a
fourth
m6
for
the
system
contract
set
abi.
C
What
I'll
probably
do
is
I'll,
probably
and
I'll
work
with
the
guys,
danny
and
matthew
and
some
of
the
other
vps
about.
I
think
we
can
flip
on
probably
power
up,
but
we
don't
want
to
flip
all
of
them,
because
that's
gonna
right,
I
think
trigger
you,
know
forking
of
whatever
so
probably
pretty
quickly.
You
know
and
just
just
taking
a
a
quick
assessment
to
make
sure
like
the
kangaroo
nodes.
You
know
they're
running
the
software
that
won't
fork
out
things
like
that,
but
we
won't
be
activating
all
of
them
instantaneously.
A
C
Anything
that's
going
to
be
working,
correct,
yeah,
definitely
the
features,
I
would
probably
say
the
system
contracts.
Things
like
that.
So
that's
why
I
haven't
signed
it.
I
wouldn't
pull
them
up.
It
does
look
like
they're
set
to
expire
like
two
months
or
something
so
we
have.
You
know
a
little
while
they're,
not
gonna
expire
in
a
day
or
two
or
at
least
the
one
or
two
I
checked
so.
A
C
A
C
A
C
A
Give
or
take
and
then
and
then
we
can
kind
of
go
through
the
activation
process,
sort
of
like
a
staging
environment
for
for
the
upgrade
perfect
cool,
any
questions
or
comments
on
kylin
testing
and
preparations
all
right
communication
plan.
So
with
the
impending
rebrand,
you
know
less
than
three
hours
from
now
we're
going
to
have
a
new
name
for
mandel.
A
Can
we,
maybe
maybe
enf,
can
speak
to
currently
all
the
github
repos
are
branded
as
mandel,
but
we're
going
to
be
creating
new
repos
or
just
changing
the
names
of
the
repos?
What's
what's
the
plan
for
the
rebrand
as
it
pertains
to
the
the
code
repos
and
things
like
the
we've
got,
the
upgrade
guide
that
we
published
under
the
mandel
brand?
B
Yeah
I'll
chime
in
here
right,
quick,
so
the
the
plan
is
to
have
the
necessary
resources
to
communicate
all
of
those
adjustments.
So
we
have
been
managing
documentation
to
kind
of
bait
and
switch
here
or
point
you
to
a
new
url.
That's
going
to
be
a
replication
of
these
items,
so
we
should
be
covered
across
the
board
and
it
should
happen
pretty
well
in
concert
with
the
announcement
that's
coming
up
later
today,.
A
Excellent,
so
yeah
eos
support
standing
by
to
they.
They
haven't
yet
done
the
big
blast
of
the
upgrade
guide.
So
we'll
we'll
do
that,
basically
right
when
the
rebrand
is
there,
so
we
can,
you
know,
have
it
all
branded
in
the
in
this
new
brand
and
and
then
in
the
meantime,
we've
been
it's
been
a
few
weeks
now,
we've
been
very
closely
working
with
all
the
bps
one-on-one,
letting
them
make
sure
they're
prepared
that
they
know.
That's
coming
that
they're.
A
A
So
we'll
have
to
do
a
big
push
on
the
exchanges.
I
had
a
good
chat
yesterday
with
randall
sounds
like
the
rapport
he
has
with
them
is
pretty
strong
he's.
What
he's
been
noticing
is
engagement
from
the
communications
he's
been
having
so
far
we're
getting
responses,
questions
so
we're
feeling
pretty
good
about.
You
know
the
level
of
engagement
we
have
from
all
the
stakeholders,
so
it's
just
a
matter
of
that
final
push.
Once
the
all
the
documentation
is
updated
with
the
new
branding,
excellent.
B
Yeah,
I
actually
just
have
a
couple
other
things
so
related
to
platform
support.
We
will
also
have
an
rc
for
dune.
Just
a
couple
of
small
fixes.
There
there's
an
issue
with
windows,
10
and
then
the
path
not
found
issue
that
had
been
surfaced
a
while
back.
We
may
work
into
the
release,
definitely
getting
that
one
item
in
at
least
okay
and
then
so.
B
A
Yeah
and
that's
different
than
there
was
another
one
about
the
block
log.
I
think
so
we
we've
got
a
survey
question
prepared
to
send
out
around
something
about
the
block
log.
I
think
this
is
something
that
ted
was
talking
to
matthew
about.
Maybe
ted
can
refresh
my
memory
on
the
specifics
and
we're
ready
to
send
that
out.
The
only
reason
we
haven't
sent
it
yet
is
we
don't
want
to
distract
from
the
image
like
the
the
big
get
ready
for
september
21
push
right
now.
A
E
I
did
so
with
matthew
darwin,
so
the
question
was:
do
any
of
the
block?
Producers
want
to
go
back
to
having
block
log
splitting
where
it
produces
small
files
versus
the
way
we're
doing
it
today
by
punching
holes
in
the
block
log
and
then
compressing
it.
We
have
gotten
a
little
bit
of
feedback.
I
haven't
gotten
the
results
from
matthew
darwin.
We
don't
need
it.
At
least
it's
not
needed.
We
put
out
the
next
release,
which
you
know
likely
will
be
in
the
march
april
time
frame
yeah.
E
So
it
was
just
a
survey.
We
wanted
randall
to
run
to
ask
the
block
producers
if
they
preferred
that
format
that
had
been
used
in
2.1
of
all
files
and
matthew.
Darwin
himself
said
he
had
not
only
liked
that,
but
had
a
couple
of
upgrades
to
that
process.
He
would
like
to
see,
but
he
was
going
to
pull
the
rest
of
them.
B
E
Today,
it
lives
in
its
own
repo,
and
so
people
can
use
it
as
a
standalone
piece
of
software
if
we
de-submodularize
it
and
pull
it
into
the
main
repo.
At
that
point,
people
would
have
a
harder
time
trying
to
use
it
as
just
a
standalone
piece
of
software.
It
makes
life
easier
for
us.
We
we
know
of
one
person
using
it
that
may
go
away
from
it,
but
we'd
like
to
know.
Are
there
other
people
that
are
using
it
and
would
be
uncomfortable
if
we
reintegrated
it
into
the
main
repo.
B
A
A
A
So
we
can
yeah,
we
can
catch
up
offline
to
figure
out
exactly.
How
do
we
phrase
that
question
and
then
work
with
you
support
to
get
that
sent
out
and
and
yeah
we'll
time
it
would
this
be
more
or
less
urgent
than
the
block
log
question
and
do
we?
Maybe
I
don't
know
if
they're
related
to
each
other,
should
we
send
them
together
as
one
survey
or
split
them
out
maybe
a
week
apart.
B
A
A
F
A
F
Nope,
so
the
name
is
already
out:
oh,
but
the
name.
Everything
was
supposed
to
happen
at
noon.
However,
the
press
release
essentially
just
went
out
at
like
shortly
after
nine,
and
so
now
the
repo
will
be
updated
and
everything
else
was
will
subsequently,
I
guess,
follow
through,
but
the
name
is
now
out,
and
I
guess
because
this
is
recording
it
will
be
published
later.
F
Gif,
what
is
it
called
guest?
Is
the
go
implementation
of
the
theorem
yep,
so
in
eos
we
never
had
a
naming
for
the
implementation
of,
and
so
whenever
you
talk
about,
eos
you'd
say
hey.
I
have
an
issue
with
yours.
What
are
you
talking
about
the
coin?
The
protocol,
the
software,
the
network,
the
like
which
one
are
you
talking
about
so
now
we
have
distinct
names
for
different
things,
so
that
it
starts
splitting
out
everything
it's
a
little
bit
easier.
So
antelope
is
the
protocol.
F
Antelope
is
is
antelope.
Io
is
the
framework
antelope
coalition
is.
Is
the
the
members
actually
developing
the
software
contributing
to
the
development
of
software
leap?
Is
the
release
name,
so
mandel
3.1
becomes
leap.
3.1
and
leap
is
the
implementation
of
so
it's
dc,
plus
plus
an
implementation.
So
if,
in
the
future
we
had
a
go
implementation
of
eos
of
node
node
os,
essentially
or
if
we
had
a
a
rust
implementation,
then
we
would
have
different
names.
Similarly
to
how
ethereum
has
parity,
it
has
gas,
okay
right.
F
Okay,
so
now
we
have
leap,
is
the
release
name
and
it's
the
first
implementation
and
in
the
future,
if
there
were
others,
we'd
have
their
names
in
the
future
as
well.
Once
we
have
another
release,
so
let's
say
in
six
months
or
whenever
we
have
the
next
release,
there
would
be
another
name,
so
it
would
just
be
the
similarly
to
how
android
had
you
know,
jelly
bean
and
ubuntu
yeah
yeah
yeah.
Exactly
so
it'd
just
be
different
names,
so
likely
the
different
names
in
the
futures
will
be
different
names
of
antelopes.
F
A
G
Because
I
see
people
even
now
in
the
in
the
twitter
and
comments
and
telegram
they
still
get
confused
between
eos
and
eos
io.
Everybody
thinks
that
they're
going
to
lose
the
eos
tokens
because
they're
going
to
be
this
new
thing,
it's
very
confusing
for
everyone.
So
what
about
this?
What
about
the
software
is?
It's
still
nadius
kiosk
ksd.
F
E
Fc
chain
base
app
base
stuff
like
that,
so
they
go
back
to
just
the
standard
part
of
their
naming
and
the
the
what
was
the
eos
repo.
What
was
the
mandel
repo
is
now
called
the
leap
refo
repo
yeah
I
get
it,
but
is
it
still
nodeos?
It's
yeah.
The
tools
are
no
tools
or
scripts
got
changes
to
their
names.
Nodeos
clios,
those
are
all
the
same.
Okay,
just
all
pretty
rushed
and
all
of
a
sudden
now
we're
launching
three
hours
earlier
than
expected
and
I'm
a
little
distracted
trying
to
get
that
done
right
now.
F
F
Yeah,
it
has
nothing
to
do
with
that.
It
is,
it
is
a
mess
up
the
so
the
the
website
will
be
up.
The
press
release
will
be
up,
there's
a
blog,
github
everything
will
be
merged.
Everything
will
be
changed,
documentation.
Everything
was
supposed
to
occur
at
noon
so
now
we're
just
catching
up.
But
yes,
all
of
that
information
with
all
the
naming
with
all
of
the
branding
assets
with
the
logo.
Blob
everything
is
is
going
to
be
provided
to.
Everybody
is.
E
F
F
G
A
F
F
Just
in
general,
the
communication
for
september
21st
really
needs
to
ramp
up
and
it
really
can't
just
be
cold
email.
Here
you
go,
there
needs
to
be
interaction,
especially
with
the
exchanges
to
minimize
any
potential
risk.
We
know
of
the
you
know
the
potential
risk
to
those
who
are
using
deprecated
v1,
which
was
deprecated
more
than
two
years
ago,
that
is
being
removed
from
the
code.
So
not
only
was
it
deprecated
years
ago,
it's
now
just
being
removed,
and
so
it
can't
just
be
cold
emails.
It
can't
just
be
here,
you
go.
F
F
I
haven't
seen
that
over
the
last
couple
of
months
or
in
call
number
27
or
28
today,
call
27
really
need
that
to
start
happening
to
ensure
that
at
least
they
are
ready
for
september
21st
and
then
for
those
who
are
currently
let's
say
using
v1
history
that
still
want
to
provide
that
still
need
that
data.
Perhaps
you
want
to
start
ramping
up
showcasing
that
at
least
eos
nation,
for
example,
provides
the
snapshots.
If
I'm
not
mistaken,
sweden
provides
them.
I
believe
they
still
do.
F
F
A
F
Number
of
people
that
have
acknowledged
that
they're
ready
for
september
21st,
regardless
of
where
leap
now
is,
have
they
acknowledged
that
they
will
be
ready
for
september
21st
out
of
the
top
21,
how
many
not
just
aware,
but
that
acknowledge
that
they
will
need
to
upgrade
to
whatever
version
is
now
final.
At
that
time,
yeah.
A
A
Yeah
so
we'll
be
we'll
be
actively.
You
know
every
week,
checking
in
on
responses
following
up
part
of
the
goal
of
that
surveys
is
really
gauging
that,
are
you
ready
who's
who's,
actually
read
this
thing
and
responded,
and
so
yeah
we're
going
to
be
so
again
that
today,
randall
eos
supporter
are
going
to
be
doing
that
big
blast
with
the
survey
to
everybody
and
we'll
start
getting
that
data
by
next
week.
Hopefully,
we'll
have
some
to
share.
F
Okay
and
then
I
saw
that
the
the
email
list
that
gets
sent
out
oftentimes
points
to
the
generic
mailbox
of
exchanges
that
anybody
can
get,
which
means
likely
goes
into
a
spam
box,
because
it's
going
to
be
a
mass
email,
but
we
also
need
to
ensure.
Not
only
is
it
okay,
we
sent
out
to
them
how
many
of
them
have
acknowledged
back
how
many
of
them
know
that
you
actually
exist
that
this
is
not
just
spam.
It's
very
very
important.
We
have
no
data
on
this
right
now.
A
D
Yes,
so
for
for
september
21st,
we
don't
have
anything
yet
on
that.
So
after
we
send
the
email
out,
then
we
will
follow
up
on
that
and
start
strategically
try
to
see.
Who
is
you
know,
engaging
with
us
and
who
we
can
actually
start
the
conversations
with
so
regarding
september
21st,
we
don't
have
anything
on
that,
but
when
we
sent
an
email
out
for
blocks
the
situation
where
blocks
that
I
o
we
were
able
to
get
some
exchanges
reach
out
to
us.
D
Some
of
them
wanted
to
know
some
of
the
most
recent
updates
that
we've
had.
So
we
were
able
to
help
some
of
them
regarding
that.
But
there
was
something
that
I
wanted
to
do,
which
is
to
go
to
each
exchange's
website
to
make
sure
that
when
they
give
us
the
the
not
that
they
updated
or
upgraded,
indeed,
they
actually
did
it.
D
F
F
So
we
are
already
too
late
if
we
have
not
engaged
them
about
september
21st
for
those
who
fall
in
that
category,
it's
too
late,
so
we
can't
go
back
for
those
that
do
mention
that
they
are
running
v1,
deprecated
history
and
that
they
still
need
history.
Then
this
is
where
we
can
offer
the
options
of
running
snapshots.
Many
of
them
will
not
want
to
run
snapshots,
or
some
of
them
will
not
want
to
run
snapshots
because
they
want
to
be
the
source
of
truth.
F
F
D
F
In
the
future,
the
enf
will
likely
host
snapshots
and
or
will
take
snapshots
and
host
them
as
the
source
of
truth,
which
may
facilitate
some
exchanges,
at
least
using
the
snapshots.
Otherwise,
for
example,
the
change
like
coinbase
wants
to
run
their
own
for
for
very
obvious
reasons.
Exchanges
typically
want
to
do
their
own,
so
we
need
to
at
least
know
which
ones
will
be
offline
so
that
we
know
that
withdrawals
and
deposits
will
be
off
for
a
period
of
time.
F
So
we
need
to
get
them
to
at
least
acknowledge
that
they
understand
this,
that
they
start
their
replay
of
trace
api.
If
that's,
if
that's
the
route
that
they
choose
to
take,
which
means
that
they
will,
it
will
take
two
or
three
months,
which
means
they
may
be
offline
for
a
month
two
months,
depending
on
on
what
they're
running
this
on.
We
need
to
know
that
we
can't
know
that
at
the
last
minute.
We
need
to
know
that
as
soon
as
possible,.
D
F
Awesome
and
then
in
the
top
21
daniel,
that's
the
obviously
the
most
important
we
do
know.
For
example,
like
whalex
runs
the
one
deprecated
history
is
what
was
said
right
and,
however,
they
may
be
willing
to
run
off
of
a
snapshot
or
replay
or
start
off
from
a
snapshot.
That
may
be
a
little
bit
easier.
The
exchanges
in
the
top
21,
which
I
believe,
there's
only
ok,
x,
binance
bitfinex
and
I'm
missing
one.
F
Actually,
that
may
be
only
it.
We
need
to
ensure
that
they're
good
as
well,
that
that
they
understand
and
either
we
offer
them
the
snapshots.
If
they're
not,
I
know
most
people
are
not
wanting
running
v1
deprecated
history,
but
some
are
so
either
way.
We
need
to
make
sure
that
they
they're
fully
aware
and
that
they
acknowledge,
if
that's
the
case,
yeah.