►
From YouTube: Developer Community Call #20
Description
Fluence overview, team updates, community demos.
Developer Community Calls Wiki https://www.notion.so/fluencenetwork/Fluence-Developer-Community-Calls-2733beddb3ff4e4986c4fcc830fc796d
Project updates
Twitter https://twitter.com/fluence_project
Newsletter https://fluence.network/
Telegram https://t.me/fluencedev
Discord https://fluence.chat
Fluence documentation https://doc.fluence.dev/docs/
A
A
All
right,
then,
let
me
share
screen
so
like
I
want
to
give
some
some
context
kind
of
where
we
are
where
we're
going.
We
had
this
core
team
offline
Summit
last
months
in
Georgia
in
mountains,
so
we've
been
discussing
a
lot
of
strategic
stuff
and
like
next
steps,
Division
and
and
goals
and
some
technical
details
so
I'll
follow
it.
A
So
roughly
we
basically
all
aligned
that
we're
trying
to
make
ruins
like
we're
kind
of
inspired
by
serverless
in
general,
and
we
always
when
we
think
of
fluences
are
kind
of
solution
for
the
compute.
We
think
a
lot
of
serverless
approach
to
compute
in
general,
because
it's
abstract
out
a
lot
of
complexity
and
it's
very
useful
to
think
of
how
fluent
is
going
to
be
used
by
developers
like
understood
by
developers
from
the
serverless
perspective.
A
A
So
we're
trying
to
think
on
on
like
having
serverless
as
an
example
here
and
building
our
way
in
order
to
enable
as
good
as
easy
developer
experience
for
fluence.
That
would
be
like
as
easy
to
use
as
traditional
server
so
like
to
think
of
serverless
as
a
kind
of
reference
to
what
we
do.
It's
not
necessarily
like
exactly
the
same.
What
we
do
like
exactly
the
same
thing
right,
but
it's
a
direction
of
simplifying
developer
experience
of
creating
cloud-based
tools.
A
We
can
think
of
serverless
like
effluence
having
similar
simplification
of
developer
experience
of
creating
decentralized
decentralized
code
execution.
So
we
were
thinking
like
about
sort
of
time,
Horizons
and
sort
of
power.
Should
we
think
of
experience
and
we
Define
this
shorter's
goal
like
in
November.
It
was
like
four
months
now.
A
A
So
there
were
a
lot
of
stuff
to
this
date
and
you
know,
release
something
announce
something
so
we
kind
of
think
as
the
next
biggest
Milestone
performance
in
terms
of
developer
experience
and
other
stuff
happening
in
in
next
three
months,
so
yeah
some
yeah.
This
is
kind
of
like
some
stuff
that
just
to
remind
everyone
what
you're
doing
here
so
we're
doing.
A
So
it's
basically
based
on
profiability
of
the
computation
instead
of
relying
on
reputation
on
the
brand,
but
that's
kind
of
all
of
those
things:
The,
Way,
We,
Now,
think
of
fluents
and
it's
kind
of
big
Parts.
Is
that
we're
trying
to
we're
kind
of
separating
the
developer
platform
that
we
are?
We
have
been
working
on
so
far
from
the
computational
Marketplace.
Basically,
that
would
be
the
resource
Market,
which
the
network
where
people
will
be
able
to
deploy
their
applications
in
the
future.
A
A
A
So
we
will
need
to
address
this
like
how
do
I
actually
should
it
be
any
like
a
standard
way
ways
to
connect
data
to
whatever
code
you
run,
influence,
whether
it's
like
ipfs
or
falcon,
or
RV,
or
blockchains
data,
or
like
surrounding
stuff,
like
that,
like
a
lot
of
this
stuff,
whenever
you
run
anything
on
on
fluence
as
a
analogy
to
Cloud
functions,
you
need
to
get
data
from
somewhere.
You
need
to
put
data
to
somewhere,
so
you
always
work
with
data,
so
we
need
to
really
think
on.
A
How
do
we
integrate
data
into
the
fluence,
and
we
have
I
will
not
go
into
like
all
details
about
all
the
concepts
that
may
be
new
here
we
will
be
talking
about
them
in
in
a
future
calls
and
like
releasing
more
materials
about
that.
But
basically
we
created
this
concept
of
subnets,
which
will
be
used
to
create
the
proper
access
to
data
for
the
fluency,
and
here
on
on
this
picture
like
on
the
right.
A
A
A
So
on
the
CLI
part,
is
we
actually
released
fluency
light?
Now
the
repo
is
public.
You
can
find
by
this
link.
You
can
try
it.
You
can
play
with
it.
The
idea
of
the
fluency
CLI
is
basically
as
serverless
cli's.
This
one
should
be
the
main
entry
point
for
developers
when
you
try
pullings
like
it's
super
easy.
It
helps
you
to
scaffold
the
project.
It
helps
you
to
run
tests,
it
helps
you
to
deploy,
but
it
will
be
dramatically
improved.
A
We're
going
to
work
on
CLI
next
few
months,
like
really
a
lot
and
we're
gonna
design
like
the
whole
experience
of
managing
your
project
life
cycle
with
a
CLI,
and
it
will
include
payments
so
basically
right
now,
it's
purely
development
tool
like
right
now
influence
network
is
nonsense
to
us
right.
So
there's
no
payments
at
all,
but
like
when
we
introduce
payments,
we
need
to
connect
this
CLI
tool
to
the
payment.
So,
whenever
you
deploy,
you
have
to
specify
the
way
how
you
pay
to
the
network.
A
So
for
payments
we
have
a
lot
of
new
Concepts
that
were
not
also
discussed
or
announced
anywhere
before
we're
working
on
the
like
the
whole
economics
paper,
but
like
roughly
the
picture
here
is
we
gonna?
Have
proofs
of
computation
they're
gonna
be
different.
They're
gonna,
be
they're.
Gonna
rely
on
different
parts
of
fluent
stack,
so
they're
going
to
be
proof.
A
Probabilistic
proofs
for
execution
like
what's
like
a
probabilistic
purification
of
Apple
execution,
they're
gonna,
be
on
proofs
for
marine
Institution
and
we
are
researching
towards
proofs
of
computer
capacity
as
well,
because
we
want
to
when
we
build
the
economics
economic
part
of
the
network.
We
want
to
incentivize
not
only
executing
the
like
real
jobs,
but
also
like
incentivizing
the
bringing
more
capacity
to
a
network,
even
if
it's
not
busy
with
with
some
real
jobs.
So
we
want
to
incentivize
the
capacity
that.
B
A
Join
to
the
network,
because
we
want
to
build
to
be
like
you
know,
big
compute
Network
that
is,
and
that
can
attract
users
because,
like
it's,
you
know
it's
widespread.
It's
has
a
huge
capacity
and
stuff
like
that.
So
we
have
some
Concepts
here.
I'm.
Also
not
gonna.
Go
into
a
lot
of
details
about
that.
A
The
what
we're
gonna
we're
gonna
have
the
on-chain
compute
Marketplace
for
providers
to
be
able
to
register.
They
will
be
able
to
enter
into
deals
with
customers
and
they
would
have
to
provide
proofs
of
their
work
when
they
serve
the
the
work
expected
by
the
by
the
contract
in
order
to
withdraw
money.
So
in
order
to
earn
money,
they
would
have
to
prove
that
they
actually
working
and
from
the
developer
perspective
it's
all
we
will
link
to
the
tooling,
so
it
will
be
linked
into
CLI.
A
So
for
the
user
it
would
be
very,
very
similar
how
they
using
the
web
to
Cloud.
So
you
know
the
connect
account
they
scaffold
projects
they
deploy.
They
manage
their
deployments
like
all.
This
financially
should
be
doable,
yeah
and,
and
so
finally,
this
is
how
we
see
the
the
next
big
kind
of
big
steps-
big
deliverables,
that
we're
going
to
have
in
in
three
months.
A
A
We
dramatically
improving
developer
platform
by
unifying
all
the
experience
with
improved
CLI,
and
it's
going
to
be
it's
gonna
be
documented,
so
we're
gonna
have.
We
will
have
the
iteration
on
the
documentation,
so
we'll
get
a
better
communication,
materials
and
education
materials
and
if
we
lucky
and
have
a
have
time,
we're
gonna
deliver
one
of
the
use
cases,
but
that's
something
it's
still
under
construction
and
a
lot
of
discussion.
So
it's
and
a
bonus
point
we'll
see
how
it
goes
in
next
month.
C
A
A
Allow
you
to
basically
have
EVMS
or
contracts
that
call
the
Rascal
that
executed
on
on
the
near
node.
So
that's
option
number
one.
The
option
number
two
is
fbm,
which
is
Falcon
VM.
They
have
also
both
evm
and
rust,
and
volume
execution
there.
So
we're
looking
into
it.
It's
a
little
bit
poorly
I
know
that
they
are
targeting
a
full
featured
evm
to
be
released
in
in
also
around
in
Denver,
but
like
we
need
to
figure
this
out
at
the
moment.
A
Yeah
so
Manu,
asking
in
in
the
chat
if
I
can
share
the
link
to
the
paper
of
food
processing.
Not
yet
so
it's
right
now.
The
document
that
is
work
in
progress
and
but
roughly
basically,
the
idea
of
processing
is
processing
means
like
processing
particles
like
Aqua
earthquake,
like
requests
generated
by
Aqua,
so
the
whole
network.
What
it
does
basically
is
like
a
process,
the
particles
right
and
then
particles
do
some
function,
calls
from
the
peers,
which
is
Marine.
A
A
That
would
basically
Define
which
particles
have
to
be
submitted
on
chain
for
verification,
so
we're
gonna
verify
on
chain,
but
we're
not
going
to
verify
every
particle
so
like
because,
like
particles
like
requests
right
like
they're
in
in
the
live
Network,
there
could
be
like
thousands
of
applications
and
billions
of
particles
right
so
and
if
you
like,
it's
just
economically,
doesn't
make
any
sense
to
verify
all
of
them
by
some
external
actors.
So
we
got
to
this
model
of
probabilistic
verification
where
the
onshine
randomness
says
Okay,
you
can
earn
money.
A
If
you
submit
a
particle
on
chain
that
fits
certain
criteria
and
nodes
just
have
to
find
such
particles
among
what
they
have
and
I'm
I'm
on
what
they
serve
during
the
the
time
they
serve
the
application
and
then,
if
they
submit
it,
notes,
who
basically
participated
to
create
this
particle,
they
get
rewarded.
If
this
particle
is
valid.
A
So
it's
a
I
also
like
don't
want
to
go
too
deep
into
details,
because
it's
some
at
the
moment
is
is
not
like
a
fully
defined
concept.
But
it
is
a
little
like
a
bit
similar
to
things
like
probabilistic
payments.
I
think
some
projects
were
experimenting
with
this
earlier,
like
in
earlier
years,
like
I,
think
life
peer
did
that
and
who
else
was
it
like
swarm,
I
think?
But
it's
it's
like,
basically,
like
all
all
always
the
same
system
when
you
have
some
way
to
Define.
A
Some
way
to
define
a
system
when
you
do
not
verify
every
job
piece
you
only.
You
create
the
rules
that
if
everyone
behaves
honestly,
they
will
have
to
only
submit
for
verification
some
parts
of
their
job
in
order
to
earn
money
and
if
they
submit
something
incorrectly,
they're
gonna
lose
some
State.
Something
like
that.
So
that's
sort
of
like
probabilities,
Pro
source
of
probabilities
in
here.
C
C
C
Can
you
see
my
screen
Yeah
so
basically
there's?
First,
there's
a
renderer
where
you
set
your
phone
to
the
phone
call
or
the
sorry.
The
phone
text
is
your
phone
number
and
then
you
input
the
phone
and
it
writes
the
peer
to
local
storage.
So,
basically,
everything
I'm
doing
right
now
is
just
with
local
storage.
There's
no
blockchain
Associated.
C
So
anyone
can
run
this
and
it's
just
using
the
fluence
network
for
the
time
being
and
then
the
idea
is
that
it
would
render
on
the
screen
and
you
would
share
by
clicking
on
the
the
spirit,
whatever
we're
calling
it
a
particle
and
then
the
cards
get
shared,
which
I'll
show
you
in
a
second.
But
that's
the
basic
premise:
that's
like
I
think
the
cool
thing
that
could
be
replicated
for
other
people
in
the
fluids
ecosystem.
C
C
That's
a
deck
that's
being
developed,
but
the
idea
is
to
have
many
different
types
of
decks
that
you
can
incorporate
into
the
mix.
Would
someone
like
to
choose
which
deck?
This
is?
Basically,
if
you
don't
know,
tarot
cards
tarot
cards
are
useful
tools
and
affordances
for
guiding
yourself
spiritually
and
the
rider
weight
deck.
The
with
the
magician
here,
there's
not
that
much
explainer
stuff
right
now,
typically
I'm
thinking
that
it's
more
for
like
people
that
are
really
involved
in
the
ecosystem.
C
To
for
this
to
be
marketed
towards
for
the
start
and
then
it'll
be
more
explainable.
As
you
know,
more
people
jump
on
or
want
to
get
involved
or
play
around,
but
the
magician
deck
is
a
little
more
externally
focused.
It
has
people
associated
with
it.
It
has
like
events
or
types
of
collaboration
and
then
there's
this
other
deck,
which
is
more
associated
with
like
utfs
or
little
logos
generated
some
generated
from
Ai,
and
it's
a
deck
that
I'm
putting
together
right
now
with
some
other
people.
C
Let's
do
the
right
one,
so
there's
only
five
cards
in
this
deck
right
now,
but
there
will
be
more
up
to
15
in
the
future.
So
this
is
not
fully
integrated,
but
the
idea
is
for
there
to
be
for
this
deck
because
it's
I'm
developing
with
some
other
people,
it's
a
stream
of
approximately
five
cents
per
hour,
which
equates
to
about
36
dollars
I
think
per
month.
C
I
could
be
wrong
with
that
calculation,
but
I,
just
like
the
fact
that
I'm
from
Canada,
so
it
just
on
the
five
cent
nickel
there's
a
beaver
and
beaver
Stanford
stands
for
teamwork
in
this
sort
of
spiritual
realm.
So
I
think
that
that's
significant,
so
yeah
we'll
pull
the
cards.
Hopefully
this
works
yeah.
It
works.
C
C
So
this
is
where
there
would
be
an
integration
with
a
protocol
like
a
liquidity
protocol
like
AP
wine
or
some
other
thing,
but
right
now
it
has
a
cool
feature
where,
with
ap
wine,
we're
basically
making
a
steak,
so
I
can
put
money
down
on
this
community
stroll
and
if
I
want
I
can
redeem
the
future
interest
of
the
the
yield
generated
from
the
protocol.
So
if
I
had
a
goal
in
mind,
like
let's
say
after
I
take
my
community
stroll
and
I
decide
that
I
want
to.
C
C
I
can
deposit
some
money
and
right
now
this
doesn't
work,
but
it
is
connected
like
it
pulls
the
different
futures.
Well,
maybe
it's
not
connected
right
now,
then.
Maybe
there
might
be
an
error
in
there
yeah
there's
an
error,
that's
okay!
It
just
it
would
just
pull
the
number
of
different
liquidity
pools,
but
it'd
be
cool
right
now.
Just
I
want
to
mention.
You
know
coming
from
the
taros
there's
only
15
pools
in
the
AP
and
wine
ecosystem
and
it'd
be
cool.
C
If
there's
another
pool,
because
you
know
that
would
make
it
16
and
16
represents
the
tower
and
or
17
would
be
better
for
the
star,
but
the
15
represents
the
devil.
So
you
know,
maybe
maybe
people
want
that
or
maybe
we
want
more
liquidity
pools.
Who
knows
so
I'm
going
to
skip
this
part
and
I'm
gonna
go
to
my
gallery
where
I've
chosen
from
past
card
polls
in
a
way
that
cyclically
brings
things
together
with
the
different
card.
C
Decks
and
I
can
see
my
Arcana
light,
which
basically
represents
like
how
much
it's
kind
of
like
a
health
metric
for
an
individual
if
they're
practicing
tarot
and
they
want
to
get
online
with
like.
Oh
how
you
know
how
staked
am
I
in
the
past
or
in
the
present
or
in
the
future.
So
they
go
down
as
you
stake
more
cars
into
each
slot.
C
So
when
you
first
pull
a
car
and
you're
fresh
it'll,
just
it'll
fill
up
yeah,
so
I
can
email.
My
the
cards
to
myself
I
won't
show
that
for
now,
but
basically
it
just
does
a
a
download
and
uploads
to
your
email
and
it'll
have
the
the
time
that
you
pull
the
cards
that
you
can
share
as
well.
So
I
can
I
can
do
this
right
now
or
I
can
share
via
text
where
I
can
I
guess.
I'll
just
use
my
phone
number
for
now.
C
C
C
C
Now,
I'm
not,
but
what
I'm
doing
is
I'm
using
a
web
2
server,
which
ideally
would
be
cool
like
I,
was
like
that
was
a
bit
of
the
preface
of
the
start
like
if
this
was
a
hosted
application
on
a
computer
and
it
can
be
hosted
in
a
you
know,
secure
way
where
the
the
connection
to
the
browser
is
authenticated
and
you're.
Not
sharing.
You
know,
text
messages
over
the
line
with
with
affluence.
Node
I
think
that
would
be
pretty
cool.
A
D
A
C
I
think
that
there's
I
think
the
sharing
thing
is
really
cool.
So
when
I
just
get
this
link,
I
can
send
it
to
you
and
you
guys
or
you
folks,
can
all
try
downloading
as
long
as,
basically
when
I
click
this
connect
button,
it
registers
it
does
a
register
to
the
the
hello
peer
example
that
you've
shared
online
and
then,
when
you
click
like
these
are
just
path
from
past
things,
but
it
when
you
click
on
the
spirit
see
if
it
came
in.
A
C
So
it
should
work
as
long
as
I
click
this
connect
button
and
within
a
certain
time
frame,
I'm,
not
exactly
sure.
Maybe
this
is
a
good
question
for
the
team
like
when
I
click
this
connect.
Now,
if
you
go
to
that
page,
if
you
open
it
up-
and
you
click
on
at
the
bottom,
I
think
that
there's
a
Rook,
a
chess
piece
or
a
horse
night.
C
Okay,
and
if
you
click
on
at
the
bottom,
click
on
the
the
the
night
sign
the
chess
piece
it
did
open.
Can
you
okay?
We've
got
mode
ball
here.
Sorry,
if
I
I
didn't
say
your
name
properly.
I
do
apologize,
but
I'm
just
wondering
if
the
cards
were
able
to
display
it's
just
cool
if
it
was
a
live
thing
that
worked,
I've
I've
only
ever
tested
with
one
other
person,
so
it's
kind
of
a
cool
cool.
A
Well,
I
mean
that's
possible
if
you
do
it
in
like.
If
you,
if
you
have
the
adapter,
you
basically
need
to
have
some
node
that
have
the
wasm
adapter
to
external
text.
Api,
like
some,
you
know
you
will
not
avoid
having
some
web
tool
Legacy
API.
That
provides
you
access
to
send
in
text
messages,
but
you
can
use
wounds
to
discover
and
call
this
API
like
if
you
have
the
influence
adapter
to
that.
C
C
Oh
okay,
cool
yeah,
that's
great
yeah!
If
I
did
that
in
Rust,
that'd
be
great
yeah
cool.
Thank
you
very
much.
Yeah
I
won't
take
any
more
time,
but
I
hope
the
project
is
called
read
and
hopefully
it
will
be
distributed
to
the
clarinet
I'm
having
issues
with
hosting
so,
alternatively
it'll
be
distributed
through
the
urban
Network
most
likely
to.
But
the
idea
is
to
make
it
and
get
enhance
as
many
people
as
possible.
So
really
I'm,
just
I
have
a
bit
of
censorship
issues
with
my
hosting
providers.
A
C
E
Okay,
so
hello
I
am
from
Team
Frost
game,
so
my
name
is
Mohamed
and
my
other
team
is
also
TN,
as
you
can
see
TL,
so
we
are
from
Malaysia.
So
I
would
like
to
say
thank
you
to
the
fluence
team
for
organizing
Alberto
hackathon,
and
actually
this
is
our
first
step
entry,
a
web
trick
hackathon
to
be
honest,
so
so
yeah.
So
the
question.
The
problem
statement
that
was
given
during
the
hackathon
was
to
create
a
tool
or
a
we'll
go
to
create
a
tool
or
a
pattern.
E
So
during
our
time
using
fluence,
we
do
notice
that
the
aqua
has
some
difficulties
to
run
with
certain
dependencies,
and
we
were
thinking
like
how
about
we
just
use
slice-
okay,
oh
in
between,
so
that
the
client
side
can
communicate
or
use
with
the
fluence.
So,
as
you
can
see
here,
this
is
the
architecture
flow.
Oh
sorry,
I
forgot
to
share
my
screen
where
she
scream
and
screenshot.
E
E
B
E
And
then
here's
a
demo,
so
the
demo
that
we
want
to
show
our
idea
is
that
for
the
cross
game
is
that
there
are
two
separate
games
which
is
created
using
Facebook,
so
phaser
uses
this
we're
called
package
manager
called
the
I
can't
remember
the
name,
but
then
we
notice
at
that
time.
It
has
some
difficulties
to
run
with
aqua
and
inside
here
we
also
have
a
decentralized
profile.
So
this
is
okay.
E
E
E
It
will
be
affected
throughout
all
the
games
are
connected
through
the
soccero,
so
to
be
honest,
for
it
doesn't
have
to
be
so.
Okay
or
it
can
actually
be
also
other
stuff,
maybe
for
the
for
the
between.
Maybe
it
can
be
an
API
and
I
just
like
it
doesn't
have
to
be
so
available.
So
the
reason
why
we
do
this
is
just
to
show
that
there's
a
way
to
make
it
easier
for
other
Game
Dev
or
for
other
client
side
to
be
able
to
use
aqua
and
fluence.
E
Actually
so
yeah,
that's
actually
the
for
the
demo.
So
you
can
see
here
the
process
inside
the
aqua
have
on
the
process
of
fluids
inside
here,
and
one
other
reason
also.
Why
we
want
to
use
fluent
is
because
we
are
amazed
at
the
feature
that
is
that
fluence
or
Aqua
is
able
to
make
parallel
requests,
which
we
find
amazing
to
be
honest
and.
A
E
E
Okay,
so
Facebook
the
game
that
we
use
is
phases
so
to
run
Facebook
we
are
using.
We
need
to
use
what
we
call
the
package
manager
called
webpack.
So
when
we
compile
the
game
and
when
we
try
to
implement
Aqua
inside
it,
we
notice
that
the
fluence
doesn't
work
with
webpack.
It
shows
an
area
so
from
there.
We
know
so
when
we
found
this
area.
So
it
becomes
a
problem
for
us
to
to
directly
implement
the
fluoroso
aqua
inside
the
game
itself.
E
So
that's
why
we
make
an
intermediate
between,
in
a
bridge
where
so
Kio
becomes
the
one
to
call
the
services
from
the
fluence
network.
So
when
game
one,
let's
say
when
game
one
wants
to
connect
to
the
mongodb
through
the
using
aqua,
so
the
gamer
will
send
the
request
to
soccer
at
all
and
then
it's
okay.
Oh,
we
run
the
aqua
to
search
for
this
service
through
the
flows
Network.
E
E
Yeah,
so
we
to
be
honest,
we
did
send.
We
did
us
the
community
inside
the
school
about
this,
but
then
it
seems
that
there's
no
there's
no
answer
about
this
one.
So
that's
why,
for
now
we
run
it
with
okay,
oh,
if
I'm
not
mistaken,
it
says
that
inside
webpack
it
cannot
handle
big
integer
number,
if
I'm
not
mistaken,
so
yeah.
That's
why
we
decided
to
use
this
kind
of
pattern
to
Implement
how
to
use
a
fluence
with
this.
They
call
this
client
sites.
A
E
C
E
E
Okay
and
also
actually
I
make
an
article
about
how
to
implement
Circle
influence.js,
as
you
can
see
here
so
inside
here,
also
make
a
record
a
brief
explanation
on
what
fluency,
so,
if
possible,
maybe
I
can
ask
from
us
some
feedback
from
the
fluency
we're
doing
my
understanding
about
fluence
is
correct
or
not.
Is
it
possible?
Maybe
I
can
share
dealing
here.
A
E
Can
I
ask
a
question
sure
clearly
right
now,
I'm
trying
to
explore
about
our
clip
FS?
So
then
I
also
currently
trying
right
right
now
I'm
trying
to
deploy
my
own
aquap
FS,
because
I
tried
to
make
some
modifications
I,
try
to
add
some
existing
ipf
SLI,
but
currently
I'm.
Having
trouble
to
understand
on
how
for
me
to
deploy
my
own
service
of
Aqua
ipfs.
So
is
there
maybe
like
what
you
call,
maybe
a
description
or
maybe
a
tutorial
on
how
I
can
run
my
own
Accords
Maybe.
D
There's
no
tutorial
per
se,
you
can
follow
tutorials
on
how
to
deploy
services
in
general.
It's
all
the
same
mechanics
or
you
can
try
to
use
fluency
CLI,
which
has
a
rather
big
readme
and
usually
guides
you
through
deploying
services.
But
there
are
some
harsh
edge
cases
you
might
run
into
so
does
two
are
your
best
options
right
now,
if
you
want
to
deploy
on
the
network
on
the
existing
nodes,
if
you
want
to
deploy
on
your
notes,
that's
a
different
story
and
might
be
easier
for
you.