►
Description
This week the Antelope Coalition discusses the progress made with RFP dates, P2P discovery. Final Finality / IBC, Wallet SDK, and more!
00:00:00 Start
00:00:40 RFP dates rescheduling
00:03:20 P2P Peer discovery
00:05:03 RAM Limitation fixes
00:06:17 Ledger App support
00:06:48 Developer onboarding and workshops
00:07:35 IBC / Instant Finality
00:12:08 Wallet SDK update
00:16:47 Provable state domains
00:17:09 Sign up for external orgs for security updates
00:18:17 Scheduling P2P vendor reviews
00:21:13 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
A
A
All
right
so,
first
of
all,
with
the
so
we
have
the
rfps
that
are
out,
but
one
thing
that
we
sort
of
touched
on
in
the
Monday
meeting
is
that,
with
the
holidays
impending
at
minimum,
we
need
to
readjust
the
dates
not
just
for
the
P2P
peer
Discovery,
but
also
the
Rand
limitation
fixes
just
to
make
sure
that
the
Coalition
has
enough
time
to
really
thoroughly
discuss
things
for
the
vendors
to
have
time
to.
You
know
properly
respond
with
all
of
their
internal
resources,
so
I
I,
guess.
A
A
quick
thing
we
need
to
know
is.
Is
there
any
concerns
of
us
adjusting
the
dates
to
essentially
skip
over
the
holidays
and
and
re-pick
them
up
in
January?
I
also
know
before
we
answer
that,
there's
other
concerns
that
we've
talked
about
like
we
want
to
make
sure
we
go
through
some
financial
review
exercises
and
budgeting
exercises.
A
D
Yeah
I
think
so
I
mean
the
I
believe
we
agreed
that
the
last
two
weeks
of
December
we
would
not
have
our
scheduled
ceremonies
because
of
people
are
traveling.
People
are
going
to
be
out
of
pocket.
You
know
I'm
I'm
already
in
Canada
and
and
my
schedule
is
clearing
out
at
this
after
this
week.
So
I
will
not
be
available
until
first
week
of
January.
A
And
this
is
probably
the
only
thing
that's
been
authorized
to
say
yes
to
so
that'll
be
unique.
I
will
get
those
updated,
we'll
get
we'll,
publish
the
dates
shortly,
to
make
sure
all
the
vendors
and
such
are
aware,
but
otherwise,
we'll
you
know
kind
of
pick
these
things
up
in
a
couple
weeks
and
so
related
to
that
P2P
peer
Discovery.
There
was
again
some
discussion
around
that,
but
I
think
let
me
hold
on
a
sec,
probably
took
some
notes.
A
No
I
did
not
so
we
had
the
just
a
summary
we
had
the
proposals
come
back.
People
have
had
the
opportunity
to
read
them,
but
what
we're
we
kind
of
need
to
have
a
broader
discussion
around
the
evaluation
of
the
event,
the
vendors
and
I
think
we
were
going
to
have
a
follow-up
meeting
on
that.
But
again
I
would
reference
back
to
the
holiday
discussion.
I,
don't
think
we're
gonna
have
time
to
do
that
before
the
beginning
of
the
year.
A
The
other
component,
just
for
the
recording,
is
that
the
Coalition
is
going
through
its
2023
budgeting
cycle,
and
so
we
do
know
that
that
needs
to
be
completed.
First
I.
You
know
I,
don't
have
a
timeline
on
that
yet,
but
it
is
a
top
priority,
and
so
once
that
discussion
is
completed,
then
the
evaluate
the
final
evaluation
of
you
know,
selecting
the
vendor
and
moving
forward
and
negotiating
with
P2P
will
be
able
to
occur.
A
A
All
right,
perfect
next
one
Rand
limitation,
sixes,
it's
just
the
rfps
in
process,
we'll
have
more
information
on
that.
When
we
get
back
from
our
holiday
break,
antler
CDT
I
can
give
you
the
update
that
project
plans
are
being
leveled
broken
out.
This
program
of
the
CDT
is
being
essentially
broken
in
the
sub
components.
I
think
there's
eight
or
nine
sub
projects
in
there.
So
we
could
manage
the
risk
of
each
individually
at
the
beginning
of
January,
I
hope
to
be
able
to
have
something
published
in
if
nothing
else.
A
The
enfs
a
public
program
report
that
we'll
end
up
publishing
about
a
week
into
January
it'll,
have
all
the
individual
dates,
but
ultimately
the
the
goal
is
to
have
the
scope,
finalized
and
everything
built
and
ready.
For
you
know,
final
Runway
testing
by
the
end
of
February,
beginning
of
March
somewhere
in
that
time
frame,
don't
want
to
give
exact
dates
right
now,
but
that
is
kind
of
the
overall
on
that
all
right.
Next
one
Ledger
app
just
we
heard
back
from
them
yet.
A
A
So
there
were
two
more
meetings
scheduled
I,
don't
I,
don't
know
if
they
have
occurred
or
not.
I
will
try
to
get
you
guys.
An
update
on
that
as
soon
as
possible.
Again
Ted
is
unavailable
today,
but
I
know
he's
been
engaged
with
oci
on
this
Guillaume.
Have
you
had
any
more
contact
with
them
kind
of
in
that
separate
thread.
E
A
E
Yeah
absolutely
so,
essentially,
we
received
the
final
report
that
just
what
there
there
was
just
a
a
small
thing
to
change
so
they're,
just
correcting
it
and
sending
it
back,
but
then
I'll
share
with
you
guys
and
essentially
it's
the
external
audit
report.
They
found
zero,
critical
or
major
or
even
low
priority
issues
with
it.
They
had
five
remarks,
but
these
remarks
are
just
like
kind
of
FYI
this
that
just
so
you're
aware.
E
E
This
I
guess,
like
naming
convention
that
we
discussed
in
previous
calls
like
as
we
as
we
agreed.
Each
chain
will
be
responsible
for
a
naming
convention
that
will
now
be
yeah
essentially
like
will
determine
the
name
of
the
contracts
that
are
used
in
IBC
and
then
once
I
have.
That
I
will
need
Every
Chain
to
also
sign
at
least
one
and
Sig,
probably
two
to
create
the
first
account,
which
is
yes,
I,
know
IBC,
and
then
what
I
would
suggest
is
on
each
of
the
chains.
E
E
So
I'll,
if
that's
okay,
I'll,
give
you
guys
like
a
few
days,
let's
say,
let's
say
like
until
Monday
or
something
to
come
up
with
that
with
that
naming
convention.
If
you
don't
at
that
point,
I'll
just
use
a
default.
One
and
I
will
start
preparing
everything
and,
with
the
invent
of
having
the
F6
ready
for
BT's
approval
in
early
January.
E
E
And
then
there's
there's
one
essentially
PR
for
system
contract
to
be
to
be
done
to
essentially
enforce
that
naming
convention,
so
I
will
also
submit
the
pr
to
your
respective
GitHub,
repos
or
whatever.
Whatever
way
you
would
prefer
the
way
you
want
to
to
handle
that
so
I
can
I
can
reach
out
to
to
you
guys
individually
to
just
make
sure
I.
Do
it
the
way
that
you're
expecting.
B
E
Other
than
that
or
another
no
I
think
I
think
it's
going
very
well
in
the
IBC
side
on
the
institutionality
as
well,
everything
is
going
going
very
good.
We
should
have
some.
We
just
completed
one
more
milestone
for
IBC
we're
expecting
to
have
our
first
one,
then
also
for
finality
in
early
January.
So
it
took
a
bit
longer
due
to
essentially
like
like
having
the
very
few
people
that
are
able
to
review
these
things,
but
it's
moving
forward
so
everything's
great.
A
F
Yeah
sure
we've
been
doing
our
calls
still,
they
are
pretty
much
bi-weekly
and
again,
if
you
ever
want
to
catch
up
on
those
they're
on
wharfkit.com,
we've
been
publishing
them
there
right
now
or
I
guess,
I
should
say.
Last
week
we
published
the
first
really
early
access
version
of
the
session
kit,
which
is
how
it's
going
to
be
performing
transactions.
F
F
We
are
writing
the
guide
right
now,
as
well
as
figuring
out
how
guides
fit
into
the
website.
I
guess
leading
into
that.
We
have
been
spending
the
last
week
or
so
really
fleshing
out
what
the
full
website's
going
to
look
like
how
it's
going
to
both
it's
going
to
kind
of
be
marketing.
It's
going
to
be
reference
material
and
it's
going
to
be
education,
so
it's
coming
together.
Those
are
the
three
big
things
that
the
website
will
feature.
F
The
other
kits
are
not
published,
yet
the
account
kid
and
the
contract
kit
there's
been
quite
a
bit
of
progress
on
the
account
kit,
but
we're
still
kind
of
fleshing
all
of
that
out.
If
you're.
Looking
just
purely
at
the
progress
reports,
the
Milestone
two
was
to
publish
the
kits
and
we
had
estimated
a
date
of
that
at
the
beginning
of
December
we're
kind
of
mid-December.
F
Now
that
is
that
milestone's,
probably
like
75
complete,
but
we
are
shifting
around
in
two
milestones:
three
through
five
I
want
to
say
and
you'll
also
notice,
progress
on
those
as
well.
So,
though,
that
Milestone
itself
is
behind,
but
it's
not
for
a
lack
of
progress.
Overall,
it
is
just
that
we
felt
it
was
best
to
shift
into
some
of
the
future
Milestones
before
we
submitted
Milestone
to
for
approval
because
they
are
just
so
intertwined
with
how
they
all
interact
with
each
other.
F
So
we
are
making
good
progress
on
everything,
I
would
say
overall,
but
the
I'm
just
saying
all
this
has
a
overview
of
if
you're,
just
purely
looking
at
reports
without
context,
so
I
think
the
only
detriment
in
that
Milestone
not
being
completed
was
just
that
like
it
is.
The
progress
is
happening
out
of
order
and
most
of
the
detriment
is
probably
to
us,
because
we're
not
getting
paid
for
that.
Yet
so
we
are
still
pushing
ahead.
A
So
would
it
be
accurate
to
say
Aaron
if
I
recall
that
in
that
report
the
schedule
went
yellow,
but
it's
only
because
of
internal
Milestones
shifting
around,
but
it's
not
going
to
Red
because
at
present
time
there's
no
risk
perceived
to
the
overall
project
schedule.
It's
just
the
orders.
A
little
different
is
that
correct,
yeah.
F
B
A
A
We
didn't
quite
decide
to
put
this
in
the
backlog
because
it's
important,
but
this
is
probably
something
we
need
to
table
till
January.
We
have
thrown
a
couple
short-term
ideas
out
there.
For
example,
people
can
sign
up
to
watch
things
on
GitHub
and
and
other
things,
but
there's
that
is
escalated
into
discussion
of
well.
There
can
be
more
than
that.
That
could
provide
value
both
to
us
to
know
who's
following
and
also
for
people
following.
Maybe
they
can,
you
know,
get
a
little
bit
more
insights.
A
A
A
This
is
tied
into
the
first
couple
things
we
talked
about,
which
is
we're
going
to
redo
the
or
extend
the
schedule
to
handle
the
end
of
the
year
holidays.
So
we
will
also
pick
this
up
as
a
needed
item
in
January.
So
with
all
of
that,
there
is
one
other
logistica
logistical
item.
We
did
vote
as
a
chain
to
cancel
this
meeting
next
week
and
the
week
after
so
it'll
pick
up
in
three
weeks
for
the
viewers
there's
also
the
Monday
Workshop
meeting.
A
C
I'm
going
to
suggest
that
we
do
the
the
biggest
part
of
the
month,
the
biggest
value
I
see
of
the
Monday
meeting
is
allowing
us
to
talk
through
things
that
we
can
then
share
with
the
rest
of
the
group
on
Thursday
foreign
and
so
having
it.
Outside
of
that
context,
doesn't
really
seem
to
make
much
sense,
plus
I,
think
they'll
be
sparsely
attended.
So
why
don't
we
just
say.