►
From YouTube: Unlimited DSP Possibilities
Description
The LiquidApps DAPP Network is offering a new mechanism for dApps to integrate with one another and to monetize their services. In this episode, we explore the many types of services that might make sense for DSPs (Dapp Service Providers) to offer.
CONTACT:
Telegram: @eosweekly
Twitter: @EOSWeekly
SOURCES:
LiquidApps Go-Live Announcement:
https://medium.com/@liquidapps/the-dapp-network-is-now-live-on-eos-db467f0dc2f
Platin website:
https://platin.io/
EOS Rio Hyperion:
https://eosrio.io/hyperion/
Everipedia's PredIQt prediction market:
https://medium.com/@prediqtnetwork/introducing-prediqt-the-first-prediction-market-built-using-eosio-technology-d9d2f98ecaa3
Effect.AI website:
https://effect.ai/
vAccounts announcement:
https://medium.com/@liquidapps/all-aboard-the-eos-train-its-free-dbc00d9b21f
Registered DSPs in the dappservices account:
https://bloks.io/account/dappservices
A
Welcome
to
heõs
weekly
on
February
26,
the
liquid
Epps
team,
launched
the
DEF
network.
This
included
the
beginning
of
the
dab
token
sale,
as
well
as
the
first
official
product
of
the
dab
Network
VRAM
VRAM
is
a
crucial
enhancement
to
the
EOC
ecosystem,
being
that
Ram
costs,
while
cheap
compared
to
other
blockchains,
have
been
a
barrier
to
entry
for
many
application.
Builders
wanting
to
get
started
with
Yeo's
vram
is
breaking
down
this
barrier,
making
it
affordable
to
build
on
the
eos
blockchain.
A
But
it's
important
to
not
let
this
one
product
overshadow
the
wider
possibilities
of
the
liquid
apps
tap
network,
because,
while
vram
is
in
and
of
itself
an
exciting
development
and
crucial
to
mass
adoption,
the
RAM
only
represents
an
initial
hint
as
to
the
wider
possibilities
of
what's
about
to
come
from
this
new
technology.
In
this
episode,
we're
going
to
explore
the
many
possibilities
as
to
what
may
develop
in
this
new
liquid
apps
layer.
What
types
of
services
will
it
make
sense
for
the
DSPs
to
offer?
A
The
view
you
are
seeing
here
is
in
no
way
meant
to
be
comprehensive
and
to
be
clear,
this
is
not
the
current
reality
of
the
DSPs.
This
is
just
a
prediction:
a
vision
based
on
what
we
know
so
far
and
based
on
what's
possible
with
this
new
technology.
Let's
read
through
these
quickly
and
then
we'll
go
through
some
scenarios
in
more
depth
to
show
why
these
would
make
sense
as
DSPs.
So
for
starters,
we
have
the
base
liquid
EPS
products,
B,
Ram,
B,
CPU
and
V
accounts.
A
Then
going
beyond
the
products
being
offered
specifically
by
liquid
ABS.
We
have
full
history,
file,
storage,
audio/video
location,
identity,
Oracle's,
email,
SMS,
token,
conversion,
prediction,
markets,
reputation,
artificial
intelligence,
content,
curation
logistics,
arbitration,
Fiat,
on-ramps,
front-end,
mobile
and
front-end
web
and
air
drops,
let's
zoom
in
on
some
of
these
now,
to
show
you
why
and
how
all
of
these
services
could
benefit
from
utilizing
the
DAP
Network.
So
to
start
with,
let's
look
at
location
one
here.
A
Some
of
you
may
have
heard
of
platen
a
proof
of
location
protocol
that
allows
anyone
to
geo
locate
a
digital
asset
anywhere
on
the
map
in
a
trustless
decentralized
way.
This
is
a
depth
that
is
being
built
on
a
OS
and,
if
you
think
about
this
platen
Deb,
a
good
portion
of
the
usage
of
this
app
won't
come
directly
through
the
plant
and
user
interface.
Most
of
the
traffic
for
this
type
of
app
will
come
from
other
apps
programmatically
accessing
Plantin
through
its
API.
Take
a
popular
game
like
Pokemon.
A
Go
Pokemon,
go
places
digital
assets
in
physical
locations
out
in
the
real
world.
Future
versions
of
these
types
of
games
or
logistics,
companies
such
as
FedEx,
DHL
or
UPS,
could
benefit
from
utilizing
the
planten's
service
and
games
and
logistics
companies
are
just
the
beginning.
Any
app
that
doesn't
want
to
put
their
trust
in
a
third
party
for
geolocation
will
want
to
consume
a
decentralized
service
like
the
one
being
offered
by
platinum.
But
the
question
is:
how
do
we
handle
the
economics
of
something
like
this?
A
Some
apps,
like
FedEx
and
Pokemon,
go,
might
pound
the
heck
out
of
the
plant
and
service
with
millions
of
requests
per
day,
while
others
will
be
much
less
reliant
on
platon
only
hitting
the
service
here
and
there
occasionally.
What's
the
best
way
to
compensate
those
engineers
who
are
providing
and
maintaining
the
servers
that
are
hosting
platon
and
the
software
developers
who
are
providing
and
maintaining
the
plant
and
code.
In
other
words,
what's
the
best
way
for
platon
to
both
monetize
their
service,
while
at
the
same
time,
throttling
API
usage
in
a
fair
way.
A
A
If
you're
that
Pokemon
Go
game,
that's
going
to
be
pounding
platon
with
millions
of
daily
requests,
you're
going
to
have
to
go
with
the
gold
package
and
stake
more
depth
tokens
to
the
plant
and
DSP,
whereas
the
lighter
usage
app
use
the
smaller
package
here,
maybe
even
the
free
tier
if
plan
turns
out
to
be
a
really
popular
service.
They'll
end
up
with
a
lot
of
tokens
stake
to
their
DSP
and
they'll,
get
paid
similar
to
how
elected
bp's
get
paid
on
the
eos
network.
A
Based
on
the
number
of
DAP
tokens
stake
to
each
DSP,
the
proportional
amount
of
annual
inflation
gets
distributed
to
each
DSP.
Now,
let's
say
platon
in
order
to
offer
their
geolocation
service
needs
to
query
the
full
history
of
the
EOS
plot
chain.
Just
like
the
platon
service,
summed
apps
by
their
very
nature,
need
regular
access
to
full
history
while
others
need
it.
Seldom,
if
ever
let's
say,
hypothetically
EOS
Ryo
is
the
one
offering
this
full
history.
A
A
This
is
just
like
what
planned
it,
except
this
time
plan
would
be
on
the
consumer
side
of
things,
so
they
will
have
to
choose
the
appropriate
package
based
on
their
full
history,
usage
and
platon
will
need
to
purchase
and
stake
their
own
DAP
tokens
to
the
eos
300d
SP
besides.
Full
history
plan
might
also
want
to
take
advantage
of
VRAM
being
offered
by
US
nation
over
here,
so
that
platen
can
utilize
their
on
chain
ram
in
a
more
optimal
way.
A
Now
it's
highly
likely
that
instead
of
each
of
these
organizations
launching
their
own
DSP
for
each
individual
product
or
service,
that
partnerships
will
form
among
dabs
and
bps,
like
Platon,
Yoast,
Ryo
and
EOS
nation,
and
these
three
entities
would
aggregate
their
services
together
into
a
single
DSP.
Having
these
multi
service
DSPs
will
be
alluring
to
depth
builders
because
it
keeps
things
simple,
enabling
them
to
stick
to
a
single
DSP
for
all
their
various
needs.
A
A
One
here
back
in
December
iver
are
pedia
announced
that
they
were
building
a
prediction
market
like
an
auger
that
would
enable
people
to
wage
against
the
outcome
of
events
and
see
the
odds
of
different
events
happening
on
April
1st
we
learned
the
name
of
this
prediction
market
predict
with
a
Q.
This
is
another
service
that
would
benefit
from
not
just
having
a
UI,
but
also
from
having
an
API
that
would
give
other
apps
programmatic
access
to
the
ever.
A
PDF
prediction.
A
A
Imagine
a
DSP
launching
that
enabled
apps
to
upload
the
HTML,
CSS
and
JavaScript
files
for
the
front
ends
of
their
applications.
This
DSP
could
store
your
front-end
files
in
a
decentralized
way
using
IP
FS
and
serve
them
up
upon
request.
Going
back
to
the
user
interfaces
of
platen
and
ever
opee.
Do
the
DAPs
could
host
the
front-end
part
of
their
apps
in
this
DSP
up
here,
pointing
those
front-end
UI's
at
the
respective
DSPs,
where
their
back-end
business
logic
resides?
A
What
we're
beginning
to
see
now
is
a
potential
future
where
applications
are
absorbed
into
a
layered,
complementary,
interconnected
set
of
DSPs,
where
no
part
of
the
app
needs
to
necessarily
reside
outside
the
DSPs.
In
this
way,
the
entirety
of
the
application
becomes
decentralized,
assuming
each
TSP
is
operating
on
chain
are
using
a
decentralized
protocol
such
as
IP
FS
for
their
various
services.
Let's
pause
on
this
example
here
now
and
take
a
closer
look:
ai
and
V
accounts.
Why
might
these
two
go
together?
A
Well
effect,
AI
incentivizes
people
to
help
classify
images
and
perform
other
tasks
in
order
to
teach
their
deep
learning.
Algorithm
participants
can
earn
EFX
tokens
for
the
tests
that
they
perform.
This
is
the
type
of
service
that
will
have
an
API,
as
other
depths
will
want
to
integrate
with
it.
So
again,
like
any
other
app
that
is
offering
an
API
for
the
purpose
of
monetization
and
throttling.
It
could
make
sense
to
offer
this
API
in
the
form
of
a
DSP.
Here's.
Why
apps?
A
Like
effect
a
I,
would
benefit
from
integrating
with
the
liquid
apps
via
accounts
product.
The
accounts
was
just
announced
in
late
March
and
offers
a
free
way
to
create
virtual
accounts
for
new
users.
This
is
perfect
for
onboarding
new
users
into
the
EOS
ecosystem
in
a
frictionless
way,
as
there
is
a
cost
involved
with
creating
an
EOS
account.
The
accounts
makes
it
possible
to
store
and
transfer
tokens
in
and
out
of
a
virtual
space,
which
behaves
just
like
a
real
account.
If
effect,
a
I
were
to
offer
a
DSP
that
integrated
with
V
accounts.
A
Newcomers
to
effect
at
AI
could
earn
their
EFX
tokens
into
their
liquid
apps
virtual
account
to
start
out
with
and
once
they've
accumulated
enough
value
in
those
EFX
tokens
they
could
choose
to
convert
their
via
count
into
a
normal
Yoast
account
watch
for
this
integration
to
happen.
Here's
another
combination
where
the
DSPs
complement
each
other
quite
nicely:
identity,
Fiat,
on-ramp
and
token
conversion
warbly
is
offering
a
permission
chain
that
requires
kyc,
know
your
customer
at
the
base
layer.
But
why
not
raise
that
kyc
up
into
an
identity
service
at
the
DSP
level?
A
A
It
would
also
make
sense
for
someone
like
Bank
or
to
launch
a
token
conversion
service
as
a
DSP
using
the
banker
protocol,
the
relays
we
described
in
our
last
video.
Not
only
would
this
be
nice
for
the
user,
in
our
current
example,
with
converting
fiat
to
crypto
to
give
some
options
as
to
which
crypto
they
are
converting
directly
into.
A
But
if
you
think
about
it,
a
large
portion
of
the
apps
out
there
will
want
to
embed
their
token
conversion
in
their
app
so
that
the
user
doesn't
need
to
leave
the
app
experience
the
game
or
the
virtual
reality
experience
in
order
to
convert
tokens.
And
finally,
let's
talk
about
arbitration,
an
arbitration
forum,
a
group
of
professional
arbitrators,
ideally
with
an
automated
element
to
their
service,
could
offer
their
services
as
a
DSP
enabling
devs
to
opt-in
to
various
levels
of
their
service.
Based
on
the
number
of
cases,
a
given
damp
will
be
filing
arbitration.
A
Dsps
could
specialize
in
various
jurisdictions
or
languages
or
types
of
disputes,
and
it
will
probably
make
sense
for
arbitration
DSPs
to
integrate
or
form
partnerships
with
identity
and
reputation
services
as
the
DEF
network.
Matures
it's
hard
to
say
whether
we'll
have
a
few
large
DSPs
that
offer
a
one-stop
shop
for
all
your
DAP
needs
or
if
we'll
have
a
lot
of
little
niche
DSPs
for
each
individual
service,
it
likely
won't
be
either
extreme,
but
somewhere
in
the
middle.
A
A
lot
of
DAP
developers
out
there
won't
want
to
deal
with
the
hardware
and
networking
infrastructure
themselves
when
launching
their
DSP
and
will
happily
partner
with
bps
who
specialized
in
the
hardware
side
of
things.
Other
app
builders,
however,
might
have
the
infrastructure,
capital
and
know-how
where
they'd
be
willing
to
launch
their
own
independent
DSP,
and
then
there
will
be
bps
who
launched
their
own
DSPs
without
any
partnership
with
debts.
All
of
these
scenarios
will
be
playing
out
in
the
months
and
years
ahead
as
this
ecosystem
forms.
A
A
This
is
where
people
register
to
be
DSPs,
so
you
can
always
see
the
current
list
of
the
DSPs
here
it's
changing
rapidly,
so
we
added
a
link
to
this
in
the
show
notes
below
you
can
see
that
yos
infra
attic,
lab
Sweden,
airdrops,
Dec,
Neos,
Detroit,
yos,
New,
York,
Yas,
nation,
Yas,
tribe
and
Boyd-
are
the
current
set
of
registered
DSPs.
Yes,
USA
hasn't
registered
yet,
but
they
have
announced
plans
to
launch
a
DSP
as
well.
A
These
first
DSPs
are
focusing
on
vram
as
they
learn
the
ropes
of
the
DSP
world
and
they
won't
likely
add
support
for
V
accounts.
Next,
the
first
DSP
that
was
launched
for
a
specific
service
is
airdrop
stack.
It
was
in
fact
air
drops
that
were
on
tails,
mind
when
he
invented
vram
and
ultimately,
the
dap
network,
michael,
the
founder
of
airdrop
stack,
worked
closely
together
with
Thao
on
one
of
the
first
real
usages
of
the
DAP
network,
which
was
to
execute
an
airdrop
using
vram
so
as
to
make
the
airdrop
more
affordable.
A
They
had
some
kinks
to
work
through
together,
but
ultimately
this
was
a
success
and
vram
proved
to
make
air
drops
about
six
times
more
affordable.
If
this,
liquid
EPS
layer
is
a
success
as
it
appears,
it
will
be.
The
potential
here
is
massive.
This
is
a
new
layer
that
never
existed
before,
and
liquid
EPS
has
first
mover
advantage
similar
to
how
Bitcoin
had
first
mover
advantage
in
the
ledger
layer
below
it.
Well,
liquid
EPS
become
the
granddaddy
of
the
integrations
layer
like
Bitcoin
is
of
the
ledger
layer.
This
is
a
definite
possibility.
A
The
EOS
community
is
lucky
that
the
liquid
Apps
team
has
built
this
here
on
Yost.
First,
this
is
a
differentiating
factor
for
our
blockchain.
None
of
the
other
smart
contract
chains
out
there
have
anything
like
this
now,
there's
nothing
to
stop
the
liquid
apps
depth
network
from
spreading
across
to
other
smart
contract
platforms
such
as
Tron
or
etherium.
This
is
probably
inevitable.
It's
also
probably
inevitable
that
other
networks
will
be
created
that
will
compete
with
the
DEF
network
in
the
integrations
layer.
A
Here
Bitcoin
was
not
the
last
blockchain
of
the
ledger
layer
and
it
would
be
naive
of
us
to
think
the
DEF
network
will
be
the
last
of
the
integrations
layer.
That's
it
for
this
week's
episode
thanks
for
watching,
and
we
hope
you
learned
something
if
you
haven't
done
so
already.
Please
subscribe
to
our
Channel,
we'll
help
you
stay
current
on
us
as
this
revolution.
Unfolds
thanks
and
we'll
see
you
next
week
right
here
on
ilos
weekly.