►
Description
In this Antelope Coalition, there's discussion and updates on RAM limitation fixes, P2P optimized transaction propagation, P2P peer discovery, Antler CDT, instant finality, and an update on SDK.
00:00 Intro and Summary
01:38 Instant Finality Update with Gnome & Yves
08:21 Questions about IF
10:11 Update on SDK with Aaron Cox
20:30 Closing
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.eosnetwork.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 #Web3
A
All
right
we
had
started
this
meeting
a
few
moments
ago.
I'll
give
a
quick
summary:
I
had
forgotten
to
click
the
record
button
in
terms
of
ram
limitation
fixes
that
process
has
started.
The
enf
team
is
going
through
and
defining
some
of
the
items,
but
for
clarity,
they're
not
going
to
be
working
on
any
items.
Nothing
at
this
time
is
planned
for
the
leap
5.0
release
the
P2P,
optimized
transaction
propagation.
A
Those
items
will
be
part
of
the
leap,
5.0
release
that
project
is
underway,
Milestones
have
been
defined
and
the
project
is
running
without
issue.
At
this
point,
P2P
peer
Discovery
is
back
on
track.
The
next
Milestone
is
July
20th,
there's
no
particular
updates
with
that
other
than
the
fact
that
the
previous
issues
or
surrounding
test
cases
and
development
procedures
I
believe,
have
largely
been
resolved.
A
But,
of
course,
we'll
we'll
know
when
the
next
Milestone
is
presented
to
Guillaume
and
Aaron,
not
Aaron
Cox,
again
for
the
July
20th
Ambler
CDT,
which
has
been
marked
as
close,
that
is
now
in
production.
The
product
team
is
watching
and
collecting
feedback
based
on
the
software
that's
being
launched,
but
at
this
time
there's
no
further
work
planned
on
that,
and
that
brings
us
to
insta
finality
again.
Would
you
like
to
give
a
brief
update
on
that.
B
Yes,
so
essentially,
we've
got
our
first
approval
for
the
first
milestone
for
that
one,
which
is
the
elf
segregate
signature
and
we
photographic
and
intrinsics
in
the
the
code
base.
So
it's
been,
it's
been
been
quite
slow,
but
understandably
so,
because
this
is
very
low
level,
very
complex
code
with
very
few
people
that
actually
have
the
the
knowledge
space
to
to
review.
B
So
we're
still
waiting
for
this
to
to
be
reviewed
to
to
be
completed
before
resuming
the
work
so
we're
still
on
standby.
We
still
have
after
that
Milestone.
We
still
have
two
other
Milestones
that
are
ready
for
review
that
need
to
be
reviewed
before
we
can
proceed
any
further.
So
I've
been
I've,
been
reassured
by
the
enf
team
that
they
are
dedicated
to
reviewing
these
Milestones
as
quickly
as
possible,
but
you
still
have
to
wait
until
that's
done
before.
C
And
to
add
context
onto
that,
so
this
would
be
the
main
feature
that
would
be
found
in
the
leave
the
leap
5.0.
It
would
be
a
hard
Fork.
We
were
trying
to
coordinate
at
least
on
eos's
end
that
we'd
have
that
sometime
in
September,
that's
likely
unlikely,
so
we've
mentioned
now
Q4,
instead,
I
think
October
or
early
November
is
doable.
We
do
want
to
get
this
out
before
the
holiday
season
starts
because
you
get
the
Western
holiday
season,
December
mid-December
and
on,
and
then
you
get
in
Asia
Chinese
New
Year.
C
That
starts
depending
on
the
year,
but
let's
say
mid-December
and
mid-January
and
on
so
you
get
a
really
a
two
month
period,
where
it's
extremely
difficult
to
coordinate
a
hard
Fork.
So
we
do
want
to
have
all
of
that
ready
beforehand.
So
we
don't
have
an
exact
date,
yet
we'll
be
putting
out
some
communication
shortly
in
terms
of
kind
of
what
we're
aiming
for,
but
I
think
realistically,
at
this
stage,
I
still
see
it's
possible
to
have
something
out
either
October
early
November.
C
Theoretically,
we
could
push
it
to
early
December
and
that's
for
on
EOS,
aside
actual
deployment,
which
means,
if
you
walk
back
from
there,
we
need
to
have
everything
finalized
start.
The
testing
process
deploying
on
on
Jungle
Etc
well
before
that
so
about
two
months
or
so
before,
give
or
take,
and
as
far
as
I
can
tell
we're
still
on
track
for
that,
but
just
to
give
an
idea
for
for
the
other
chains
here,
that's
what
we're
aiming
for,
but
that
instant
finality
really.
C
C
B
Yeah
so
the
first,
the
first
main
component,
I
guess
of
the
instant
finality
upgrade,
is
the
set
of
new
intrinsics
and
new
cryptographic
functions.
Post
functions
that
now
allow
for
a
wide
variety
of
very
interesting
use
cases.
So
we
did
deploy
this
and
we've
been
testing
this
extensively
over
a
private
testnet
that
we
have
and
we're
about
to
roll
it
out
on
our
on
the
ux
public
test
net.
So
this
is
slightly
ahead
of
the
I
guess,
like
the
the
typical
release
cycle.
B
Typically,
yes,
upgrades
first,
but
since
we
also
have
been
working
on
on
a
number
of
I
guess
like
shielded
transaction
protocols
that
rely
on
these
intrinsic
groups
deployed
them,
we've
been
testing
them
like
ahead
of
the
typical
release
cycle
and
so
far
so
good
everything
has
been
working
very
well.
These
interns
are
actually
really
really
fast
and
that
will
give
Antelope
as
a
holy
very
nice
Competitive
Edge
when
it
comes
to
zero
knowledge,
Crews
protocols
and
systems.
C
D
C
E
B
E
E
I
had
a
question:
I'd
raise
my
hand
on
back
on
the
the
CDT
and
I've
been
hearing
for
some
folks
that
that
it'd
be
great.
If
there
was
a
a
Mac,
OS,
deliverable
or
binary
for
that,
instead
of
is
there.
Is
that
on
the
is
that
kind
of
of
a
binary
on
the
on
the
plan
at
all
or
or
should
everyone
just
use
the
the
Dune
implementation.
C
I
guess
I
can
kind
of
address
this.
One
Bart
just
left
the
dunamination
is
for
that
thing
is
it's
it's
darker,
so
you
can
run
it
in
Mac.
We
also
just
went
through
a
a
restructuring
inside
of
the
enf,
and
so
we
we,
the
resources
that
were
on
doing
CDT,
are
no
longer
with
us.
So
I
think
it's
unlikely
that
we
would
make
any
additions
to
that.
So
I
think
it's
safe
to
stay
at
this
stage
that
that
will
remain
the
case
for
the
foreseeable
future.
Okay,.
C
E
A
F
Yeah
sure
it's
been
since
April
I
want
to
say
that
I've
been
on
one
of
these
calls,
so
a
lot
has
happened
since
we've
last
talked
the
session
kit,
which
is
the
it's
the
ual
replacement.
Essentially
it's
kind
of
that
wallet
connectivity
layer,
the
thing
that
does
transactions,
that
is
in
a
stable
position.
It
is
released
as
0.5
right
now,
but
the
next
release
will
be
the
1.0
release,
we're
staging
like
all
of
the
reigning
changes
for
that
they're
all
going
to
be
fairly
minor,
except
for
some
syntax
type
stuff.
F
The
biggest
changes
left
there
are
based
on
the
contract
kit,
which
is
what
has
been
in
full
swing
development
wise
for
a
couple
months
now.
The
contract
kit
is
something
we
have
never
had
before
in
the
Antelope
ecosystem.
It
is
basically
a
code
generation
tool
and
an
abstraction
on
top
of
smart
contracts
and
tables.
F
Never
had
before
we
have
run
into
some
edge
cases
that
may
lead
us
back
to
this
group
or
back
to
the
enf
for
things
that
we
may
need
out
of
the
CDT,
the
like
the
abis,
specifically
that
the
CDT
outputs
are
missing
data
and
a
lot
of
the
work
we're
doing
are
based
on
the
abis.
It's
how
we're
doing
code
generation
and
understanding
the
contract
from
a
logic
perspective.
F
We've
opened
one
issue
for
that.
So
far
it's
on
GitHub.
We
notified
Nathan
of
that,
but
there
may
be
other
aspects
of
the
contract
kit
that
we
may
need
to
lean
on
some
CDT
improvements
to
help
with,
but,
like
I
said
the
contract
here,
that's
coming
along.
It's
leading
to
some
changes
in
the
session
kit.
That'll
lead
us
to
a
1.0
of
both
of
those
and
the
website
along
with
I.
Don't
know,
I,
don't
even
know
how
to
quantify
the
amount
of
documentation.
That's
coming!
F
That's
all
in
a
really
good
position.
There's
previews!
We
just
showed
it
off
in
the
weekly
Wharf
kit
call
this
week,
hopefully
it'll
be
a
really
good
place
for
developers
to
jump
in
and
start
building
on.
Native
when
they
are
doing
the
front
end
aspects,
the
client
development
aspects
of
their
project,
we
also
have
links
that
will
send
them
off
to
other
resources
for
contract
development.
B
F
Yep,
that
is
actually
the
one
issue.
I
was
referencing
that
we
already
opened
so
perfect
yeah
right
now,
we
don't
know
like
when
you
look
at
a
table.
We
don't
know
what
the
indices
are,
so
we
can't
strongly
type
that
data
yeah
I've
been
talking
with
Shaq
a
decent
amount
about
that
on
these
calls.
So.
B
F
We
probably
could
learn
it,
but
it
would
just
take
some
time
and
it's
would
slow
us
down.
So
if
it
comes
to
it,
we're
hopeful
that,
like
the
the
reason
that
the
ABI
is
in
like
this
one
specific
issue
that
nobody's
really
addressed
it
up
to
the
state
is
because
nobody
was
truly
leveraging
that
part
of
the
ABI,
and
so
we
figure
by
actually
leveraging
that
part
in
the
contract
kit.
F
E
F
Yes
and
we're
pretty
sure
that
the
data
fields
exist
already
in
the
current
structure
like
if
you
go
look
at
any
contract
on
any
of
these
networks.
It'll
have
the
fields
they're,
just
all
empty,
like
the
CDT
is
not
inputting
the
data
into
those
fields,
so
this
might
be
just
a
bug
that
nobody's
noticed
until
now,
but
I'm
gonna
leave
that
determination
up
to
those
who
know
more
than
me
on
this
subject.
F
But
if
we
are
asking
for
changes,
we
are
going
to
hope
that
they're
going
to
be
reverse,
compatible
and
we're
going
to
push
forward
with
contract
kit,
assuming
that
that
data
is
empty
and
we
will
make
it
work
under
current
conditions.
It
just
won't
be
as
good
as
it
can
be
if
we
get
those
things
filled
out
so.
E
Yeah
I
think
that's
the
way
to
not
that
you're
asking
my
opinion,
but
I
do
think.
That's
the
way
to
go.
It's
no
one
else
is
working
on
this
right.
If
you
guys
are
going
to
blaze
the
trail
then
then
do
it.
The
way
you
may
think
makes
sense,
keep
coming
back
to
to
the
group
and
and
keeping
us
informed
of
what
you're
doing
and
I
mean.
That's
to
me.
F
So
we'll
make
it
work
with
the
way
that
they
work
live
right
now
and
then,
as
developers
start
adopting
the
contract
kit
when
they
point
this
out
and
they're
like
oh
the
tables.
Don't
do
this
thing
because
and
then
we
can
point
to
this
issue
in
the
CDT
and
that
might
rally
support
around
improving
that
aspect
of
the
CDT
itself.
So
it's
it.
We're
kind
of
going
this
method
to
prove
demand
to
show
that
it
is
actually
worth
improving.
This
aspect
of
the
ecosystem.
E
I
think
that's
good
I
wanted
I've,
always
wondered
why
why
the
tables
weren't
there,
the
table
table
fields,
are
sort
of
all
implied
through
the
actions
right
through
the
values
of
the
actions
but
they're
but
yeah
it
seems.
Maybe
you
could
have
had
it
the
whole
time,
but
so
maybe
the
0.1
version
of
this
is
simply
to
have
the
CDT
spit
out
those
those
you
know
just
spit
out
the
tables
and
and
end
of
the
seas,
because
if
they're,
there
they're
good
they're
there
in
the
contracts
right
so
yeah.
F
So
it's
just
it's
kind
of
a
little
bit
of
a
headache
to
say:
oh
I've
got
this
thing
that
was
made
for
me,
but
now
I
gotta
go
fill
in
the
missing
parts
that
weren't
filled
in,
so
there
are
options
to
make
it
work
and
we
can
show
how
it
works.
It's
just
having
that
part,
automated
and
actually
output
properly
would
be
the
best
developer.
Experience
possible.
E
F
So
that
way
like
we
could
do
that
with
the
system
contracts,
even
where
it's
just
an
ABI
update
and
the
blossom
doesn't
change.
It
wouldn't
affects
the
operations
in
that
way,
but
then,
all
of
a
sudden,
it
would
enable
all
developers
leveraging
the
system
contract
to
have
this
better
developer
experience
through
stronger
typing
and
auto
completion
and
like
the
things
that,
like
help
developers,
learn
passively.
F
So
yeah
other
than
that
it
is
full
steam
ahead
on
the
contract.
Yet,
like
I
said,
the
website's
gonna
probably
mid
this
month,
have
a
big
update.
It'll
actually
have
some
marketing
materials.
It
will
have
a
good
portion
of
documentation
and
I
it'll,
also
document
what
was
previously
known
as
eosio
core
the
eos.js
alternative
that
we
built
years
ago
and
have
been
maintaining
since
that
is
now
part
of
the
wharf
kit
project,
and
it
is
just
called
the
antelope
library
now.
F
F
We're
gonna
go
over
in
terms
of
hours
for
what
we
said
for
the
contract
kit,
but
we're
going
to
eat
that
cost
we're
not
coming
back
to
the
Coalition
asking
for
more
money
or
anything
the
timeline
just
on
that
contract
kit,
maybe
longer
than
what
we
originally
anticipated
yeah.
That's
where
we're
at
any
other
questions
or
thoughts,
comments.
C
A
D
D
Obviously,
there's
differences,
but
it'll
be
something
that
works.
I
think
most
valuably
so
far.
The
the
deploy
preview
link
that
we
do
have
that's
not
at
the
main
URL
or
you
know,
a
Well
published
one
works
for
Jungle,
so
I've
shared
it
with
a
couple
people
that
needed
a
jungle
Explorer
and
they
were
happy.
It
happened.
So
they
said
they're
looking
forward
to
the
the
real
thing
being
deployed,
so
that
is
happening.
That's
all
I've
got
to
share
relevant.