►
Description
Matthew Darwin and Areg Hayrapetian talk about the 3 new Mandel release candidates that are now available for testing and detail several new features that have been unlocked.
Timestamp Links
https://www.youtube.com/watch?v=s9DS3wEQe6A&t=204s
https://www.youtube.com/watch?v=s9DS3wEQe6A&t=467s
https://www.youtube.com/watch?v=s9DS3wEQe6A&t=671s
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
B
But
at
this
point
we
have
felt
that
it's
reliable
enough
actually
to
deploy
on
eos
mainnet,
and
we
have
done
so.
The
eos
nation
infrastructure
is
running
mandel
3.1
with
this
candidate
2,
except
for
the
block
producer
node.
So
the
block
producer
node,
we've
left
it
on
the
existing
node
eos
earlier
versions,
but
the
rest
of
the
infrastructure
that
you
might
be
using
are
api
nodes
or,
if
you're,
connecting
to
our
peer-to-peer
nodes.
B
Yeah
it's
running
mandel
3.1
already,
so
the
official
upgrade
date
is
still
a
few
weeks
a
month
away,
but
already
it's
working
good
stable.
I
can
sleep
through
the
night
when
it's
running,
that's
a
good
sign.
The
new
features
that
are
provided
that
came
from
api
plus
blue
paper.
Those
features
are
actually
enabled
on
our
api
node.
So
if
you
want
to
try
the
transaction
retry,
for
example,
that
feature
is
available.
You're
welcome
to
try
it.
We
are
using
the
new
block
station
or
I
don't
know
exactly
what
I
forget,
the
name
of
it.
B
There
was
a
few
different
names,
but
the
future
that
allows
the
block
log
to
be
trimmed,
so
it
doesn't
take
up
huge
amounts
of
disk
space
for
nodes
that
don't
need
the
full
history.
That
was
a
feature
in
2.1
and
the
enf
development
team
rewrote
that
for
the
mandel
3.1.
So
that's
a
cool
feature
as
well.
Great.
A
C
Okay,
so
last
week
we
were
busy.
We
had
three
releases
in
the
last
fireside
chat.
I
did
already
mentioned
the
3.1.0
rc2,
so
I
won't
go
over
that
again.
I
will,
however,
mention
that
we
have
so
I
mentioned
last
time
that
we're
still
holding
off
on
recommending
activation
of
the
crypto
primitives
protocol
feature
on
test
networks
until
we
do
some
further
testing
so
that
testing
has
now
been
completed,
and
now
we
can
recommend
that
the
all
the
protocol
features
of
3.1.0
rc2
can
be
activated
on
test
networks.
C
So
that's
the
only
update
there
since
last
week.
So
the
day
after
the
fireside
chat
last
week
we
also
released
cdt
3.0.0
rc1,
as
well
as
contracts
system
contracts,
version,
3.1.0,
rc1,
so
I'll
briefly
go
over
those
cdt
the
cdt
release.
One
of
the
big
changes
here
that
contract
developers
should
be
aware
of.
C
Is
it's
been
renamed
from
eosio.cdt
to
just
cdt,
so
there
will
be
some
small
rename
changes
needed
in
your
cmake
files,
just
renaming
essay
sct
to
cvt,
essentially
in
order
to
use
the
the
new
cdt
3.00
release,
but
there's
no
other
breaking
changes
to
the
api.
So
contracts
should
compile
fine.
This
is
just
cut
away
to
a
new
version,
get
a
fresh
start
there
with
the
name
as
far
as
new
features
go,
there's
some
c
plus
wrappers
for
the
crypto
primitives,
there's
more
c,
plus
wrappers
that
we
want
to
add
in
the
future.
C
For
now,
we
just
add
the
support
for
getting
the
current
block
number,
as
well
as
some
of
the
hashes,
the
shot
three
hashes
functionality,
and
then
there's
this
cool
new
feature
called
the
stack
canary.
So
I
will
get
a
little
bit
technical
into
this.
I
think
it's
worth
going
into
so
the
way
the
wasm
linear
memory
works
is
so
you
have
just
this
blob
of
memory,
addressable
memory
and
the
heap
and
the
stack
are
all
placed
there
and
cdt
gives
you
some
level
of
control
of
where
you
place
the
stack.
C
So
normally
it
would
place
the
stack
stuff
that
grows
as
you
go
deeper
into.
As
you
call
functions,
nest
calling
functions
that
thing
will
grow
or
nothing
will
be
positioned
at
the
beginning
of
the
memory
and
the
benefit
of
doing.
That
is
that,
if
you
ever
overflow,
your
stack,
it
will
be
a
memory,
access
violation
and
your
program
will
terminate
rather
than
doing
bad
undefined
things.
There
is
a
problem
with
that,
though,
which
is
webassembly
has
a
limitation
where
the
static
data
of
your
program.
C
You
can
imagine
like
your
strings
that
you
have
in
your
program.
They
have
to
all
be
stored
in
the
first
page
of
webassembly
memory,
which
is
64
kilobytes
and
there's
a
conflict
there
of
putting
the
stack
at
the
beginning
and
putting
and
requiring
the
data
to
be
also
in
that
first
page,
which
essentially
restricts
your
stack
size
if
it's
at
the
beginning
to
less
than
to
basically
64
kilobytes
less
than
whatever
the
data
of
your
contract
is
takes
up,
and
so
that
could
be
limiting
for
some
contracts.
C
So
cdt
has
for
a
while
now
had
the
option
of
allowing
you
to
put
the
stack
in
the
end
of
the
memory
rather
than
the
beginning,
which
allows
you
to
have
much
larger
stack
sizes.
The
issue
with
that
is
that
if
you
ever
go
over
that
stack
size,
you
will
start
overriding
over
your
deep
memory
and
bad
things
can
happen.
C
C
Contract
development
toolkit
there
we
go
thanks,
sure,
all
right
and
then
finally,
the
contracts
version
3.1.0
rc1.
By
the
way
it
might
be
a
little
bit
confusing
here.
We've
had
3.00
for
cdt
and
3.10
for
both
mandel
or
really
esio
and
the
system
contracts
releases.
This
is
because
we
had
the
not
really
a
release
3.0
of
both
mandolin
contracts.
This
was
the
work
done
by
clarion
os
now
fractality
team
commissioned
by
the
enf,
and
that
was
never
actually
fully
released
as
a
stable
release.
C
We
just
moved
straight
to
3.1
because
we
wanted
to
do
additional
changes
and
do
things
a
little
differently,
so
we
skipped
over
that,
which
is
why
contracts
and
and
esi
or
mandel,
is
ahead
by
one,
and
so
that's
relevant
here
too,
because
the
contracts
3.00
release
that
was
never
actually
fully
released
include
a
lot
of
great
changes
that
we
wanted
to
release,
and
now
we
are
officially
releasing
through
this
3.1.0
release.
So
a
lot
of
these
nice
features
you'll,
find
in
the
readme
here
are
from
that
work.
That
was
done
previously.
C
C
It
has,
first
of
all
ads
actions
to
make
use
of
some
of
the
new
protocol
features
like
configurable
wasm
limits,
so
there's
an
action
that
block
producers
could
call
to
set
a
configuration
for
higher
limits
on
webassembly
contracts.
So
that
means
that
you
might
be
able
to
deploy
larger
contracts
that
you
couldn't
deploy
before.
It
means
that
you
might
be
able
to
have
a
larger
call
depth
which
might
impact
some
some
contracts
that
do
some
heavier
things.
This
is
far
more
the
at
the
protocol
level.
C
This
is
far
more
configurable,
but
we
have
to
be
careful
with
what
numbers
we
provide,
because
it
is
possible
to
provide
really
extremely
high
numbers
that
are
that
make
the
chain
unstable
or
make
it
an
attack
vector.
So
for
now,
we
basically
have
two
settings
the
default
setting
of
low
and
a
setting
of
high,
which
just
bumps
up
some
of
these
values
that
we
think
are
safe,
and
then
this
is
a
feature
that
I
think
this
is
a
feature
that's
coming
about
from
looking
at
what
the
community.
C
So
this
next
feature
is
one
that's
come
about.
Looking
at
what
the
community
has
been
trying
to
build
with
contract
pace
by
themselves
and
some
of
the
issues
they've
led
they've
hit.
So
one
solution,
a
contract
pays
is
to
distribute
a
private
key
publicly
like
as
built
into
your
application,
but
to
restrict
its
usage
in
a
way
such
that
you
can't
really
do
anything.
That's
not
desirable
with
that
key.
C
It's
mainly
just
used
as
a
way
to
have
the
cut
the
have
some
contract
authorize,
your
transaction
to
reuse,
the
cpu
and
net
resources
of
the
account
that
that
key
can
access.
There
was
a
problem
with
that,
though,
which
is
in
esio
in
the
eosi
protocol.
If
you
have
a
key
to
a
permission,
you
can
change
that
permission
and
that's
just
how
the
protocol
works.
C
And
then
I
won't
go
through
everything.
There's
some
new
feature
added
in
3.1
of
getting
some
of
tracking
some
block
information,
although
that's
mostly
unnecessary
due
to
the
get
block
number
protocol
host
function.
That's
also
added,
but
there's
some
extra
data
there
there's
a
new
boot
contract,
which
is
used
useful
for
bootstrapping
a
new
chain
or
especially
a
test
chain,
and
then
there's
some
back
ported
stuff.
So
there's
the
rex
rounding
bug
that
hit
a
lot
of
people
that
has
been
finally
back
ported
in
and
part
of
this
release
as
well.