►
From YouTube: Decentralized Dapp Scaling w/ IPFS! How LiquidApps Dapp Service Providers Work | Developer Explains
Description
vRAM's use of IPFS will scale dapps in a decentralized way! Here's an intro to the latest tech information on LiquidApps DSPs (Dapp Services Providers).
See the Medium article mentioned, LiquidApps' "vRAM Guide for Experts" at https://medium.com/@liquidapps/vram-guide-for-experts-f809c8f82a27
Everything EOS is the longest running EOS podcast. Zack Gall and Rob Finch go in-depth on the latest EOS news, and Peter Keay produces resources and courses on the latest EOSIO development tools.
***
Series Sponsor:
Cypherglass - www.cypherglass.com
For more information on sponsorship opportunities or content partnerships, please contact zack@everythingeos.io
https://www.EverythingEOS.io
https://youtube.com/c/Everything_EOS
http://t.me/Everything_EOS
https://anchor.fm/everythingeos
https://itunes.apple.com/us/podcast/everything-eos/id1434560651?mt=2
A
Hey
guys,
my
name
is
Peter
Kay
I'm,
the
newest
member
of
the
everything
US
team,
I'm,
a
developer
I'll
be
focusing
more
on
technical
content.
You'll
be
seeing
some
developer
courses
coming
out,
keep
an
eye
out
for
them.
They're
gonna
be
great,
but
we'll
also
be
doing
these
short
little.
Videos
on
the
latest
moves
in
the
US
development
space
and
the
one
I
want
to
talk
about
today
is
liquid
apps
vram.
A
Things
like
that,
but
right
now
neos.
It's
being
used
as
long-term
storage
and
the
better
contracts
will
delete
things
that
aren't
needed,
but
still,
if
you
have
accounts
with
taps,
if
you
have
like
progress
with
taps,
you
have
token
balances
whatever
with
taps.
You
have
even
history
with
taps,
that's
relevant
to
the
future
operation
of
the
dab,
your
all
those
things
are
kept
in
ramp
and
there's
only
64
gigabytes
of
it,
as
you
can
imagine
that
can't
really
hold
a
lot
of
DAPs.
So
we
need
another
solution
and
layer.
A
2
solutions
are
a
big
thing
in
the
blockchain
space,
and
you
might
have
this
like
sense
that
layer,
2
solutions
are
more
centralizing
that
you're
making
some
trade-offs
for
speed
and
capacity
you're
kind
of
trading
away.
Maybe
decentralization
or
some
other
aspects-
I
mean
I
like
layer,
2
solutions,
I
have
a
have
a
lightning
node
running
right
now,
but
this
is
different.
A
This
layer,
2
solution,
if
anything,
is
going
to
increase
decentralization
and
liquid
apps
has
put
forth
a
vision
and
a
plan
of
action
where
this
layer
2
solution
will
make
it
so
not
only
the
smart
contract
and
its
execution,
but
the
entire
DAP
from
front
end.
All
the
way
to
back
end
will
be
decentralized
even
hosting
so
like
you,
don't
ever
have
a
centralized
choke
point
along
the
way
how
in
the
world
do
they
do
that?
A
Well,
there
are
going
to
be
DAP
service
providers
on
the
network
that
provide
resources
and
the
first
one
is
storage
which
we're
calling
vram
I.
Guess
that's
virtual
Ram,
an
article
just
came
out
yesterday
with
more
details
on
how
this
works.
So
if
I'm,
a
smart
contract,
I,
usually
keep
all
my
information
right
in
RAM
for
easy
access,
there's
not
really
an
easy
way
to
do
it.
Otherwise,
right
now
there
are
some
plugins
to
other
databases.
You
could
rig
up
your
own
ipfs
solution,
but
the
vram
promises
to
be
an
easy,
plug-and-play
solution.
A
Where,
if
you
have
some
DAP
tokens,
you
can
purchase
these
services
from
a
DAP
service
provider.
So
a
smart
contract
can
make
two
kinds
of
requests
that
will
use
this
decentralized
storage
and
asynchronous
requests
or
asynchronous
requests.
Let's
talk
about
synchronous
requests.
First,
I
just
want
to
tell
you
how
it
works,
because
it's
actually
pretty
fascinating.
A
synchronous
request
means
that
you
need
to
have
the
answer
before
you
can
proceed
with
computation.
So,
for
instance,
maybe
I
need
a
random
number
in
order
to
do
something
or
I
need
to
retrieve
some
data
from
storage.
A
That's
not
in
RAM
anymore
and
I
have
to
have
it
before
I
proceed.
If
you
send
that
smart
contract
request
that
command
to
do
that,
action
to
a
node
that
doesn't
have
a
DSP
to
a
non
DSP
node
like
most
of
the
EOS
nodes
right
now,
the
code
will
just
throw
an
exception.
It'll
throw
an
error
and
it
won't
even
execute,
won't
show
up
on
the
blockchain.
A
None
of
that,
if
you
send
it
to
a
DSP
node,
then
the
same
thing
happens:
it
throws
an
exception,
but
the
DSP
is
configured
to
realize
that
that
kind
of
exception
is
a
request
for
services.
So
once
your
command
throws
an
exception,
as
it
would
on
any
other
node
the
DSP
realizes
it
needs
to
step
in
provide
what
you're
asking
for
whether
it's
a
random
number
or
some
information
from
a
web
Oracle
or
maybe
something
that's
stored
on
ipfs.
It
will
provide
that
information
and
then
execute
the
transaction.
A
A
So
when
adapt
makes
a
VRAM
request,
which
again
they're
very
easy
to
implement
the
elemental
battles,
contract
has
already
been
modified
so
that
you
can
go
ahead
and
take
a
look
at
how
to
implement
vram,
and
there
are
maybe
six
or
seven
block
producers,
including
EO,
Sweden
and
addict
labs.
A
number
of
others
I
just
forget
that
have
are
up
and
running
DSPs
already
and
they're
improving
the
performance
of
the
DSPs.
A
All
the
time,
if
you're
smart
contract
makes
a
VRAM
request
that
say,
I
need
some
data
that
was
saved
a
long
time
ago
about
a
user
and
stored
in
ipfs
through
the
vram
mechanism
and
isn't
in
the
block
producers
Ram
anymore.
Then,
first,
the
there's
a
warm-up
phase
where
the
data
is
retrieved
and
validated,
because
there's
still
a
hash
of
the
data
on
chain.
We
retrieve
the
data
and
we
make
sure
it
hasn't
been
tampered
with.
A
We
make
sure
that
no
one
has
seen-
maybe
you
know,
improved
their
high
school
or
skipped
a
bunch
of
levels
or
or
whatever,
and
we
make
sure
it
hasn't
been
tampered
with,
and
then
we
bring
it
in
temporarily
into
RAM
in
there
like
a
temporary
local
cache,
not
local.
That's
not
the
right
word:
a
temporary
cache
in
block
producers
Ram
to
work
with
it
and
then,
when
we're
done,
we
have
a
cleanup
phase,
ditches
the
cache
the
RAM
is
freed
up
again
and
we're
back
to
ipfs.
A
It's
great
I've
been
working
on
a
few
EOS
projects
and
it's
been
a
tough
challenge,
sometimes
to
figure
out
how
we're
gonna
keep
people
from
cheating.
I.
Think
this
is
a
really
interesting.
It's
a
really
helpful
mechanism.
Not
only
will
the
smart
contract
ultimately
be
kept
in
a
decentralized
fashion
where
you
can't
just
arbitrarily
alter
it
or
you
know,
pay
for
it
to
be
altered
or
whatever
and
its
execution
will
be
kept
decentralized,
but
also
the
front
end,
all
the
code
and
all
the
storage
of
user
files,
all
the
records
of
history.
A
You
know
all
the
databases
all
of
that
will
be
kept
in
a
decentralized
fashion,
which
will
lead
to
the
most
decentralized
applications
that
we
have
seen
on
other
platforms.
This
isn't
nearly
as
far
along
to
my
knowledge
as
it
is
on
EOS
now
with
liquid
apps
and
the
guys
who
have
programmed
liquid
apps,
who
the
guys,
who
are
behind
a
lot
of
this
code,
they're
behind
some
of
the
code
in
iOS
io
as
well.
They've
worked
on
things
like
the
the
RAM
markets,
and
things
like
that.
A
So
these
are
skilled
developers,
building
an
amazing
product
that
is
going
to
revolutionize
the
dab
space.
It
goes
beyond
storage,
like
I,
said
a
random
number
generation.
That's
a
major
problem.
It's
something
that
cardano's
been
working
a
lot
on,
it's
something
that
iOS
T
prides
itself
in
in
having
a
solution
for
right
now
on
EO.
So
you
have
to
do
a
kind
of
multi-party
compute
where
I
have
a
secret
and
you
have
a
secret
and
then
I
mean
it's
fine.
A
It
works,
but
it's
kind
of
clunky
and
now
we'll
be
able
to
do
things
like
that.
It's
also
difficult
to
get
web
Oracle's
and
working
on
another
project
where
we
need
cryptocurrency
price
data
and
right
now
we
have
to
kind
of
do
that
in
a
centralized
fashion.
We
decentralizes
ism
as
much
as
possible.
We
grabbed
from
a
bunch
of
different
api's
different
services,
so
that
one
can't
bring
the
whole
thing
down,
but
but
liquid
apps
is
offering
a
way
to
do
decentralized.
A
Web
Oracle's,
in
other
words,
decentralized
places
to
get
information
about
the
outside
world
that
the
blockchain
normally
can't
find
out
about
in
a
decentralized
way.
It's
amazing
project,
I
highly
recommend
you
check
it
out.
If
you're
a
developer,
you
can
go
and
start
implementing,
vram
right
now,
which
helped
Vivi.
It's
a
lot
of
concerns
and
I.
Don't
know
what
the
costs
will
be
ultimately,
but
the
way
it's
set
up
is
that
DSPs
can
offer
their
own
packages
in
a
free
market
system.
A
So
if
you're
not
happy
with
the
services
that
you're
being
provided
by
your
DSP
you're,
not
happy
with
the
price,
you
can
go
and
shop
for
something
better,
that's
great
and
that's
what
we're
looking
at
for
liquid
apps
DSPs,
that's
how
they
work.
It's
a
game,
changer
guys
it's
a
game.
Changer
for
iOS.
We
have
a
layer
to
resource
scaling
solution
that
is
not
centralized
and
we
are
going
to
be
able
to
create
apps
that
are
from
the
smart
contract
all
the
way
to
the
user
facing
front-end.
A
The
database
are
all
decentralized
and
the
Oracles
it
gets
the
random
numbers.
It's
all
going
to
be
decentralized
fashion.
It's
amazing!
It
enables
a
level
of
decentralization
that
I
think
we
have
not
seen
before
it's.
It's
really
brilliant.
There's
a
lot
more
details
on
how
exactly
this
connects
to
IP
fess
on
how
all
the
Merkel
tree,
validation
works,
and
things
like
that,
and
even
some
hints
as
to
how
other
things
beyond
just
decentralized
storage
are
gonna
work
in
a
new
article
and
on
the
liquid
apps
medium.
That
was
again,
it
was
just
posted
yesterday.