►
From YouTube: DXdev Weekly Sync [2023-01-17]
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Today
we
are
going
to
be
doing
the
usual
Roundup
over
the
Excel
projects
and
we
are
going
to
have
I
believe
like
two
short
presentations
from
from
dscope
team
that
are
going
to
be
presenting
the
integration
of
Sentry
in
in
W
application
and
from
Dino
he's
going
to
be
presenting
an
architecture
on
how
they
design
and
start
of
hooks
in
order
to
fetch
data
from
different
guilds
on
them
and
show
it
in
a
yeah
and
how
they
implement
it
in
the
in
in
code
in
in
David,
when
he,
when
he
talked
with
me
last
week
when
he
come
to
visit
to
my
house,
I
thought
it
was
really
interesting
and
it
proposed
him
to
to
share
what
they
did
in
in
the
weekly
development
difficult.
C
C
The
deal
is
going
to
present
later,
so
that's
mostly
I'll
completely
have
a
couple
of
PRS
remaining,
but
it's
all
gone
very
well,
and
so
now
we're
moving
on
to
kind
of
actually
using
the
architecture
for
something
interesting,
which
is
what
it
was
originally
designed
for,
which
is
supporting
both
RPC
calls
and
subgraph
fetching
store,
so
we're
implementing
the
subgraph
side
of
that,
starting
from
the
Sprint
now
yeah.
C
We're
actually
just
done
a
call
mobbing
the
setup
of
that
I'll
leave
the
rest
for
Dino
to
explain
later
other
interesting
stuff.
The
at
some
point
this
week.
Hopefully
the
next
couple
of
days
we'll
have
a
release
going
out
of
Davi
V
2.4,
so
keep
an
eye
out
for
that.
It's
just
going
through
the
last
stages
of
quinoa
and
I.
Think
that's
probably
everything
for
the
Roundup.
Unless
you
have
anything
to
add
a
good
stuff.
B
Yeah
on
the
DXL
contract
side,
we
received
the
final
report.
The
final
report
from
Omega.
There
are
I
think,
like
three
issues
left
to
fix
three
or
four:
they
are
small
ones
and
there
is
I'm
currently
discussing
with
them.
How
we
can
finally
agree
on
on
a
safe
on
yeah,
on
a
good
and
safe
way
to
execute
proposal
from
The
Body
Machine,
because
we
did
change
it
there
and
yeah.
That
is
that
is
in
the
last
stage
we
will
be
yeah.
B
We
will
be
closing
the
the
final
report
and
implement
the
final
fixes
this
week.
An
important,
a
very
good
thing
is
that
it
was
audited.
The
Avatar,
with
the
same
snapshot,
reputation
token
that
we
are
using
on
the
on
the
guilds
this
this
is.
This
is
cool
because
we
had
we
had
the
re-audited
again
the
snap,
the
elc20
snapshot,
token
that
we
use
for
the
gears
we
use
exactly
the
same
for
the
Dao
avatar
for
the
avatar
for
the
double
repetition,
token
and
yep.
B
The
final
report
will
be
hopefully
share
I
think
next
week
and
we
will
be
able
to
start
working
on
how
we
are
going
to
fetch
the
data
from
Davi
and
we
are
going
to
start
planning
how
we
are
going
to
integrate
this
Dao
framework
into
that
way.
C
C
B
Yeah
yeah
and
next
and
I'm
planning
to
the
Gathering
From
the
contributors
that
are
here
in
Argentina
at
my
house
here
in
Plata,
where
we
are
going
to
be
talking
about
the
final
steps
on
implementing
governance.
D
D
Miko
is
working
on
a
new
thoughtbox,
V2
I
believe
he
demoed
it
on
the
weekly
call.
It's
really
minimalistic
I,
like
it
I'm,
not
sure
if
maker
is
available.
If
he
wants
to
do
a
demo
of
that,
but
yeah,
that's
the
current
state
of
things:
you're
not
always
working
on
some
patches
for
the
limit
order,
we're
also
working
on
adding
Platinum
for
the
Eco
Bridge,
but
also
adding
some
other
additional
Microsoft
track
who's
using
the
pro
mode
or
who's
using
just
a
regular,
simple
mode
for
swapper.
D
So
those
are
the
main
things
happening
at
solver.
Yes,
I
forgot
we're.
Also.
We
have
like
one
inch
integration,
so
this
was
done
by
violet,
it's
basically
Taps
into
one
inch
and
then
tabs
and
one
inch
tabs
for
onto
like
all
of
the
available
oracles
that
have
integrated.
So
this
is
available
on
Avalanche,
polygon,
arbitrant,
mainnet
and
then
venosis
and
basically
we're
just
going
to
have
like
the
ones
that
swapper
gravity
supports.
B
D
But
I
have
to
mention
that,
like
one
inch
has
like
the
gasp
because,
like
it's
usually
more
cost
in
terms
of
gas,
but
also
they
also
take
a
feast
and
also
the
slippage.
If
it's
positive,
one
inch
is
going
to
take
that
as
a
profit
for
themselves.
B
D
B
Okay:
okay,
interesting
well,
awesome!
Milco!
If
you
want
to
demo
the
the
Dropbox
you
you've
been
working
on,
we
can
do
it
at
the
end
of
the
call.
A
I
can
do
it
now
as
well.
Why
not
yeah?
Let's
do
it
now?
Okay,
this
is
this
is
currently
what
we
have
regarding
designs.
There
are
some
things
missing:
I
have
a
sync
up
call
with
with
set
and
ranking
today,
and
we
went
through
it
and
right
now,
I
think
it's
cleared
and
every
we
have
everything
that
we
need
for
this.
This
part
of
the
of
the
process
and
what
this
is.
This
is
how
it
looks
like
you
can.
You
can
take
it.
A
This
is
closed,
swap
box.
This
is
this
expanded
with
with
the
details
about
about
transactions,
and
this
is
these-
are
the
states
that
we
were
discussing
today?
A
This
is
what
is
what
is
done
right
now,
so,
basically,
the
focus
was
on
creating
the
UI
first
after
this
we'll
we'll
proceed
with
with
the
implementation,
and
we
are
still
discussing
whether
we
should
use
the
the
old
functionalities
or
we
should.
We
should
I
mean
rewrite
everything
right
now.
This
is
this
is
what
we
have
I
component
as
the
the
small
box.
A
I
try
to
make
it
modular
if
we,
if
you're,
for
example,
to
to
dim
it
in
the
future
and
I
mean
this
is
work
in
progress,
though
all
of
the
values
are
are
placeholder
values
and
it
currently
has
no
functionalities.
But
I
should
I
think
that
we
will
proceed
with
the
functionalities
in
in
the
next
week.
B
Yeah
yeah,
it's
definitely
cleaner,
I've
been
using
software
I.
Think
last
week
and
yeah
I
can
see
the
difference.
Now
it
is
easier
to
understand
less
information.
There
way
cleaner.
A
B
Good
good
work,
okay
next
project
will
be
carried.
We
have
Dior
here
right.
B
E
Current
we've
been
working
on
campaigns
page.
They
will
allow
you
to
filter
campaigns.
We
are
working
on
that.
For
now
we
just
have
the
structure,
the
UI
structure,
but
now
we'll
start
to
play
with
that
as
well
and
start
to
do
some.
Some
filtering
on
that
Federico
also
deployed
the
epfs
Gateway
for
carrots
and
yeah.
I.
Think
that's
it
for
for
this
week,.
B
B
Hopefully
something
that
we
can
use
later
for
that,
we
can
add,
let's
say
like
abis
or
information,
I-
want
to
be
ready
to
other
projects
that.
B
B
Okay,
I
think
it
was
all
the
all
the
project
Roundup
any
other
project
or
initiative
that
we
want
to
review
before.
We
start
with
the
two
other
presentations
of
the
xcode
foreign.
B
What
do
you
want
to
show
first
I
believe
we
have
Sentry
yeah
the
sort
of
hooks.
C
Magnifying
versus
fairly
quickly
so
yeah
I
wrote
a
message
briefly
in
the
development
public
development
Channel
just
at
the
end
of
last
week
about
centuries,
like
kind
of
calls
over
goes
over
it,
but
also
good
for
anyone
wanting
to
collect
some
links,
but
essentially
I
mean
most
people
are
probably
at
least
relatively
aware
that
error
monitoring
tools
are
fairly
common,
at
least
outside
of
DX
style
and
I
guess,
potentially
we're
free,
but
yeah
they're,
just
chills
the
monitor
arrows
from
your
front
end
or
back
end
for
those
who
are
talking
about
the
front-ended
w
instance.
C
Entry
is
just
a
service
that
basically
Aggregates
all
those
those
errors
and
gives
you
so
much
good.
Look
at
all
of
them.
Yeah
yeah,
it's
a
pretty
cool
tool.
There's
lots
of
Alternatives
too,
as
well.
It's
a
pretty
I
guess:
project
hacked
Market,
but
yeah
we're
kind
of
running
to
the
issue
where
yeah
like,
if
you've,
probably
if
you've
used
dx4.
If
you've
used
a
Debbie.
If
you
run
into
errors,
it's
very
difficult
for
us
to
pinpoint
exactly
what's
happening.
C
Often
it
involves
asking
users
to
open
up
the
console
and
show
us
what
they're
seeing
this.
Basically,
let's
just
get
around
this
at
a
very
basic
level.
C
It
lets
us
look
at
the
exact
error,
that's
happening
in
a
user's
machine
and
give
us
some
more
details
so
that
we
know
where
to
actually
take
it
through
the
code,
without
bothering
the
user
for
more
details
and
a
further
level
that
allows
us
to
actually
look
at
errors
over
time,
seeing
if
there's
a
regression,
seeing
if
there's
like
a
trend
towards
certain
errors
and
actually
checking
the
errors
go
away
once
we
do
with
new
releases,
it's
just
quite
a
lot
of
cool
stuff.
C
There
obviously
I
think
it's
it's
relatively
similar
to
how
we
used
to
approach
like
analytics,
indeed
style,
where
it's
a
super
useful
feature
this
this
time
of
your
development
than
business
or
decision
making
stuff
that
it
was
with
analytics.
C
C
So
it
does
make
it
a
little
bit
different,
but
by
default
it
is
still
a
bit
of
a
security
concern,
the
log
IPS
and
by
default
they
have
some
data
scrolling
stuff,
but
it's
still
for
the
most
part,
storing
most
data-
that's
happening
inside
your
user's
consoles,
so
fortunately
we
can
just
choose
to
not
log
IPS,
that's
a
nice
thing
in
Sentry
and
the
other
side
of
it
is
scrubbing,
so
they
have
server.
C
Side,
scrubbing,
scrubbing,
just
being
basically
have
all
this
data,
that's
coming
and
they're,
storing
from
the
errors
and
the
logs
and
taking
personal
identifiable
information
outside
out
of
that
we're
basically
relying
on
the
the
default
stuff
that
they
provide,
but
also
adding
on
top
of
that
from
client
sites
scrubbing
of
Our
Own.
So
that
goes
through
transactions
addresses
EMS
names,
I
think!
C
That's
all
we
have
just
know,
basically
any
web3
specific
pii
information
we
can
think
of,
and
so
by
removing
that
there
isn't
really
a
lot
you
can
do
to
identify
users.
That's
kind
of
the
main
concern
is
just
trying
to
keep
any
privacy
issues
to
a
minimum
that
we
can
yeah.
B
Yeah
yeah
this
is
yeah.
This
is
very
important.
Both
things
first
protecting
the
users,
so
we
should
be
very
strict
on
what
we
are
sending
to
Century
and
and
then
using
centering
on
reporting
issues
right,
so
I
believe
that
Center
is
going
to
save
a
session
or
regarding
a
user,
when
you
are
using
the
application,
let's
say
Davi
and
if
you
find
an
issue
and
you
want
to
submit
a
bug,
what
do
you
have
to
look
for
a
Sentry?
So
we
can
so
the
team,
the
DX
club
team
can
access
to
that.
C
Yeah
pretty
much
we
haven't
got
it
set
up
perfectly
I.
Think
there'll
be
certainly
some
guesswork
of
working
out.
What
exactly
is
happening,
but
it's
just
an
additional
tool
in
our
tools
for
finding
bugs,
essentially
again,
it's
not
fully
set
up.
I
can
show
what
it
looks
like
I
guess
if
no
one's
seen
it
before,
we
just
have
it
set
up
in
QA
just
now,
and
we
haven't
gone
through
any
of
these
issues.
A
lot
of
them
are
non-issues
or
issues
we
know
about,
but
it's
pretty
cool.
C
Let's
see
how
many
times
it's
happening
we
go
into,
we
can
see.
What's
happening
from
this
would
usually
have
an
IP
address
in
it,
which
obviously
we
don't
want
to
be
doing
where
you
can
see
browsers,
which
is
stuff,
obviously
would
be
normally
filling
out
in
a
very
boring
bug.
Report
application,
I,
don't
think
we
have
any
examples.
I
can
maybe
try
and
find
one
and
post
it
in
a
chat
later
where
we
scrub
addresses,
but
it
just
replaces
strings.
C
Basically,
the
one
exception
to
that
is
urls,
so
that's
pretty
essential
to
debugging
the
rest
of
it.
We
can
certainly
it
would
be
nice
if
we
had
all
of
the
data.
Obviously,
if
we
could
see
the
exact
transaction
IDs
and
addresses
and
stuff,
it
would
make
life
easier,
but
it's
it's
enough
that
we
can
get
rid
of
it
and
have
the
the
privacy
and
still
get
enough
debugging
information
to
to
solve
stuff.
C
B
What
is
enabled
when
they
change
the
the
content
hash
from
and
I,
think
it
was
from.
B
Okay,
okay,
but
in
case,
for
example,
in
case
that
when
when
they
broke
it,
when
he
changed
the
content
hash
and
we
weren't
able
to
fetch
any
question
already
and
everyone
and
you
couldn't
use
it,
we
would
have
been
able
to
see
that
right.
If
we
had
it
set
configured
yeah.
C
That's
happening
and
we
can
set
it
up.
Obviously,
there's
a
lot
of
configuration.
We
can
do
to
actually
like
highlight
your
errors,
highlighting
breaking
errors
versus
just
like
things
are
happening
in
the
console,
so
you
can
actually
see
like
unhandled
errors,
yeah
as
I
say
it's
just
in
QA
right
now,
so
we
haven't
committed
to
putting
it
into
production
kind
of
wanted
to
see
what
people's
reactions
to
it.
Where
have
maybe
some
more
privacy
oriented
people
I.
B
I
guess:
let's
leave
it
in
QA.
So
if
you
want
to
use
only
production
because
you
don't
trust
Sentry
or
you
don't
trust
the
analytics
of
nto
or
what
your?
What
is
consuming
just
use
it
just
let's
leave
it
in
QA
and
we
can
use
in
production
anything
we
want.
And
if
we
find
the
bug,
if
we
think
we
find
about
production,
we
can
replicate
the
nqa
and
it
will
be
shown
in
in
inside.
C
Yeah
I
would
like
to
listen
to
Productions
the
whole
point
that
we're
doing
it
for
it's
just
encourages
now,
because
we're
not
released
yet
so
we're
planning
on
making
a
call
before
we
do
the
really
soon,
if
we
include
it
in
production
or
not,
we're
not
trying
react
qas
just
for
internal
stuff,
so
we're
not
trying
to
help
people
use
that
yeah
yeah.
B
Yeah,
maybe,
as
internally
we're
gonna,
still
do
like
heavy
testing
internally
using
QA
yeah.
Just
for
that
I
know.
We
have
to
be
careful
if
we
are
going
to
be
interested
in
something
like
this
in
production
that
we
need
to
be
100
sure
that
it's
not
going
to
leak
any
Personnel
or
private
data
into
Sentry
shut
up.
C
A
G
I
make
a
suggestion
about
something:
it's
not
related
to
privacy,
but
I've
used
them
in
the
past,
and
one
issue
we
encourage
was
like
very
repetitive
issue,
like
an
error
happening
on
loops,
for
example.
This
this
was
on
the
back
end.
I
know
this.
G
This
is
going
to
be
in
the
front
end,
so
it's
less
usual,
but
you
still
have
to
be
careful
if
you
find
something
that
gets
triggered
like
many
times
per
second,
it
will
fill
up
all
the
Sentry
errors
on
because
you
pay
based
on
the
amount
of
data
you
get
in
happened
to
us
in
the
past,
where
we
got
the
the
quota
like
the
the
money
we
filled
up
just
because
of
one
error,
so
we
had
to
implement
things
to
prevent
if
the
same
area
happening
over
and
over
just
to
stop
it.
G
G
C
C
Area
they
want
to
have
just
nose,
vein
and
I.
Think
there's
an
even
better
one.
That's
like
fairly
cheap,
so
long
as
it's
not
unlimited,
because
it
seems
like
a
a
dangerous
combination
of
infinite.
B
B
Okay.
We
can
move
to
the
next
thing.
Dino,
do
you
wanna
resend,
the
thought
of
hooks
or
I?
Don't
know
if,
if
that
the
proper
name
for
it
or
not,
yeah.
F
How
this
came
up,
we
were
implementing
data
fetching
using
the
subgraph.
I
mean
right
now.
David
does
a
little
Fiji
using
your
particles,
but
we
had
two
two
wishes.
One
is
the
amount
of
data
that
we
get
the
amount,
not
the
amount
of
data,
but
the
aggregating
data
and
doing
stuff
like
that
doing.
Rpc
calls
it's
gonna,
be
very.
F
What's
going
to
be
very
complicated
and
some
things
we
couldn't
even
Implement
and
the
other
thing
was
we
had
one
if
you've
been
using
Derby,
some
RPC
issues
are
common
or
I,
don't
know
if
you've
come
under
there.
There
are
RPC
issues,
and
so,
with
the
subgraph
things
are,
we
can
do
more
data
transformation
before.
F
Send
it
to
a
user
and
it's
way
way
faster
and
we
hope
it's
way
more
stable
than
their
physicals.
So
the
initial
issue
we
had
is
like:
how
do
we
combined
two
data
sources?
How
do
we
fetch
data
from
two
data
sources
that.
F
A
F
F
So
the
idea
is
this
zooming
part
it's
like
we
could
have
a
store
that
has
a
features
hook
under
pressure
cook.
Just
will
expose
one
set
of
hooks
that
gets
I,
don't
know,
for
example,
get
proposal
data
and
the
component
won't
won't
care
about
what
the
use
proposal
data.
Does
it
just
guess
that
it
gets
the
information
of
The
Proposal
information
that
the
proposal
information
it
doesn't
care
if
it
comes
from
the.
F
An
RPC
code
and
when
we
zoom
out
of
out
of
that
idea,
we
are
really.
We
realized
that
we
could
solve
another
problem.
It
was
how
do
we
support
more
than
one
governance
implementation
right
right
now
we
only
have
guilds,
but
in
the
near
future
we're
gonna
have
governance,
1.5,
then
governance,
2.0
and
then
I
know
maybe
Governor
or
or
whatever
other
governance
implementation
we
we
might
need.
F
F
F
This
is
like
the
the
cool
part.
It's
like
we
have
this.
This
governance
implementation
is
shared
across
all
the
all
the
the
app
and
these
hooks
are
gonna
expose
yeah
the
the
hooks
related
to
that
data,
fetching
implementation,
so.
F
F
We
get
the
well
right
now
we
we
match
byte
codes
with
governance
implementation,
but
that's
how
we
do
it
and
the
good
thing
is
we
just
return
one
object
and
say
sorry:
this
is
the
name
of
the
governance
type,
whatever
this
ethical,
the
capabilities
that
lets
us,
for
example,
discover
less
implementation,
has
snapshot
this
governance
permutation
it's
on
the
prep
whatever,
and
then
you
have
hooks
that
hooks
are
filled
with
features
and
writers.
F
So
the
the
component
will
only
call
hooks
dot,
Fetchers
dot,
get
Focus
information
or
cooks.writers
dot
vote
proposal,
and
it
will
send
the.
D
F
The
hook
and
how
the
data
is
processed
will
depend
on
the
governance
implementation
that
we
have
here
on
the
right.
Each
module
will
have
a
different
governance
implementation
that
each
module
have
its
factors.
Events
well
writers
in
the
here
in
the
common
common
folder.
This
will
change
soon,
but
but
yeah,
that's
that's
the
core
idea.
So
in
each
component
we
just
call
yeah,
that's
good.
One
hurdle
we
had
was
react
really
doesn't
like
their
hooks
order
to
be
changed.
F
So
when
we
implemented
two
kinds
of
in
the
same
hook
with
two
different
implement
implementations,
we
call
different
hooks
at
different
order.
That's
expected!
We
are
getting
errors
so
how
we
solved.
It
was
a
very
high
level
loading
state
that
if
the
hook
in
rotation
is
still
loading,
it
derenders
the
whole
app
and
changes
switches
and
hooks
and
renders
the
app
again.
So,
let's
solve
the
the
different
hook
order
error
in
react.
F
So
that's
that's!
Basically,
it
I'll,
just
you
know,
I
think
we
have
this
check
data
source
availability
that
will
check
every
10
seconds,
but
it
could
be
more
or
less
if
the
default
data
source
is
healthy
and
that
could
be
whatever
you
want.
The.
E
A
F
If
their
default
data
source
is
healthy,
how
are
you
find
healthy
and
returns
either
true
or
false?
If
it's
not
healthy,
it
will
like
go
to
a
fallback
data
source,
fetching
mechanism
that
you'll
find
so
sorry
they
did
is
to
check
if
the
subgraph
is
healthy.
If
it's
not,
we
default
to
RPC
calls
and
the
way
it's
done.
You
don't
need
two
data
sources,
that's
just
if
you
want
it
or
robust,
but.
F
Source
and
basically
that
health
check
will
always
return
true,
and
you
can
just
every
every
time
have
only
one
data
source
for
Fiji.
So
that's
it
the
code.
Well,
it's
basically
your
merch
and
yeah.
We
had
to
do
a
lot
of
typing
to
assure
that
we
get
past
the
same
data
and
return
the
same
data
for
every
hook.
B
Awesome
awesome:
it
is
great
to
have
choose
Source
two
sources
of
data.
I
think
we
are
usually
relying
on
one
swapper
uses
only
the
graph
right,
Adam.
B
Swapper
uses
only
the
graph
right.
Yes,.
B
D
Thing
about
the
thing
about
the
sub
Graphics
that
allows
you
to
actually
retrieve
all
data.
For
example.
Let
me
give
an
example:
if
you
want
to
calculate
your
principle
on
swapper
right
now,
there
is
no
way
you
can
do
it
without
having
to
track
all
of
the
minting
and
burning
of
lpps
or
flp
tokens.
Since
the
Inception
of
the
router
or
swapper
router
in
the
flat
in
the
factory
with
the
subgraph,
you
have
all
of
these
data,
and
then
you
add
them.
D
You
take
the
burn
and
then
the
mint,
and
then
you
get
the
original
principle.
I,
don't
think
it's
possible
with
the
RPC
without
a
subgraph,
you.
G
D
C
C
Way
we're
getting
that.
Obviously,
we
have
a
bit
of
a
nicer
time
in
governance.
There's
only
a
few
features
that
we
can
that
we
can't
do
with
just
very
getter
functions,
and
so
we
just
have
some
features
that
are
of
graph
only
exactly
but
yeah.
The
aim
for
us
is
to
be
able
to
still
operate
the
dial
if
the
sub
graph
is
down.
D
It's
totally
doable.
It
depends
on
your
the
data
you
wanted
to
retrieve.
Are
you
trying
to
get
like
a
after
date?
Information?
Let's
say
you
want
to
you
want
to
get
the
balance
of
faith
a
token
you
can
do
this.
You
can
do
this
like
using
the
RPC
or
you
can
do
it
using
the
sub
graph,
because
the
sub
Graphics
can
also
track
those
information
if
you
want
to,
but
I
would
rather
go
with
your
obviously
just
one
call.
B
Yeah,
the
idea
is
also
here
to
have
well
now
the
graph
cards
become
like
in
a
standard
right
and
like
every
application
use
it,
and
we
don't
know
if
this
is
going
to
be
the
case
in
the
future.
Hopefully,
there's
going
to
be
an
alternative,
an
automatic
for
the
graph
in
the
future
or
someone
that
I
know
will
form
the
process
or
start
their
own
index
or
service
or
we.
You
can
also
rely
on
on
RPC
and
reject
connection
to
to
nodes
right
actually.
G
B
G
G
D
We
have
a
telegram
group
with
them:
okay,
cool
yeah,
yeah,
well
also
the
sub
the
graph
is
moving
to
the
decentralized
Network
like
every
every
subgraph
deployed
today
is
going
to
be
shut
down
in
June,
I
believe,
but
right
now,
if
you
want
to,
if
you
want
to
deploy
a
new
subgraph,
the
recommended
way
is
that
you
go
and
get
about
3
000,
GRT
tokens,
and
then
you
stake
that
and
then
you
deploy
it
using
the
graph
Studio.
G
Not
sure
now
but
like
when
I
used
to
deploy
things
to
the
decentralized
network
it.
What
happened
was
because
the
the
indexes
get
paid
based
on
the
amount
of
queries
you
make
to
your
own
supraphs
when
the
soup
graphs
are
big
enough.
So
it's
not
that
profitable
for
the
indexes
they
drop,
indexing,
you're
so
graph,
so
you
they
just
stopped
doing
it
and
it
was
quite
bad.
So
we
keep
using
the
like
the
hosted
services,
not.
D
B
The
scope
team
for
that
hacking
implementation
looks
good,
looking
forward
to
continue
testing
it
and
I
think
this
will
be
all
for
today's
weekly
developer
call.
Hopefully
we
are
going
to
have
a
good
content
for
the
next
developer
call
in
a
week,
so
yeah
awesome
to
have
you
guys
here
and
see
you
in
Cubase
gracias.