►
Description
Imagine a search engine for Web3—that's what KEN Labs is building, with an indexing layer for the Filecoin dataverse. The idea is to be able to search by content through a single control panel, which is also tightly integrated with the data storage and retrieval markets.
A
Is
our
great
pleasure
to
to
be
here
to
celebrate
the
fair
coin?
Rpg
event
for
one
year
anniversary
of
faircoin
midnight
launch
for
past
three
years
and
for
past
one
years
I
have
spent
most
of
my
time
on
the
faircoin
from
from
testnet
this
one
phase,
2
and
swiss
race,
and
to
the
fair,
convenient
launch.
A
It
is
a
really
amazing
journey
for
past
three
years
and
for
past
one
year
I
left
ipf
sports
and
and
set
up
a
new
startup
of
kin
labs
and
focused
on
the
next
generation
cloud
for
web
3.
and
for
the
next
generating
cloud.
There
is
three
parts
computing
computation
storage
at
cdn,
and
today
we
will
introduce
our
working
on
the
cdn
and
about
the
counter
plan
of
the
cdn,
and
my
teammates
william,
will
give
a
detailed
introduction
about
the
index
in
the
database.
Due
on
the
data
index.
B
Hello,
everyone-
this
is
william
from
the
ken
labs,
so
I'm
going
to
talk
about
index
in
the
database
so
deal
and
the
data
indexing
from
ken
labs
okay.
So
this
is
the
agenda
today,
I'm
going
to
briefly
introduce
our
can
labs.
Then
we'll
move
on
to
time
rules
the
indexing
solution
that
we
are
going
to
index.
We
all
will
be
indexing
the
database,
so
there
will
be
a
couple
of
aspects
I'm
going
to
go
through
all
of
them
shortly.
B
B
Now
we
are
building
the
cloud
2.0
based
on
ipvs,
so
based
on
the
content
adjustable
computation
and
storage,
we
have
introduced
the
ideas
of
sdn,
I'm
going
to
talk
about
shortly
and
the
incentive
mechanism
of
blockchain
to
build
the
next
generation
of
cloud
operating
system
so
from
the
the
chart
on
the
right
bottom.
So
you
will
see
the
the
ken
labs
cloud
os
architecture
and
the
os
will
cover
the
computing
storage
and
cdn.
B
I'm
going
to
go
through
all
these
different
aspects.
Firstly,
let
me
compare
the
indexing
with
the
marketplace
in
web
2.0,
so
the
data
value
chain
of
web
2.0,
for
you,
you
can
see-
is
broken
so
in
web
2.0.
The
data
are
silos
with
ad
based
revenues
and
in
web
3.
You
can
see.
The
chain
has
been
unified
in
the
metaverse
based
on
far
coin
and
the
ipfs
protocol
in
the
following
industries
or
areas,
the
content,
curator
search
engine
marketplace
and
payment
or
lending.
B
B
So
let
me
now,
let's
take
a
look
at
cdn,
which
is
a
very
important
product
in
web
2.0
with
the
sdn.
So
what
is
sdn
sdn?
Is
software
defined
network,
so
the
history
of
the
internet
maps
roughly
to
the
evolution
of
the
following
aspects
in
the
face
of
challenges,
including
the
control
schemes
for
managing
reachability
information
and
protocol
for
the
distribution
of
such
information
and
the
algorithmic
generation
of
the
optimized
path?
B
B
B
B
So
let's
take
a
look
at
the
the
charts
below,
so
we
have
a
comparison.
So
in
the
web
2.0
we
have
the
big
brands.
They
provide
the
cloud
service
for
structured,
semi-structured
or
even
unstructured
data
to
the
top
layer,
the
application
layer.
So
in
the
web
3,
we
believe
the
data
source
will
be
ipfs
far
coin
and
on-chain
data,
including
the
web
2.0.
On-Premise
data
sets
on
top
of
this
all
these
data
sources.
B
We
have
we
we
need
that
indexing
layer
which
provides
the
data
provider,
discovery
mechanism,
the
content,
searching
functionality
and
the
information
creation
mechanism.
We
also
need
the
scheduling
service
and
the
data
analytics
feature
on
the
top.
We
will
build
the
qre
api,
which
will
power
the
application
layer.
B
Okay,
you
can
see,
so
this
is
how
we
can
see
the
architecture
evolution,
so
the
standalone,
host
or
node
architecture
has
been
transformed
into
a
decentralized
organization.
So
each
node
of
the
network
contributes
to
all
the
features
or
interfaces
of
query
storage
and
the
integration
they
cooperate
with
each
other
and
build
the
control
plane
and
the
serve
on
top
of
the
data
plane.
B
B
B
B
So
in
all
these
data
provider
we
have
the
indexing
support.
So
for
filecam
data
we
have
the
deal
indexing
for
ipfs
and
other
file
content
that
need
to
be
on
the
ipfs
network.
They
surely
have
a
cid
indexing
based
on
all
these
basic
indexing
functionality
for
cid.
We
can
provide
the
full
text
indexing,
which
will
eventually
allow
the
end
users
or
any
application
to
consume
the
full
text
indexing
feature
and
provided
in
the
user
application
or
functionality
allow
users
to
efficiently
find
content
in
their
most
familiar
way.
B
B
B
B
It
will
utilize
the
http
api
to
help
you
find
provider
of
a
cid
or
do
the
full
text
in
searching
at
the
top
of
the
the
chart.
You
can
also
see
that
I
preface
watch
this
is
a
solution
for
the
regular
file
system.
So
you
have
imagine
you
have
a
huge
amount
of
data,
a
data
set
from
your
local
file
system.
B
It
can
be
some
enterprise
data.
You
want
to
get
it
synchronized
to
ffs
network,
so
you
don't
want
to
put
all
of
them
to
the
network
to
duplicate
the
data,
so
you
can
use
our
applicator
watch
solution
with
a
no
copy
support,
which
means
the
content
won't
be
copied
to
network.
At
the
same
time,
all
these
files
will
still
be
indexed
to
the
network.
B
Also,
if
you
want,
you
can
also
provide
the
cid.
The
search
engine
will
return
you,
the
provider,
if
it's
found
also.
Alternatively,
if
you
do
want
to
just
search
as
a
keyword,
it
can
also
work
for
you.
It
will
try
to
find
some
files.
I
have
that
have
the
the
cid
as
a
content
or
part
of
the
file
name.
B
B
B
So
if
we
just
view
the
green
line,
so
the
provider
the
unique
providers,
it's
growing
steadily,
so
it's
looking
for
providers
and
the
cid
from
the
network.
All
these
data
can
be
fed
to
the
full
text
indexing
and
the
build
the
search
engine
with
more
and
more
content
so
and
the
user
can
consume
from
there.
B
B
Ipfs
cid
indexing
is
surely
supported
by
time
rows
and
the
ipv4
text
indexing,
as
just
mentioned
so
ipvs
process
can
use
the
time
rules
api
to
find
providers
which
can
be
more
efficient
and
our
ipvs
content
crawler
will
give
the
metadata
aggregation
support
the
search
engine.
Web
application
gives
you
the
ability
to
look
up
cid
provider
and
for
text
search.
B
So
what's
next,
we
have
a
future
plan.
As
you
can
see,
we
are
going
to
segregate
the
full
tech
indexing
service
for
now
it's
embedded
and
it's
a
standalone
time
rails
application
with
all
the
modules
components
embedded
we're
going
to
segregate
the
full
text
indexing
and
then
make
it
as
a
processes
can
be
separately
executed
and
wrong
in
the
network.