►
From YouTube: End-to-End Decentralization | LiquidCMS | Limitless and Affordable RAM (DAPP Network Series 3/3)
Description
DAPP Network Series
Part 1: https://youtu.be/yb-D-4M1CtM
Part 2: https://youtu.be/tB1Gvq3yV8E
Beni Hakak and Tal Muskal are the CEO and CTO of both LiquidEOS and LiquidApps. In this episode, Zack Gall and Peter Keay are told the story behind LiquidApps and the implications of the DAPP Network.
The DAPP Network paves the way for an entirely new class of decentralized applications to emerge. dApps that were previously unimaginable due to the cost or systemic limitations of the existing technology stack.
This is part three of a three part series with the team building the DAPP Network.
Everything EOS is the longest running EOS podcast. Zack Gall and Rob Finch go in-depth on EOS dapp news, EOS VC announcements, dapp funding announcements, EOSIO upgrades, EOS mainnet news, EOS side chain news, and more.
Peter Keay produces resources and programming courses on the latest EOSIO development tools and is the host of our technical series.
https://twitter.com/BlockchainZack
https://twitter.com/bitgensteinx
https://twitter.com/tmuskal
https://twitter.com/BeniHakak
***
Series Sponsor:
Cypherglass - https://www.cypherglass.com
Friends of Everything EOS:
https://www.eosnameservice.io
https://www.dappiness.io
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
Decentralized Dapp Scaling w/ IPFS! How LiquidApps Dapp Service Providers Work | Developer Explains https://youtu.be/-XdVnK22mZc
LiquidApps and LiquidEOS:
https://www.liquidapps.io
https://www.liquideos.com
https://t.me/LiquidAppsOfficial
A
B
A
Didn't
even
imagine
yet
what
are
the
possibilities
of
endless
ran,
because
until
now,
okay,
until
theorem
was
introduced
to
the
world,
all
the
dab
developers
were
sure
that
RAM
is
expensive
and
they
envisioned
their
depth
in
a
certain
way
in
which
M
is
a
scarce
resource.
We
cannot
use
a
lot
of
it,
but
we
still
a
lot
of
gambling
apps,
because
gambling
do
not
require
any
memory.
Okay,
not
a
lot
anyway.
A
C
Yeah
as
a
nomad
I'm,
not
this
is
a
no
new
topic,
just
as
a
contractor.
I
do
all
kinds
of
things
like
you
know.
If
you
do
a
lot
of
things
implicitly
like
if
I,
if
I
cannot
get
away
from
storing
it
and
just
you
know,
kind
of
act
like
it
exists,
even
though
it's
not
stored
than
I
do,
and
you
also
you
delete
things
liberally
yeah,
so
I
get
what
you're
saying
we've
all
grown
to
think
that,
like
RAM,
should
not
be
used
if
at
all
possible,
exactly.
B
With,
if
there's
not
a
cost
limitation,
why
not
is
the
thing
so
all
of
these
reasons
for
them
doing
it
it's?
What
is
the
reason
behind
that
and
the
reason
is
economic,
the?
Why
not
if
it's
cheap
and
available,
why
are
you
you
pigeon
holing
yourself
to
only
put
the
most
important
stuff
there?
If,
if
you
could
put
everything
there
more.
A
Than
that,
if
you
don't
put
the
game
logic
on
top
of
the
chain,
you
can
cheat
essentially
like.
How
do
you
know
right
now?
If
an
item
is
only,
it
is
rare.
It's
because
the
game
creator
tells
you
that
it's
rare,
but
if
the
game
logic
is
on
chain,
you
can
make
sure
that
it
is
the
only
sword.
You're
gonna
have
ever
created
by
the
game
right.
It's.
D
Even
its
rarity,
who
gets
right
and
and
Trust
is
entrusted,
is
something
that
that's
again,
it's
interesting
not
just
to
prevent
your
customer
from
from,
or
your
player
from
cheating
you
also
now.
You
can
think
in
terms
of
not
trusting
your
partners
not
to
cheat
your
games
you're
connecting
with,
because
once
you're
relying
on
them,
they
get
the
opportunity
to
cheat
if
you're,
having
shared
logic
or
sure
anything
sure
the
economy's.
D
C
C
D
Public
aspects
we're
only
using
IP
FS
everything
that
this
is
supposed
to
fetch
is
already
local.
It's
you
can
think
of
it
as
just
a
storage
layer
that
sits
locally,
with
the
added
benefit
of
being
able
to
access
it
from
client
side
through
the
IPS
s
cloud.
But
that's
like
a
bonus.
It's
not
how
it's
being
used
in
the
in
the
in
the
data
path
you
get.
You
should
never
rely
on
the
IBF
s
cloud
itself
for
thing.
That's
so
rapid
as
a
warm-up
requests
from
in
in
terms
of
the
latency.
D
The
latency
itself
comes
from
simulating
the
action
and
trying
to
understand
what's
needed
to
be
basically
trying
to
simulate
the
cache
hit
or
miss
decision
run.
So
potentially
that
can
happen.
There
is
no
limit
on.
There
is
no
practical
limit
on
how
much
it
can
be.
Optimized,
there's
three
weeks,
thinking,
there's
so
much
potentials
in
cutting
down
in
making
this
process
more
option,
life
and-
and
one
misconceptions,
that's
always
brought
up-
is
the
fact
that
it's
in
quant
of
blocks
the
latency.
So
technically
it
can
happen
in
the
same
block
and
was
right.
D
It's
actually
very
reasonable.
Some
people
even
thought
that
that
you'd
probably
need
to
wait
for
finality.
Otherwise,
why?
How
do
you
know
if
the
warm-up
succeeded
or
not
and
and
the
beauty
about
it
is-
is
that
it's
not
like
a
false
warm-up
for
the
cache
is
harmless
and
the
cache
myth
is
also
harmless.
So
there
is
no
need
to
wait
for
confirmation
that
the
warm-up
actually
happened
so
there
there
both
can
happen
as
as
fast
as
possible
and
potentially
once
it's
optimized
enough
to
happen
in
the
same
block.
C
So,
if
I
just
want
to
throw
out
there,
if
any
of
anyone
watching
doesn't
understand,
what's
going
on
with
warm
ups
and
and
all
that,
and
why
we're
talking
about
latency-
and
you
know-
simulating
actions,
go
ahead
and
watch
my
little
video
on
this
or
read
the
article
that
liquid
apps
put
out.
We
could
throw
up
a
link
to
understand.
What's
going
on
with
that,
one.
D
Of
the
things
that
you
touched
in
your
technical
video
was
one
of
the
thing
that
I'm
most
excited
about
today,
which
is
the
entire
concept
of
exception,
as
a
signal
for
changing
how
the
flow
or
the
sequence
of
the
code
is
actually
treated
by
the
runtime
to
to
emulate
the
situation
were
in
the
code.
It
looks
like
you're
fetching
your
resource
and
you're,
getting
it
right
back
in
the
same
line
of
code,
and
you
can
just
use
it
the
next
line
later,
even
though
it's
not
really
possible
right.
D
It's
if
you
look
at
code
and
if
you,
if
you
examine
the
code
and
you'll,
ask
okay,
it
can't
act.
Ask
for
something
and
get
it
in
the
same
transaction.
So
what's
going
on
here,
so
this
kind
of
magic,
this
that
hides
this,
this
synchronous
mechanism,
which
can
sound
trivial
trivial
for
for
programmers
to
come
outside
our
industry.
D
This
kind
of
mechanism,
I
think
the
potential
is
great
for
doing
many
other
services
with
it
like
randomness
service.
That's
something
that
you
need
just
in
time
in
the
code
to
get
a
random
seed
or
even
a
resources.
Resources
from
the
web
from
API,
so
imagine
things
like
prediction:
markets
where
you
have
Oracle's
providing
the
end
results
and
you
don't
need
a
different
blockchain
for
that.
D
B
B
B
You
guys
build
this
and
I
think
your
core
teams
working
on
it
as
well,
but
what
other
services,
as
you
guys,
excited
that
we
haven't
covered
yet
and
I
guess
out
of
backtrack
and
I'll,
just
tell
you
mine
and
that's
the
free
accounts,
so
how?
How
is
the
free
accounts
going
to
affect
user
adoption?
And
you
just
put
out
a
blog
article
recently
about
reaching
virality
and
how
free
accounts
is
a
huge
part
of
that?
B
And
that's
true
there's
this
huge
point
of
friction
asking
someone
to
pay
what
at
minimum
$1,
but
that's
even
too
much.
We've
seen
that,
like
the
freemium
model,
how
it
took
off
in
like
the
late
2000s,
people
want
to
try
things
before
they
put
any
money
in
and
then
same
is
going
to
go
for
account.
Creations,
I,
think.
A
Any
price
above
zero
is
problematic
that
at
that
sense,
because
until
you
know
what
you're
paying
for
you
might
hesitate,
mm-hmm
Simon
I'm,
imagining
a
world
when
you
download
an
app
and
you
press
the
sign
in
and
it
instantly
create
an
account
on
the
back
and
it's
an
EOS
account
in
accounting.
You
can
actually
upgrade
at
any
time
to
become
a
real
EOS
account,
we've
paying
ram
for
it.
But
until
you
do
it,
you
can
still
use
the
app
as
if
you'll
have
your
own
account.
So
I
think.
There's.
D
A
D
Another
aspect
to
to
the
accounts
issue
for
Facebook:
each
user
also
costs
money
right.
You
pay
for
resources
for
your
users
in
in
any
any
other.
But
here
the
difference
is
that
you
ask
your
users
to
pay.
You
can't
take
the
cost
from
them,
so,
whether
it's
expensive
or
cheap,
whether
it's
on
RAM
or
environ
you
you
still
need
the
ability
to
take
the
cost
on
yourself
as
adapt,
developer
and
I
think
that's
even
a
bigger
barrier
than
whatever
it's
going
to
cost.
C
Okay,
all
right,
so
let's
talk
about
okay,
so
right
now,
let's
say
bet
dice
on
enos
right
bet:
dice
is
you
know,
sort
of
decentralized,
there's
a
contract
on
the
back
end,
but
something
could
happen
that
takes
the
domain
down
or
like
the
front
end
down
right.
It
could
be
a
rogue
actor
in
the
company.
It
could
be
the
company
itself,
it
could
be
some
legal
order,
it
could
be
some
kind
of
other.
C
You
know,
despite
even
if
the
back
and
was
still
up
right,
sure
and-
and
so
that
would
be-
that
would
be
a
big
hit
too
I'm
just
taking
bet
dice
as
an
example
here,
but
any
any
tap.
But
with
this
with
the
the
prospect
of
hosting
things
in
a
decentralized
way
from
start
to
finish
from
back
to
front,
are
we
creating
a
breed
of
DAPs
that
can't
be
shut
down?
C
That
can't
be
hurt
in
that
way
where,
if
there's
a
government
or
a
hacker
or
a
rogue
actor
or
some
some,
you
know
the
company
just
decides
to
exit
scam
are?
Are
we
creating
apps
that
can
live
on
forever,
that
are
immortal
that
can't
be
taken
down
by
a
hacked
or
a
hacker
or
the
company,
or
a
government
or
or
a
rogue
actor?
So.
D
That's
a
great
point
and
and
I
think
that
there
there
is
another
aspect
to
it,
having
the
front
and
in
a
in
a
centralized
place
where
it
not
only
can
be
taken
down,
but
the
hacker
can
can
abuse
it.
Hacker
can
replace
your
front
end
and
it
won't
help
you
if
your
contract
and
your
logic
is
safe
and
then
decentralized
and
trustless.
If
the
entry
point
of
your
application
is
something
that
someone
can
hijack
and
point
you
to
something
that
doesn't
even
talk
to
to
the
blockchain,
so
I
think
if
it's
it's
definitely
a
huge.
D
Disruption
in
in
the
way
we
can
envision
web
services,
I
am
really
excited.
I.
Think
the
first
I
can't
wait
to
have
like
the
the
first
immortal
game,
the
first
game
that
you
know
that
it's
going
to
live
forever
and
it
doesn't
matter
if
the
company
know
no
longer
exists
or
if
nobody
wants
to
to
pay
for.
D
I'm
the
way
I
see
it
is
that
eventually,
because
of
Moore's
law,
the
cost
for
providing
the
service
is
going
to
go
down.
So
I
I'm.
Assuming
that,
if
you
stick
enough,
if
you
look
enough
tokens,
there
is
a
model
where
you
can
potentially
just
very
breaking
the
key
and
keeping
this
stick
tokens
scores
who
they
will
need
to
be
another
layer
of
automatically
choosing
the
DSPs
and
things
that
the
community
is
already
talking
about.
But
but
eventually
you
can
get
to
a
point
where
the
staking
is
enough.
C
B
For
comparison
on
the
main
that
we
could
stake
CPU
to
other
accounts,
so
we
could
assume
that,
like
this
eternal
game,
if
the
adapt
service
providers,
maybe
they
increase
the
bar
of
how
many
tokens
are
required
to
be
staked
for
a
certain
amount
of
storage,
the
community
that's
playing
this
game,
they
could
basically
stake
their
tokens,
their
DAP
tokens
towards
this
these
DSPs,
and
then
they
might
just
forget
about
them
and
say
this
game
I
want
it
to
live
forever.
I'm
leave
it
I,
don't
even
want
these
tokens
anymore.
They're.
D
B
B
D
The
process
that
we're
trying
to
do
is
process
this
highly
engaged
with
the
developers
community
and
and
really
trying
to
focus
on
the
underneath
and
that's
why?
Whenever
we
progress
and
we
and
we
have
something
new,
whether
it's
a
blueprint
or
the
data
structures
or
beginning
of
a
service,
we
we
don't
wait,
we
release
it
and
we
want
to
hear
the.
B
B
D
D
D
That
knows
exactly
how
things
should
be
in
the
first
iteration.
Whenever
you
see
a
very,
very
good
product,
it's
usually
giving
this
kind
of
of
of
perception,
but
that
that
exactly
means
that
the
product
work
in
the
process
was
was
good,
not
because
there
was
a
product,
a
Steve,
Jobs
kind
of
product
genius.
That
just
knows
what
to
do.
It's
always
a
gradual,
tedious
process
and
then
result
may
look
like
magic.
So
it's
so
it's
it's
kind
of
a
misleading.
A
I
can
I
can
add
to
that
and
the
last
week
or
so
I
had
a
lot
of
calls
with
various
developers
in
different
areas,
and
they
were
talking
about
utilizing
different
part
of
the
deaf
Network
asking.
If
some
some
things
are
possible
and
I'm
I'll
try
to
throw
a
few
ideas
that
I
know
that
are
ok
to
discuss,
not
breaking
any
NDA.
We.
B
C
B
B
A
Right
in
video,
like
that,
the
next
few
months
or
yeah
up
to
a
year,
as
it
said,
branches
of
Oracle's
popping
out
in
many
different
fields
allowing
for
data
coming
off
of
the
actual
World
Wide
Web
into
the
blockchain
and
onto
different
pricing
and
randomness,
is
achieved
a
way
to
hide
your
data,
even
though
it's
on
blockchain
for
certain
period
of
time
for
various
games
or
other
features
that
we
can't
even
imagine
yet
kyc
process
unchained
by
coming
from
a
DSP,
a
payment
solution
from
a
DSP
history.
Nodes
is
no
longer
longer
an
issue.
A
B
D
For
example,
a
service
that
can
can
protect
your
key
that
can
can
have
part
of
your
multi
sinky,
where,
if
you
need
to
recover
your
your
key,
you
can
identify
with
him
and
you
basically
use
this
service,
just
as
any
other
service
ended
up
in
the
ended
up
player
network.
But
for
most
for
more
applicative
very
thing.
A
The
most
interesting
for
me
about
that
network
is
the
fact
that,
in
a
free
market
ecosystem,
you
can
build
any
service.
You
would
like,
as
a
DSP
and
as
a
developer
as
well,
on
the
other
hand,
to
be
able
to
request
a
specific
service
and
with
a
plug-and-play
effort,
after
obviously
writing
the
code
that
allows
it.
You
can
connect
it
to
the
network
itself,
and
this
will
encourage
more
developers
and
vice
versa.
It's
like
it's
an
endless
effort,
but
but
it's
an
endless
scale
as
well.
If.
D
I
imagine
the
ideal
future
I,
don't
know
if
or
if
we'll
get
there,
but
that
would
be
the
ideal
future.
In
my
perspective,
is
that
we
reached,
for
which
a
point
were
it's
not
only
seamless
and
in
Tarapur,
interoperable
in
terms
of
different
chains
and
and
resources,
but
even
code
compatible
with
classic
software,
like
the
actual
ability
to
take
source
code
that
wasn't
meant
to
run
on
the
chain
and
without
modifying
it
running
on
the
chain
like
taking
a
classic
web
application
and
with
meaning
work,
making.
B
A
B
D
I
I
think
that
that's
the
vision
getting
getting
to
a
place
where
software
development
is
is
compatible
off
chain
and
on
chain
is
seamless
and
compatible,
and
there
is
no
real
effort
and
barrier
like
absolutely
no
effort
in
there
yeah
the
end.
Switching
between
one
to
the
other
I
think
the
technology
and
the
echo
system
can
can
get
there.
I
hope,
but
I
definitely
think
it's.
It
should
go
there.
This
in
this
direction
and.
C
B
Yeah,
all
right,
so
we've
actually
I,
don't
know
how
what
episode
this
will
be
whenever
we
get
to
this
end
here,
we've
been
on
this
call
for
I
think
almost
three
hours
you
guys
broke
the
scatter
record.
This
is
gonna,
be
a.
This
is
probably
the
last
episode
of
I.
Don't
know
if
it's
a
three
or
a
four
part
series,
but
I
really
really
appreciate
everyone's
time
here.
If
anyone
has
anything
else,
they
want
to
talk
about.
Now
is
the
time
to
get
it
in.
B
D
We're
looking
to
expand
the
team
now
and
we
want
to
build
the
team,
continue
having
the
team
with
very,
very
high
caliber
and
the
best
people
we
can.
You
can
get
basically
so
we're
looking
to
expand
if
you're,
if
you
think
you're
up
to
the
challenge
and
feel
free
to
send
us,
send
us
your
details
and.