►
From YouTube: Nader Dabit (Edge & Node) - APIs and Indexing in Web3
Description
Nader walks you through Edge&Node's technical journey to build projects including The Graph – an indexing protocol for organizing blockchain data – to Everest, a universally shared projects registry.
B
Fantastic
yeah,
and
if
you
want
to
dive
into
anything
else,
you
know
infrastructure-related
nato
go
for
it.
I
know
I
know
you
probably
have
a
lot
to
say
so.
Yeah
I'll
give
you
the
stage.
B
Yeah,
let's
do
it,
let's
do
it?
Tell
us
yeah
tell
us
the
story.
Tell
us
what
you
know:
web3
infrastructure.
What
is
it.
A
A
I
was
looking
to
kind
of
apply
the
same
ideas
that
I
had
in
the
web,
two-space
or
quote-unquote
web
two-space
into
web3,
and
for
me
that
meant
I
wanted
to
build
out
an
application,
and
I
have
these
building
blocks
that
I'm
kind
of
used
to
using
to
kind
of
get
me
there
and
using
these
primitives.
I
can
build
out
95
of
the
applications
that
I
can
think
of
in
my
head
and
the
other
five
percent
are
typically
going
to
be
specific
to
that
app
to
that
app.
So
it
might
be
something
like.
A
Oh,
I
need
this
machine
learning
service
or
I
need
this,
this
messaging
service
or
I
need
this
notification
system
or
whatever,
but
the
basic
primitives
were
the
same.
You
need
a
database,
you
need
a
server,
you
need
a
file,
storage
layer.
You
need
a
front
end,
whether
it
be
a
web
or
a
mobile,
app
and
kind
of
that.
That
would
be
it.
A
So
that's
kind
of
the
way
I
usually
speak
to
it,
and
it
usually
is
you
know
easy
for
developers
to
kind
of
understand
when
you
kind
of
break
that
stack
apart
like
what
is
that
web
3
stack
and
that's
kind
of
been
what
I've
tried
to
focus
on
over
the
last
few
months
at
edge
of
node.
We
even
have
a
entire
team
of
researchers
of
when
I
say
the
entire
team.
A
It's
a
couple
of
people
that
spent
a
lot
of
the
last
year,
looking
at
all
the
different
protocols
that
were
out
there
and
trying
to
understand
where
they
fit
in
trying
to
understand
what
the
future
viability
of
that
protocol
is
like.
Is
that
a
team
going
to
be
around
a
year
from
now?
Is
this
something
that
they're
focused
on
building
and
they're
serious
about?
Or
is
this
something
that
they're
kind
of
just
playing
around
with
and
trying
to
kind
of
understand?
A
You
know
what
this
web
three
stack
looked
like,
so
I
wrote
a
blog
post
called
defining
the
web
three-step
he
kind
of
dives
into
this,
but
going
specifically
in
the
apis.
One
of
the
reasons
that
I
joined
the
graph
protocol
team,
which
is
kind
of
a
sister
protocol
of
edge
and
node,
is
that
they
kind
of
provided
a
core
piece
of
this
web
3
infrastructure,
which
is
the
api
layer,
because
when
I'm
coming
from
the
web
2
space,
I
have
a
server
and
on
that
server
I
can
talk
to
a
database.
A
I
can
do
things
like
filtering
and
sorting,
or
I
can
do-
data
plunging
essentially
kind
of
like
data
manipulation,
but
that
server
piece
is
kind
of
missing
from
the
web
3
layer,
because
we
are
interacting
with
blockchains
and
we're
supposed
to
trust
that
that
data
is
kind
of
the
data
that
is
there
and
when
you
have
a
centralized
layer,
you're
kind
of
like
missing
that
important
security
principle
that
you're
expecting
from
a
blockchain,
because
if
you're
reading
directly
from
the
chain,
then
you
can
expect
that
that
data
is
there.
A
But
if
you
have
someone,
that's
taking
all
that
data
centralizing
in
a
server
and
then
serving
up
in
an
api
request.
How
can
you
verify
that
data
so
kind
of
the
graph
protocol
offers
this
decentralized
indexing
inquiring
layer?
And
that's
one
of
the
reasons
why
I
joined
this
team
is
because
I
thought
that
it
kind
of
filled
this
very,
very
necessary
infrastructure
piece
for
most
developers,
kind
of
like
trying
to
build
out
web3
apps
and
that's
kind
of
what
I'll
probably
be
talking
about.
Mostly
today
like.
A
Why
can't
you
just
read
data
directly
from
the
chain?
Well,
you
can
read
certain
data,
so
you
can
say
okay,
I
want
to
get
data
from
this
smart
contract
at
this
point
in
time.
But
let's
say
you
want
to
do
the
type
of
query
that
you
would
need
for
almost
any
app
like
twitter,
for
example,
you
want
to
get
a
friends
list
or
you
want
to
get
a
filtered
search.
A
You
want
to
kind
of
do
some
type
of
filtering
or
sorting
or
data
relationships
like
none
of
that
is
typically
able
to
be
done
directly
from
the
chain.
So
how
can
you
actually
do
that
and
that's
kind
of
the
answer
that
the
graph
protocol
is
there
to
kind
of
give
you
but
also
a
question
that
a
lot
of
developers,
I
think,
when
they're
coming
into
the
space?
B
Gotcha-
and
one
question
I
had
netter
is,
is
that
is
the
experience
they
would
find
with
something
like
the
graph
familiar
to
web
to
developers
coming
into
web3.
A
It
was
one
of
the
reasons
that
it
was
easy
for
me
to
kind
of
learn
it
because
I've
been
writing
graphql
at
aws
for
about
three
or
four
years,
but
I
would
say
it's
kind
of
not
the
main
way
that
developers
typically
interact
with
endpoints
there's
two
main
ways
that
developers,
I
would
say
in
the
web2
space
use
or
two
main
specifications.
A
One
is
just
a
typical
like
rest
api,
where
you
have
a
an
endpoint.
You
send
a
request
to
that
endpoint
using
like
a
git
or
a
post
request.
A
get
request
would
be
reading.
Data
post
requests
would
be
like
writing
data,
so
you
have
rest,
and
then
you
have
graphql
so
yeah.
So
graphql
is
fairly
well
adopted
at
this
point
and
then
the
other
language
you
would
use
is
assembly,
script
and
assembly.
Script
is
very
similar
to
something
like
typescript,
which
is
very,
very
widely
adopted.
At
this
point,.
B
Awesome
awesome
and
quick,
quick
question.
You
know
because
we're
on
this
topic
is
you
know
what
kind
of
things
have
you
seen
stem
out
of
of
of
the
graph
right
like
what
kind
of
success
or
projects
have
you
seen
using
the
graphql?
I
know
there
are
a
lot,
but
I'm
curious
to
hear
from
you.
You
know
how
have
you
seen
people
use
that
you
know
that
technology
in
a
way
that
was
maybe
surprising
to
you
or
have
you
seen?
People
really,
you
know,
react
to
it
and
say
wow.
B
You
know
this.
Is
you
know
this
is
something
I
can
use
every
day
right.
This
is
a
piece
of
the
infrastructure.
That's
been
missing,
I'm
kind
of
curious
about
those
stories.
A
Yeah
I
mean,
I
think,
that
most
developers,
when
they
start
diving
into
this
stack
and
they
start
building
something
for
themselves.
They
they
immediately
run
into
this
this.
This
problem,
like
how
can
I
actually
create
these
queries,
that
I
need
for
a
real,
real
world
application
like
like?
I
guess
once
you
get
past
hello
world,
you
run
into
this
this
problem
and
almost
immediately,
they
kind
of
start
looking
for
solutions
and,
typically
when
they
find
the
graph
they're
just
like
they're,
just
like
you
know,
sending
out
tweets
and
they're
like
oh
wow.
A
This
is
like
solving
my
problem
or
they
get
excited
and
they
just
kind
of
talk
about
it,
some
of
the
apps
that
are
using
it.
You
know
the
ones
that
are
coolest
to
me.
I'm
a
big
fan
of
some
of
these
nfc
marketplaces,
so
like
foundation,
is
a
really
cool
one.
That's
using
the
graph.
A
They
even
have
a
developer
portal
with
their
own
subgraph
that
anyone
can
use
anyone
can
like
fork
if
they
would
like
to
there's
a
lot
of
d5
protocols
like
like
unit
swap-
and
you
know,
ave
and
things
like
that
that
have
sub
graphs
there
are
metaverse
plays
like
the
decentraland
has
a
subgraph,
and
so
I
would
say
just
pretty
much
any
any
application
that
is
deployed
to
a
protocol,
that's
supported
by
the
graph,
can
be,
can
have
a
subgraph
or
an
api,
that's
built
using
the
graph.
A
B
Okay,
awesome,
awesome
and-
and
you
know
I
I
guess
I
have
a
kind
of
a
maybe
a
similar
question
that
I
asked
lily
and
you
you've
touched
on
this
a
little
bit,
but
it's
you
know
what
kind
of
challenges
have
you
seen
up
to
developers
moving
into
this
space
you
know
face.
Are
there
some
of
the
kind
of
are
there
junction
points
where
you've
seen
people
fall
off
and
are
there
ways
of
saving
them.
A
A
For
that
you
know,
because
you
don't
want
those
private
messages,
obviously
stored
on
a
blockchain
publicly,
and
you
might
say:
okay,
I'm
going
to
encrypt
those
messages,
but
there
isn't,
I
would
say
a
lot
of
best
practices
around
how
to
do
that
at
scale
right
now,
for
the
average
developer
so,
like
I
guess,
trying
to
kind
of
map
a
web
2
application
directly
into
web3
is
typically,
maybe
not
the
right
way
to
do
it.
Instead,
it's
kind
of
like
okay.
A
Let
me
learn
these
technologies
and
let
me
kind
of
build
out
some
hello
world
applications
and
kind
of
use
them,
and
then
I
want
to
apply
these
ideas
to
maybe
find
a
solution
to
a
problem
that
exists,
as
opposed
to
kind
of
like
using
these
technologies,
to
find
a
solution
to
a
problem
that
might
not
exist.
You
know
if
that
makes
any
sense.
B
Yeah,
no,
absolutely
absolutely
yeah,
I
mean.
Is
there
anything
else
you
wanted
to
touch
on
on
the
graph?
I
know
I
know
you're
involved
in
other
projects.
I
know
I
believe,
you're
part
of
the
developer
shop
correct.
B
I
don't
know
if
you
founded
that
or
if
you,
if
you're
a
co-founder
or
just
a
part
of
that,
but
I
I
was
looking
through
that
yesterday
after
the
call-
and
I
found
that
really
really
cool,
because
I
think
you
know
I'll,
let
you
talk
about
it,
but
it
seemed
like
a
really
interesting
approach
to
bringing
a
lot
more
people
into
this
space.
So.
A
A
We
have
investment
and
sponsorships
that
are
kind
of
right,
close
to
a
million
dollars
right
now
from
a
lot
of
different
protocols
and
projects
in
web3,
and
the
main
focus
of
of
the
dow
is
for
a
bunch
of
developers
to
kind
of
get
together
share
ownership
of
a
community,
build
stuff,
create
stuff
and
share
it
publicly
and
freely,
and
to
kind
of
build
out
free
and
public
education
and
public
goods.
So
what
we've
done
so
far
is
that
we've
announced
a
big
web
3
conference.
A
That's
coming
up,
that's
going
to
be
free
to
attend
for
anyone
that
wants
to
attend.
We've
created
a
few
open
source
projects
like
we
have
when
I
say
we
actually
haven't
personally
contributed
to
any
of
this
code,
I'm
speaking
on
behalf
of
like
all
the
community
members
built
out
like
a
web
3
ui
library.
That's
I
think
we
have
over
like
300
something
stars,
and
it's
been
downloaded,
like
tens
of
thousands
of
times
for
developers
that
want
to
build
out
front-end
applications
on
top
of
like
web3.
A
A
lot
of
tutorials
and
stuff
have
been
created
by
the
community,
so
we're
still
kind
of
trying
to
figure
out
exactly
where
we
want
to
go
with
this.
But
it's
just
a
great
way
for
people
to
kind
of
get
together,
build
stuff,
learn
together.
Also,
a
lot
of
people
have
landed
jobs
and
roles
and
stuff,
and
we
even
have
a
few
people
that
are
going
to
be
employed
full-time
by
the
dao,
because
we
have
now
income
coming
in
and
stuff
like
that,
so
yeah.
A
B
No,
that's
great,
that's
great,
and
so
what's
some
of
the
discourse
around
you
know
I
you
know.
Obviously
the
topic
for
today's
is
infrastructure
and
tooling,
but
you
know
from
an
it's
awesome
that
it's
open
source
right
that
that's
edigoric,
especially
you
know
we're
big
fans
of
that
and
most
people
in
this
space
are
you
know
what
what's
some
of
the
discourse?
B
That's,
you
know
happening
at
the
developer
dao
and
you
know,
maybe
that
translates
to
the
conversations
you're
having
at
edge
and
note
as
well,
but
yeah
I'd
love
to
kind
of
you
know
we
have
a
few
minutes
left.
So
maybe
you
can
dive
into
that
a
bit
some
of
those
discussions
that
that
you're
having
with
the
developers
in
that
that
community.
A
Yeah,
so
dows
are
kind
of
like
a
new
way
for
people
to
organize
and
build
teams,
companies,
projects
and
communities,
and
we
don't
really
have
a
lot
of
the
tooling
that
needs
to
be
there
to
make
it
the
most
effective.
So
we're
kind
of
like
using
what's
available
to
us
today.
That
typically
means
for
most
dows.
There
are
discord,
servers
that
are
token
gated
and
from
within
those
servers
like
people
are
able
to
communicate
and
create
and
come
up
with
ideas
and
build
the
stuff
that
ends
up
coming
out
of
that.
A
There
are
daos
already
created
that
have
multi
billions
of
dollars
of
you,
know
investment
or
capital
or
different
different
things,
so
like
the
fact
that
these
are
so
popular
and
they're,
already
so
effective
with
the
limited
tools
and
resources
that
we
have
today,
it's
kind
of
like
sprung
up
this
new,
I
would
say
industry,
that's
at
within
web3,
which
is
dow,
tooling
and
you're-
definitely
seeing
a
lot
of
projects
that
are
out
there.
A
So
that's
a
pretty
cool
opportunity
in
web3,
if
you're
a
part
of
a
dow
and
you
kind
of
find
a
problem
that
you
know
that
you're
trying
to
solve
as
far
as
how
you're,
organizing
or
how
you're
voting
or
how
you're
collaborating
you
know
coming
up
with
a
tool
to
solve.
That
would
be
a
probably
a
cool
thing
to
do.
B
So
I
I
think
just
for
the
audience
for
clarification
when
you
say
dow,
tooling,
it's
building,
building
tools
and
infrastructure
to
better
optimize
and
have
better
processes
inside
that
decentralized,
autonomous
organization,
correct,
gotcha,
okay,
cool,
and
so
this
you
know
this
is
kind
of
a
low-hanging
one,
but
I
you
know
in
the
web3
space
today.
What
tools
do
you
want
to
see
exist
that
don't
exist?
A
I
think
that
we
have
a
long
way
to
go
as
far
as
peer-to-peer
databases
or
what
you
might
call
like,
off-chain
storage
protocols.
So
if
I
want
to
build
out
an
app,
I
have
like
this
stack
of
primitives
that
I
want
to
use.
I
want
to
use
a
blockchain
as
where
I'm
going
to
kind
of
have
my
own
chain
data,
I'm
going
to
have
a
file
storage
layer,
something
like
we
ipfs,
but
let's
say
I
want
to
build
out
something
like
twitter.
Where
am
I
going
to
store
those
messages?
A
Well,
right
now
you
can
use
something
like
ceramic,
but
right
now,
ceramic
is
is
really
great,
but
it's
kind
of
one
of
the
only
protocols
that's
out
there,
that
offers
kind
of
like
this
piece
of
the
stack
and
it
doesn't
really
have
a
great
way
to
index
and
read
data.
So
I
think
that
in
the
future
we're
going
to
see
more
peer-to-peer
databases
or
more
of
these
off-chain
storage
protocols
that
are
out
there.
A
Also,
we
at
the
graph
are
building
out
an
indexing
system
for
ceramic,
so
you
can
kind
of
like
use
us
to
index
that
data
and
query
it
as
well
in
a
few
months.
So
that's
something
that
we're
still
like
working
on
so
yeah.
So
definitely
that
part
there's
also
a
few
areas
like
if
you
think
about
a
piece
of
functionality
that
most
applications
have
is
messaging
and
notifications.
A
So
how
do
you
do
push
notifications
or
something
like
that
in
web3?
We
don't
really
have
a
protocol
for
that
and
then
lastly,
video
video
storage,
so
ipfs
works
really
great
for
file
storage.
Are
we
works
really
great
for
file
storage,
but
you
probably
wouldn't
want
to
store
a
whole
video
there
because
of
how
expensive
that
would
be.
So
if
you
want
to
build
like
the
web3
version
of
youtube
like
where
would
that
video
storage
primitive,
be,
I
don't
think
we
have
like
a
great
answer
to
that.
A
So
I
think
that
that's
a
huge
opportunity
I
would
check
out
live
pier
though
they
have
like
a
live
streaming
protocol
that
does
video.
I'm
wondering
if
they'll
offer
that
at
some
point
in
the
future.
B
Yeah
fantastic,
I
I've.
I
have
a
few
friends
who
are
building
games
in
the
in
the
in
the
web
3
space
and
they.
That
is
a
big
challenge.
Where
do
we
store
all
this
data
animations,
especially?
So,
that's
you
know
for
any
listeners
out
there
who
are
interested.
That's
a
huge
one
to
tackle
that.
I
know
many
people
are
looking
forward
to
so
you
know,
nader
is
great.
Having
you
is
there
any
kind
of
last
words
last
things
you
want
to
say.