►
Description
Decentralized RPC (FRPC) significantly reduces dAPPs' single-point of failure and verification risks without requiring changes to existing dApp code. Moreover, enterprises can implement a wide range of control algos further decentralizing their dApps.
A
Hello
I'm
further
from
fluence
labs
and
today,
I'm
going
to
be
talking
about
managing
business,
continuing
to
risk
with
the
centralized
rpcs.
So
in
the
previous
talk,
Alexander
told
us
about
how
Enterprises
could
sort
of
on
board
with
web3
Technologies
and
I'm
gonna
talk
about
the
Enterprises
who
already
like
onboard
it
in
the
web,
3
and
created
the
Rd
apps,
and
how
can
how
and
how
they
can
manage
their
risks
and
their
business
continuity
risks
with
decentralized
rpcs,
so
yeah.
Let's
start
so.
First
of
all,
let's
talk
the
apps.
A
B
A
A
So
your
interest,
the
Reliance.
You
rely
on
some
third
party
to
sort
of
manage
this
infrastructure
for
you,
so
yeah
and
also
there
is.
There
is
a
thing
called,
so
those
risks
are
associated
with
the
centralized
providers.
So
is
there
basically
any
way
to
manage
those
risks?
Is
there
any
way
to
sort
of
work
with
them.
A
And
those
are
not
the
only
risks,
there's
there's
also
some
regulatory
risks.
So,
as
you
know,
there
were
recent
events
when
SEC
just
chased
the
companies
who
issued
the
apps-
and
they
inquired
about
their
native
token-
and
they
tried
to
you-
know,
try
to
sort
of
make
them
make
those
make
their
tokens
removed
from
the
centralized
exchanges
they
can.
They
wanted
to
call
their
token
a
security.
A
A
B
C
A
A
Okay,
and
so,
if
we
take
a
look
at
the
first
at
the
first
way,
so
it
basically
it
gives
us
a
lot
of
control.
But
we
have
to
handle
all
the
calorim
and
fill
our
Solutions
inside
our
inside
of
our
our
app.
We
have
to
sort
of
create
all
that
logic
ourselves
and
it
can
be
really
cumbersome
and
it
creates-
and
it
makes
the
idea
app
very
coupled
to
this
this
code
and
we
have
lots
of
complexity
to
manage.
A
A
For
your
app
so
meet
fluence
fluence
is
the
decentralized
serverless
compute
platform,
so
it's
verifiable
and
trustless
it's
Unstoppable
and
suddenly
ship
resistant,
it's
fault,
tolerant
and
it's
a
compute
platform.
So
this
basically
allows
you
to
run
your
apps
in
decentralized
cloud
with
it
replicates
the
cloud
stack
and
it
allows
you
to
build
decentralized
apps
easily.
So,
basically,
if
you
need
an
analogy,
it's
a
file
coin
in
compute,
so
white
fluence.
A
So
it's
basically
a
platform
that
allow
you
to
create
the
to
library
costs
and
create
your
and
create
the
backends
from
your
deferred
apps.
So
there
is
no
controlling
party,
it's
controlled
by
a
Dao,
no
vendor
login.
You
can
basically
switch
any
provider
that
uses
fluence
or
provides
compute
refluence.
It's
secure.
There
is
a
zero
trust,
security,
it's
open
source
and
it
doesn't
require
no
identity
in
okyc.
So
no
one
can
like
cancel
your
the
app,
but
what
about
the
risk
in
rpcs?
A
So
this
is
the
thing
we've
created
based
on
fluence
network.
It's
called
frpc.
So
basically
it's
a
decentralized
inferior
based
on
fluence.
It's
a
super.
Convenient
super
convenient
Showcase
of
what
is
possible
with
fluence
and
it
allows
you
to
deploy
simple
self-hosted
RPC
based
on
fluence
and
connected
to
your
DF,
configure
RPC
providers
and
then
basically
run
any
Quorum
load,
Billings
and
RPC
methods
on
top
of
it
and
it's
available
on
fluence
testnet
right
now.
So
you
can
like
scan
this
QR
code
and
find
the
the
source
code
of
this
app.
A
Your
web
3D
app
front-end
and
you
basically
replace
the
centralized
RPC
endpoints
with
our
self-hosted
HTTP
Gateway.
So
it's
very
simple:
it's
just
a
very
simple
app
that
you
can
run
on
anywhere
and
it
uses
fluence
decentralized,
Network
to
access
RPC,
endpoints,
centralized
RPC,
endpoints
and
load
balance
and
run
Quorum
on
them.
So
you
can
basically
validate
the
output
that
you
get
from
there
before
sending
it
to
your
D
app
right
and
this
basically
a
big
deal.
A
So
you
do
not
modify
your
the
app
in
any
way
and
you
still
just
redirect
it
to
a
special
self-hosted
Gateway
or
to
affluence,
hosted
Gateway
and
basically
you
get
a
real
real
decentralization.
You
do
not
depend
on
any
one
on
any
single
RPC
endpoint
solution
and
you
just
work
with
your
d-app
and
get
all
the
benefits
and
it's
really
cost
effective.
A
A
A
A
C
C
A
A
A
A
A
A
And
it
just
gets
got
the
current
block
number
and
the
transaction
details
and,
as
you
can
see,
the
app
itself
doesn't
know
anything
that
it's
run
against
the
centralized
serverless
networks.
Compute
Network,
it's
a
simple
drop-in
replacement
for
for
your
existing
the
apps,
and
we
basically
have
solved
the
and
removed
the
risks
of
centralized
rpcs.
Now
you
can
run
the
Quorum
and
the
round
robin
against
those
RPC
endpoints,
and
you
can
make
sure
that
you're
not
dependent
on
a
single
RPC
provider.
You
don't
need
to
modify
your
d-app
and.
A
So
basically,
we
we
just
get
a
solution
for
this
problem.
So
what
else
can
you
do
with
fluence
platform
and
after
you
have
implemented
the
the
centralized
or
PC?
So
the
first
thing
you
can
utilize
fluence
to
create
the
back
end
for
your
app
centralized
backend.
So
you
can
you
not
only
can
deploy
this
sample
a
simple
frpc
app
to
influence
you
can
deploy
any
kind
of
or
any
kind
of
app
backend
to
it.
A
So
right
now
fluent
supports
rust
that
can
be
compiled
to
awesome
as
a
the
language,
but
we
are
going
to
introduce
support
for
Python
and
JavaScript
so
right
now
there
is
a
test
net
running
and
you
can
access
the
test
net
and
basically
there
is
a
way
to
to
run
different
small
apps
that
are
available
in
our
example
repository
against
it.
So
we
are
currently
in
a
test
net
stage.
We
are
going
to
release
to
mainnet
in
Q4
this
year.
B
A
So
regarding,
thank
you
for
the
question
regarding
the
latency,
so
it's
usually
adds
about
500
milliseconds
of
latency,
but
it
depends
on
the
algorithm
that
you
use
to
sort
of
query
those
endpoints.
So
if
you
chronic
War
Room
against
multiple
endpoints,
it
will
take
more
time,
and
if
you
do
the
just
a
round
robin
or
you
just
query
the
first
endpoint
that
actually
answers
you,
then
it's
will
be
much
faster
and
you
will
be
able
to
the
basically.
You
will
not
be
able
to
notice
any
any
latency
issues
with
it.
A
A
C
Yeah
I
I
was
wondering
how
how
cost
competitive
it
is
right
now
compared
to
to
Imperial
Alchemy,
choose
influence
for
for
RPC
endpoints
right,
because
I
I
assume
that
the
cost
is
indexed
on
the
value
of
the
token
for
for
compute.
So
right
now,
how
would
you?
How
would
you
say
how
much
sir,
what's
what's
the
the
cautious
solution
using
Alchemy
using
your
solution.
A
You
still
have
to
pay
for
the
RPC
endpoints,
but
the
fluence
will
allow
you
to
sort
of
skip,
skip,
implementing
the
round
robin
or
Quorum
Solutions
in
your
app
and
Coast
wise.
We
are.
We
are
launching
the
network
with
the
the
centralized
with
affluence,
Lambda
showcase
or
basically
we
allow
running
Lambda
functions
and
applications
like
frpc
on
it
and
you
just
pay
for
each
execution
and
it's
it's
a
fraction
of
what
you're
paying
if
you
are
doing
that
on
Amazon,
Lambda
or
gcp
or
any
other
platform.
A
B
A
A
Okay,
so
right
now
now
we
can
talk
a
little
bit
about
so
how
actually
fluence
Works.
So
we
so
as
if
you
can
see
there
are
like
traditional
Cloud
backends
that
that
use
centralized
apis.
So
we
use
a
set
of
decentralized
services
that
can
be
choreographed
in
terms
into
and
stacked
together,
without
like
Central
Authority,
but
the
with
the
decentralized
network.
And
basically
you
can
write
decentralized
backends
for
daos.
You
can
write
solutions
that
allow
you
to
just
move
any
kind
of
backend
to
this
network.
A
Okay
and
I.
Think
so.
I'm
done
with
this.
So
to
summarize,
frpc
is
just
a
Showcase
of
what's
possible
with
fluence
and
you
can
decentralize
your
whole
back
end
by
moving
it
into
a
centralized
permissionless
network,
and
you
can
easily
audit
and
share
interviews
review,
distributed,
algorithms
that
are
created
with
aqua.
It's
language
that
we
have
created
to
sort
of
write
those
algorithms
and
you
can
write.