►
Description
n this engaging team meeting, the coalition delves into the status and prospects of the Antelope project, discussing potential obstacles and strategies for the website redesign. The dynamics within the go-to-market team are explored, considering potential roles and responsibilities. The discussion also emphasizes the need for regular updates from team leads to streamline project management. Tune in for an insightful glimpse into the coalition's collaborative efforts and the mechanisms behind their project planning.
00:00:00 - Intro
00:01:27 - Discussing Data Visualizations
00:02:55 - New Product Ideas and Challenges
00:04:23 - Discussing Explorer Questions and App Interface
00:08:19 - Comments on Data Exploration and Analysis
00:09:47 - Data Implementation
00:11:15 - OpenAI's Technology and Market Strategies
00:12:43 - Status of the Antelope Project
00:18:15 - Wrapping Up
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
could
give
a
pretty
quick
update
and
and
mention
just
some
of
the
things
we've
discovered
or
what
we've
kind
of
engaged
in
so
far.
Most
of
most
of
what
we've
done
so
far
is
simple
fact:
finding
trying
to
figure
out
where
exactly
the
ram
that
is
being
utilized
and
the
system
is
going,
we
are
analyzing,
both
the
es
mainnet
and
the
and
the
wax
Network
just
to
kind
of
get
a
nicer
breadth
of
of
this
usage.
I.
B
So
the
next
next
I'll
be
getting
a
little
bit
more
fine-grained
information
about
that
and
then
also
trying
to
evaluate
each
specific
use
of
the
ram
as
to
whether
or
not
we
are
matching
the
capabilities
we
need
out
of
the
system
using
that
Ram
to
to
what
the
the
data
structure
that
we're
using
is
offering
to
see
if
there's
any
low
hanging
fruit.
For
that,
but
yeah,
that's,
that's
kind
of
where
we're
at
things
are
moving
along.
C
B
Of
it
is
yes,
I,
don't
think
it's
gonna
I,
don't
think.
There's
gonna
be
a
an
operational
so
to
speak.
Cost
to
this
so
like
I'm,
not
expecting
at
this
point
with
what
we've
seen
so
far
to
see
a
dramatic
increase
in
the
CPU
cost,
for
instance,
in
order
to
support
the
same
load
on
the
Chain.
So
it
might
be
a
situation
where
we're
just
kind
of
the
low
hanging
fruit
gives
us
some
pretty
good
wins
and
we
don't
have
to
make
calculated
trades
based
on
it.
B
C
A
There
are
some
scattered
requirements
defined
on
that,
but
I
don't
really
have
a
solid
update
to
give.
Today
we
did
have
a
lot
of
the
release
work
finish
up
over
the
past
month,
so
we
are
starting
to
move
ahead
in
other
initiatives
later
this
week
or
actually
no
excuse
me
mid
next
week.
Enf
will
be
publishing
our
Public
Health
Report,
and
so
there
should
be
a
more
detailed
update
on
just
the
various
Project
work.
That's
going
on
at
that
point
all
right!
A
E
My
I
guess,
like
understanding
the
previous
PR
that
that
that
was
proposed
was
not
really
at
the
pr
in
my
in
my
in
my
in
my
book.
If
there
was
a
basically
a
half
a
half-built
feature
that
was
not
gonna
Google
that
should
not
be
merged
in
the
code.
It
was
basically
like
another.
Let's
say
like
a
work
in
progress
that
was
not
internally
consistent
and
complete,
so
so
I
was
not
gonna
approve
that
one
and
I
don't
think
that
changed
at
least
not
my
knowledge.
A
E
A
All
right
next
item-
antler
CDT:
this
has
had
multiple
release
candidates
at
this
point,
I
believe
in
Bart.
It
would
be
great
if
you
could
confirm
this,
but
I
believe
that
the
final
candidate
was
like
at
this
point
is
out
now
and
there's
been
no
questions
or
additional
feedback
on
the
most
recent
version.
Is
that
correct.
A
A
E
Yes,
right
now,
there's
not
much
to
report
because
we're
still
in
the
face
of
reviewing
the
the
work
that
has
already
been
done
so
and
the
NF
has
been-
has
been
harder
to
work
on
that
one.
There's
there's
like
little
progress
that
I
can
report.
Is
that
anything
that
the
that
the
engineers
have
found
so
far
has
been
corrected
promptly.
E
They
just
they
just
didn't,
have
the
time
to
complete
these
things,
these
reviews,
yet
to
the
reviewing
committee,
so
there's
a
another
other
engineered.
It
has
now
been
tasked
to
review
these
essentially
the
work
and
is
one
of
the
guys
that
actually
did
some
work
on
the
Hot
Stuff
protocol.
So
that's
quite
quite
quite
nice
to
have
someone
like
him
participate,
but
I'm
still
waiting,
also
to
hear
from
the
enf
engineering
regarding
the
status
of
these
updates.
E
E
The
entire
list
of
a
PR
student
review,
there's
quite
a
few
there's
a
there's
there's
the
first
one,
which
is
the
VLS
signatures
and
the
biblical
Primitives
and
then
there's
the
hot
stuff
for
and
the
unit
tests
as
well
and
as
well
as
the
map
proofs
and
the
the
pseudocode
that
we
produced.
So
all
of
these.
Unfortunately,
these
are
all
quite
complex
and
I
will
require
quite
a
bit
of
work
from
the
Engineers.
E
A
All
right
right
now,
SDK
is
closing
in
on
Milestone
six.
That
would
be
the
contract
kit
and
the
account
kit
of.
In
fact
it
might
it's
theoretically
going
to
be
ready
for
acceptance
tomorrow,
get
give
or
take
a
day.
Also,
there
has
been
a
delay
on
Milestone
five,
simply
because
some
of
the
sequencing
of
the
work
was
refactored,
but
that
is
also
closing
in
on
completion.
So
we're
we're
not
there
quite
yet,
but
both
and
Milestone
five
by
the
way
is
the
session
kit,
Integrations
and
localization.
F
Yeah,
just
so
that
file's
been
ongoing
now
for
quite
some
time,
and
at
this
stage
it's
gonna
hold
indefinitely.
Unless
somebody
else
can
pick
it
up,
we
just
don't
have
the
resources
to
continue
this
file.
It's
been
extremely
slow
in
general,
and
the
person
that
was
in
charge
of
this
is
now
assigned
to
to
completely
different
work.
So
if
somebody
else
in
the
Coalition
wants
to
pick
it
up,
we
can
likely
hand
that
off
otherwise
it's
it's
basically
on
hold.
E
F
I
don't
know,
maybe
Bart
can
comment
a
little
bit
more
or
we
can
talk
about
it
afterwards.
I
know
a
lot
of
it
was
the
coordination
with
The
Ledger
team
I.
Think
it
needed
I
think
we
needed
to
rewrite
some
stuff
as
well
to
do
the
coding
to
split
the
apps,
make
sure
that
there
are
multiple
heads
so
I
think
there
is
actual
technical
work
involved.
D
Yeah,
the
the
product
stuff
I,
think
was
being
managed
by
Adam
and
and
Brian
Hazard,
but
splitting
the
software
so
that
it's
got
a
head
and
a
base.
And
then
we
had
the
five
different
heads,
including
a
special
Antelope
head,
that
all
worked
against
that
same
base
so
that
it
took
up
less
space
on
The
Ledger.
That
work
did
not
get
done.
G
F
Another
one's
good
with
that,
as
I
said,
my
only
concerns
were
that,
if
we're
setting
up
the
expectations
that
we're
going
to
be
funding
this,
as
you
mentioned
and
and
as
adamant
mentioned,
he
was
gonna
apply
for
the
grant
framework,
if
I'm
not
mistaken,
that
that
actual
Grant
application
came
through
and
I
believe
that
it
did
not
pass
I'm,
not
sure
if
that's
been
communicated
yet
because
I
think
the
last
vote
came
in
this
morning.
But
that
was
my
only
concern
really.
G
E
G
H
G
Yeah
and
the
the
cost
to
actually
operate
it.
Given
all
four
of
our
networks,
have
you
know
public
Hyperion
endpoints,
which
is
what
the
whole
thing's
built
around
for
history?
Is
you
know
the
deployment
link
I've
shared
has
been
up
for
a
while.
It
works
fine
right,
nobody
had
to
pay
anything
for
that,
it's
free,
CDN
based
hosting
and
it
just
hits
Hyperion,
so
it's
kind
of
a
no-brainer
to
actually
just
turn
it
on
and
then
from
there.
G
You
know,
features
specific
to
each
Network
and
new
features
that
we
would
all
benefit
from.
You
know
will
happen
as
they
can.
You
know,
organically
or
through
funding
that
accelerates
it
and
I
know,
there's
some
non-coalition
chains
that
maybe
are
interested
too.
That
may
you
know
want
to
fund
some
features
as
well.
So
you
know
it's
I,
think
it's
best
just
to
get
it
out
there
get
more
people
using
it
and
see,
see
what
happens.
There's
not
a
real
cost.
To
that.
H
G
G
Yep
just
domain
and
because
it
makes
sense
so
then
we
will
use
that
the
to
close
on
it.
The
only
other
thing
was
like
I,
think
Lucas,
you
mentioned
I
think
you
mentioned
the
Explorer
and
something
about
go
to
market.
If
you
do
want
us
to
coordinate
anything
about
turning
that
on,
it's
obviously
not
going
to
happen.
You
know
tomorrow
and
we
can
coordinate
when
it's
ready
to
actually
be
flipped
on.
If
there's
anything
that
we
want
to
coordinate.