►
From YouTube: Developer Community Call #19
Description
ETHTransport team is presenting the project built with Fluence
Tech team updates
Q&A
Useful links
ETHTransport https://github.com/aspiringsecurity/EthTransport
Hacking On Fluence https://fluencenetwork.notion.site/Hacking-On-Fluence-Primer-28a87754397048e1bec72e3bfc91fd9b
Community Calls wiki https://www.notion.so/fluencenetwork/Fluence-Developer-Community-Calls-2733beddb3ff4e4986c4fcc830fc796d
Fluence Documentation https://doc.fluence.dev/docs/
Aqua Book https://doc.fluence.dev/aqua-book/
Discord https://fluence.chat
A
Speak
we
spend
a
lot
of
time
on
like
protocol
Labs
network
events
like
ipfs
cam,
Phil
Lisbon,
like
some
smaller,
like
a
smaller
events
and
and
and
like
a
more
like
a
private
things
were
happening
because
this
Meetup,
like
critical
networks
assignment
with
live
pure
ceramic.
A
Who
else
are
there
us
and
someone
else
and
film?
My
oh
a
few
mind
yes
and
really
great
in
Lisbon,
really
great
time
a
lot
of
meetings.
You
know
getting
a
lot
of
feedback
for
Florence
I
mean
virgin
people
and
so
yeah.
It's
it's
been
super
cool,
super,
useful
and
I.
A
Guess,
like
you
know
now,
actually
like
our
core
team
Heads
next
week
to
the
to
Georgia,
where
we
have
our
like
internal
site
sort
of
like
summit
gathering
in
person
to
work
really
together,
which
happens
right
now,
like
maybe
once
per
year,
but
we
we
wish
it
to
happen
more
often.
But
that's
you
know
how
the
world
works
right
now,
anyway,
yeah
it's
been
super
cool
here
in
in
Lisbon,
but
let's
maybe
move
to
technical
updates
for
the
October
engineering
updates
and
demos.
A
I
know
that
we
have
a
couple
of
presentations
from
the
court
team
members
and
we
have
demo
from
we
lost
hackathon
that
we
supported,
which
was
like
brothers
yeah.
So
should
we
start
from
from
you
know,
hackathon
demo
or.
B
Giving
us
the
opportunity
to
present
our
project
I
wish
to
share
with
you
that
I
have
been
following
fluence
for
considerable
time,
and
it's
wonderful
to
be
here
in
the
community
called
I
wish
to
share
about
the
initiative.
So.
B
Screen,
let's
there.
E
B
A
number
of
things
which
I
wish
to
present
so
we'll
how
much
time
will
I
have
for
presenting
and
I
hope
you
can
share
that.
B
Give
me
keep
it
short
and
quick.
Basically,.
D
B
Fantastic,
so
let
me
share
what
exactly
we
are
trying
to
do
and
how
this
entire
project
and
the
problem
statement
that
we're
trying
to
solve.
So,
basically,
we
are
focusing
on
a
Mobility
sector
and
in
Mobility.
The
biggest
challenge
currently
is
the
road
accidents
and
the
road
Incident
Management
that
every
government
faces
in
South
Asia,
even
in
South,
America
Africa
and
certain
parts
of
North
America.
B
So
I
wish
to
give
a
quick
background
of
where
I'm
coming
from
I
did
my
undergraduate
research,
both
in
Delhi,
as
well
as
in
MIT
Boston
I,
am
working
on
a
project
which
was
focused
on
distributed
Network
and
basically
I
was
I've,
been
working
with
the
government
on
a
variety
of
initiatives
around
Healthcare,
around
mobility
and
in
this
hackathon.
What
we
were
trying
to
do
was
utilize
fluent
peer-to-peer
infrastructure
and
reduce
the
bottlenecks
that
we
face
in
the
centralized
infrastructure.
B
So
our
mission
basically
was
how
we
can
capitalize
on
the
key
strengths
of
a
distributed
environment
and
a
peer-to-peer
infrastructure
of
fluence
for
doing
Road,
Incident
Management
and
organize
it
in
five
different
roles.
So
the
five
rules
were
basically
of
a
citizen
who
reports
a
road
accident
or
a
road
incident.
B
The
second
is
of
a
police
cop
or
a
person
who
is
in
charge
of
handling
a
particular
incident,
providing
the
requisite
ambulance
needs
or
the
first
aid
needs
at
in
case
of
any
accident
and
the
third,
basically,
what
is
of
the
admin
or
the
government
Ministry,
who
is
involved
in
charge
of
the
overall
structure?
So
basically,
in
this
particular
project,
I'll
very
quickly
begin
with
a
quick
demo,
a
video
demo
which
will
help
you
understand
where
we
were
coming
from.
So
here's
a
small
demo.
B
Our
project
is
divided
into
five
different
roles,
so
I'm
beginning
with
the
citizen
role,
so
in
the
citizen
rule
we
can
create
an
incident
at
a
particular
point
of
time,
use
fluence
as
a
peer-to-peer
infrastructure
for
sharing
it,
and
also
have
this
particular
incident
record
in
a
method
where
we
have
a
snapshot
or
a
video
stream.
So
we
were
using
live.
We
are
on
open
source
video
streaming,
along
with
the
peer-to-peer
infrastructure,
the
aqua
and
the
marine
ecosystems
that
are
available.
So
here
you
can
see
a
particular
incident
that
has
been
recorded
now.
B
This
particular
incident
gets
saved
and
is
shared
so
we'll
share
the
exact
ipfs
and
the
Falcon
integration.
Also
that
we
did.
In
fact,
we
got
very
good
support
from
the
GitHub
repos,
which
are
available
on
fluence
network.
We
are
still
learning
rust,
so
some
of
the
things
that
we
did
was
based
on
the
GitHub
examples
there.
So
here
we
have
the
second
rule
that
is
of
a
police
cop,
so
is
basically
responsible
or
is
assigned
to
a
particular
incident
and
reports
that
particular
incident
via
a
particular
setup.
F
B
Particular
incident-
and
you
can
see
that
this
particular
incident
is
assigned
to
a
particular
person
and
this
particular
person
is
then
basically
rewarded
or
incentivized,
based
on
how
that
particular
person
handles
that
incident.
So
here
you
can
see
a
particular
live
video
stream.
We
were
using
YOLO
machine
learning,
library,
it's
open
source,
machine
learning,
library
for
doing
a
real-time
incident
detection
at
any.
Given
point
of
sight,
so
here
you
can
see
so
this.
These
are
the
first
two
three
rules.
Now
we
we
are
coming
to
the
admin
room
in
admin
room.
B
What
we
are
basically
doing
is
we
are
doing
a
text
mining
or
you
can
see.
The
problem
we
are
trying
to
solve
is
an
early
detection
of
Road
incidents
at
any
given
point
of
time.
So
in
case,
if
there
is
a
particular
incident,
so
we
based
on
certain
parameters
and
based
on
a
certain
data
set.
We
are
trying
to
arrive
at
a
point
where
we
can
give
up
a
particular
set
of
schema
or
parameters
or
Define
a
set
of
rules
through
which
we
can
better
handle
the
incident.
B
So
here
you
can
see
in
the
admin
section
how
a
particular
incident
is
being
managed.
So
let
me
very
quickly
share
the
ipfs
and
the
file
coin
and
the
fluence
part.
So
there
are,
there
is
another.
So
it's
a
longer
video,
it's
a
six
minute.
Video
I'll
be
showing
the
fluence
Integrations,
also
in
it,
but
this
is
basically
the
storyline.
So
before
I
move
further
any
pointers,
feedback
or
questions
anything
anyone
would
like
to
ask
before
I
can
can
move
forward
any
thoughts,
suggestions,
I
can
move
forward.
B
Okay,
great
so
so
here
we
had
the
analytics
or
the
incident
analysis
in
a
particular
place.
So
the
data
that
was
available
to
us
it
was
of
multiple
sites,
as
you
will
see
in
the
video.
So
this
particular
data
I
have
taken
from
Delhi,
but
there
are
data
sets
from
New
York
City
from
San
Francisco
that
you
will
see
in
the
further
section,
so
I'll
I'll
be
showing
that
particular
thing
like
how
we
are
doing
real-time,
Incident
Management
in
a
decentralized
manner.
So
here
you
have
the
visualization
of
the
incidents
at
any.
B
Given
point
of
time
you
can
see
the
severity
index.
The
way
that
incidents
are
managed-
and
basically
this
is
like
a
top
level
kind
of
a
visualization
on
how
a
particular
incident
system
is
applied
in
a
particular
area,
so
we
had
the
entire
analytics
being
developed
for
it.
The
entire
system
been
organized
and
also
the
requisite
statistics
for
the
incident.
So
here
you
can
see
cases
per
incident
time
at
the
cases
and
also
we
had
the
overview
surveillance
and
the
incidence
prediction.
B
So
basically,
our
objective
was
how
we
can
utilize
the
strengths
of
what
is
available
in
the
ethereum
infrastructure
and
the
fluence
infrastructure
to
basically
do
a
better
incident
analysis
and
prediction.
So
so
this
was
the
first
part
of
the
project.
Now
let
me
share
the
second
part
of
the
project.
So,
basically,
as
you
can
see,
we
are
doing
an
overview
surveillance
also
over
here.
Basically,
what
we
have
done
is
we
have
developed,
developed,
a
very
simple
module
of
utilizing
drones
for
doing
better
analysis
and,
as
you
can
see,
a
communication
setup
in
a
particular
City.
B
So
we'll
do
that.
So
here
we
have
the
mobile
version
of
the
system,
which
means
what
is
available
to
a
particular
person.
So
you
can
see
the
different
IP
cameras
which
are
available.
You
can
see
the
different
types
of
objects
against
which
a
particular
incident
is
recorded.
So,
if
you
find
a
particular
object,
which
is
very
common
in
South
Asia
like
you
might
find
Hawks
on
the
roads
or
sometimes
various
kinds
of
animals
on
the
road.
So
these
are
the
different
detection
systems
that
we
have
I've
taken
the
snapshot
this
one
from
New
York
City.
B
This
is
somewhere
right
near
Times
Square
and
what
I'm
basically
doing
is
I'm
trying
to
find
out
what
are
the
abnormalities
in
a
particular
section
at
any
given
point
of
time
that
needs
to
be
notified
to
the
system.
That
is
the
ipfs
system.
So
we
basically
take
a
snapshot
in
case
if
this
is
abnormality,
put
it
on
ipfs
and
then
retrieve
from
ipfs
and
share
it
to
the
command
and
control
center.
B
B
Also,
very
quickly
jump
over
to
the
exact
repo
and
the
set
of
pointers
that
were
helpful
and
I'll
also
like
to
share
some
feedback
and
pointers
on
how
we
could
have
done
certain
things
better
and
how
we
can
do
it
further
better,
as
we
move
forward
in
the
project,
any
thoughts,
pointers
or
suggestion
till
now
any
questions.
B
A
B
Yes,
so
basically,
we
have
the
project
that
is
the
mobile
phone
version,
as
well
as
the
entire
Cloud
platform
version.
I
wish
to
share
that
the
idea
of
the
project,
basically
that
we
did
so
that
was
there
in
our
minds.
We
had
spend
some
time
on
the
Web
2.0
version
of
the
project
way
back
in
2018,
but
this
is
the
first
time
when.
F
B
Actually
did
it
in
a
web
3.0
manner,
so
in
2018
2017.
The
pointers
were
available
to
us
that
you
can
work.
So
basically,
the
skill
set
was
there
that
we
had
and
the
execution
and
the
entire
I
would
say
understanding
of
how
we
could
utilize
fluence,
how
we
could
utilize
file
coin
ipfs.
So
this
particular
initiative
happened
during
that.
Basically.
A
Super
cool
just
like
gurus
to
better
understand
how
you
guys
use
fluence,
maybe
like
you,
can
show
something.
B
F
B
So
so
these
are
certain
IP
cameras
on
which
we
did
the
real-time
detection
of
incidents
and
shared
it
on
ipfs
and
basically
the
admin
role
that
I
was
talking
about.
So
all
this
gets
recorded.
So
we
have
taken
couple
of
examples
during
the
course
and
now
let
me
very
quickly
share
what
are
the
repos
of
fluents
that
we
checked
on
and
where
we
are
in
terms
of
project
updates
and.
D
F
B
Couple
of
questions
regarding
it
so
I
have
four
more
minutes
with
me:
I'll
try
and
make
it
in
a
I'll
make
it
quick,
but
at
the
same
time,
I'll
share
what
all
we
have
done
so
specific
to
fluence.
So
these
are
the
updates
on
utilizing
influence,
peer-to-peer
infrastructure
in
a
project,
so
we
are
working
towards
decentralizing
key
components:
bottlenecks
in
our
existing
filecoin
solution.
B
Second,
we
are
learning
to
create
decentralized
peer-to-peer
protocols
to
replace,
centralized
off-chain
solutions
that
we
have
currently
by
swapping
centralized
service
providers
like
AWS,
Azure
and
also
Google
Cloud.
Currently,
I
am
more
comfortable
with
all
of
them,
but
I'm
trying
to
swap
these
centralized
service
providers
for
fluent
peer-to-peer
infrastructure.
So
these
are
the
two
main
objectives
currently
that
we
are
focusing
towards
and
I
wish
to
share
the
reports
that
we
are
utilizing
in
reference
to
fluence.
So
let
me
share
the
exact
repos,
so
one
I
personally
wish
to
share
that.
B
B
And
Marine
examples
so
so,
basically,
this
was
one
particular
repo
that
was
very,
very
helpful
and
also
it
gave
us
an
understanding
on
how
Aqua
gets
integrated
with
the
decentralized
storage
system
that
is
ipfs
using
aqua
ipfs
system.
So
you
can
see
in
the
resource
directory
I
think
it
was
probably
second
Point
yeah
the
ipfs
integration,
so
it
basically
gave
us
the
understanding
on
how
we
could
utilize
the
aqua
ipfs
library
to
basically
deploy
a
vasm
service
to
affluence
nodes.
So
so
this
was
something
which
was
very,
very
helpful.
B
The
couple
of
areas
where
we
perhaps
are
very
new
and
I
would
love
to
learn
more
I
think
we
perhaps
didn't
have
much
understanding
on
timestamp
during
the
course
of
hackathon,
and
this
is
something
where
we
are
trying
to
learn
more
and
trying
to
understand
how
we
could
better
use
some
of
these
services
in
our
particular
project.
So
there
are
certain
problems
which
we
can
solve
using
this.
The
near
integration
is
also
something
which
is
very,
very
important,
and
we
have
not
looked
into
that.
B
So
these
two
three
areas
is
something
which
is
still
I
would
say
in
the
next
two
months,
especially
in
the
next
21
days,
I'm
focusing
on
the
near
integration
in
totality
and
really
do
that.
Well
and
after
that,
I
look
at
timestamp,
Oracle
and
price
Oracle
after
21
days
or
30
days.
So
so
that's
the
plan,
that
of
plan
that
I
have
in
terms
of
learning
and
implementing
it
in
the
project
I'll
also
share
what
else?
What
are
the
other
things
that
was
very
helpful
during
the
hackathon
and
how?
B
What
are
the
things
we
are
planning
for?
That
I
wish
to
share
ceramic
integration
comes
much
later.
We
also
have
covalent
and
a
lot
of
other
ecosystems
that
are
coming
up,
but
the
ceramic
integration
I
would
definitely
try
to
focus
on
sometime,
I
would
say
towards
January,
but
these
are
the
set
of
things
that
we
have
in
mind.
At
this
juncture.
There
are
a
couple
of
before
I
move
on
to
the
rust
sphere.
B
Github
repo,
which
was
again
super
helpful
in
this
particular
hackathon
I,
mean
because
we
are
learning
rust
and
we
find
that
a
lot
of
things
we
can
derive
from
this
project.
So
before
I.
Move
on
to
that,
I'd
like
to
share
a
couple
of
collaborations,
which
are
happening
on
the
business
front,
which
are
giving
us
some
strength
and
which
are
giving
us
some
understanding
on
how
we
can
take
the
project.
So
one
there
is
a
company
based
out
of
Switzerland
by
the
name,
ZF
Mobility.
B
So
they
basically
came
to
know
about
our
project
and
because
it
was
publicized
all
over
and
they
are
trying
to
utilize
connected
vehicles
in
Europe
for
sustainability
and
efficiency.
So
they.
B
Set
that
they
shared
with
us
of
15,
000
trips,
45
plus
trucks
and
175
plus
drivers.
So,
instead
of
just
having
this
particular
project,
which
is
focused
towards
I,
would
say
governments
they
have
asked
us
if
we
could
kind
of
customize
this
project
for
doing
better,
Fleet,
Management
and
for
doing
connected
vehicles,
like
I,
mean
arrive
at
a
solution
for
connected
Vehicles
specific
to
Europe
for
sustainability
and
efficiency.
So
we're
still
at
the
brainstorming
stage,
but
I
personally
feel
that
this
is
where
fluence
rust,
Network
I
mean
using
rust,
influence.
Peer-To-Peer,
Network
I.
B
Think
that
will
be
very,
very
helpful.
Specifically
this
particular
level
so
I'm
going
to
share
this
with
them
in
the
coming
call,
I
already
updated
them.
What
all
we
have
done
is
influence
and.
D
B
To
share
updates,
as
we
move
forward
on
this,
so
this
is
one
particular
update
which
I
wish
to
share.
There
are
a
couple
of
others.
Also
I
mean
we
we
have
like
whenever
we
get
a
chance.
We
do
share
a
couple
of
things
with
the
community
on
how
we
wish
to
develop
a
monetization
model,
so
I've
written
a
small
white
paper
on
that
it
is
very
much
available.
I'll
share
it
in
the
GitHub
repo
as
well,
which
will
help
share
I
mean
how
we
can
sustain
this
project
over
time.
B
I
mean
what
are
the
like:
how
if
someone
is
using
our
project,
how
they
can
sustain
that
project
in
a
particular
area,
and
if
there
is
any
particular
question
I
mean
you
can
definitely
ask
on
this.
So
here
we
are
definitely
looking
at
considerable,
so
the
entire
decentralized
infrastructure
is
that
affluence.
I
mean
the
way
we
have
designed
the
monetization
model.
So
so
this.
F
B
Another
small
community
writing
that
I
did
I'll,
publish
a
Blog
on
it
very
quickly
and
I'll
definitely
share
this
across
so
so
this
is
another
feature
that
we
have
done
so
I
just
wish
to
share.
On
the
Rust
part,
I
mean
that
is
the
rust
peer
ecosystem.
Like
I
mean
what
should
be
the
manner
in
which
we
should
be.
You
can
say
piloting
some
of
the
things
we
are
doing
for
the
in
using
fluency.
What
would
be
the
appropriate
manner
through
which
we
can
get?
B
You
can
say
community
health
as
we
scale
the
project
forward,
so
so
this
is
one
particular
question
because
I
mean
there
is
a
lot
of
learning
that
is
happening.
I
wish
to
share
that
we
are
still
beginners.
We
are
not.
We
are
not
even
in
the
intermediate
stage
or
Advanced
stage,
but
we
definitely
are
finding
our
learnings
very
nice,
and
we
wish
to
take
this
forward.
So
just
an
open
question
to
everyone
in
the
community
like
what
has
been
their
experience.
B
This
is
my
first
Community
call,
so
I
would
love
to
hear
on
how
what
are
the
ways
through
which
we
can
expedite
our
learning
on
utilizing
experience
as
a
peer-to-peer
infrastructure.
So
so,
with
that
any
questions,
any
feedback
I'll
be
more
than
happy
to
answer.
A
Well,
I
guess
you
know
some
some
highlights
basically
rust.
Note
rust.
Beer
is
the
sort
of
main
implementation
of
the
fluence
node
that
you
run
as
a
kind
of
work
around
your
back
end
and
basically
like
when
you
think
of
the
American
Staff
like
this
is
the
default
peer
implementation
that
that
we
recommend
to
use
and
when
you
think
of
using
fluence
on
the
client
in
a
browser
on
a
device,
there
is
a
fluency,
yes,
which
is
basically
sort
of
something
between
the
client
and
the
peer.
A
So
it's
it's
kind
of
like
some
lighter
fluence
Network
here,
but
its
usual
role
is
to
be
used
in
kind
of
in
the
role
of
the
client
or
like
work
which
initiates
Aqua
requests.
But
you
also
can
you
know,
reach
the
other,
client
and
and
execute
function
called
rbr.
Okay,.
D
A
And
there
are
a
few
other
things
that
like
important
thing
that
that
are
coming
and
I
hope,
like
guys,
will,
will
do
some
updates
on
it,
like
registry
and
and
CLI,
which
will
also
be
like
very
important
thing
that
we
recommend
to
use
mobile
influence.
D
B
Thank
you
so
much
one
quick
question:
a
follow-up
question
on
this
I
wish
to
share
that
in
reference
to
differentiating
where
to
use
aqua
and
where
to
use
the
Marine
ecosystem
and
if
you
can
share
some
thoughts
or
pointers
on
that,
like
I
mean
both
of
them
are
very
nicely
documented
and
a
ton
of
good
examples
available,
but
love
to
hear
more
on.
B
What's
like
what
is
the
basic
Genesis
of
scaling
up
a
project
with
either
of
these
ecosystems,
I
mean
what
should
we
keep
in
mind
while
we
evolve
a
project
using
influence,
basically.
A
Yeah
sure
so,
like
the
basic
distinction
here
is
Marine
is
a
wasn't
runtime,
it's
basically
the
code,
the
the
the
functions
that
you
run
on
peers
and
the
aqua
is
basically
the
workflow
management
on
top
of
these
functions.
If
you
like,
you
know,
if
you're
familiar
with
Amazon
Cloud
stack,
you
can
think
of
Aqua
Amazon
step
functions
and
Marine
is
Amazon
Lambda.
So
like
you're
right,
it's
on
top
of
Lambda
and
that's
that's.
D
A
B
A
Thank
you
manoon.
That
was,
that
was
a
great
demo
thanks.
So
much
for
for
joining
and
sharing
this
show
so
I
guess
we
we're
gonna
have
some
a
couple
of
updates
from
the
development
team
as
well
Mike
you
wanna
be
next.
C
G
G
G
So
let
me
share
a
screen,
so
my
name
is
Mike
and
I
want
to
present
a
machine.
Department
team
progress
for
the
previous
month
so
and
British.
G
Should
be
there
like
a
part
of
the
presentation
that
we
had
in
September,
so
in
September
you
can
see
the
scheme,
so
the
team
represents
like
that
that
we
have
done,
and
we
like
wanted
to
be
done
in
next
month
or
like
no
in
like
calpo
of
next
month,
and
here
you
can
see
that
we
use
a
rhombus
by
rhombus.
The
rod
does
that
I
have
done
in
previous
months.
G
Or
like
next
album
and
the
actual
progress
for
October,
so
here
you
can
see
that
our
main
Direction
was
like
to
complete
the
Termini
record.
The
support
determinism.
G
In
progress
discovered
to
two
more
issues
and
we
spend
the
like
kinda
of
one
and
a
half
week
fixing
all
of
this,
and
then
we
had
internal
hackathon
and
during
Donna
hackathon,
no
more
issues
have
been
recovered.
So
I
think
that
we
can
say
that
for
this
moment,
so
this
track
is
finished,
yes
and
no
more
tasks
at
the
neck
like
in
the
neck
in
the
nursery,
like
won't,
be
a
dessert
for
this
track.
Also,
the
other
drug
that
has
been
finished
in
October.
G
It
was
track
of
testing
framework,
so
you're
building
tasting
framework
that
allow
us
to
like
test
aquarium
more
naturally
and
more
easier
manner,
and
we
released
or
almost
really
two
parts
of
the
system
framework
they're
like
all
in
in
their
pure
stage,
but
I
I
believe
that
we
will
finish
it
until
this
end
of
this
week.
So
we
are
also
like
it's
also
kind
definition
of
this
truck
and
speaking
about
other
activities
that
we
had
in
this
month.
G
So
we
designed
iPod
support
specification
that
will
allow
us
to
use
to
move
aquarium
to
iPod
stack
and
also
like
we
designed
our
canons
production
Network
used
in
this
summer.
You
use
iPod
you're,
based
on
iPod
and
also
like
in
the
next
months.
Our
goal
will
be
to
implement
this
apod
spec
in
Aquarium
awesome
regarding
factors.
So
functors
is
a
very
valuable
addition
to
aquarium.
G
We
want
to
concentrate
next
month
on
collection
requirements,
for
factors
to
make
a
VM
more
handy,
to
become
like
Target
of
calculation
and
then
I'm,
not
sure
we
would
be
in
November
or
not,
but
then
after
collecting
requirements,
we'll
design
factors
and
make
like
a
document
in
this
specification
specification.
G
So
regarding
so
instruction
track,
we
haven't
done
anything
like
in
field
of
instructions.
There
will
know
any
new
instructions,
but
in
a
plan
I'm
not
sure
we'll
be
in
this
year
or
not.
There
is
only
joint
instructions
that
will
allow
us
to
express
certain
Behavior
more
in
more
strict
manner
and
regarding
the
last
one
about
hardening.
G
So,
in
order
to
fix
a
bugs
with
updates
on
aqueous
of
all
our
stack
and
JavaScript
Marine
JS
part,
and
all
of
this,
we
added
version
interpreter
version
to
data,
and
this
allow
us
to
teach
up
like
outdated
interpreters
and
like
fixed
all
this
kind
of
boxed,
with
like
an
appropriate
updates
here.
You
can
see
this
slide
with
the
release
like
bug,
with
a
hook
of
using
old
and
Canon.
So
actually,
this
is
what
kinda
kind
of
beak.
G
As
I
said,
we
spend
a
lot
of
time,
fixing
it
so
by
the
basic,
like
a
proof
of
concept
is
not
so
big,
so
here
you
can
see
that
actually
it's
it
can
see.
Only
all
this
like
so
the
main
part
here
is
the
fault
or
we
can
mute
Cannon
and
the
body
in
in
the
world
of
port,
with
upper
instruction
and
in
certain
case
so
like
when
external
addresses
has
several
Generations
more
than
one.
G
Then
this
bug
this
like
crash
could
happen
so,
but
it
was
fixed,
it
was
deployed
with
new
version.
We
tested
an
internal
hackathon,
so
no
more
any
problem
with
it,
I
believe
and
in
future.
One
of
our
plan
is
to
make
it
more
stable
in
terms
of
change
the
form
of
data
a
bit
it
will
be
in
this
iPod
and
like
specification,
it
will
also
fix
this
kind
of
hack
that
we
introduced
in
this
October
regarding
Marine
in
Marine.
Now
we
have
only
two
tracks,
so
first
one
is
developer
experience.
G
The
next
one
is
the
area
Factory
and
for
the
first
pack
for
developer
experience,
we
were
factored
in,
beat
power,
mapped
and
pre-op
and
directories
handled
by
marine
and
like
how
they
put
into
the
wasmer.
G
Then,
on
the
on
the
following
months.
We
want
to
improve
in
repo
According
to
some
hyperton
requirements
that
we
that
was
like
this
requirements
were
collected
during
the
our
last
internal
hackathon
and
regarding
refactoring.
We
are
working
on
manufacturing
and
working
hard
and,
like
is
about
computer
Dust,
We
researched
and
then
a
customer
watching
time.
Then
now
we
are
working
and
it's
almost
like
done
we're
working
on
how
to
design
a
proper
trades
for
this.
G
And
finally,
we
want
to
implement
all
this
and
why
it's
important
is
important,
because
you
want
to
support
modern
investment
and
modern
Western
time
so
to
add
more
blue
rectangles
to
the
skin.
So
here
you
can
see
that
there
is
a
core
and
between
core
and
this
blue
rectangles.
We
want
to
have
a
abstraction
layer.
G
It
will
allow
us
to
use
different
like
underline
engines,
especially
Western
time,
and
also
we
have
some
other
updates
like
we
during
this
fixing
box
the
support,
convergence
and
aqua
VM,
we
refactored
certain
parts
like
in
Trade,
Center
and
aqua
VM,
so
like
it
made.
So
this
refractor
made
it
much
more
understandable
and
much
more
I
know
readable
I.
Also,
we
fixed
the
minor
issues
with
Marine
minor
issues
with
Marine
sky
and
probably
the
bit
from
the
machine
Department
team
inside.
A
E
Yep,
so
we've
been
deep
in
our
journal,
hackathon
and
all
this
stuff.
After
that,
we've
been
doing
some
work
on
deploying
and
really.
E
F
E
Was
describing
so
that's
great?
Also,
we
added
a
few
built-ins
to
help
with
the,
for
example,
array
slice
operation.
It's
a
python-like
thing
where
you
can
choose
two
indexes
of
the
array
and
get
a
sub
range
of
the
elements.
It's
useful
for
some
stuff.
When
you
have
like
data
that
you
want
want
to
get
some
set
of.
Also,
we've
been
doing
some
work
on
Json
buildings.
They
are
meant
to
help
Implement,
functors
and
control
factors
in
aqua
before
they
are
implemented
in
aqua
VM.
E
So,
with
this
kind
of
stubs,
Aqua
developers
can
already
Implement
Contra
factors
and
when
they
will
be
shipped
to
awm,
AVM,
sorry
to
AVM,
they
will
be
implemented
on
top
of
those
native
implementations.
Instead
of
this.
A
E
Expensive
things
that
are
implemented
by
both
rust
beer
and
JavaScript
peer
also,
we
started
a
big
work
on
the
design
of
this
so-called
spells.
This
is
a
abstraction
to
implement.
This
is
how
we
call
obstruction
to
implement
stateful
recurring
computations
influence
its
evolution
of
current
scheduled
script
right
now.
Scale
scripts
are
stateless,
they
can
be
addressed
and
there's
a
lot
of
issues
with
them.
The
ux
could
be
much.
E
Like
a
lot
of
things,
aren't
possible
with
current
schedule.
Scripts,
not
even
touching
the
security
and
economics
things
so
spells
are
meant
to
solve
a
lot
of
things,
and
they
are
meant
to
solve
local
routing
where
you,
when
you
have
different
sources
on
the
same
peer
and
you
want
to
Route
particles
between.
F
E
So
it's
an
evolution
of
scale
scripts
and
it
will
be
possible
to
implement
HTTP
triggers
with
that.
E
So
when
HTTP
request
comes
to
a
rust
peer
into
all
possible
to
trigger
Aqua
script
from
that
HTTP
request,
that
would
be
pretty
nice
and
Powerful
same
things
from
for
trigram
from
peer
events
like
new
connection
or
disconnection
that
will
allow
us
to
implement
Academia
on
top
of
aqua
and
there's
like
a
whole
bunch
of
nuances
to
implement
we're
still
discussing
it,
and
there
is
still
how
how
it
connects
a
question:
how
connected
security,
how
to
it
connects
to
economics,
then
we
will
all
discuss
and
design
that
on
the
coming
Summit
that
will
have
and
we'll
all
gather
together
to
discuss
those
things.
E
Also,
there
was
a
lot
of
work
on
devops
side,
so
to
call
it
on
CI
side
we're
working
hard
on
making
the
whole
fluent
stack
testable.
So
where,
when
some
change
happens
in
one
part
of
the
fluent
stack,
all
the
tests
of
all
the
other
parts
include
that
new
change
and
run
again
and
check
whether
that
new
change
campaign,
people
with
everything
and
whether
just
buses
and
invariance
hold
that
will
improve
our
quality
of
life
and
quality
of
work.
A
lot
and
I
hope.
E
E
Workflows
also,
there
was
a
work
on
observability
stuff.
We
had
alerts,
implemented
and
refined
and
fixed
and
right
now,
working
on
making
Aqua
powered
alerts
happen
for
rust
peers.
So
it's
not
just
like
whether
Docker
container
is
up
or
down
or
port
is
open
or
closed.
It
would
be
also
whether
some
complicated
logic
written
in
aqua
gives
like
error
or
not
hold.
Some
invariants
will
be
that
way.
It
will
be
possible
to
check
for
different
distributed
properties
of
the
whole
network,
like
latency,
conversions
and
all
this
stuff.
E
That
would
be
nice
and
we're
working
hard
on
it.
Some
parts
are
already
implemented
basic
Aqua
health
checks
already
there
and
as
soon
as
we're
done,
we
will
start
working
on
making
those
changes
like
usable
for
by
other
people,
so
publish.
D
E
A
Amazing,
thank
you
products,
great
updates.
Anyone
has
any
any
questions
to
products.
B
Yeah,
can
you
sorry
can
we
share
the
spell
link?
The
notion
link
that
was
there
yeah.
E
A
If
not,
I
would
just
tell
one
thing,
so
we
have
this
telegram
Channel,
with
a
developer
updates
with
address
influence,
Dev
I,
I'm,
gonna
post.
The
link
here
in
this
chart.
A
So
we
we're
trying
to
set
up
like
a
regular.
A
You
know
schedule
of
updating
about
different
pieces
of
phones,
development
stack,
so
there
are
some
fresh
updates,
just
posted
as
like
in
a
batch
there
about
registry
like
food
and
GS
like
some
of
these
cowards
coverage
already
on
this
call
like
CLI,
Russia
and
stuff,
and
so
on
so
like
if
anyone
interested
to
to
kind
of
like
read
through
all
the
latest
updates,
that's
the
place
to
look
and
yeah
I.
Think
that's,
then,
if
no.
C
One
wants
to
share
anything
else,
then
that's
it
for
today,
10
minutes.
C
Alert
guys
Lord.
A
Fluency
all
right
thanks
so
much
everyone
for
joining
today
and.