►
Description
In this Antelope Coalition meeting, the network leaders discuss RAM limitation fixes, P2P optimized transactions, peer discovery, Instant Finality, IBC Approvers, and provide an update on Wallet SDK Approvers.
00:00:00 RAM Limitation Fixes
00:04:50 P2P Optimized Transaction
00:06:18 P2P Peer Discovery
00:08:34 Instant Finality & IBC Approvers
00:18:58 Wallet SDK Approvers
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
B
Matt's
still
making
some
progress
on
it,
we've
got
almost
everything
we
need
to
produce
the
report
that
we're
going
to
produce
we're
just
missing
a
few
kind
of
key
findings
and
maybe
some
reproducible
cases,
so
other
people
can
see
those
numbers
themselves.
That's
been
delayed
a
little
bit
because
we
pulled
Matt
into
some
of
the
other
priorities
we
have
such
as
finale,
helping
us
review
that,
so
it's
slowed
them
down
a
little
bit
on
the
ram
invitations.
C
B
That's
a
good
question:
I
don't
want
to
make
any
promises
right
now.
I
know
I
know
we
have
enough
to
where,
if
we
needed
to
have
a
a
tech
team
to
Tech
team
meeting,
we
could
probably
explain
enough
to
get
started
at
this
point.
We
just
don't
quite
have
enough
for,
like
the
full
formal
report
that
we'd
like
to
publish.
So
that's
really
the
phase
we're
in
we're
I
think
the
findings
are
sound.
B
B
E
F
G
H
A
Giving
up
given
the
fact
that
I
can't
see
the
majority
of
the
calendars
I
might
send
like
a
calendar
link
or
I
can't
remember
the
other
tool
I
used
last
time,
but
something
like
that
where
I
might
look
at
Bart
and
Matt's
calendars
find
a
bunch
of
available
spots.
There
send
everybody
links,
and
then
you
guys
can
tell
us
when
you're
available.
B
A
D
A
A
B
Our
voice
can
pass
that
one.
Just
if
you
don't
mind
we,
the
the
core
leap
team,
knows
that
they're
Distributing
a
patch
to
work
on
Jungle,
but
looking
at
the
PRS
that
have
actually
hit
our
repository
so
that
we
can
have
some
visibility
interview.
Those
seem
very
stale
and
and
not
complete.
As
far
as
the
patch
is
concerned,
if
there's
any
way
we
could
reach
out
to
them
and
ask
them
to
either
update
those
PR
so
that
they
are
at
least
pointing
to
like
what
they
are
running
on
Jungle.
B
So
we
can
start
our
our
kind
of
integration
review
as
well.
I
think
that
would
that
would
facilitate
later
Milestones
or
will
later
acceptance
into
the
actual
Mainland
Ranch,
because
there's
a
there's
an
entire
conversation
there
that
we
haven't
really
started
having
yet
about
getting
the
final
product
into
the
actual
Mainline
code.
A
B
F
D
D
So
that's
that's
very
good,
we'll
see
we're
still
uncertain
about
any
of
the
the
timelines,
because
everything
kind
of
depends
on
the
on
the
on
the
speed
at
which
these
reviews
can
be
performed
and
as
as
you
guys
understand,
we
were
quite
quite
late
on
the
original
schedule
we
had
originally
the
specifications.
The
first
Milestone
That
was
supposed
to
be
approved
late
last
year
and
we're
still
reviewing
these.
The
the
review
of
the
specifications
has
only
started
a
couple
weeks
ago,
so
we
did
some
work
in
the
meanwhile,
we.
D
Fortunately
we
were
able
to
progress
in
the
meanwhile,
but
there
was
a
seven
month
gap
between
the
moment
at
which
the
specifications
would
be
approved
and
the
moment
at
which
code
would
be
essentially
released
on
testnet.
So
obviously,
now
considering
the
specifications
are
not
yet
approved.
Yet
at
this
point
it's
still
uncertain
what
work
is
gonna
have
to
be
done
based
on
the
review
and
what
needs
to
be
to
be
adjusted
from
that
and
all
the
the
work
that
remains
to
be
done.
D
So
it's
still
a
very
like
I,
said
very
uncertain
in
terms
of
timelines
well
or
were
definitely
committed
to
doing
whatever
is
possible
to
deploy
this
before
the
end
of
the
year.
But
at
this
stage
it
really
depends
on
on
the
the
rate
at
which
the
review
progresses.
So
this
is
this
is
for
instant
finality,
for
there
was
also
a
a
milestone
that
was
completed
recently,
which
was
the
BLS
intrinsics,
so
essentially
originally
as
part
of
our
contract.
D
We
were
supposed
to
deliver
PLS
aggregate
signatures,
and
then
we
originally
discussed
with
arig
the
possibility
to
take
a
step
back
and
to,
instead
of
only
delivering
these
aggregate
signatures
to
build
more
like
low
level
cryptographic
intrinsics,
which
we
did
and
which
have
now
been
reviewed,
but
that
turned
out
to
be
a
massive
massive
undertaking,
so
something
that
was
supposed
to
take
about
a
month
of
work
I
ended
up
taking
six
or
seven
months.
It's
extremely
good
quality
code.
D
This
is
something
that
has
just
been
merged
now
into
the
the
code
base
and
that
will
allow
for
extremely
interesting
use.
Cases,
as
we've
discussed,
I
believe
on
the
last
call,
including
confidential
transactions,
including
secret
ballot,
voting,
including
all
sorts
of
enhancements,
I
guess
for
game
five
and
for
D5
in
general.
So
I
understand
that
we
we
took
that
mandate.
We
accepted
this.
D
We
didn't
ask
for
more
money,
we're
not
asking
for
more
money
or
anything
either,
but
I
would
still
encourage
you,
as
a
representatives
of
each
of
these
chains,
to
look
at
what
you're
funding
right
now
and
see.
If
there's
any
additional
money,
that's
available
to
pay
the
developer
a
little
bit
of
extra
for
what
what
they've
done.
D
The
developer
in
question
is
Mathias
Sean
back
from
the
zias
zias
protocol
and
the
reason
why
I'm
saying
this
is
because,
like
I
said
like
this
was
a
massive
massive
undertaking
took
six
months
and
it
has
improved
the
core
capabilities
of
antelope
very,
very
significantly
like
it's.
It's
still
it's
still
early
days,
but
this
is
essentially
like
10
times
faster
than
the
output
began.
Intrinsics
that
were
there
before
and
it's
a
hundred
times
faster
than
the
equivalent
code
written
in
wasm.
So
I,
don't
know
what
you
guys
are.
D
What
are
your
objectives
at
this
point,
but
this
is
another
I
guess
not
I,
guess
I
know
it's
another
game-changing
narrative
that
can
be
definitely
promoted
and
I.
Think
I
think
it
would
be
very,
very
helpful
if
you
had
any
sort
of
like
funds
to
spare
to
recognize
the
work
that
has
been
done.
It's
not
mandatory.
That
was
not
part
of
our
contract,
but
kind
of
goes
both
ways.
D
We
did
it
and
we
funded
it
despite
not
being
a
part
of
our
Mandate
of
what
was
required
of
us,
and
now
everyone
is
going
to
benefit
from
it.
So,
like
I
said,
I
encourage
you
strongly
to
look
at
what
you
can
do,
what
you
can
spare
and
if
there's
anything
that
can
be
done
on
that
front,
Matias
would
definitely
be
appreciative
for
the
work
that
he's
done.
D
C
You
and
I'm
also
interested
in
that
as
well,
because
I
I
this
is
going
to
be
great
to
send
us
yeah.
It
will
be
great
to
kind
of
see
like
you
know,
here's
the
initial
scope-
and
this
is
this-
is
so
much
who
went
beyond
that
and
and
yeah
I
would
like
to
you
know
just
kind
of
gauge
the
level
of
effort
in
in
terms
of
like
maybe
man,
hours
or
man
days
that
we
went
beyond
to
kind
of
gauge.
D
Absolutely
so
I'm
gonna,
I'm
gonna
think
right
up
to
the
telegram
group,
and
this
is
essentially
like
it
brings
us
basically
neck
to
neck
with
the
ethereum
implementation
of
the
same
intrinsics.
So
this
is
the
basis
for
all
Continental
reduction
protocols
that
exist
on
ethereum
for
all
the
zks
large
ZK
Stark's
zq,
like
mechanisms
that
existence
there
so
now.
This
is
essentially
going
to
be
added
to
the
lead.
Point
leap
5.0
upgrade
so
this
is.
D
This
is
again
like
a
fun,
a
foundational
piece
that
will
dramatically
increase
the
potential
I
guess
of
of
antelope
as
a
whole,
so
yeah
I'm
gonna,
just
share
this
with
you
guys
and
then
yeah
like
like
I,
said
like
if
there's
a
new
year
and
yeah
funds
available
by
all
means,
Mathias
would
be
very
appreciative.
He's
worked
really
really.
Hardly.
D
D
Okay
and
there's
a
another
thing:
I
want
to
bring
up
as
well
with
regards
to
IBC
right
after
this
call.
I
have
another
call
with
some
other
members
of
the
enf
and
we're
essentially
going
to
be
we're
preparing
a
IBC
AMA,
which
was
which
is
going
to
be
a
technical
presentation,
plus
q,
a
and
and
that
mostly
towards
developers.
D
D
Instead,
where
we
would
go
a
really
like
make
a
really
deep
dive
into
the
specifics
of
the
IBC
protocol,
how
it
works,
how
to
build
applications
on
top
of
it,
how
the
the
mechanisms
function
and
all
of
the
all
of
the
fun
stuff.
So
this
is
really
intended
for
technical
audience
for
people
that
intend
to
build
additional,
no
tools
on
top
of
IBC.
You
want
to
use
it
as
a
building
block
for
additional
applications
that
we
might
might
Envision.
D
So
we
will
be
essentially
deciding
today
if
this
is
going
to
take
place
next
week
or
the
week
after
or
maybe
that's
an
alter
your
date,
but
anyone
that
would
be
interested-
or
that
knows
developers
that
would
be
interested
by
all
means.
You
can
contact
me
and
I'm
going
to
make
sure
that
they
get
an
invite
when
this
event
takes
place.
D
It's
going
to
be
recorded,
of
course,
but
yeah
like
I
said
we
want
to
Target
Advanced
developers
and
have
a
very
high
level
technical
discussion
there,
and
this
is
going
to
serve
as
the
basis
for
additional
technical
materials.
So
the
idea
is
that
we're
going
to
record
this
and
then
we're
going
to
send
that
to
to
technical
documentation
themes
and
they
will
extract
the
content.
D
A
G
G
G
You
know,
get
started
by
themselves
and
alongside
that,
we
locked
down
and
released
the
first
version,
like
version
1.0
of
the
session
kit
and
I
guess,
just
as
a
refractor
for
what
that
is,
the
session
kit
was
The,
Reaper
re-prioritization
we
did
in
early
spring
I
think
it
was.
It
is
the
replacement
for
ual,
it's
the
replacement
for
eosjs.
G
It
is
the
it's
it's
the
stuff
that
we
have
had
in
the
past,
and
this
is
now
kind
of
the
next
iteration
of
that
it,
after
lots
of
feedback,
lots
of
calls,
we've
been
having
weekly
calls
or
bi-weekly.
Sometimes
calls
with
the
developers
in
the
space
that
want
to
engage
on
this
from
most
of
the
chains
that
are
represented
here,
to
make
sure
that
it
fills
those
voids,
or
you
know
the
needs
that
those
past
products
offer.
So
the
1.0
is
released.
G
We're
gonna
start
really
pushing
developers
to
start
adopting
this
code
base,
and
so
far
it's
been
really
positive
feedback
from
the
developer
space
about
the
things
that
they're
able
to
do
now
much
more
easily
than
they
have
in
the
past.
So
we
are
going
to
continue
to
iterate
on
that
from
a
milestone
perspective,
the
session
kit
is
all
but
done
from
the
project
plan
specifically,
but,
like
I
just
said,
we're
going
to
keep
iterating
on
it
based
on
Improvement.
G
We
do
have
support
kind
of
built
into
the
contract
we
have
so
there
will
be
more
updates
coming
to
that.
The
next
big
thing
coming
is
the
contract
kit,
which
was
the
thing
that
we've
never
had,
and
it
is
kind
of
an
abstraction
layer
on
Smart
contract
data
and
making
sure
that
developers
are
more
easily
able
to
access
the
data
from
their
contracts
and
use
it
in
their
applications.
G
The
flip
side
of
that
is
also
this
code
generation
Suite
that
comes
with
the
contract
kit,
which
takes
basically
ABI
data
and
the
definition
of
the
contract
itself
and
generates
code
for
them.
That
is
based
on
that.
It's
going
to
really
help
the
the
developer
experience
and
make
sure
that
they
are
like
there's
Auto
completion
and
there's
type
hinting
and
there's
all
these
other
things
that
developers
may
need
or
may
benefit
from,
while
they're
actually
building
their
application.
That
is
in
a
early
release.
State,
we
I
think
it's
a
0.3
version
right
now.
G
We
have
some
people
starting
to
experiment
with
it.
I
think
the
the
code
itself
is
from
the
contract
side
is
getting
to
a
point
where
it's
worth
experimenting
with
and
providing
feedback
on
sort
of,
like
we
did
with
the
session
kit
in
this
late
spring
early
summer
and
we're
hoping
to
have
kind
of
an
MVP
of
that
and
then
not
too
distant
future
and
be
able
to
use
the
new
website
to
promote
that
and
document
it
and
really
show
it
off.
G
There's
a
couple
other
parts
left
in
the
project
that
are
in
the
really
early
prototype
phases,
and
that's
some
of
these
external
apis
that
we're
wrapping.
There
may
be
a
fourth
kit
coming
for
that,
I'm,
not
sure
about
that.
Quite
yet,
it's
something
we're
heavily
discuzzling
right
now
and
then
the
account
kit,
which
is
for
developers
to
be
able
to
basically
work
with
the
system
contracts
in
their
applications
more
easily.
So
those
two
kits
lots
of
documentation
coming
up
we're
going
to
continue
evolving
this
website.
G
So
that
way,
if
somebody
wants
to
build
on
any
of
these
chains,
it
is
you
know,
there's
going
to
be
one
home
for
smart
contracts,
because
that's
a
completely
different
world
and
then,
when
you
want
to
build
a
web
application,
hopefullywarf
kid.com
is
going
to
be
that
place.
Where
you'll
be
able
to
get
all
the
information
you
need.
G
So
we'll
we're
happy
to
link
out
from
the
site
to
any
chains,
specific
documentation,
for
you
know
the
variants
and
differences
that
each
chain
may
have
for
some
of
these
things,
and
then
you
guys
are
welcome
to
start
linking
out
to
that,
as
we
flesh
this
out
a
little
bit
more
and
make
it
really
a
home.
That
explains
how
you
build
these
types
of
apps,
so
yeah
all
is
going
well,
I
would
say
from
the
project
planning
perspective.
G
We
might
be
a
little
bit
behind
the
ball,
but
it
is
a
lot
is
happening
in
parallel
and
we're
still
pretty
confident,
there's
going
to
be
some
form
of
production,
ready
release
of
all
of
this.
By
our
scheduled
time,
the
documentation
might
bleed
a
little
bit
over,
depending
on
how
quickly
we
can
collect
feedback
from
the
community
right
that
sort
of
knowledge
that
they're
they
need.
So.