►
From YouTube: Developer Community Call #16
Description
Upcoming online & in-person events and hackathons
DOSA team presenting the project built with Fluence
TrustGraph and Registry docs
Aqua metrics and log collection, VSCode advancements
AquaVm performance analyzer
Useful links
DOSA project https://github.com/iqbalbaharum/dosa_project
Hacking On Fluence https://fluencenetwork.notion.site/Hacking-On-Fluence-Primer-28a87754397048e1bec72e3bfc91fd9b
Community Calls wiki https://www.notion.so/fluencenetwork/August-4-2022-Community-call-16-AquaVM-performance-analyzer-b83e6ac649f245a8830690198b475957
Fluence Documentation https://doc.fluence.dev/docs/
Aqua Book https://doc.fluence.dev/aqua-book/
Discord https://fluence.chat
A
A
We've
got
full
legs
with
stuff,
including
trust,
graph
and
registry
documentation,
our
new
aqua
metrics
log
collection
and
vs
code
advancements,
and
we
have
community
members.
I
think,
are
you
here
we're
looking
for
sorghum
and
that
was
a
team
okay,
so
we
got
that
all
right
so
and
then,
with
evan
who's,
gonna
give
a
deep
dive
with
the
aqua
vm
performance
analyzer
and
I've
had
a
preview
of
it.
So
if
you're
in
in
aqua
micro
vm
definitely
stick
around
all
right,
let's
start
with
anna.
B
Right,
so
there
are
some
of
the
upcoming
events
that
we
are
participating
and
also
hackathons.
So,
first
of
all,
just
to
remind
everyone.
We
have
community
calls
it's
every
month
now
and
the
next
one
is
september
1st,
then
october,
6
november
3rd,
etc,
etc
is
every
first
thursday
of
each
month.
We
get
together
here
in
discord,
we're
not
using
zoom
and
recording
is
going
to
be
in
our
youtube.
B
Then
the
first
fluence
meetup
in
nigeria,
built
by
one
of
our
community
members
active
community
members
purity.
So
it's
happening
actually
on
friday,
the
information
in
our
discord.
Then
we
probably
is
gonna
one.
One
of
our
team
members
is
probably
planning
to
participate
in
the
mata
cartel
conference
in
denver.
So
if
you
want
to
get
to
know
more
about,
dows
feel
free
to
join
that,
then
there
is
berlin
week
the
massive
blockchain
week
september,
12
to
18.
B
adapcon,
the
conference
for
ethereum
developers
and
developers
who
want
to
build
with
decentralized
stack.
We,
our
team,
is
planning
to
be
there
so
very
welcome,
let's
meet
and
and
chat,
and
the
well-known
ith
berlin
september
16th
to
18th
so
full
week
of
events.
B
If
berlin
is
going
to
be
only
offline,
I
think
only
in
person,
so
you
can
apply
now
token2049.
That's
a
big
crypto
conference
in
singapore
running
through
the
september
28
to
29th.
We
are
having
m4
stand
there,
so
you
can
see
it
right
here.
So
there
are.
A
lot
of
companies
are
planning
to
be
there
and
us
as
well
and
they're.
Also,
okay,
I'll
tell
a
bit
later
that
field
community
is
planning
to
have
conference
as
well,
and
that
one
is
all
things
open
in
raleigh
us
october,
3rd
october.
B
C
B
So
it's
fine
okay!
Okay,
maybe
I
should
speak
louder
or
something
I
think,
because
I'm
recording
the
same
time.
It's
not
writing,
but
anyway,
that's
the
conference
for
all
open
source
about
the
tools
about
the
like
technologies
for
the
developers.
B
Then,
lisbon
week
again,
east
lisbon,
hackathon
offline
in
person
the
week
of
events
around
it
file
coin
event,
the
big
file
coin
conference.
You
can
see
here
some
of
the
dates
compute
on
data
community,
meetup
and
solana,
breakpoint
conference
and
a
lot
of
other
conferences,
just
watch,
twitter
and
they're
going
to
be
all
the
updates
and
I'll
post
this.
This
pdf
in
our
discord
and
in
our
community
calls
wiki
and
then
some
of
the
hackathons
that
running
right.
B
Right
now,
you
can
still
take
part
in
web
3,
infinity
hackathon
run
by
a
local
singapore
community,
the
deadline,
I
think
it's
august,
17th
or
something
and
hackathon,
is
running
until
august
23rd,
it's
via
death
post
check
out.
You
can
build
with
fluence
check
out
the
rules
there
and
submit
your
project.
We
have
youtube.
We
have
a
workshop
published
in
youtube
already
and
they're
going
to
be
in
person
conference.
As
I
mentioned
just
before,
talking
2049
in
singapore,
the
big
falcon
singapore
summit
also
very
very
welcome.
B
A
All
right,
very
cool
you
want
to
hack.
This
is
plenty
of
opportunity.
Okay,
so
next
we
get
the
the
dosa
team
from
hack
fest.
Why
don't
you
tell
us
a
little
bit
about
your
project
and
congratulations
by
the
way
you
did
very
well
and
yeah.
It's
the!
Let
us
know
what
you
did,
how
you
did
it
and
what
are
you
gonna
do.
D
E
E
A
E
D
D
D
So
basically,
our
background
is
that
we
actually
came
from
what
we
call
a
game
industry
right.
So
we
actually
build
a
blockchain
games,
so
they
actually
have
a
lot
of
limitations
in
building
what
we
call
a
crypto
native
game.
So,
most
of
the
time
the
implementation
is
actually
more
towards.
You
need
to
combine
a
lot
of
what
we
call
a
web
2
and
a
website
technology
together
to
win
a
single
game
right.
D
So
one
one,
the
very
high-
and
I
mean
the
most
important
part-
is
actually
that
in
game
we
we
need
a
lot
a
lot
of
what
we
call
high
throughput
like
in
term
of
what
we
need
to
streaming
the
game
and
we
need
to
stream
about
the
information
and
also
in
terms
of
changing
a
blockchain
itself
to
become
a
database
all
right.
D
So
this
is
actually
the
infrastructure
that
we
built
at
the
back,
actually
one
of
it
that
you
can
actually
check
out
in
our.
I
will
share
it
afterwards.
This
is
actually
the
the
the
codes
that
we
publish
for
the
hackathons,
so
what
we
built
is
actually
we
actually
work
with
two
blockchain
for
the
project.
One
is
a
polygon
blockchain.
D
To
achieve
it,
one
thing
that
we
actually
missed
out
on
this.
We
actually
plan
to
do
a
consensus.
It
means
that
we
are
reading
it
for
different,
different
different
resources,
we're
actually
planning
to
use
a
moralist
at
the
graph,
but
because
of
the
limit
of
time
we
just
stick
with
the
in
the
graph.
Everything
managed
to
do
the
processes,
part
of
the
fluence
right.
D
So
once
they
read
the
information
from
the
graph,
then
only
the
certain
information
actually
going
for
to
remain
the
the
what
we
call
to
remain
the
the
industrial
agreement
right
to
mean
the
nfp
to
the
user
wallet
with
a
randomized
stats,
and
it
also
be
used
also
for
a
couple
of
things,
so
they
actually
in
general,
we
have
a
couple
of
services
that
you
can
see
here
that
we
run
it.
We
have
the.
D
But
to
sum
it
up
is
that
they
have
two
main
things
like:
basically,
the
dosamin
service
and
dosage
game
service
to
service
is
the
one
that
interacting
a
lot
on
these
two
blockchain,
whereby
the
dosage
is
the
one
that
interacting
to
the
game
right
so,
but
we're
having
a
problem
when
we
try
to
implement
the
service
directly
into
a
phaser
3
game
engine
right,
something
I'm
not
sure
something
that
is
when
we
try
to
compile
it.
It
cannot
read
the
fluence
js
right
so
to
to
solve
it
out.
D
D
Actually,
inclusive
with
we
actually
tried
on
this
hackathon,
but
we
didn't
manage
to
complete
we.
What
we
do
is
we're
building
an
anti-cheat
system,
wherever
we
are
sending
the
information
directly
from
the
game,
a
certain
interval
for
every
hit
right
for
every
account
and
the
information
also
been
oh
yeah.
Another
thing
is
that
the
data
are
being
stored
also,
but
this
is
also
it's
a
bit
incomplete
that
we
actually
try
to
pull
everything
together
to
the
ipfs
for
any
of
the
services,
the
broadcaster
to
the
ipfs.
D
So
this
is
how
that
the
information
looks.
Basically
the
oracle
is
the
part
that
the
service
every
time
you
do,
the
main
you
do
the
relay
here.
Then
we
actually
need
the
nft
to
the
user.
So
then,
after
that
the
information
are
being
stopped
inside
the
bigchaindb
right.
So
for
the
service
itself,
we
acted
for
the
key
for
the
pitching
debate
information.
D
D
So
the
one
that
you
see
actually
for
what
we
built
one
one
thing
that
we
try
to
build
is
what
we
call
a
consumable
nft.
So
most
of
it
like
the
biggest
problem
in
the
game,
industry
is
like
when
you're
trying
to
compare
multiple
nft
to
a
single
nft.
So
most
of
the
time,
if
you
have
two
nft,
you
need
to
burn
through
nft
and
build
and
create
another
nft
whereby
it's
actually
it's
not
efficient
in
terms
of
the
gas
and
also
for
the
process.
It's
not
seamless,
so
what
we
built.
D
So
what
we
do
is
actually
the
service
one
of
the
services
right
by
the
dosamin
service
will
be
the
one
that
actually
responsible
to
do
the
check
so
yeah.
What
we
try
to
focus
to
do
is
actually
that,
because
we
are
actually
interacting
for
two
blockchain
so
to
produce
a
seamless
and
decentralized
oracle
to
deciding
in
terms
of
merging
between
the
base
and
also
for
the
slot
and
ft
right.
So
what
we
call
the
slot?
D
The
scheme
that
you
saw
in
the
video
just
like
it's
what
we
call
the
slots,
so
it
means
that
anyone
can
create
a
skin
right
now.
So
the
idea
is
that
anyone
can
create
the
skin
and
the
skin
that
you
can
send
a
request
to
throw
through
a
smart
contract,
especially
smart
contract,
and
it
can
merge
directly
to
what
we
call
the
base
and
ft
whereby
it's
the
base
rocket
that
you
saw
just
now
and
he's
updating
the
metadata
directly
from
that
right,
so
yeah.
So
that's!
Basically,
I
guess.
D
Every
time
we
do
the
merge
all
that
we
are
embedding
the
base
metadata
in
term
of
adding
the
what
we
call
the
nft,
the
nft
information
that
the
slot
and
the
slottable
nft
information
back
to
the
base,
nft
right
and
so
from
there
then.
So
it
means
that
we
generate
what
we
call
we
we
plan
to
do
more,
what
we
call
a
created
economy
and
displacer
using
this,
our
cost
removal,
nft.
A
A
Nobody
all
right,
I
have
a
couple
questions
for
you.
It
took
you
three
weeks
to
figure
out
what
influence
was
doing,
what
tricks
you
up
and
what
made
you
present
beer
to
to
actually
try
and
play
with
it.
D
D
We
have
been
too
through,
like
a
couple
of
hackathons
right.
The
services
that
have
been
provided,
the
things
are
not
really
to
the
things
that
we
are
looking
at,
because
most
of
it
is
not
scalable
whereby
actually
at
the
first,
we
all
didn't
know
about
the
fluence
right.
But
when
we
attend
your
your
your
session,
actually
every
I
mean
when
we
entered
the
session.
D
D
I
know
some
of
it
is
actually
a
quite
a
stupid
question
at
that
point,
but
because,
like
we
try
to
understand,
what's
going
on
that,
this
part
like
like
it
is,
and-
and
that's
what
make
us
like,
we
need
to
sleep
with
it.
Doesn't
matter
because,
at
that
time
we
have
one
week
before
the
submission
we
said
we
don't
mind,
we
don't
really
care
at
that
point
like
we
just
need
to
complete
it.
We
just
need
to
have
this,
because
this
is
to
be
honest.
D
It's
not
trying
to
to
put
you
out
it's
just
that,
like
what
you
feel.
This
is
basically
the
solution
that
can
solve
a
lot
of
problem,
so
we
need
this
doesn't
matter
for
the
hackathon.
At
that
point,
we
just
need
it
for
our
projects
and
ongoing
things
that
we
are
doing
so
we
just
get
through
it,
but
luckily
we
need
to
complete
it,
but
even
though
we
cannot
complete
all
of
it,
but
we
managed
to
complete
at
least
enough
for
the
presentation.
I
guess.
A
Very
cool,
very
cool:
well,
again,
congratulations
and
definitely
stay
in
touch
and
we've
got
a
few
pull
outs
and
I
think
folic
is
going
to
talk
a
little
bit
about
trust,
graph
and
registry
documentation,
which
I
believe
will
be
helpful
for
your
future
endeavors
anyway.
Congratulations
again
well
done!
Thank
you
very
much.
C
So
what
should
I
start
with
okay?
So
I
want
to
show
you
that
we
implemented
log
collection
for
for
our
network.
So
now
we
can
like
better
debug
this
stuff
when
people
come
to
us
with
problems
and
soon
you
know
sooner
or
later,
I
hope
sooner
will
have
a
thing.
So
anyone
who
runs
their
own
friends
account
will
be
able
to
send
their
logs
to
this
system
and
be
able
to
just
use
our
infrastructure
for
debugging
and
for
observability
into
their
own
networks
if
they
want
it
or
as
well.
C
We
provide
like
all
this
is
open
source.
So
all
this
infrastructure
as
code
is
open
source.
So
you
can
just
run
your
own
log
collection
performance
pretty
easily
and
we
will
have
a
documentation
over
it,
but
right
now
it
gives
us
the
actual,
like
look
into
the
system.
What
we're
like
what's
happening,
for
example,
I
can
see
that
here
is
a
particle.
It
came
at
this
time
and
it
went
for
through
all
these
nodes.
Then
it
did
something
in
that
time
and
I
can
like
debug
further
further
further
and
yeah.
C
So
that
slope
collection,
that's
pretty
pretty
awesome,
yeah
and
we're
constantly
working
on
metrics
that
I
usually
show
a
lot
so,
but
not
much
changes
and
soon
will
change
a
lot
okay.
So
that's
log
collection,
as
bernard
said:
yeah,
we'll
talk
a
little
bit
about
register
and
trust
grab
documentation.
C
We
have
a
huge
effort
in
writing
and
rewriting
editing
and
re-editing
the
readme
and
documentation
for
registry.
That's
our
service
for
service
discovery.
That's
our
basic
tool
for
service
discovery,
because
now
nice
pictures
that
hopefully
explain
what
happens.
C
I
think
those
features
they
can
give
a
good
overview
of
what
registry
is
it's
like
a
thing
that
you
can
that
allows
you
to
store
routing
information
for
services.
So
if
you
like,
deploy
a
bunch
of
services
like
10
of
them
or
some
something,
then
you
want
the
services
to
be
discoverable
by
other
people.
You
just
share
with
them
a
single
identification
string
and
they
can
find
their
services
in
network
registry
yeah.
So
that's,
basically
a
decentralized
content.
C
C
This
is
our
distributed
public
infrastructure
thing
that
allows
you
to
assign
different
weights
to
different
services.
Soon
we
will
use
it
for
resource
management,
so,
like
more
trusted,
services
will
get
more
resources,
resource
locations-
stuff
like
that,
so
it
all
will
be
programmable
and
flexible
and
yeah
it's
already
there.
You
can
already
start
to
to
learn
about
it
and
soon
we
will
integrate
it
into
registry
completely
and
it
will
be
possible
to
discover
services
judging
by
their
weights
in
transgraph,
so
yeah,
okay.
C
Another
thing
that
we
have
another
thing
that
we
have
is:
where
is
it?
Okay
is
we
we
have
implemented?
Let
me
make
it
a
little
bit
bigger.
We
have
implemented
metrics
that
are
available
from
within
the
aqua,
so
it's
a
service
matrix.
C
So
if
you,
for
example,
have
some
service,
for
example,
here
I
have
a
built-in
service
called
registry
that
we
just
saw
documentation
for
and
like
has
some
functions,
and
these
functions
you
you
might
want
to
know
how
often
they
called
how
many
calls
were
there,
which
calls
like
failed,
which
calls
took
what
time
on
average
or
hero
show
like
average
time
call
time
and
last
five
calls,
and
also
we
show
the
change
in
memory
consumption
by
the
service.
C
So
you
here
is
zero,
because
the
function
merge
is
stateless
and
it
doesn't
consume
any
memory,
but
if
it
was,
there
would
be
different
numbers
and
you
can
track
like
allocation
of
memory
in
your
service.
That's
very
useful
when
you
deploying
your
own
services
and
you
want
to
know
how
they
perform
like
how
which
functions
are
most
used
like
if
you
think
about
it
as
an
api.
C
That's
basically
metrics
for
your
api
for
its
call
time
for
performance,
for
memory
usage
and
for
popularity,
should
I
say
yeah
for
how
how
many
requests
are
there
so
yeah
and
I
hope
at
some
point
we
will
drop
some
dashboard
for
this
metric,
so
it
would
be
possible
to
like
explore
the
network
and
see
which
services
perform,
how
and
see
charts
on
that
stuff,
so
yeah
that
would
be.
That
would
be
awesome,
but
that
will
take
time.
C
What
else
would
I
was?
I
yeah
and
also
we've
been
working
hard
on
the
base
code,
integration
so
now
aqua
give
aqua.
So
we
have
a
programming
language
for
distributed
algorithms
and
we
have
a
vs
code
plugin
for
it,
and
it
supports
different
things
now,
for
example,
it
supports
go
into
definition,
so
you
can
go
control,
click
on
the
function
name
and
it
will
go
to
the
service
where
we'll
show
you
like,
the
definition
of
that
function.
Same
works
for
like
services
themselves
and
same
works
for
data
structures.
C
So
if
you're
like
point
and
click
on
this
structure,
you
will
see
what
fields
fields
it
has
and
where
is
it
defined?
Also,
a
very
important
thing
is
that
if
you
have
some
imports,
you
can
now
click
on
them
and
actually
see
their
api
before
that.
That
would
pretty
hard.
You
have
to
go
to
github
and
read
code
there,
but
now
you
can
just
control
click
on
imports
and
you
will
see
like
what.
C
What's
the
what
kind
of
built-in
functions
through
these
protocols
provide,
for
example,
you
can
concatenate
arrays,
you
can
like
connect
to
create
services
and
stuff
like
that,
and
it's
all
documented
all
here
so
yeah,
that's
pretty
a
pretty
big
change
in
quality
of
life
for
developers,
and
I
guess
that's
it.
A
F
F
What
allowed
us
to
measure
the
execution
time
of
different
parts
of
the
aqua
vm
tracing,
of
course
tracing
is
not,
is
not
good
for
estimating
performance
as
a
proper
profile.
However,
for
coarse
grained
parts
it
works
very
well
and
to
run
the
aqua
vm
locally
one
needs
some
tool.
F
F
F
F
F
F
F
F
F
F
For
example,
loading
of
this
data
took
five
milliseconds.
F
F
F
F
C
F
More
detailed
tracing
levels,
there
are
some
operations
that
are
executed
repeatedly,
and
this
wrapper
just
sounds
same
spans.
A
All
right-
and
I
have
some
questions
first,
how
does
a
developer,
who
wants
to
get
more
information,
actually
start
using
aqua
vm
trace?
What
do
they
have
to
do?
How
do
they
set
it
up?
How
do
they
prepare
the
data
that
needs
to
be
processed
like
you
had
in
that
file?
If
you
could
maybe
speak
a
little
bit
to
that.
F
Or
one
can
even
run
it
with
cargo
run
within
micro,
vm
project.