►
Description
This week the Antelope Coalition discusses Ledger app support, adding new chains to the coalition, reprioritization of the top items, secure smart contract library, developer onboarding, instant finality and ibc, Wallet SDK and more!
00:00:00 Start
00:00:04 Ledger app
00:04:43 Adding new chains to the coalition
00:11:14 Re-prioritization of top items for the coalition
00:18:44 Secure smart contract library
00:21:47 Developer onboarding and developer workshops
00:23:53 Instant Finality / IBC approvers
00:28:30 Wallet SDK approvers
00:31:28 Antelope brand deliverables
00:33:09 End
Antelope Coalition Weekly Meeting - October 27th - Blog Post:
https://eosnetwork.com/blog/antelope-coalition-weekly-meeting-october-27th/
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 #EOSIO #ENF
A
B
C
D
B
D
B
E
Really,
oh
yeah
I
know
it
it
has
to
be.
We
have
to
figure
that
out
for
sure
I
actually
think
we
should.
We
should
be
talking
with
Satoshi
Labs
on
getting
treasure
on
board
too,
because
that's
sort
of
the
other.
You
know
OG
series
tool
for
for
as
a
hard
walk
as
a
as
a
cold
wallet
yeah,
so
yeah
foreign.
D
Let's
do
it
as
its
own
task
I
think
this
is.
This
is
more
of
a
priority
and
right,
and
if
you
know
if,
if
if
we
have,
if
we
don't
have
bandwidth
of
ens
or
in
an
enf
side
to
to
solve
this,
then
I'm
willing
to
dedicate
some
engineering
time
from
us
to
to
see
like
whatever
needs
to
be
done
to
to
to
get
this
resolved
right.
E
E
B
A
A
However,
he
needed
to
you
know,
as
we
discussed
he's
not
here
right
now,
so
I
will
send
out
another
doodle
one
thing:
I've
well,
there's
actually
two
things.
First
of
all,
my
first
idea
is
not
only
this,
but
there's
going
to
be
a
lot
of
topics
that
we
need
to
get
key
people
involved
for
discussing
things.
Is
there
an
hour
that
everybody
can
block
out
every
week
and
that
at
the
beginning
of
the
like
by
Friday,
I
will
fill
that
in
with
the
topic
du
jour
that
we
need.
A
So,
instead
of
like
playing
this
game,
we
can
just
go
yep
our
Tuesday
scheduled
slot.
This
is
the
topic
we're
going
to
talk
about,
make
that
a
working
meeting
as
opposed
to
this
one,
which
is
a
much
higher
level
status
meeting.
That's
covering
broad
things,
just
curious.
If
not,
you
know
we
can
continue
the
doodle
process,
but
again
if
people
are
not
responding
to
those
Doodles
like
within
24
hours,
they're
almost
like
it's
not
working
because
I
guess
I.
E
E
A
F
C
G
C
G
E
C
E
A
E
E
E
E
A
Prioritization
of
top
development
items
I'll
just
give
everybody
a
quick
update,
we'll
we'll
come
back
to
P2P
in
a
second,
because
there's
been
some
movement
on
this,
the
other
ones,
the
smart
contracts,
tooling,
Ram
limitation,
provable
State
domains.
Those
have
all
moved
into
essentially
the
more
detailed
requirements,
development
stage.
I,
don't
have
an
estimate
back
on
how
long
that
will
take
you
know
so,
there's
really
no
additional
update
there.
Ted
do
you
wanna.
C
C
Although
I
was
able
to
drag
it
out
of
them
through
a
follow-on
meeting,
so
this
is
just
going
to
be
for
peer
network
discovery.
So
when
a
person
brings
a
note
up
it,
it
has
a
you
know,
a
list
that
helps
it
find
its
peers
get
up
in
the
network
and
start
you
know,
start
the
P2P
process
and
then
later
we'll
do
a
separate
RFP.
If
the
appetite
is
there
from
the
Coalition
for
the
Swarm
download,
so
we
believe
from
early
analysis
that
this
will
be
about
half
the
duration.
C
C
A
C
Did
so
it's
it's
in
the
telegram
group
now
for
you
all
to
read
and
really
now
focuses
on
the
peer
network
discovery
portion
and
that
will
be
the
smaller,
so
it'll
be
shorter
in
scope
and
less
cost
and
from
what
you
know.
The
engineers
have
said
the
you
know
the
The
three
principal
Engineers.
This
is
the
more
delicate
part
of
the
code
that
probably
needs
the
rewrite
most
and,
of
course,
there'll
be
a
lot
of
benefit
if
we
do
work
out
a
swarm
design
to
follow
on.
C
A
It
would
be
great
if
we
could
release
this
RFP
on
Monday,
but
I
do
want
to
make
sure
everybody
has
time
to
review
it.
If
you
are
going
to
review
it
in
depth,
I'm
putting
it
that
way,
because
if,
if
you're
going
to
approach
it
potentially
as
well,
if
it's
less
than
the
other
one,
then
I'll
skim
it
then
maybe
I
would
say:
hey
just
take
the
next
24
hours
to
do
that,
and
then
we
could
get
this
moving,
but
again
I'm,
not
pressuring
I'm.
This
is
a
logistical
thing.
A
C
I
mean
I
think
your
point
Jeff
about
the
fact
that
it
is
just
a
subset
of
what
was
already
approved
by
the
Coalition.
If
you
could
trust
us
enough
to
know
that
it's
just
the
first
half
of
the
two
parts
that
were
in
the
last
one,
it
should
make
the
review
a
lot
simpler
for
you.
We
have
ensured
that's
what
it
has
distilled
down
to.
E
F
C
Guess,
I
guess
the
options
are,
if
you
guys
would
be
willing
to
just
you
know,
vote
in
the
telegram
Group
by
Monday,
then
we
could
get
the
thing
moving
sooner.
Otherwise
we
could
wait
and
just
have
a
full
vote.
Next
Thursday
in
the
normally
scheduled
call
next
Thursday,
and
so
it
would
just
be
a
week
that
would
give
you
a
week
to
look
it
over
and
and
we
would
do
a
formal
vote
on
the
call
next.
D
C
A
Okay,
so
this
will
be
on
the
agenda
for
next
week.
Great
all
right
next
item
the
secure
smart
contract
Library.
So
the
question
really.
This
actually
comes
to
you
Douglas,
because-
and
we
made
a
very
big
point-
that
you
were
traveling
and
not
as
available
last
week.
But
if
you
have
had
time
or
when
will
you
have
time
to
review
this?
A
Ted
and
I
did
meet
with
the
vendors
I
I
posted
into
the
Coalition
Channel,
a
fairly
detailed
breakdown
of
their
rate
structure,
the
hours
they
assigned
to
each
item
and
then
or
each
a
task
and
then
which
tasks
rolled
up
into
which
deliverables?
Actually
they
even
said
which
deliverables
would
be
in
each
Milestone,
so
I
think
we
really
just
need
you
to
review
it.
A
E
A
E
Yeah
yeah,
no,
that's
what
I
mean
I
I,
you
guys
have
already
reviewed
it.
You've
seen
you've
posted
your
thoughts
and
and
I
just
need
to
I.
Just
need
to
you
know:
go
through
that.
You
know
make
sure
that
your
thoughts
align
with
mine,
as
is
usually
the
pattern
pull
out
any
you
know
any
points
that
I
have
concern
about,
which
you
know
I
sometimes
sometimes
do,
and
you
know
I
can
do
that.
E
Why
don't
we
say
we'll
get
that
for
sure
and
be
already
by
by
next
week
on
this
call,
but
I'll
aim
to
do
it
I'll
aim
to
do
it
and
have
it
this
weekend
and
have
it
for
you
guys
sooner,
but
there's
no
call
necessary.
You
guys
have
you
guys
have
thoroughly
documented
anything
I
think
we
would
talk
about
that.
You
know
the
rest.
We
can
just
do
asynchronously.
E
C
So
you
know
this
is
in
my
area
again:
oci
failed
to
schedule.
The
meeting
I
was
waiting.
I
gave
them
five
slots
this
week
and
they
reached
out
to
me
you
know.
Finally,
today
saying
hey:
do
you
still
have
a
time
at
this?
You
know
when
you
know
I
gave
them
the
slots
Wednesday
Thursday
last
week
and
then
they're
reaching
out
on
Thursday.
You
know
to
say:
do
you
have
any
of
those
slots
available,
so
they're
ready
to
talk
with
me
and
again
I'm
that
they
didn't
schedule
again?
C
You
know
they
haven't
scheduled
for
I'm
available
all
next
week
and
they
still
have
been
set
a
time
slot
up.
I'm,
I'm
I
think
the
problem
on
their
end.
Is
they
want
all
of
these
VP
level,
people
in
their
company
in
the
meeting
and
they're
having
a
real
trouble
getting
those
people
all
to
get
to
get
the
calendars
together?
C
They
don't
have
anyone
that
can
actually
glue
those
calendars
together,
other
and
so
it
takes
them
a
week
to
find
out
that
they're
all
available
at
4
pm
on
Thursday
or
whatever
it
is
and
by
then
you
know,
my
slot
is
gone.
So
yeah
I
I,
you
heard
me
give
them
that
feedback
pretty
directly
on
the
call
today,
I.
A
G
G
I'm
I'm
expecting
this
review
to
be
complete
sometime
by
the
end
of
next
week,
and
that
is
essentially
the
last
I
mean
second
to
last
hurdle
before
releasing
to
to
mainnet
the
first.
The
other
question
is
essentially
the
IBC
governance
questions
that
we
have
to
discuss
so
so
these
are
the
main,
the
two
main
things
that
we
were
waiting
for.
We
also
have
now
confirmation
that
the
auditing
team
is
ready
to
to
perform
the
the
audit.
G
So
the
timeline
is
essentially
like
waiting
for
the
review
from
enf
first
and
then,
once
that's
done,
send
it
to
the
auditing
team
and
and
by
the
time
that
this
is
done.
We
should
have
been
able
to
to
answer
the
questions
related
to
to
the
IBC
governance,
and
hopefully,
sometime
in
November,
be
able
to
deploy
this
towards
the
Coalition
main
Nets.
G
So
that's
for
that's
for
that's
the
update
for
the
Milestone
number
one
for
IBC
Milestone
number,
five
for
for
the
combined
IBC
and,
if
is
essentially
the
release
of
the
the
basically
like
the
the
proof,
server
API,
as
well
as
what
we
call
the
light.
Bb
light
proof,
DB
optimized,
at
a
store
to
store
the
intermediate
states
of
Merkel
trees
at
all
block
Heights.
So
this
is
this
was
a
milestone
scheduled
for
next
month.
G
We
completed
this
this
week,
so
essentially,
we've
now
started
engaging
with
block
producers
with
several
block
producers
teams
to
try
to
get
it
tested
and
reviewed
and
we'll
be
posting
more
feedback
on
that
as
we
as
We
Gather
it.
So
we've
got
a
essentially
like
it's
right
now,
there's
three
components
to
it:
it's
Firehouse
server,
the
light
proof,
DB
and
the
proof
server
itself.
G
All
of
the
three
together
are
also
available
as
a
Docker
bundle,
so
for
people
that
don't
necessarily
want
to
to
to
to
run
fire
hose
independently
and
that
are
not
necessarily
like
all
like
technically,
very
technically
Savvy.
They
had
that
option
as
well.
So
this
has
now
been
open
sourced
and
is
available
for
for
testing.
G
So
if
anyone
from
the
Coalition
chains
I
want
to
participate
in
that
testing
phase,
just
reach
out
to
me
happy
to
point
you
in
the
right
direction-
and
we
are
we're
also
planning
at
some
point
to
also
support
State
history
plugin
for
that
one.
So,
from
these
three
components,
basically,
fire
hose
is
you
can
swap
it
for
you,
you're
gonna
be
able
to
swap
it
for
ship
and
essentially
the
whole
solution
will
will
work
with
with
either
of
them.
G
So
that's
for
Milestone
number,
five
now
for
instant
finality.
We
also
completed
with
the
one
that
was
Milestone
I,
believe
number
four,
which
is
essentially
like
specifications
and
mathematical
proofs.
We're
going
to
be
meeting
with
enf
engineering
to
review
it
next
Tuesday,
and
that
is
about
it.
So
that's
pretty
much
it
that's
pretty
much!
It.
B
Good
thing
we
we
are
rescheduling
the
meeting
right
now.
I
guess
that's,
first
and
foremost
for
everybody.
That's
involved!
If
you
want
to
be
in
that
meeting,
there's
a
doodle
running
in
the
channel
right
now,
I'm-
probably
going
to
try
to
schedule
something
either
tomorrow
or
over
the
weekend,
depending
on
the
dates
based
on
when
most
people
are
available,
and
then
that
will
be
our
new
reoccurring
time
slot.
We
kind
of
rushed
to
get
the
first
meeting
scheduled
and
I.
B
B
We
can
talk
about
that
on
the
next
call
for
that,
as
far
as
actual
work
goes,
we
are
currently
working
on
the
new
Milestone
number
two,
as
well
as
Milestone,
eight,
which
these
numbers
may
have
changed
and
the
names
may
have
changed,
but
number
two
is
kind
of
the
core
that
we
need
to
expand
off
of
for
everything
else
and
number
eight
is
The
Branding
for
the
project.
We
just
had
a
design
call
this
morning
and
everybody
seems
to
really
like
the
direction
it's
going
internally.
B
So
I'm
really
excited
to
share
that
stuff,
but
we're
kind
of
holding
off
until
we
can
show
the
name,
the
logo,
the
color
palettes
kind
of
the
meaning,
the
ideas,
the
themes
we
want
to
like
include
it
all
in
one
as
well
as
some
mock-ups
sort
of
like
the
antelope
branding
process
went
through.
So
we
really.
We
want
this
to
be
something
that
the
community
latches
on
to
and
it's
like.
B
Oh
yeah,
there's
this
thing
you
can
use-
and
this
is
what
it's
called
and
just
be
very
recognizable
staple
of
the
developer
Community
within
the
space,
so
we're
all
excited
to
be
getting
our
hands
dirty
with
some
code.
That's
what
I
had
to
pull
myself
away
from
to
come,
join
this
meeting
and
and
we're
excited
to
keep
pushing
on
it.
So
it's
it's
coming
together
nicely.
It's
been
years
of
planning
and
thinking
of
this
thing
and
now
we're
executing
on
it.
A
Very
cool
all
right:
let's
see
document
Antelope
work
group
I
believe
this
is
still
on,
holds
that
correct,
Ted,
yes,
okay
and
so
there's
one
announcement
that
Patty
asked
me
to
provide.
She
said
we
are
very
close
to
finalizing
all
the
brand
deliverables
for
antelope.
A
word
will
work
to
close
out
and
we
will
publish
the
guidelines
to
the
website.
She
did
not
include
a
specific
date,
but
you
know
other
than
very
close.