►
From YouTube: Developer Community Call #11
Description
00:00 Intro
00:48 Latest updates by Dmitry Kurinsky
04:49 Work in progress project presentation by Joera Mulders. Aragon.IPFS.Fluence. Scripts
20:15 Q&A
23:23 Hackathons info, bounties
Useful Links
https://fluence.network/
https://twitter.com/fluence_project
https://doc.fluence.dev/docs/
https://doc.fluence.dev/aqua-book/
https://github.com/fluencelabs/aqua
https://github.com/fluencelabs/aquavm
https://fluencenetwork.notion.site/fluencenetwork/Fluence-Developer-Community-Calls-2733beddb3ff4e4986c4fcc830fc796d
https://github.com/fluencelabs/marine-rs-sdk
https://t.me/fluencedev
https://fluence.chat
A
All
right:
well,
let's
get
started,
welcome
everybody
for
another
affluence,
community
edition
and
march
so
time,
time's
flying
by
and
today.
A
A
B
During
the
last,
during
the
last
two
weeks,
we
were
working
on
different
stuff,
but
delivered
mainly
some
things
around
aqua,
and
I
would
point
your
attention
on
two
particular
features.
The
first
one
is
what
we
call
recursive
streams.
B
It
was
delivered
to
arcway
vm,
and
then
we
found
some
bugs
and
we
fixed
them,
so
they
are
finally
delivered
and
recursive
streams
is
one
of
the
holy
grails
of
aqua.
Actually
because
it
it
means
that
you
can
have
a
recursive
or
iterative
distributed,
algorithms
coded
in
aqua,
for
example,
cademlia
or
a
gossip,
or
back
pressure
with
pushpull
model,
or
something
like
that.
B
So
that's
that's
quite
nice
and
we've
finally
updated
the
network
to
do
the
latest
version
with
the
other
bugs
fixed
today
and
going
to
implement,
to
use
it
and
implement
new
distributed
algorithms
in
a
aqua
library
during
the
next
I
don't
know
weeks.
B
The
second
update
is
the
collection
creation
syntax
in
aqua.
We
should
be
very
useful.
Actually
it's
just
a
sugar
but
should
be
very
convenient.
B
Now
you
can
create
a
race,
optional
values
and
streams
with
the
syntax
sugar
in
aqua
and
introducing
this
syntax
is
a
part
of
the
consequences
of
the
huge
refactoring
that
we
had
for
for
aqua
in
january
and
beginning
of
february,
and
more
changes
are
about
to
to
come,
but
let's
announce
them
next
next
time.
A
That's
sad
all
right.
Well,
then,
on
to
anybody
else
from
the
team
wants
to
present
an
update,
give
an
update.
C
C
So
it's
mostly
people
from
the
team
right
there
now
right,
so
l
with
all
those
mics,
oh
yeah,
we
don't
know
who
the
mics
are.
It's
true.
Are
you
seeing
a
screen.
C
Okay,
so
I've
been
working
with
fluence
now
for
a
couple
of
months
started
off
with
the
hackathon.
C
What
I
really
like
is
that
you
know
for
like
any
web
3
thing,
you're
thinking
of
blockchains
and
ipfs,
and
then
you
have
these
computation
networks
like
fluence,
which
can
like
connect
everything
together,
and
you
can
actually
start
programming
and
why
I,
like
specifically
fluence,
is
because
it's
like
sort
of
an
opinionated
and
I
can
find
my
own
way
in
it.
So
what
I'm
trying
to
do
is
that
I
like
to
aggregate
data
in
a
decentralized
manner,
so,
for
example,
from.
C
Interface
and
I
have
a
vote,
and
I
can
if,
when
I'm
connected,
no
I'm
not,
I
can
change
my
vote
or
create
a
new
vote
and
the
code
on
fluence
will
listening
to
it
and
when
it
records
like
a
new
vote
or
a
new
vote,
a
vote
on
a
vote,
it
will
create
a
new
data
structure
in
on
ipfs,
which
looks
like
this.
C
So
it's
like
this
ipld
sort
of
tree,
and
it
starts
off
with
the
that.
This
is
a
data
model
for
governance,
because
we're
talking
about
these
dowels
and
then
this
pair
dow
example.
Two,
that's
like
the
one
dow
that
subscribes
to
it.
There's
only
one
dollar
yet
subscribe
to
it.
It's
got
votes,
and
here
there
are
like
23
votes
recorded,
and
then
there
is
like
the
different
data,
for
example.
Here
you
can
see
like
it
should
have
recorded.
C
Oh
that's
in
a
file
format,
but
it
should
not
be.
If
I
do
this
one,
oh
yeah,
so
here
you
can
see
that
the
data
has
been
stored
on
the
ipfs
and
what
it
also
does
is
that
the
fluence
is
now
creating
a
widget,
which
is
an
example
here.
C
So
this
widget
is
like
created
with
fluence,
so
the
data
comes
in
and
then
it
renders
html
and
it
makes
the
folder
with
ipfs
so
that,
if
you
go
to
this
address,
you
can
actually
see
the
widget.
C
How
am
I
doing
this
with
the
fluence
now
so
I
have
two
scheduled
scripts
running
like
this.
One
is
on
kasundar
the
one
and
basically
it
needs
to
create
a
filter
for
ethereum
blockchain,
and
it
needs
to
do
that.
C
Every
50
minutes
because,
like
normal,
like
a
sort
of
ether,
client
like
eaters
or
what's
the
other
one
called
web3,
they
connect,
I
think,
through
something
like
a
web
socket,
so
they
can
have
like
a
continuous
sort
of
filter
connection,
but
because
we're
confined
to
working
with
the
curl,
it
needs
to
cre,
recreate
one
every
50
minutes,
and
that's
so
one
script
is
doing
that
and
within
the
let's
see.
C
So
that
is
this
one?
What
we're
looking
at
so
that
I
forgot
to
say
anyway,
so
this
one
is
creating
a
new
filter
and
then
it's
storing
it
on
the
dht
of
the
nodes
that
want
to
cooperate.
C
So
yeah,
so
this
this
one,
this
script
is
basically
running
after
50
minutes.
It
creates
on
basic
of
the
subscriptions,
which
is
now
only
one
dow.
C
It
creates
a
new
filter
and
that
filter
is
then
stored
on
the
node
of
on
another
node
and
on
the
that
other
node
is
not
a
script,
is
running,
it's
a
large
one,
and
that's
this
one
and
it
again
starts
looping
through
all
descriptions
that
are
there
and
then
it
goes
to
look
up
the
filter
id
and
then
it
filters
and
then
it
starts
doing
all
things
to
create
the
widget
and
the
data
structure.
C
Okay,
good,
do
you
have
any
questions
I
can
I
can
go
on,
but
maybe
there
are
questions.
C
The
script
is
running
like
every
15
minutes,
and
then
it
just
it
creates
it.
It
makes
a
call
to
the
ethereum
blockchain
and
that
returns
like
an
id
of
a
filter
and
with
that.
A
C
Okay,
so
the
part
is
that
what
I'm,
what
I'm
doing
with
all
my
scripts,
is
that
I'm
creating
all
the
surfaces
every
time
it
runs.
Okay,
gotcha,
all
right
and-
and
I'm
not
really
sure
if
that
is
like
the
the
way
to
go
in
the
future.
But
my
my
thinking
was
that
if
you
want
to
have
something
that
is,
cannot
be
tampered
with
is
like
truly
unstoppable.
C
You
cannot
like
really
confine
yourself
to
existing
scripts
that
are
tied
to
a
specific
note,
because
then
you
would
just
have
no
somebody
could
like
okay,
it's
that
note
that
it's
like
creating
this
website
with
this
terrible
misinformation
or
whatever,
let's
take,
and
then
you
there
could
be
a
request
to
take
down
that
specific
note.
C
So
I'm
thinking
of
in
a
ways
of
how
it
can
be
really
like
portable
but
yeah,
I'm
I'm
it's
so
early
for
me
to
start
figuring
out
how
this
works,
that
it
can
be
really
stupid
as
well.
I
don't
know
anyway,
but
I'm
creating
all
the
surfaces
and
then
at
the
end,
I'm
removing
them,
which
I
thought
to
be
very
clean.
So
what
happens
with
the
bigger
one?
C
Sometimes
it
starts
running
in
problems,
so
I
had
this
one
running
for
a
couple
of
days
and
then
suddenly
there
are
like
400
services
of
each.
So
at
a
certain
point
together,
there
was
like
on
one
note:
there
were
like
maybe
2,
000
services
running
so
then
I
had
to
stop
the
script
and
clean
it
up.
So
there
was
something
happening
and
it's
very
hard
for
me
to
debug
how
that's
happening,
what
what
sort
of
caused
that
issue
and
also
the.
C
Well,
I
I
was
running
it
on
my
own
notes,
but
then
I
could.
I
only
have
like
the
server
power
to
run
one
node
right
so
that
wasn't
helping.
C
And
maybe
the
logs
oh
yeah,
I
was
thinking
that
I
was
going
to
write
another
script.
That
is
basically
counting
the
number
of
services
and
and
then
connect
that
to
like
a
whatsapp
thing
or
sms
thing,
and
then
it
would
like
alert
me
whenever
the
actual
mistake
starts
occur.
And
then
I
can
call
you
and
we
can
figure
out
what's
going
wrong.
C
Gotcha
well
with
requests.
What
I
would
really
like
is
yeah.
C
I've
said
it
before
that
that
if
you
run
a
scheduled
script,
that
you
can
put
arguments
inside
and
get
things
out
because
then
also,
I
would
be
able
to
cut
up
this
bigger
one
in
smaller
ones,
because
you
see
that,
basically,
when,
when
I
pull
successfully
for
an
event,
then
it
starts
doing,
it
starts
like
using
the
surfaces
that
are
more
heavier
and
actually
do
stuff,
but
that
could
be
inside
another
script
so
that
the
one
script
calls
another.
So
the
the
recurring
script
calls
a
script
that
runs
only
once.
C
C
And
oh
yeah,
so,
and
maybe
that
if,
if
there
is
like
this
script,
it
has
like
a
sort
of
pre
and
post
function
like
so
that,
for
example,
this
the
the
removal
of
the
surfaces
that
you
can
put
it
in
a
post
function
so
that
even
when
the
script
sort
of
fails
it.
C
Oh
yeah,
and
what
can
I
else?
Can
I
say:
oh
yeah
so-
and
I
have
this
this-
this
is
the
the
other
one
that's
running
on
on
custom.2
now
or
the
scheduled
script.
That's
actually
doing
the
things
and
I
I'm
logging
from
the
out
of
the
services,
basically
all
the
time
to
this
console.
C
So
then
I
can
just
see
what
I'm
doing
and
it's
not
working
at
the
moment,
and
so
otherwise
I
would
be
demoing
it
anyway.
So
here
just
about
an
hour
ago,
I
had
one
result
and
then
it
started
doing
things
and
then
it
ran
into
a
bug.
C
C
C
I'm
working
on
a
a
surface,
for
example
this
one
so
you're
familiar
with
this
like
built
a
shell
script.
I
think
I
stole
it
from
from
you,
but
then,
on
the
end,
I'm
I'm
uploading
the
the
output
to
ipfs
and
the
cid
I
get
back
to
ipfs
I
store
on
on
the
blockchain
on
ethereum
somewhere,
and
so
every
time
I'm
creating
a
surface,
I'm
going
to
the
blockchain
to
check
okay.
C
C
And
so
this
week
I've
been
doing
this.
I
was
making
this
form,
so
you
can,
if
you're
a
dow,
and
you
want
to
subscribe
to
the
surface
it.
It
just
has
a
form
which
asks
for
the
the
information
needed
and
then
it
it
stores
the
storage
it's
on
ethereum
and
ipfs,
and
then
the
scheduled
script
is
like
gathering
that
information
to
run
scripts.
A
C
C
So
so
this
one
every
time
the
script
is
running:
yeah,
okay,
one
that
is
creating
a
filter.
It
goes
to
a
surface
and
that
surface
gets
all
the
subscriptions
and
their
metadata
from
the
blockchain.
C
Are
there
something
strange
with
that
any
I
I
started
doing
that
only
a
few
days
ago,
because
after
the
you
talk
about
the
registry,
I
thought.
Okay,
I
have
to
start
looking
into
this
stuff
and
then
I
thought
I
start
with
well.
The
registry
wasn't
really
fit
for
this,
so
I
I
tried
this
one
here
it
is,
can
you
can
you
see
this
on
a.
B
Well,
as
far
as
I
understand
it's
awkward,
hd,
not
registry,
and
not
the
library
but
the
low
level
api
and
I'm
curious.
Why?
Why
it's
so
and
would
be
awesome
to
maybe
to
have
a
call
and
discuss?
D
A
All
right,
it's
probably
gonna
reconnect
but
in
the
meantime,
key
up
your
questions
for
jurera
and
what
else
anna
do
you
have
any
updates?
E
Actually
we
have,
we
have
two
hackathons
running
at
the
moment,
so
there
is
one
with
the
swarm
called.
We
are
millions
and
the
bounties,
you
can
still
apply
and
we
have
two
bounties
from
fluence
and
there
are
many
more
from
swarm,
so
just
check
it
out
it's
in
git
coin.
If
you
go
to
hackathons
and
they're,
the
hackathon
called
one
and
you
will
see
the
bounties
there,
so
you
can
apply
and
try
to
to
have
that
to
to
solve
those
challenges.
E
And
then
the
other
one
that
is
running
at
the
moment
and
you
can
still
apply-
is
east
denver.
That's
a
virtual
e
denver
hackathon.
There
are
lots
of
sponsors
and
we
at
fluence.
We
have
seven
and
a
half
thousand
usdc
in
bounties.
E
So
please
check
it
out
I'll,
send
the
link
in
the
channels
and
also
here
in
zoom,
so
yeah.
That's
that's
the
news
and
we're
also
getting
ready
for
8th
amsterdam.
We
will
not
be
participating
in
amsterdam
like
supporting
like
we're
supporting,
but
we
are
not
sponsoring
the
hackathon
itself
because
it's
just
too
short
for
like
for
fluence
just
two
days
of
offline
hackathon,
but
we
want
to
organize
side
events,
and
hopefully
yuka
can
help
us
with
that,
because
he
is
local
and
yeah.
E
Let's
see,
what's
what's
gonna
happen
it's
end
of
april.
If
anybody
is
planning
to
be
there.
A
I
thought
I
saw
a
new
mic
sign
up,
but
maybe
not
all
right.
Anybody
else.
A
Well
then,
three
two
one
all
right
form
close.
Well
thanks.
Everybody
thanks
for
signing
in
thanks
for
hanging
out
and
where,
even
though
you're
not
here,
thanks
for
this
great
presentation
we'll
follow
up
on
the
dht,
we
really
want
to
talk
to
you
and
see
everybody
in
two
weeks.
Thank
you.