►
Description
Matthew Darwin of EOS Nation drops in on the March 2nd, EOS Fireside Chat, and discusses his experience being part of API+ while providing a great overview of the specific proposals that emerged from that working group. Matthew also discusses what actions the EOS community can take based on these proposals, what should be our priorities, and some other critical details to keep in mind as we advance API services on EOS.
Everything EOS is the official media channel of the EOS Network Foundation (ENF). 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://eosn.foundation
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosn.foundation
#EOS #EOSIO #ENF
A
Api
plus
started
like
six
months
ago.
We
started
talking
about
this
project.
A
lot
of
the
early
days
were
just
you
know,
coming
together
as
a
team,
I
think
one
of
the
interesting
things
is
es
nation,
grey,
mass
esrio,
we've
all
been
around
for
a
long
time,
but
we
never
really
collaborated
on
a
project
so
just
getting
to
know
each
other
and
how
to
work
together,
because
the
team
was
formed
without
a
you
know,
defined
leader
right.
So
it
was
a
collab
here,
three
groups
you
guys
get
together
figured
out.
A
We
came
up
with
eight
proposals,
which
some
of
them
have
dollar
amounts
attached
to
them
of
what
we
think
needs
for
that
thing,
and,
and
one
of
them
doesn't
have
a
dollar
amount
because
well,
quite
frankly,
there
was
so
many
options
and
a
way
to
do
it
that
we
wanted
more
community
feedback
before
picking
one
of
them
and
then
costing
that
out.
We
can
just
go
through
them
kind
of
high
level.
A
Apis
have
existed
in
eos
since
the
beginning,
they're
really
important,
but
nobody
was
really
defining
how
they
work
in
relation
to
how
applications
use
them,
so
features
would
come
out.
New
apis
would
get
written,
but
there
was
never
a
concentrated
design
process
to
get
developer
input
feedback
modified
the
apis
come
up
with
new
things,
whatever
you
know,
so
it
was
all
very
ad
hoc
lots
of
teams
did
their
own
thing.
We've
got
different
history
solutions
or
we
call
them
specialized
apis
in
the
paper.
A
What
we
need
going
forward
is
really
to
consolidate
all
of
that
work.
That's
going
on
and
actually
come
together
as
a
community
and
try
to
build
a
roadmap
going
forward.
So
we
can
stop
confusing
all
the
developers
about
which
solution
they
need
to
use
where
and
where
they
can
find
the
documentation
and
all
of
these
kinds
of
things.
The
first
proposal
is
really.
A
The
blue
paper
is
a
good
start,
but
we
need
this
going
forward
to
keep
talking
and
you
know,
build
new
community
around
designing
apis
figure
out
what
those
apis
need
to
look
like,
and
that's
that's
really
the
proposal,
one.
The
second
one
is
a
proposal.
That's
already
been
funded,
which
is
awesome
based
on
our
conversation
with
a
bunch
of
developers
and
users.
Add
some
new
features
to
the
core
software
that
will
make
their
lives
easier.
A
One
of
the
things,
for
example,
if
you
use
anchor
is
it
will
try
to
estimate
the
cost
of
your
transaction,
and
then
you
know,
there's
a
feature
that
will
fuel
will
cover
the
cost,
depending
on
the
current
situation,
but
there
is
no
standard
api
to
come
up
with
the
cost
of
a
transaction.
Well,
maybe
we
should
just
have
one
isn't
that
great
now
anybody
can
use
it
defuse
has
a
feature
to
allow
an
application
developer
to
retry
a
transaction.
A
Here,
I'm
going
to
submit
a
transaction,
keep
retrying
it
until
certain
conditions
are
met
and
then
give
me
the
successful
trace
of
that
transaction
or
give
up.
That's
not
a
standard
feature
in
node
us.
Let's
add
that.
So
these
are
kind
of
examples
of
features
that
that
certain
teams
have
in
their
solutions.
That
would
be
very
useful
for
multiple
developers.
So
let's
put
them
in
the
standard
software
and
make
them
available
to
everyone.
The
next
proposal
is,
let's
support
the
existing
operators.
A
The
first
proposal
is:
let's
design
new
apis
that
are
well
supported
and
community
led
and
there's
a
nice
collaboration,
but
until
we
get
to
a
point
where
those
kind
of
apis
fully
exist
and
we
need
to
support
the
existing
ones,
we've
got
light
api.
We
have
defuse
fire
hose
hyperion
and
robo.
Robo
is
also
known
as
the
grey
mass
api.
All
of
these
solutions
exist.
They
all
have
slightly
different
features.
We
kind
of
need
to
make
sure
that
they
stay
online
while
new
apis
are
built
and
new
features
are
delivered
related
to
that.
A
There's
two
ideas
around:
how
do
we
incentivize
or
create
robust
apis
that
the
developers
can
rely
on
so
up
until
now,
everything's
relied
on
block
producers
through
their
block
rewards,
we'll
provide
some
apis
or
maybe
there's
some
paid
solutions,
but
you
know:
should
the
network
as
a
whole
provide
a
centralized
api
solution
that
says:
okay,
here's
a
standard
thing
you
can
go
to
this
website.
It's
all
well
documented!
You
can
click
on
here
you
can
pay
for
the
access
that
you
need.
A
Maybe
that's
a
thing
or
maybe
we
should
come
up
with
a
here's,
an
incentive
way,
hey
api
providers
that
are
all
distributed
all
over
with,
like
the
current
block
producers,
but
there's
a
way
to
pay
them.
So
there's
a
wide
number
of
options
between
those
two
things
and
that's
kind
of
where
I
said
the
funding
is
a
question
mark,
because
we
really
want
to
understand
from
the
community
where
on
the
chain
which
or
the
the
continuum
of
different
options,
do
people
want
to
see
and
then
the
last
two
proposals
are
around
supporting
blockchain
standards.
A
A
I
think
one
of
the
things
that's
really
important,
even
if
you
don't
have
detailed
feedback
on
any
one
proposal,
is
to
think
about
which
thing
is
more
important
than
one
other
thing
or
has
higher
priority,
because
if
we
look
at
api
plus
audit
plus
core
plus
and
the
forthcoming
wallet
plus
there's
a
lot
of
different
projects
here
and
it's
like
impossible
to
do
all
of
them
at
once,
we
just
don't
have
enough
people.
What's
the
most
important
thing
out
of
api
plus
that
you
think
or
what's
the
one?
A
Definitely
don't
do
this
right
so
definitely
do
or
definitely
don't
do
you
know
some
sort
of
rank
priority
is
definitely
helpful.
Even
if
you
don't
have
detailed
feedback
on
the
specific
proposals.
So
yeah
we've
got
four
solutions.
The
idea
going
forward
is
we
should
reduce
the
number
of
these
solutions
or
reduce
the
extra
features
that
are
in
some
of
the
solutions
so
that
we
reduce
the
cost
right
now.
Maintaining
four
solutions
is
a
high
cost.
If
we
only
had
one,
it
would
be
a
lower
cost.
We
can't
go
from
four
to
one
overnight.
A
We
need
the
architecture
and
standards
research
to
figure
out.
How
do
we
evolve
the
existing
four
solutions
in
a
way
that
gets
us
to
having
less?
We
need
to
reduce
the
cost
of
maintaining
this.
It's
just
cost
for
the
maintenance
and
cost
for
the
developer.
Confusion,
because
there's
multiple
different
solutions,
I'm
most
excited
to
look
at
the
supporting
existing
blockchain
standards.
So
that's
like
rosetta
and
the
graph
looking
outside
the
es
or
the
esio
bubble
and
thinking
in
our
world.