►
Description
This week, the Antelope Coalition discusses the progress made with P2P Peer discovery, Coalition top-ups, IBC, Wallet SDK, Ledger app, and more!
00:00:00 Intro
00:00:03 This week's topics and updates
00:00:23 Coalition top-up to fund RFPs
00:10:50 P2P Peer discovery
00:11:57 IBC update
00:29:51 Wallet SDK
00:33:33 Antler CDT
00:34:32 Ledger app support
00:39:35 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
I'd
be
happy
to
thanks.
We
started
out
having
what
what
seemed
like
it
might
be
a
simple
conversation
about
about
how
to
divide
the
cost
sharing
in
the
future,
the
problem
being
that
we're
sharing
unevenly
in
the
costs,
and
there
are
good
reasons
for
that.
But
that
may
not
be
a
long-term
solution
for
the
the
health
of
the
of
the
organization.
B
You
know
that
they
need
to
leave,
and
so
that
you
know
the
larger
valuation
change
which
currently
just
means
EOS
is
just
paying
for
a
vast
majority
of
what
we're
doing.
So.
It
also
feels
like
it's
getting
enough
from
the
other
partners
in
terms
of
pay
and
other
contributions
for
it
to
be
worthwhile
for
them
to.
B
You
know
keep
putting
us
in
in
in
a
position
of
of
this
decision
making
with
them,
even
though
they're
paying
so
much
so
it
seems
like
a
simple
thing
and
but
I
think
going
forward.
My
concern
is
that
that
the
equities
or
perceived
inequities,
either
by
us
or
by
our
constituents
who
ultimately
Drive
our
decisions,
will
will
grow
and
I
want
to
head
that
out.
So
we
talked
about
some
things.
B
It
turned
out
that
it
is
actually
a
very
complex
topic
and
we're
going
to
be
there's
no
way
to
reach
a
decision,
because
at
this
in
such
a
short
amount
of
time
and
we're
going
to
be
going
into
ongoing
meetings
about
it.
The
good
news
is:
there's
no
need
to
immediately
come
up
with
any
answer,
because
we're
trying
to
head
off
problems
in
the
future
but
I
think
there's
a
there's,
a
general
recognition
that
every
side
has
concerns
and
points
at
which
you
know
it
won't
be.
B
B
It
Rose
was
three
percent.
Last
year's
five
five
percent
this
year.
The
other
is
is
the
other
approach,
is
a
fixed
percentage
method
where
we
would,
we
would
say:
okay,
here's
the
economic
part
of
it,
we're
sharing
economically
and
part
of
it.
We're
just
sharing
splitting
down
the
middle
four
ways
or
however
many
ways
and
at
the
in
the
beginning
that
part,
that's
fixed
stays
small,
but
it
grows
over
time
to
potentially
being
you
know,
half
or
or
all
of
the
contribution
and
there's
lots
of
lots
of
thoughts
on
every
side.
B
A
I
think
my
main
question
is:
what
are
we
deciding?
Is
the
next
steps
it
like,
because
this
doesn't
seem
like
a
weekly
agenda
item
anymore?
It
seems
like
there
might
be
a
working
group
coming
down
the
pipe,
but
I.
Don't
know
that
that's
the
top
of
priority
at
this
point.
Do
we
just
put
this
in
the
backlog
and
maybe
in
a
couple
months
we
get
a
little
blog
find
it
like.
How
do
we
know
Ford.
B
So
what
it
was,
what
I
believe
we
all
discussed
and
and
agreed
to
was
I
think
we
all
recognize
that
this
is
a
real
issue
that
we
will
have
to
find
a
solution
for
and
the
sooner
the
better.
However,
it's
not
critical,
but
it
you
know
in
its
timing
we
can
we
could.
We
could
put
it
off
for
as
long
as
we
wanted
to
until
it
reared
its
head
as
a
problem.
B
What
we're
trying
to
do
is
stay
ahead
of
it,
because
in
a
way
it
would
be,
it
could
potentially
be
an
existential
issue
for
for
the
longevity
of
the
of
the
Coalition,
and
so
we
want
to
work
on
it
on
a
regular
basis.
I
don't
know
if
that's
weak,
I
think
that's,
maybe
monthly
talks
either
Lucas
somebody
can,
or
somebody
can
help
me
remember
exactly
what
we
decided
there,
but
it's
it's
regular,
ongoing
discussions,
not
anticipating.
B
We
probably
won't
have
a
a
proposed
solution
right
away
and
we
may
have
to
bring
in
community
feedback
and
things
like
that
for
this,
but
but
not,
but
we
are
not
going
to
backlog
it
and,
and
then
just
and
do
nothing
and
come
to
it
later
and
say.
Is
this
a
time
we
need
to
make
ongoing
efforts
towards
us.
C
Yeah,
we
discussed
something
a
monthly
retrospective
between
the
Coalition
members.
To
have
a
discussion
about
are,
we
you
know
are
we
doing
enough
is
are
the
expectations
that
are
not
being
met
so
that
you
know
from
watch
perspective.
I
would
like
to
know
you
know.
Are
we
contributing
enough?
Are
the
areas
where
we
need
to
show
up?
Do
we
need
to
stuff
more?
C
You
know,
members
on
our
side
to
to
contribute
here
and
then
having
that
monthly
feedback
would
be
very,
very
good
for
us,
because
we
dub,
we
definitely
don't
want
to
get
into
a
place
where
you
know
there
are
resentments
that
are
not
vocalized
so
having
a
monthly
retrospective
would
be
very
helpful,
at
least
for
me
for
sure
and
I'm
sure.
Other
changes
would
benefit
from
that
process.
Yeah.
B
Thanks
thanks
for
reminding
me,
it
was
monthly
and,
in
addition
to
ongoing
talks
about
how
to
make
these
and
that'll
be
ongoing
right,
even
once
we
solve
this
problem,
so
part
of
that
will
be
part
of
the
time
will
be
used
to
address
this
problem
until
we
find
a
solution,
but
on
an
ongoing
basis.
We
just
want
to
have
a
way
like
Lucas
says,
to
make
sure
that
things-
don't
don't
you
know,
are
don't
go
unvoiced,
for
example,
up
the
positive
or
the
better
or
the
or
the
negative.
B
B
A
C
I
can
I
can
wrestling
run
these
monthly
retrospectives?
That's
not
that's,
not
a
problem.
I
can
I
can
schedule
it
out.
It's
just
or
maybe
you
guys
can
own
the
the
actual
meeting,
but
I
can
actually
run
it
Rhonda
retrospective
process
and
then
put
together
a
summary
and
then
send
it
out
to
everyone
in
the
telegram
China.
D
C
Let's
pay
attention,
I
mean,
let's,
let's
figure
out
when
we're
gonna,
do
it
so
it's
beginning
of
March.
So
this
is
a
good
time
to
actually,
maybe
maybe
we
could
use
either
our
Monday
call
to
to
do
a
15-minute
retrospective
at
the
very
beginning
or
towards
the
end
of
that
call
I'm,
not
sure
what
how
packed
the
agenda
is.
I,
I,
don't
know
if
we
need
an
yet
another
meeting
today.
C
B
You
sounds
great:
if
we
have
anything
pressing,
we
can,
we
can
punch
it
a
week
or
or
if
it's
really
pressing,
we
can.
We
can
add
an
additional
meeting,
but
I
have
a
feeling
that
most
you
know,
we've
gotten
through
that.
A
lot
of
that
time,
where
everything
is
is
go
go
go
and
it
may
be
a
little
bit
less
of
a
weekly
list
on
discussing
proposals
and
things
for
a
while.
So
it
seems
like
we
can
spare
one
week
a
month.
A
All
right,
the
next
two
items
just
worth
mentioning
about
it.
The
progress
for
the
requirements
has
not
move
forward,
as
previously
explained
we
are,
we
have
the
upcoming
release,
it
will
likely
be
another
week
or
so
before
that
unwinds
and
we
can
jump
more
into
those
items
all
right.
The
remainder
items
are
all
status
updates.
I
figured.
This
would
probably
be
an
easier
way
of
doing
that
to
just
staring
at
the
found
one
board.
A
So
we'll
start
with
peer-to-peer
discovery.
The
project
has
been
kicked
off.
This
is
a
tentative
timeline.
You
can
see
some
of
the
Milestone
dates,
the
the
first
one,
with
the
design
phase
being
done
on
March
27th
I
do
know
that
the
project
manager
is
pushing
into
the
team
as
they're
kind
of
doing
initial
design
to
get
better
Milestone
deliverables.
But
you
know
we
don't
just
want
to
say,
hey
development's
done.
We
want
specific,
workable
software
at
different
phases
or
at
the
end
of
the
design
like
what
specific
Architectural
Components
are
designed.
A
A
A
A
You
can
see
a
lot
of
the
later
items
that
were
scheduled
towards
the
end
of
the
year
for
completion
down
here,
the
timeline
you
can
see
they're,
they're
well
underway
and
as
Guillaume
as
mentioned
in
previous
weeks,
that
some
of
them
are
probably
going
to
drop
much
much
sooner,
which
and
we
talked
about
nobody-
cares
if
deliverables
come
early.
We
only
want
to
know
if
they're
late
Guillen
do
you
want
to
add
anything
to
that.
F
F
If
we
wanted
to
use
the
antelope
IBC
domain
until
maybe
see
the
win
until
ibc.com
I
think
domain.
For
that,
we
can
definitely
do
that
as
well,
and
my
question
here
is
as
part
of
that
Milestone.
We
also
discussed
having
a
an
alert
mechanism
if
there
is
any
discrepancy
between,
say
the
amount
of
tokens
that
have
been
locked
on
a
given
Chain
versus
the
amount
of
tokens
that
have
been
minted
on
the
corresponding
chain.
So
that
is
essentially
what
I'd
like
to
verify
with.
F
With
all
of
you
see
what
would
be
an
appropriate
channel
to
issue
such
an
alert
if
there
was
a
problem,
and
these
these
would
be
like
like
major
problems.
That
would
only
occur
if
there
was
probably
like
a
hack
or
if
there
was
like
a
governance.
Failure,
as
we've
discussed,
like
on
any
of
the
chains
like
BP,
is
essentially
like
hijacking
the
contract
and
doing
something
they're
not
supposed
to
so
so.
F
Yeah
I
mean
what
would
be
like
a
proper
channel
to
essentially
like
communicate
that
that
that
problem
to
raise
the
alarm,
would
you
guys
be
okay
with
the
telegram
bot
or
would
you
prefer
I,
don't
know
like
an
email
list,
or
just
just
figure?
I
had
asked
what
what
people
were
still
comfortable
with.
F
I
would
probably
suggest
a
telegram,
but
but
that
would
probably
be
the
most
I
guess,
like
the
better
way
to
reach
the
the
people,
because,
essentially,
what
happens?
If
there's
a
hack
like
this,
we
would
need
to
reach
BPS
on
the
the
chases
that
have
been
affected
and
probably
probably
like
having
a
telegram
bot
in
a
channel
where
there's
enough
people
that
can
relate
a
message
to
to
BPS
would
be
would
be
appropriate
so
that
this
is
where
it
would
suggests.
Unless,
and
one
has
a
better
idea.
G
F
Well,
I
mean
what
I
would
suggest
is.
Maybe
we
create
a
yet
another
telegram,
group
or
channel
in
this
case.
Probably
that
would
have
the
butt
and
the
butt
would
essentially
only
alert
that
there's
if
there's
an
issue
and
then
Every
Chain
can
basically
add
people
as
as
required
to
be
yeah
to
have
that
that
channel,
monitored
and
then
and
then
yeah
they
would.
They
would
leave
it
with
notifications
on
anyway.
F
All
right,
so,
if,
if
nobody
else,
if
nobody
objects,
then
we'll
do
that,
so
that's
for
I,
guess
our
Milestone
number
five
monitoring
analysis
tool
tools
and
then
we
will
also
deploy
it,
like
I,
said
to
a
sub
domain
on
ux
network.io.
If,
if
you
guys
want,
we
can
also
can
also
discuss
having
having
the
the
envelope
IBC
domain
having
hosting
there
and
basically
deploying
some
of
the
of
these
things.
F
C
I
suggest
we,
we
should
all
run
this
API,
so
each
each
chain
that
is
actually
participating
in
IBC.
There
should
be
this
endpoint
under
so
for
for
us
for
us,
we
would
expose
it
under.
You
know
something
like
IVC.
The
wax
dot
or
IBC
right,
analytics,
dot,
wax
dot.
Io
would
be
good
to
stand
standardized,
maybe
even
on
like
the
supplemented.
This
would
be
exposed
and
then
and
then
we'll
run.
F
Yeah
perfect
so
anyway,
I'll
I'll,
make
sure,
like
I,
think
I
think
we've
already
open
sourced
it,
but
I'll
I'll
double
check
and
I'll
I'll
ping.
The
group
in
the
telegram
group,
with
the
GitHub
repo
for
these
tools,
so
anyone
can
censor
like
deploy
it
and
host
it
and
make
it
available
under
their
their
domain.
F
F
When
I
wrote
that
Milestone
I
should
have
been
a
bit
more
explicit,
it's
a
bit
vague
as
you
can,
as
you
can
imagine,
so,
I
was
wondering
how
I
mean
if
we
could,
if
you
could
gonna,
give
it
some
sort
of
I
guess
like
a
a
more
precise
definition
at
at
this
point,
we
support
fire
hose
and
we
support
stake
history,
plugin,
there's
I
I,
believe
hikarian.
Chronicles
are
also
essentially
a
build
with
support.
F
I
mean
essentially
based
on
State,
history,
plugin
and
I.
Think
the
only
one
the
only
other
solution
is
the
resolution
I'm
aware
of
that
is
widely
used
is
is
robot
for
from
from
Gray
Mass
I
think
Aaron
at
any
point.
Basically,
we
can
have
that
discussion
if
you
need
anything
from
our
end,
we're
happy
to
to
help
I
think
you
mentioned
Trace
API,
so
we
can
look
at
having
a
trace
API
adjuster
for
the
data
there
and
then.
H
F
Yeah
essentially
like
I
I
I'd,
like
to
figure
out
like
how
would
we
consider
that
Milestone,
complete
and
like
who
would
be
reviewing
that
it's
a
bit.
It's
a
bit
vague,
so
I'm,
not
I'm,
not
not
necessarily
asking
today
for
a
for
foreclosure
on
that
one,
but
yeah.
It's
just
something
that
I'd
like
to
to
make
sure
that
we
yeah
we
Define
a
bit
a
bit
more
so
that
we
can
can.
We
can
know
basically,
what's
expected
of
us
to
complete
that
now
so
I
don't
know.
F
A
E
F
We
essentially
have
the
aggregate
signatures.
That's
pretty
much
ready
for
review.
I,
think
I
think
we're
yeah
like
we're.
It's.
We
haven't
submitted
it
yet
for
review
if
it
was
not
ready
for
Tuesday
call
but
I
believe
it
is
now
or
it
it
will
be
momentarily.
So
that's
that's
essentially
now
ready
for
for
the
enf
engineers
to
to
look
into
for
the
core
instead
Fidelity
features.
F
Also
the
31st
March
is
still
the
the
the
the
date
we
have
we're
we're
aiming
for
for
that
delivery
and
then
the
rest
is
also
is
also
pretty
much
on
target,
as
as
a
kind
of
anecdote,
I've
got
I've
got
it
running
now
for
about
like
48
Hours
on
my
own
private
test
net,
without
any
issues.
So
far,
so
that's
that's
a
good
sign
keeping
my
finger
crossed
but
like
the
the
Prototype.
F
But
it's
there
so
like
that's
that
that's
working
the
Hot
Stuff
algorithm
has
been
implemented,
and
we
we've
had
like
several
discussion
with
the
Edith
Engineers
as
well,
so
like
We've
refined
that
algorithm
quite
extensively
already
and
it's
it's.
It's
actually
very.
Very
cool
I
think
yeah
I'm
very
happy
with
the
way
that
the
things
are
are
moving.
So
so
yeah.
G
F
G
G
It
is
so
we
do
have
a
new
I
guess,
recent
employee
that
has
a
PHD
in
cryptography,
but
what
I
didn't
know
was
that
he
actually
worked
on
the
Hot
Stuff
algorithm
back
in
2018
no
way
is
quite
knowledgeable
about
and
so
I
would.
That
was
news
to
me.
I
did
not
know
this,
so
I,
don't
know
if
either
of
the
barbs
or
I
don't
know
Jeff
or
Tad.
That
would
somehow
Loop
Doctor
Who
in
this
if
eat
it.
But
I
would
imagine
that
over
time.
G
G
But,
yes,
he
has
been
in
the
blockchain
space
now
for
I,
guess,
five
years
or
so
and
yeah
as
as
it
turns
out,
he's
also
somewhat
of
an
I
know.
I,
don't
know
if
the
expert's
the
right
thing,
but
he
definitely
has
an
experience
in
hot
stuff,
as
that
was
the
first
project
that
he
tried
to
work
with
Slash
Implement,
slash,
yeah,
so
anyways
well,.
B
F
And
so
so
for
sure
100,
if
you
I
mean
like
I,
don't
know
a
Bart
or
anyone
else.
If
she
want
to
put
me
in
touch
I'd,
be
happy
to
gonna.
Just
just
give
him
a
few,
a
few
pointers
where
we're
at
then
sure
to
get
that
records
and
invite
on
the
Tuesday
calls
and
all
of
that
I
don't
want
to
also
like
step
on
any
one,
toes
I'm
sure
I'm
assuming
you've,
you've
hired
him
for.
I
H
F
J
Awesome
we
are
probably
going
to
have
a
0.3
release
tomorrow,
which
features
the
first
implementation
of
the
ual
replacement.
Essentially
it's
the
user
interface
that
web
apps
will
be
able
to
start
implementing.
It
is
not
going
to
be
the
final
design,
nor
is
it
going
to
be
incredibly
optimized,
but
this
will
be
the
first
opportunity
that
other
applications
will
be
able
to
really
Implement
and
try
this
out
we're
hoping
to
get
a
blog
post
out
shortly
thereafter.
That's
my
attention's
gone
to
now.
J
J
So
now
the
the
thing
that
pops
up
in
your
web
browser
that
you
use
to
log
in
or
sign
transactions
will
be
localized
to
three
set
languages
to
begin
with,
and
then
with
the
possibility
of
expanding
that
to
whatever
the
user
interface
wants
to
offer.
For
that,
we
have
a
document
that
we
need
to
complete
for
the
user
interface
specification
and
other
than
that
that
will
bring
Milestone
4
over
there
in
the
sidebar
to
a
good
review
Point.
J
As
with
everything
else,
we're
doing,
we
don't
want
to
say
everything's
done,
because
we
do
really
want
feedback
from
application
developers
on
how
to
improve
this,
but
in
terms
of
how
the
Milestone
is
represented,
that
one
will
be
probably
submitted
to
review
and
the
not
too
distant
future,
so
that
will
be
moving
on
to
the
next
milestones
and
keep
chugging
along
on
the
project.
So
it's
really
coming
together.
A
G
I
just
want
to
add
that
this
is
one
of
the
most
exciting
things
as
well,
because
in
terms
of
usability
or
I
guess
front
facing
user
experience.
This
component
is
is
quite
massive,
long-awaited
war
and
I.
Just
can't
wait
to
see
you
know
as
this
progresses
along,
because
this
is
going
to
change
the
experience
for
a
lot
of
people,
whether
they
be
developers
end
users
whatever
it
may
be.
This
is
this
is
a
huge,
huge,
huge
win
for
the
coalition,
such
as
kudos
to
It's,
a
Great
Mouse
Aaron,
the
rest
of
the
day.
B
Really
Andrew
I
mean
we
all
you.
You
started
this
effort
to
get
us
all
together
and
I.
Think
this
is
this.
These
types
of
things
are
the
the
really
strong
culmination
of
of
showing
the
value
of
that.
So
thank
you
and
I
think
there's
a
lot
I,
think
and
and
Aaron,
and
your
team
and
I
think
there's
a
lot
of
really
exciting
things
that
are
happening
right
now
because
of
this
Coalition.
That's
why
I
want
to
make
sure
that
it,
you
know
long
endures,
but
yeah
thanks
for
your
leadership
on
this
too.
If.
A
All
right
next
project
CDT,
so
the
quick
update
the
code
is
the
second
PR
on
list
is
under
review,
going
through
yet
another
feedback
round,
while
the
schedule
is
slightly
behind
again
I.
This
is
not
at
this
point,
a
real
concern
for
us
missing
our
March
release,
and
so
you
know
once
the
code
review
peer
review
comes
back.
You
know.
A
A
All
right
so
the
last
status
review.
It
was
a
coalition
LED
here
at
so
this
is
a
schedule
that
Adam
has
put
together.
It's
a
tentative
scheduled
I'm
gonna
emphasize
that
we
do
want
to
send
this
out
to
the
Coalition
and
have
each
of
you
essentially
accept
the
dates
or,
if
not,
you
know,
suggest
new
ones,
and
the
main
reason
is
because
there's
a
lot
of
components
in
this
that
we're
going
to
ask
for
some
back
and
forth
and
so
to
make
sure
the
project
moves
along.
I
Okay,
because
there's
one
thing:
I,
don't
maybe
I'm
wrong,
and
maybe
you
guys
have
made
a
ton
of
progress
here.
Did
we
get
past
the
point
of
it?
Having
a
you
know,
a
core
app
and
then
the
five
thin
head
apps
as
Eric
gotten
that
far
in
research
of
discussion
or
conversations
with
Thomas
Julian?
Or
is
that
not
part
of
this?
This
is
assuming
that
they're
all
just
big
fat
apps
and
to
Aaron's
point
you
maybe
can
get
two
onto
a
ledger.
I
Even
though
they'd
all
work
and
I
know
we
still
I
still
have
an
outstanding
question.
I
was
just
noticed
that
ping
dot
Thomas
again
on
the
you
know
the
antelope
app,
which
again
I
have
some
search
questions
that
he
missed
for
you
know
how
we
can't
put
all
four
symbols
after
Antelope
and
out
of
search
work
when
it
comes
up
in
the
market,
Place
catalog,
that's
or
the
app
catalog,
whatever
they
call
it.
A
E
A
A
D
G
Update
I
have
spoken
to
a
few
of
them,
but
not
not
all
of
them.
It
is
on
the
agenda
Zach's,
not
here,
I,
believe
it
is
March
9th
we're
having
our
next
March,
9th
or
8th
we're
having
our
next
DP
call.
We
host
a
monthly
BP
call
with
top
30
BPS,
and
that
is
on
the
agenda,
so
I'll
be
able
to
get
back
to
you
with
maybe
more
feedback,
more
precise
feedback
after
that
date.
So
I
believe
this
is
next
next
Wednesday
night.