►
Description
This week the Antelope Coalition discusses the progress made with Scalability+ RFP, IBC deployment, P2P discovery, RAM limitations, Antler CDT, Instant Finality, Wallet SDK, and more!
00:00:00 Start
00:00:04 Scalability+ update
00:01:35 IBC Deployment vote
00:04:47 P2P Peer Discovery
00:05:18 Coalition top-off to fund RFPs
00:09:31 RAM limitation fixes
00:11:24 Antler CDT
00:12:17 Ledger app support
00:12:39 Developer onboarding and workshops
00:13:34 Instant Finality
00:14:48 Wallet SDK
00:21:39 IBC use case and marketing discussion
00:34:26 End
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
Yeah,
so
on
Tuesday
we
met
representatives
of
of
all
chains
and
and
as
well
as
the
engineers
of
enf,
and
we
discussed
essentially
the
revised
RFP
that
the
NF
is
proposing
to
submit.
So
essentially,
it's
a
kind
of
toned
down
like
like
slightly
smaller
in
scope,
version
of
the
RFP
that
we
issued
that
we
that
we
sent
out
so
they
would
be
essentially
responding
to
that
RFP
with
a
proposal
that
would
address
some
of
the
elements
in
there.
B
B
B
A
No
okay,
one
of
the
first
actions
we'll
do
today
is
we're
going
to
hold
a
go,
no
go
vote
to
complete
the
IBC
deployment
this
weekend.
The
one
caveat
will
be
wax
will
not
be
part
of
this
weekend's
deployment,
but
the
announcement
from
wax
is
they
will
deploy
as
soon
as
is
practical
within
their
competing
priorities.
E
D
A
C
D
G
C
D
This
call
were
expecting
five
years
ago,
and
we've
been
talking
about
this
particular
item
IDC
for
an
eternity
and
the
Coalition
got
together
now,
a
little
less
than
a
a
year
ago,
formally,
and
within
that
short
time
span,
we've
been
able
to
tackle
something
that
was
on
the
back
burner
for
almost
five
years
and
something
that's
quite
incremental
and
Monumental
in
terms
of
technology
for
each
of
our
respected
chains.
So
just
kudos
to
all
of
you
for
having
made
this
happen.
This
is
this
is
awesome.
This
is
quite
historic,.
A
A
E
D
We
can
because
I
believe
that
this
would
be
the
first
time
that
we
maybe
not
the
first
time,
but
that
we
publicly
kind
of
make
this
official
but
I
would
say
the
caveat
that
we're
not
there
yet,
because
we're
still
waiting
for
Douglas
to
bring
in
a
key
piece
of
information
that
may
or
may
not
change
slightly
the
numbers.
And
so
maybe,
if
everybody's
comfortable,
we
can
post
the
numbers,
because
this
is
recorded,
everybody
will
see
and
give
a
general
idea
of
what
it
is
and
then
I
believe.
D
D
D
A
D
It'll
it'll
make
or
break
us
this
year.
Wax
is
179,
531,
179,
531,
82
cents
and
ux
is
the
same
as
tell
us
and
for
those
listening.
So
those
numbers
come
from
the
formula
that
we
traditionally
use
looking
at
liquidity
depth
as
well
as
market
cap,
and
what
we've
done
this
time
around
is
we've
adjusted
the
floor.
D
The
previously
the
floor
was
at
a
three
percent
floor
and
we've
increased
that
to
a
five
percent
floor
to
come
up
to
these
numbers
and
the
the
number
guiding
in
the
beginning
was
eos,
mentioning
that
they'd
be
able
to
commit
a
million
dollars.
So
we
basically
you
know,
then
went
through
the
the
regular
process
to
determine
the
numbers
that
you
see
on
screen
and
as
I
mentioned
earlier,
this
is,
has
tentatively
been
agreed
by
Every
Chain.
D
We
have
not
taken
a
formal
vote,
we're
still
missing
some
information,
but
generally
what
you're
seeing
on
screen
is
pretty
much
what
we
should
be
committing
to
this
year.
That
number,
if
you
add
all
of
those,
gives
roughly
up
1.3
million
dollars,
the
Coalition
Coalition
still
has
a
little
over
600
000
in
its
treasury.
When
we
add
both
together,
it
is
just
shy
of
two
million
dollars
for
your
2023.
D
A
B
So
it's
kind
of
what
that
was
explaining
about
earlier.
The
the
we
asked
the
enf
to
essentially
beat
a
little
bit
more,
what
they
were
proposing
to
do
and
and
then
we
reached
consensus
that
these
were
essentially
worthwhile
even
in
the
reduced
scope,
and
that
we
would
be
interested
in
reviewing
a
formal
bid
from
the
NF.
A
E
E
A
A
From
what
I
understand
from
the
project
management
side
is
that
there,
as
we
talked
about
last
week,
there
were
some
resource
constrained
hiccups
due
to
uncontrollable
issues.
The
debugger
component
was
going
to
be
excluded.
Largely
things
are
back
on
track,
although
at
this
point
our
project
managers
are
not
calling
it
green.
Yet
it's
I,
don't
know
again
Bart
or
Ted.
If
there's
any
flavor,
you
want
to
add
to
that.
A
H
Had
two
meetings
with
oci
today,
they
did
not
bring
it
up.
They
do
not
have
a
status
yet
I'm
I'm
again,
assuming
it
is
going
to
be
very
low
priority
for
them
in
terms
of
them
running
this
program,
I
will
bring
it
up.
We
have
some
other
work.
We
need
to
do
with
them
and
once
we've
completed
that
and
I
mean
in
terms
of
larger
scope
negotiations
once
we've
completed
that
I'll
bring
this
up
again.
B
A
B
So
essentially,
we've
been
there's
been
a
bit
of
back
and
forth
between
dnf
engineering
and
myself
on
the
IBC
stuff,
sorry
instructionality
stuff.
So
there's
there's
a
few
decisions
that
we
that
we
took
that
are
essentially
pushing
back
a
few
of
the
Milestones
a
little
bit.
But
the
final
Milestones
themselves
will
probably
not
be
affected
because
we're
gonna
putting
more
work
in
the
front
and
less
at
the
back,
so
essentially
I
think
I.
B
A
I
I
So
this
new
proposed
schedule
reshapes
the
project
kind
of
do
that
I
guess
on
that
front
we
are
already
kind
of
moving
faster
as
if
this
was
the
direction
we're
going,
but
we
still
do
need
kind
of
just
to
cement
that
in
we've
started
on
the
user
interface
elements
kind
of
the
ual
like
side
of
this
project
there
were
was
a
brief
animated,
gif
shared.
It
was
last
week,
maybe
earlier
this
week,
but
that's
starting
to
come
to
life.
I
So
we
kind
of
have
the
eosjs
side
covered
through
the
session
kit
and
the
user
interface
is
starting
to
come
to
life.
So
hopefully,
we'll
start
seeing
some
wallet
Integrations
in
the
not
too
distant
future
at
a
very
like
rudimentary
level
and
yeah
I
mean
overall,
things
are
going
really
well
with
the
project.
It
doesn't
really
align
with
the
version
three
milestones
and
that's
why
we
kind
of
brought
the
version
four
up
which
it
looks
like
you've
got
up
right
now,
the
same
hours,
it's
the
same
costs
it's
just
if
like.
A
I
was
gonna
say
so.
One
thing
this
group
needs
to
do
is
because
our
the
Milestone
payments
in
the
contract
are
tied
to
the
previous
schedule
of
is
this
group
needs
to
approve
the
Change
Control
to
essentially
distribute
the
funds
slightly
differently,
even
though
the
total
cost
is
exactly
the
same
and
the
end
State
scope
is
also
exactly
the
same.
I
mean.
A
Is
there
any
questions
about
that
and
the
reason
why
we
have
to
do
this
is
because
again
there's
a
contract,
so
we
can't
just
ignore
the
contract
because
we
don't
want
to
we,
but
we
have
some
flexibility
in
the
Milestone
statements.
The
way
the
contract
is
written
is
they're
estimated,
and
so,
if
this
group
approves
the
changes
that
can
fall
under
the
estimation
clause.
I
Yep,
it's
both
the
payments
and
then
just
the
the
weekly
status
reports.
We
work
with
the
enf
to
fill
out
those
don't
look
super
healthy
right
now,
just
because
of
the
way
that
the
Milestones
were
structured
in
three
and
the
project.
Just
from
like
that,
quick
glance,
perspective
would
look
a
lot
more
healthy
under
version
4.
F
Just
to
say
a
word
for
this:
the
the
discussion
around
what
how
to
approach
this
is
very
much
community-led
and
and
I
think
that
these
are
this.
We
are
hearing
back
from
people.
What
would
be
most
useful
for
the
developer,
Community
now
so
I
hope,
I
I
would
I
said
in
that
in
those
discussions
that
I
would
speak
up
and
in
favor
of
of
this
I
think
it's
always
right
to
to
listen
to
your
community
and
and
do
what
they're
asking
you
to
do
so.
D
Yeah
I'd
propose
that
we
vote
on
this
I
guess
reprioritization
change
and
if
the
bill
passes
which
I
imagine
it
it
will
based
on
the
discussions
that
we've
had
previously
on
this,
and
in
that
specific
Channel,
then
we
can
make
addendums
to
the
current
contract
and
then,
when
we're
doing
the
program
updates.
That
will
also
then
be
reflected
going
forward.
D
E
D
D
And
then
I
think,
as
as
you
mentioned,
Aaron,
it's
not
a
it's
just
a
reprioritization,
so
it
means
that
we
will
likely
be
paying
for
a
milestone
before
another
one,
but
ultimately
it
ends
up
being
the
exact
same
thing
yep
so
and
for
everybody
else.
We've
already
allocated
those
funds
in
a
separate
count,
so
really
nothing
changes.
I
Not
that
I
mean
I
could
rant
about
this
project
for
a
long
time,
but
not
that's
relevant
to
the
larger
group.
You
know
if
you
are
interested
in
like
the
minutia
of
what's
going
on.
We
do
have
the
transcripts
and
the
weekly
recorded
calls
and
the
telegram
Channel
That's
available
for
that
kind
of
stuff,
so
happy
to
answer
any
questions.
A
I
I
may
be
missing
out
on
conversations,
but
related
to
IBC
is
their.
Are
there,
discussions
going
around
about
like
I,
know
we're
talking
about
marketing
and
the
actual
launch
and
the
deployments
of
it,
but,
like
the
use
case,
the
kind
of
first
use
case
afterwards,
as
you
guys
were
talking
last
week.
That's
what
I
was
thinking
about
is
like
if
it's
deployed
and
there's
no
way
for
people
to
interact
with
it
in
a
way
that
they're
actually
going
to
want
to
interact.
I
D
B
That's
part
of
the
release
we
we
did
build
a
go
to
reference
front
end
that
allows
you
to
use
a
the
red
blood
token
construct
to
essentially
move
tokens
across
chains,
so
that's
available
on
on
basically
day
one
as
well,
and
we
recorded
as
well
two
podcasts
I'm,
not
sure
if
they,
if
they're
out
yet
but
with
Eric
and
and
everything
yes
team,
where
we
discuss
additional
use.
Cases
that
could
be
could
come
at
some
point.
B
Another
thing
that
we've
done
that
we've
kind
of
not
done
but
like
where
we
have
in
the
in
the
The
Works,
is
to
organize
a
kind
of
developer
q
a
for
IBC.
So
we
would
like
to
invite
essentially
like
a
prominent
well-known
people
in
the
community
that
have
either
expressed
interest
or
that
have
essentially
achieved
a
certain
level
of
technical
recognition
and
then
have
a
session
during
which
we
will
essentially
present
in
technical
details.
B
So
the
the
the
the
aspect,
I
think
is
probably
most
important
is
to
highlight-
is
that
IBC
is
a
building
block
that
is
essentially
the
foundation
for
a
lot
of
other
applications
and
a
lot
of
other
use
cases,
and
it
the
next
phase,
essentially
now
to
explain
this
to
developers
and
to
lead
that
second
wave
of
builders
that
will
start
building
applications.
On
top
of
it.
C
One
of
the
big
reasons
why
Avalanche
was
picked
by
Amazon
as
official
partner
for
Enterprise
blockchain
deployments
is
their
subnets,
which
is
our
version
of
IBC,
so
so
yeah,
maybe
maybe
tying
that
to
maybe
I,
don't
know
indirectly,
so
we're
not
hyping
Avalanche,
but
you
know
this
is.
This
is
a
very,
very
important
feature
that
not
that
many
other
technologies
have.
D
F
It
if
we
target
our
message
towards
Builders
and
and
where
it
intersects
with
investors-
or
you
know,
Community
enthusiasts
talk
about
how
how
this
allows
new
things
to
be
built,
I
think
that'll.
You
know
that
will
be
a
more
clear
message.
It
doesn't
set
up
the
wrong
expectations,
so
I
think
it's
mainly
an
issue
of
how
we
focus
those
those
Community
Communications
going
forward.
B
Yeah
I
tend
to
agree.
I
think
this
is.
This
should
be
the
focus
for
now.
The
other
thing,
as
I
mentioned
also
is
we
have
been
building
the
amm.
That
is
also
I,
guess,
like
nearing
completion
and
I
mean
like
we
have
it
on
testnet
right
now.
We've
been
testing
it
quite
thoroughly
for
the
last
few
like
couple
months,
so
that's
something
that
we
will
eventually
be
deploying
to
maintenance
as
well.
B
It's
going
to
be
dictated
by
commercial
considerations
and
not
and
not
necessarily
like
the
technology
is
already
there.
It's
just
it
just
has
to
be,
has
to
be
launched
in
a
way
that
that
makes
sense
commercially.
But
that
might
be
another
discussion
if
we
want
to
discuss
that
between
the
chain.
Heads
maybe
on
Monday
I
could
provide
a
bit
of
an
overview
there
and
there
might
be
some
some
things
you
guys
can
do
to
help
accelerating
that
timeline.
F
I
I
think
that
would
be
great
I
think
if
we,
if
we
pitch
this
to
people
as
a
starting
line,
not
a
Finish
Line
that
will
be
helpful
and
then,
as
that
being
one
of
the
first
one
of
the
first
public
uses,
I
think
would
be
great.
People
would
be
excited
about
that
and
then
finally,
she's
gonna
be
who's
that
first
Apple.
You
know
useful
application
out
there
using
this.
F
D
G
D
B
So
essentially
like
the
the
milestone
for
documentation
is
all-encompassing,
so
it's
essentially
at
the
tail
end
of
the
project
and
covers
the
documentation
for
IBC
plus
instant
Fidelity.
That's
when
payment
is
due.
This
being
said,
we
already
have
the
documentation
for
IBC
it's
up
and
running
At
Hello
by
bc.io,
so
you
can
can
go
there
and
you
have
a
pretty
exhaustive
documentation
for.
D
B
Going
to
be
a
work
in
progress
as
people
as
people,
you
know
like
I
guess
as
as
the
project
evolves
and
as
we
collect
more
questions
for
the
FAQ
and,
of
course,
if
anyone
finds
any
any
typos
or
anything,
it's
not
it's
not
officially
out
yet
like,
but
it's
it's
it's
been
submitted
for
for
review.
Enf
guys
were
at
enough
marketing.
B
D
D
D
Be
pushing
the
button
over
this
weekend
and
so
in
order
to
have
a
formal
vote.
The
following
meeting
is
the
only
one
and
then
we'd
be
releasing
the
payment.
I
believe
it's
100
on
EOS
skill
at
this
stage.
Anyways!
Yes,
because
it's
a
it's
a
tripartite
or
Juan
part
type
contract,
then
I
think
having
that
formal
vote
for
release
of
payment
would
be.
You
know
just
standard
operating
procedure,
you're.