►
From YouTube: Developer Community Call #23
Description
Welcome to the monthly community call with the Fluence developer community ⚡️
This time we're going to discuss some of the lates updates, the future plans and have a Q&A session
Join the call via link: https://us06web.zoom.us/j/82025547767
_________________
Join the community!
Discord 🔹 https://fluence.chat
Telegram 🔹 https://t.me/fluence_project
Follow Fluence!
Twitter 🔹 https://www.twitter.com/fluence_project
Build with Fluence!
Quick Start🔹 https://fluence.dev/docs/build/quick-start/
Tutorials 🔹 https://fluence.dev/docs/build/tutorials/setting-up-your-environment
Docs 🔹 https://fluence.dev/docs/build/introduction
A
A
A
A
B
Regarding
our
agenda
for
today,
so
today
we
will
have
a
small
check-in.
Then
I'll
tell
you
about
the
highlights
of
the
development
process.
That's
what
we're
having
of
new
features
and
new
updates.
We
are
running
out
after
that.
We
will
have
rtom
who
is
leading
the
development
of
our
CLI,
with
the
updates
on
CLI
development
and
the
eqra
session
after
art,
and
we
will
have
Mikhail
Warner,
who
will
present
the
distributed,
choreography
and
composition
working
group.
It's
one
of
our
latest.
B
A
B
Okay,
so
then,
let's,
let's
talk
about
some
updates
regarding
our
latest
developments,
so,
first
of
all
a
recipe
or
the
the
components
which
is
basically
the
basic
component
of
our
Network,
the
node
was
updated
from
async
STD
to
Tokyo.
So
what
what
does
it
allow
the
developers
to
do?
It
allows
better
debugging
tools
and
the
enhanced
ability
to
diagnose
what's
actually
happening
so
today,
on
the
call
we
have
Nick,
who
was
doing
his
development.
So
if
you
have
any
questions,
you
can
ping
him.
B
He
is
the
guy
who
made
this
possible.
Thank
you.
Nick.
We
also
updated
Marine,
CLI
and
SDK
Marine
Sila
is
a
two.
That's
well
underground,
very
massive
fixes.
We
improved
of
equality
of
version
handling
from
cargo
lock.
We
resolved
issues
with
some
commandlets
and
overall
made
it
much
nicer
and
smoother.
B
There
was
also
I
think
it's
with
we
didn't
announce
before,
but
we've
changed
the
naming
of
fluence.js
component.
So
previously
it
was
called
Flynn's,
JS
and
right
now
we
renamed
it
to
JS
client
to
better,
let's
say,
Telegraph,
the
our
understanding
of
it.
So
it
will
not
be
like
the
full-fledged
JavaScript
node.
It
will
be
a
client
component
which
will
allow
developers
to
call
their
backend
code,
which
is
deployed
to
fluence
network
from
the
browser.
B
Okay.
So
what
else
do
we
have
regarding
the
tune
updates?
So
the
machines
team
have
released
the
new
air
tools,
so
air
is
our
Aqua
intermediate
representation.
B
Some
of
our
tools
that
previously
like
individual
tools,
air
trace
and
airbt5,
were
United
in
the
single
tool
called
air
and
it's
really
simplified
the
process
of
working
with
air
scripts.
It
provides
enhanced
functionality
and
it
actually
can
beautify
the
air
script
that
you've
generated.
So
it's
more
readable
and
it
also
has
new
tracing
capabilities.
So
for
more
info.
You
can
check
out
the
this
tool
in
our
GitHub
representator,
so
we
also
release
the
new
version
of
M
Rebel
Tool.
B
B
Another
update
is
that
we've
finally
released
our
beautiful
grafana
dashboards,
along
with
our
raspberry
register.
Also,
we
initially
we
created
them
to
manage
our
network
and
we've
made
a
lot
of
adjustments
to
them
and
we're
using
them
then
day
to
day
when
we
support
and
maintain
our
Network.
B
So
right
now
we
released
those
grafana
dashboards
to
public,
so
in
the
raspberry
distribute
you
can
see
the
deploy
the
new
directory
deploy
where
you
can
see
like
Docker
compose
files,
and
you
can-
and
there
is
also
a
readme
which
describes
the
process
of
how
to
install
fluence
node,
along
with
our
new
and
beautiful
grafana
dashboards.
B
So
this
is
probably
it's
regarding
the
tooling
updates
right
now
we
have
enough
on
our
Callum.
Can
you
hear
us.
B
So
please
share
your
screen.
D
D
When
some
event
happens
now
they
are
supported
with
the
fluency
line
you
can
generate
spell
which
says
the
command
fluent
spell
new,
and
then
you
can
see
that
two
files
are
generated,
one
is
a
config
and
the
other
one
is
aqua
and
you
can
write
any
app
where
you
want
there
and
our
configure
and
the
silai
currently
supports
only
clocks.
D
So
basically
it's
kind
of
like
Crown
jobs.
We
had
the
concept
similar
to
this
before
called
the
schedule
Scripts.
So
the
config
looks
like
this.
Nothing
I
think
everything
is
clear.
Here
you
can
choose
the
function,
you
can
choose
the
file
in
which
this
function
resides.
D
You
can
choose
the
initial
arguments
to
the
function
and
you
can
set
when
and
how
often
do
you
want
the
script
to
be
executed
and
you
can
deploy
together
with
your
whole
application
and
of
course
you
can
read
more
about
this
config
in
the
docs
of
fluency
or
just
by
exploring
it
in
vs
code
with
yaml
extension.
We
have
documentation
available
right
there.
D
D
I
was
switching
to
pnpm.
Just
so
our
builds
are
faster.
The
development
is
faster
and
switching
to
pre-built
binaries
for
marine
and
the
marapple,
so
this
is
currently
only
working
in
testing
environment,
but
we
expect
to
at
some
point
give
this
functionality
to
our
users,
so
they
don't
have
to
build
these
components
by
themselves
on
their
computers
and
then
can
so
they
can
just
download
the
binaries
and
save
time
and
another
big
part
of
all
this
conversation
about
reliability.
Was
this
file
versions
Json
that
we
added
to
our
wrapper.
D
Currently,
we
hook
up
all
our
processes,
so
this
file
is
updated,
properly
and
test
it.
So
this
file
contains
all
our
components
and
on
each
release
they
will
be
tested
and.
D
And
that's
how
we
can
make
sure
everything
works
together,
so
this
file
is
currently
hard
coded
inside
the
specific
versions
of
fluency
line.
So
you
don't
have
to
specify
the
versions
of
dependencies
valenciano
anymore.
D
So
if
you
want
to
make
sure
your
project
always
works
and
is
compatible
with
all
the
versions
of
all
the
numerous
components
we
have
at
fluence,
you
can
just
specify
this
property,
and
then
CLI
will
complain
to
you
that
you
need
to
upgrade,
or
just
it's
better
to
use
that
version,
because
it
was
tested
with
that
version
and
so
on,
or
also
you
can
overwrite
some
of
the
dependencies
if
you
want
to
or
install
your
own
as
previously,
so
this
functionality
remains
unchanged
and
is
still
available.
D
If
you
want
to
know
all
the
versions
you
can
use
fluence
dependency
versions
command
with
this
command.
You
will
see
the
versions
that
I
showed
you
in
versus
Json.
It
also
includes
a
raspberry
image,
so
you
are
able
to,
for
example,
spin
up
some
appears
locally
and
test
against
that
to
make
sure
everything
is
compatible.
D
Also,
this
command
will
show
you
internal
components
of
CLI,
which
are
influence.js,
client
and
other
stuff,
or
also
one
of
the
things
we
did
is
we
removed
fluence
lock
file
because
it
made
things
more
complicated.
Now
you
can
just
specify
exact
versions
if
you
want
to
overwrite
them
or
use
them,
but
mostly
it's
expected
that
you
just
don't
have
to
think
about
dependencies
and
you
can
just
install
the
latest
version
of
CLI
and
you
are
good
to
go
another
one.
D
Is
you
can
use
Global
flags
for
installing
or
overriding
some
of
the
components
globally
and
and
the
Imports
array
influence
yaml,
where
you
can
specify
the
aqua
that
that
you
want
to
be
available
to
be
import
imported
in
your
Aqua
script
also
did
a
lot
of
refactoring
but
fixes
and
improvements.
D
Some
of
them
are
breaking,
but
hopefully
it's
pretty
easy
to
fix.
So
their
name
is
one
of
them.
Also
I
worked
a
lot
on
improving
our
messages
and
just
to
listen.
The
most
recent
features.
D
Now
the
silai
will
tell
you
that
the
new
version
is
available,
so
this
is
cool
another
one
is
the
test
for
influence
workers
deploy.
Also,
there
is
a
no
build
flag
if
you
don't
want
to
build
before
deploying
for
some
reason.
Sometimes
it
might
be
helpful
another
one.
You
can
now
use
both
yumu
and
yamo
for
your
extensions
for
conflicts
before,
because
previously
we
only
yaml
would
work
now
you
can
use
them
interchangeably
and
everything
about
the
most
recent
features
is
related
to
the
unstable
versions
of
CLI.
D
So
you
can
install
the
unstable
one
to
check
it
out.
Also,
coming
soon
are
fluent
still
deploy
tests
and
logs
for
fluence
deals,
they're
implemented
in
CLI,
but
they're
still.
Some
work
need
to
admitted
to
be
done
on
the
raspberry
side
and
we
have
a
lot
of
other
conveniences
and
stability
improvements
in
the
pipeline
now
so
stay
tuned,
pretty
much,
that's
pretty
much
it.
Thank
you
very
much.
B
B
So
while,
while
like
you're
thinking,
I
have
a
question,
so
this
versions
that
Json
file,
so,
for
instance,
if
I
yeah,
for
instance,
if
I
have
like
the
environment,
which
I
deployed
for
myself
and
my
local
machine,
so
what
versions
should
I
specify
there
like?
Should
it
be
the
like
the
version?
That's
that
is
installed
or
it
will
automatically
install
update
them,
how
it
will
work.
D
D
So
if
you
have
fluency
line
of
specific
version
and
you,
for
example,
locally
have
a
raspir
of
the
compatible
version,
everything
should
just
work.
You
don't
have
to
specify
anything
by
hand
anywhere
and
for
our
environments
that
are
not
local
but
that
managed
by
fluence.
D
B
Yeah.
Thank
you.
Another
question
is
regarding
running
individual
Aqua
files
with
the
global
settings
that
are
saved
there.
So
could
you
please
tell
a
little
bit
more
about
about
that.
D
If
you
really
want
to
override
or
install
your
own
dependencies,
you
can
do
it
and
you
can
do
it
not
only
on
a
project
level
but
but
also
on
the
global
level.
That's
basically
it
everything
you
install
regarding
dependencies
from
npm.
It
will
also
be
included
and
available
in
aqua,
so
you
can
install,
for
example,
a
package
with
our
library
or
your
own,
some
kind
of
your
library
for
aqua,
and
it
will
always
be
available
for
you
to
use
in
your
Aqua
code.
B
Okay,
thank
you.
Thank
you,
so
Eve
anyone
else
have
any
questions
for
our
tune.
B
Okay
and
I
guess
we
can
go
on
so
let.
B
Okay,
so
right
now,
Mikhail
warnov,
who
is
with
us,
will
tell
you
a
little
bit
about
our
new
thing,
which
we
want
to
introduce
into
the
distributed
computing
Community,
the
Distributors,
choreography
and
composition,
working
group,
Mikhail.
E
F
Guys
so,
on
the
last
IP
first
thing
we
established
a
new
group
called
distributed.
Paragraph
and
composition
is
Provo
said,
and
so
it
was
three
years
we
have
been
focusing
on
news
influence
on
building
the
centralized
about,
and
actually
there
are
a
lot
of
problems
that
we
have
solved
and
the
fluid
consists
of
different
wires.
So
it's
important
to
solve
different
problems,
but
one
of
the
most
promising.
F
Where
is
the
so
code
like
orchestration
or
like
orchestration
and
composition,
where
that's
represented
by
Aqua,
our
Aqua
stack
and
this
oil
actually
so
like
it
doesn't
solve
a
lot
of
problems
in
distributed
systems
and
then
the
last
couple
of
years
through
like
and
some
some
other
project,
that's
doing
some
form
of
decentralized
computing
like
it
could
be
a
cloud
it
could
be.
F
I
know
like
kind
of
Roll-Ups
and
applications
for
just
like
spreading
webassembly
tasks
across
networks
and
bunch
of
them,
and
it
seems
that
a
lot
of
such
projects
they're
solving
kind
of
similar
problems
like
how
you
can
advertise
service
to
distribute
Network
how
you
can
compose
different
functions,
so
I
get
in
different
Services
how
we
can,
for
example,
let's
say,
distribute
code
to
data
or
data
to
code
or
how
you
can
compute
distributed
workloads
and,
like
we
have
solution
for
some
of
these
problems
and
actually
like
for
some
of
those
problems.
F
We
don't
have
solution,
but
have
some
ideas
how
it
could
be
solved,
and
we
decided
that
it's
better
to
share
our
experience
across
people
and
across
like
such
projects.
That's
like
suitable
for
that
and
could
use
this
stack
and
could
like
contribute
to
the
stack
and
verify
our
ideas
propose
the
owner
ideas.
So
our
main
goal
is
to
make
like
research
and
development
project
of
Paco
VM.
C
F
Aqua
stack
at
Hull
is
transparent
and
opened
for
any
other
developers
who
want
to
participate
and
further.
Could
you
please
go
to
this
next
fight
yeah
in
particular,
they're
thinking
about
three
main
groups
of
people
who
could
be
interested
in
this
working
group
and
in
particular,
necro
stack.
The
first
one
is,
as
I
already
said,
as
a
developers
who
build
in
distribute
compute
in
any
form
yeah.
F
The
second
is
a
like
people
who
are
Keen
in
developing
distributed,
algorithms,
let's
say,
for
example,
distributed
probably
distributed
like
Academia,
but
programmable
Academia
or
plugable
Academia
yeah,
because,
like
like
a
lot
of
implementations
of
Academia,
but
if
you
want
to
experiment,
if
you
want
to
like
build
your
own
Academia
or
change
or
exam
parameters
in
Academia,
sometimes
it's
really
difficult
to
to
do
that.
Yeah,
probably
you
need
to
build
your
own
Academia
from
scratch,
and
it's
like
in
every
station.
F
It's
becomes
too
hard
because
a
lot
of
moving
parts,
it
would
be
much
more
easy
yeah
and
it
would
be.
It
could
be
a
testable
and
a
real
networks
with
real
problems,
and
also
you
will
be
happy
to
see
everyone
who's.
Like
cares
about
decentralized,
distributed
computing,
all
those
kind
of
problems,
so
we're
expecting
people
from
like
different
areas,
so
everyone
who
is
interested,
please
join
us
further.
F
Could
you
please
go
to
the
next
slide
and
on
this
slide,
you
could
see
our
resources
for
that
on
the
right
side,
you
could
see
here
code
for
GitHub,
where
the
like
all
main
updates
regarding
these
working
groups,
you
will
be
posted
posters-
is
a
telegram
group.
That's
intended
mostly
for
like
kind
of
chatting
about
proposals
about
different
problems.
In
like
these
working
groups,
I
mean
like
different
problems.
What
were
how
they
should
be
solved
and
what
the
approach
and
all
the
stuff?
So
please
everyone
Chris,
cares
about
that.
Please
join.
F
If
you
have
any
question
you
can
like
join,
for
example,
the
telegram
group
and
ask
them
question
about,
for
example,
organization,
or
how
can
they
participate
or,
for
example,
why
should
it
here?
So
please
go
to
telegram
group
and
you'll
be
happy
to
answer
them.
So
probably
that's
all
from
my
side
regarding
working
group.
B
Mihail,
thank
you
so
much
for
this
really
exciting
news.
So
could
you
please
tell
me
if
this
group
is
open
up
only
for
like
the
projects
who
are
doing
decentralized,
choreography
and
composition,
or
anyone
who
is
interested
in
the
topic
can
join.
F
Yeah
anyone
anyone
we
want
to
make
it
as
open
as
possible,
and
we
are
really
really
like
to
share
our
ideas
to
like
ear
people,
thoughts
about
distributed.
F
Algorithms
people
needs,
like
I,
mean,
like
food,
have
stumbled
across
different
problems
and
all
the
stuff
so
I
think
and
I
believe
that,
like
together,
we
can
like
make
our
future
and
our
for
I
mean,
like
our
own
future,
yeah
more
more
happy,
more
technological
and
like
this
problem
that
everyone
could
solve
like
by
building
distributed
computing,
they
could
be
sold
together
in
a
good
in
a
great
company
with
us.
So
yeah
everyone
prepares.
So
please
join.
B
Okay,
thank
you.
Thank
you.
So
much
Mikhail,
aside
from
that,
can
you
like
share
the
your
thoughts
about
the
ipfest
thing
which
we
as
fluency
participated
in.
E
Hello,
hello,
hello,
so
we
participated
in
a
ipfs
thing
in
Brussels
and
it
was
extremely
productive,
extremely
productive.
E
We,
like
I,
cannot
tell
anything
in
particular
like
the
outcomes,
except
that
we
have
this
working
group
and
we
established
and
launched
it
during
the
ipfs
thing
and
Mike
presented
it
from
the
stage
and
he
gave
a
talk
about
doc,
VM
and
our
approach
and
so
on
so
forth,
and
that
was
really
nice
and
we
had
many
connections
with
the
community,
both
the
fluence
community
and
the
compute
community
and
different
projects.
So
that
was
really
fruitful
and
very
insightful
and
I
called
that.
E
We
will
like
show
this
inside
later
once
we
formalize
them.
But
that
was
an
amazing
event
and
these
planets
we
we
did
it
very
productive,
don't
know
what
else
to
say.
B
Okay
Dimitri.
Thank
you.
Thank
you,
okay,
so
those
are
some
pictures
with
the
guys.
So
you
can
take
a
look.
C
Yes,
of
course,
so,
oh
yeah,
can
you
maybe
refresh
the
slide,
because
I've
added
some
QR
code
there
so
yeah
the
pipeline
is
actually
the
same
as
we
announced
on
the
previous
Community
call.
So
we
are
going
to
be
at
consensus
next
and
then
we're
going
to
have
computer
over
data
in
Boston,
also
United
States,
and
then
we
have
ethereum
CC
in
Paris
in
July
and
then
like
bunch
of
events
on
September,
so
yeah.
Let's
take
a
look
at
the
consensus
because
it's
gonna
be
pretty
intense
yeah.
C
The
next
slide
next
slide
yeah.
So
you
can
scan
the
QR
code
and
go
to
the
page
where,
with
a
schedule
for
where
you
can
meet
our
team
and
participate
in
some
activities
that
we
are
also
involved.
So
there
are
several
talks
Keynotes.
There
will
not
be
any
Workshop
this
time,
since
the
consensus
is
not
really
like
developer
oriented,
but
still
it's
going
to
be
a
file
coin.
C
C
Super
excited
about
this
one.
This
is
something
new
for
us,
so
yeah
like
any,
if,
like
any
chance
that
you
can
be
in
United
States
this
time
join
us
in
Austin
and
further
can
I
ask
you
to
go
back
to
the
previous
slide,
so
yeah
this
QR
code
actually
leads
you
to
the
calendar
of
all
the
affluence
events.
So
if
you
scan
it
and
if
you
import
it
to
your
calendar,
so
you're
gonna
see
all
our
events
so
yeah.
If
you're
interested.
Please
follow
this
link,
that's
pretty
it
from
my
side
today.
B
I
think
it's.
There
is
one
more
thing:
The
Poets,
oh.
C
B
So
you
guys
just
expect
some
private
message
in
Zoom
chat
from
Niger,
with
a
link
to
get
our
fresh
Pro
app.
For
this
call.
C
B
Okay,
so
yeah
there
is
like
the
QR
code
for
our
community.
B
But
so
please,
if
you
don't
know
about
our
Discord
or
if
you
like,
Discord,
then
just
please
scan
this
QR
codes
to
go
there.
There
is
a
bunch
of
guys
already
there
I
also
like
participating
some
discussion
there.
So
let's
keep
in
touch
and
yeah.
This
is
probably
it
thank
you
and
let's
go
means.
Those
pull
ups
right.
B
Okay,
anyone
anyone
have
some
questions.
B
B
Those
wonderful
news
and
updates
and
see
you
guys
on
the
next
Community
call
have
a
good
day.
Bye.