►
From YouTube: DXbiz Weekly Meeting [2020-09-28]
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
So
yeah,
I
think,
there's
two
kind
of
significantly
different
states
of
dx
swap
right,
there's
going
to
be
pre-aggregation
when
there's
like
going
to
be
a
limited
number
of
tokens
effectively
that
you
can
trade
due
to
limited
liquidity
right,
so
that's
going
to
be
totally
different
than
when
aggregation
is
added,
and
you
can
basically
trade
everything
that
unit
swap
has
plus
what
dx
swap
has
so
yeah.
I
mean
I
think
for
that
when
you're
thinking
about
the
designs
there's
those
kind
of
like
two,
those
are
going
to
be
different.
A
C
D
B
Yeah,
that's
something
we
have
to
figure
out.
I
think
you
would
just
use
the
bigger
pool
clip.
B
But
we
have
to
look
at
that
because
I
mean,
I
think,
that's
how
we
implement
the
aggregator
like
that's,
we
could
choose
to
do
it
either
way.
B
B
But
exactly
how
it's
going
to
be
done
is
not
implemented
yet,
but
I
do
think
there's
like
those.
C
I
think
there's
also
an
interesting
idea
floating
around,
which
which
is
basically
merging
balance
the
balancer
protocol
with
with
dx4
protocol
and
make
it
so
that
the
user
will
actually
don't
think
about
two
different
protocols.
But
rather
it
will
be
just
one
trading
interface,
where
users
can
provide
liquidity
for
either
two
tokens
or
like
several
tokens,
and
we
don't
need
to
like
explain
them
that
it's
actually
like
two
different
protocols.
B
B
I
do
I
do
know
that
the
that
is
going
to
be
much
further
out
than
unisoft
integra
integration:
okay,
okay,
yeah
yeah.
I.
B
An
idea
that's
floating
around
right
like,
but
I'm
just
saying
like
right
in
terms
of
time
frames
here,
like
I
think
you
know,
uniswap
aggregation
could
be
a
quick
follow-on
feature
after
it
launches
very
like
maybe
like
weeks
after
the
initial
launch,
whereas
I
think
integrating
something
like
balancer
is
going
to
take
probably
months
of
work
to
like
really
understand
how
that
would
work
and
do
it.
But.
A
A
I
guess
the
I
think
I
do
think
the
router
is
important
for
or
just
like,
as
part
of
like
how
it
fits
into
the
strategy.
Knowing
that
we
can
do
it.
A
F
F
But
yeah,
this
is
why
I
think
we
can
win
win
by
having
a
really
good
experience
like
just
short
short
term,
and
then
we
we
do
all
the
long
term.
Meanwhile,.
F
C
I
think
I
mean
it
basically
fixes
the
I
go
to
one
inch
check
the
price,
which
is
basically
probably
uni
swipe,
and
then
they
go
to
unicef
and
actually
do
the
trade.
But
on
dx
swap
you
go
to
dx
swap
and
you
you
get
the
best
price
because
it
is
connected
to
the
uni
swap
and
then
you
like
stay
there
and
actually
do
the
trade.
Because
you
know
it
is
the
cheapest.
C
And
chris,
do
you
actually
like
you,
don't
think
that
we
can
actually
win
a
few
pools
by
doing
the
whole
rewards
program.
A
No,
I
do,
I
think,
that's
like
I
think
that
is
like
expensive
when
you
think
about
it,
because
you
are
like
paying
that
out
and
that's
what
I'm
saying
is
the
nice
thing
about
the
router
experience
is,
if
you
have
that
it's
just
a
lot
cheaper
to
get
to
the
end
state
of
like
a
nice
trader
experience
where
they
can
trade
a
whole
bunch
of
things,
because
otherwise,
without
that
we
do
have
to
do
like
the
dxd
rewards,
and
I
think
we
should.
You
know
do
that.
A
I
think
that's
part
of
the
plan,
but
I
just
prefer
not
to
have
it
as
big
yeah.
I
mean.
I
think
that
we
should
the
way
I'm
thinking
of
it
is
basically
the
same
kind
of
pairs
that
we've
been
talking
about
the
whole
time,
the
10
or
so
loopering
gnosis,
dow,
stat
and
jen
and
and
those
but
not
like,
not
like
random
pairs.
C
Yeah
still
pretty
focused
yeah
like
I
still.
I
still
think
that,
like
this
is
like
the
last
gun,
and
we
should
use
it
only
like
when
we
realize
okay,
we
actually
need
to
pull
out
the
guns.
Now
I
I
think
we
have
like
zed
already
said.
We
have
a
lot
of
other
things
to
do,
and
I
think
we
can
already
like
prepare
to
like
actually
create
the
biggest
guns
we
have,
which
is
like
making
sure
that
we
have.
The
whole
migration
process
are
like
ready
right
like
the
the
migration
should
be
like.
C
C
And
like,
and
with
that
like,
then
we
can
shoot
the
rewards
program
and
then,
but
what
is
important
is
that
we
we
need
to
have
the
whole
dhd
governance
ready,
which
is
like.
Oh,
I
don't
need
to
sell
the
dxp
because
they
actually
give
you
like
true
governance
rights
right.
So
it's
like,
I
think
we
have
a
huge
task
list
which
we
need
to
like
deliver,
so
we
can
actually
have
like
the
biggest
gun
ever
and
that's
yeah,
and
I
think
that
is
that
will
be
successful.
F
I
think
actually,
the
uni
drop
thing
was
healthy
for
us,
because
people
are
actually
talking
about
governance
and
it's
not
fair
to
own
one
percent
of
something
to
do
a
proposal
whatever
they
have.
I
think
it's
healthy,
because
I've
seen
a
lot
of
discussions
and
people
think
that
governance
will
be
some
kind
of
new
high,
because
whales
are
interested
in
actually
not
only
trading
and
making
money.
Actually
they
are
interested
in
products
and
changing
stuff
and
making
stuff
better.
F
C
Like
even
even
hazu-
and
I
think,
some
some
other
big
vc
guy
actually
like
oh
yeah,
it
makes
sense
to
dilute
mkr
holders
who
are
not
voting
and
it's
like
yeah.
We
already
know
that
since
a
few
months
and
we're
like
already
progressing
as
a
dxr
who's
like
if
you're
not
contribute,
you
will
be
diluted
and
like
they
just
they.
I
guess
they're
just
waking
up
a
little
bit.
C
I
still
think
like
this
liquid
token
governance
will
keep
them
busy
for
a
while
until
they
like
got
made
actually
like
a
lot
of
money
out
of
this
whole.
But
then
the
real
game
actually
happens
with
like
true
governance,
and
I
think
we
are
like
already
progressing
so
relaxed
like
so
chilled
our
way,
and
I
think
we
should
keep
being
chilled
and
just
continue
our.
G
I
agree:
okay,
if
we
have
time
I'd
love
to
continue
this
later,
we
have
two
two
guests
on
on
the
call
we
have
chris
s
from
badger
dao
who
would
just
like
to
you
know
just
reach
out
and
just
start
an
initial
conversation
with
us,
and
we
have
jordan
from
diorg
looking
to
introduce
web3
api
to
us.
So
first,
I'd
like
to
have
chris
take
the
floor.
If
you're
there
chris
hello.
I
I
Just
to
give
you
guys
a
brief
overview
of
badger,
I
think
there
could
be
some
cool
collaboration
points
between
our
groups,
but
nonetheless,
really
what
what
we're
building
is
we're
trying
to
build
an
ecosystem
dao
where
all
the
best
projects
and
developers
and
really
the
best
builders
in
the
space
come
together
with
shared
ownership,
to
create
cool
products
and
infrastructure,
and
that
product
and
infrastructure
focus
is
specifically
on
bitcoin
and
d5,
so
really
building
better
bridges.
Once
it's
in
different
networks,
you
know
better
tools,
better
products,
more
products.
I
I
just
think
today
we
have
such
limited
products
in
the
market
if
it's
just
curved
for
liquidity-
or
you
know
just
run
btc
or
nwbc
for
wrapping
there's
just
so
many
more
things.
We
can
do
better,
vault,
better
bulk
strategies
and
hedging
and
so
forth,
and
so
on.
I
So
nonetheless,
we're
committed
to
building
those
products
and
the
way
that
we're
doing
it
is
we
want
as
many
of
the
community
members
involved
and
we're
trying
to
really
change
how
products
are
created
so
every
product,
and
every
idea
is
something
that's
ideated
within
the
community
pitch
to
the
community
voted
on
and
then
once
approved,
our
internal
operations
team
will
work
with
the
community
members
that
are
proposing
the
products
and
bring
it
to
life
and,
and
then
anybody
that
participated
in
it
would
have
a
percentage
share
in
any
value
or
revenue
or
fees
or
anything
that's
created
from
it.
I
So
we
anticipate
a
lot
of
great
projects
in
the
space
to
get
involved.
We
have
a
few
that
we're
going
to
be
announcing
shortly
and
what
we're
doing
prior
to
launch,
which
is
in
a
few
weeks,
is
we're
going
to
be
launching
with
two
products,
one
that's
similar
to
that
of
a
wi-fi
vault.
I
We
call
it
set
and
we're
gonna
have
different
strategies
for
btc
lp
tokens,
so
the
uniswap
wbtce
we're
going
to
do
com
we're
going
to
take
a
compounding
strategy
there,
where
you
can
deposit
those
lp
tokens
and
then
we'll
systematically
sell
the
unit,
swap
put
it
back
into
the
pool
to
compound
the
returns
and
then
similar
with
the
curved
ram
btc
and
curve
sptc
lp
token.
I
So
we're
gonna
go
to
market
with
that
product
and
our
second
product
that
we
built
is
elastic
supply
cryptocurrency,
but
pegged
to
the
price
of
bitcoin
and
completely
owned
by
the
the
community
endowed.
So
I
can
get
into
some
more
details
around
like
how
we're
attempting
to
do
a
fair
launch
and
some
of
these
other
things.
I
A
Cool
yeah,
I'd
just
say,
really
interested
in
kind
of
the
the
btc
angle.
I
don't
think
there's.
Obviously
I
think
it's
a
big
market
growth.
A
lot
of
areas.
Wptc
is
obviously
kind
of
gone
through
the
roof
here
in
the
last
couple
months.
I
imagine
we
would
not
be
comfortable
with
that
product,
and
so
I
think
we're
interested
in
kind
of,
but
I
think
bitcoin
is
clearly
a
important
part
of
whatever
decentralized
future
is
coming.
So
I
think
we're
when
we
talk
about
like
some
of
these
products.
A
I
Our
idea
is
obviously,
but
it's
going
to
be
community
driven
regardless,
but
we'd
love
to
have
a
community-owned
bridge
with
you
know,
50-plus
community
members
voted
in
that
are
managing
bitcoin,
multiple
series
and
from
having
you
know
that
through
the
bridge
into
our
products
and
other
people's
products
and
having
like
the
badger
btc,
which
in
turn
is
owned
by
everyone
like
we
have
like
10
amazing
projects
and
a
bunch
of
developers
that
are
part
of
the
community
and
help
build
it.
I
You
know
everyone's
going
to
share
in
those
withdrawal,
deposit
fees
and
and
everything
that
can
come
from
it
right
so
yeah.
I
agree
we're
also
not
that
comfortable
with
the
products
in
the
market,
but
that
ptc,
you
know,
I'm
a
long-term
bitcoin
guy
and
it
just.
We
just
need
it
right
like
it's.
It's
it's
indelible
so.
G
We're
building
bridges
between
blockchains,
so
it's
good
that
you
know
we.
You
know
we
have
dials,
get
to
know
each
other
and
like
know
what
each
taos
are
up
to,
and
I
think
chris
is
up
to
some
really
interesting
stuff
and
it's
definitely
captured
like
a
very,
very
unique
and
specific
audience,
which
is
dope.
G
Not
yours
thanks
love,
coming
up
all
right,
so
jordan,
if
you're
there
we'd
love
for
you
to
present
web3
api
onto
the
dxf,
some
great.
J
Stuff
hi
everyone
yeah,
my
name
is
jordan.
I'm
a
developer.
I've
been
working
with
d-org,
and
so
I
want
to
talk
to
you
today
about
web3
api,
because
it's
a
project
that
I
think
will
help
the
whole
web
3
space
and
particularly
organizations
like
the
dxo
that
are
managing
multiple
different
applications
that
are
using
one
or
more
protocols
so,
first
off
what
is
web3
api,
so
there
was
a
video
center
on.
I
can
also
just
show
like
a
quick
little
three
minute.
Video.
J
Would
you
all,
rather
that
or
would
you
rather
me
dictate
it?
The
downside
with
me
you
know
speaking,
is
that
there's
no
visuals,
so
there
is
a
feature
in
jitsi
where
I
can
just
play
a
quick
youtube
video.
So
if
you
guys
want
to
sit
through
a
quick,
three
minute
youtube
video,
we
could
do
that.
J
Video
all
right,
web3
api
is
a
developer
tool
chain
that
brings
the
ease
of
web
2
to
web3.
It
enables
multi-platform
and
dynamic
web
3
applications,
there's
a
problem
going
largely
unnoticed
in
the
web3
ecosystem.
The
integration
problem
in
web
2
applications
are
lightweight
and
all
complex
logic
is
executed
within
central
servers.
When
a
user
tweets,
the
application
simply
makes
a
request
to
twitter's
api,
but
in
web3
applications
must
handle
complex
logic
themselves,
because
central
servers
have
been
replaced
with
expensive,
smart
contracts
and
other
peer-to-peer
networks.
J
As
a
result,
web3
applications
are
bloated
with
libraries
and
sdks
to
do
the
heavy
lifting
this
is
the
integration
problem,
for
example,
consider
a
dial
proposal
or
a
dex
aggregated
token,
swap
in
both
of
these
instances
we
have
complex
logic
being
executed
within
the
application,
making
developments
slower
and
more
error-prone.
This
integration
strategy
also
means
programming.
Languages
must
be
manually
supported
by
rewriting
the
protocol's
in-app
logic.
J
This
slows
web
3's
rate
of
adoption
and
innovation
by
at
least
an
order
of
magnitude
when
compared
to
web
2..
Web
3
needs
to
be
simple.
We
can
do
better
enter
web3
api,
a
standard
that
makes
integrating
web3
as
easy
as
web.
2.
web3
api
allows
any
type
of
application
to
execute
complex
protocol
logic
on
the
fly
simply
send
a
query
to
the
protocol's
decentralized
api
endpoint.
All
protocol
logic
will
be
downloaded
and
run
in
the
application.
J
Thanks
to
the
magic
of
webassembly,
for
example,
we
might
send
a
swap
graphql
query
to
api.univ
web3
apis
can
be
used
in
any
programming.
Language
simply
add
the
web3
api
client
to
your
project.
Web3Api
modules
can
also
query
each
other
enabling
composability
and
extendability,
like
we've
never
seen
before.
J
Now,
our
web
3
applications
can
go
back
to
being
simple
and
multi-platform.
Just
like
we've
come
to
expect
from
web
2..
We
recently
finished
this
finalist
and
won
several
prizes
at
hackfs.
Since
then,
we
have
been
all
right
cool.
I
I
won't
bore
you
with
the
rest
of
the
video,
but
that's
the
essence
of
it.
Why
is
this
interesting?
The
dx
style
it
makes
you
know
your
lives
easier
as
application
developers
it.
It
also
can
allow
you
to
fork
apis
and
modify
them
and
do
different
cool
things
with
them.
J
A
lot
easier
and
we're
also
spinning
up
a
dial
for
web3
api,
so
the
point
of
the
style
is
to
be
able
to
steward
the
standard
and
have
funders
come
in
and
contribute
funds
and
then
have
builder
organizations
like,
for
instance,
the
dxdo
could
be
a
funder
or
a
builder,
and
then
allow
builder
organizations
to
make
proposals
to
build
out
different
web
3
apis
and
then
also
the
the
different
tooling
within
the
stack.
Let's
say
so,
do
you
guys
have
any
questions
about
the
tech
itself?
J
G
More
on,
like
the
quarter
part
like.
What's
that
sorry,
what
what
would
I
guess,
how
how
would
dxdow
function
as
like
a
builder
partner
for
four
web
through
api
yeah
for.
J
Sure
so,
let's
sit
like
in
standing
up
this
new
standard
for
these
application.
Libraries
popular
protocols
will
need
to
be
recreated
within
webassembly,
using
let's
say
like
assembly
script
or
some
other
languages
that
compose
the
wasm.
J
And
so
you
know,
there's
lots
of
opportunity
here
to
make
proposals
to
the
web3
api
dial
to
be
able
to
implement
these,
and
then
also
you
know
if,
let's
say
the
dx
style
wanted
web
3
apis
to
be
made
for
its
protocols
that
it
that
it
manages
it
could
make
a
proposal
in
this
dial
to
have
that
done.
And
then,
if
the
dx
dial,
let's
say,
contributed
funds
to
this
dow,
I
would
it
would
have
shareholder
ship,
and
so
it
could.
J
Not
just
within
the
browser
or
node
and
so
yeah
like
it,
it
could
mean
lots
more
users
on
your
various
different
protocols
that
dx
dial
stewards,
yeah
ori
do
do
you
have
anything
to
add
from
that?
Was
there
anything
that
I
had
missed.
E
G
Bird,
I
do
want
to
say
that,
like
we've
been
approached,
I
guess
a
couple
times
around
like
investments
in
startups
and
stuff,
and
you
know
obviously
that,
like
a
lot
of
us
are
busy
with
like
products
and
things
like
that,
I
just
I
think
it's
a
it's.
A
interesting
idea
to
start
thinking
about
that,
like
dao,
is
investing
in
other
things,
especially
if.
J
J
If,
if
this
is
tooling
that
you
all
think
would
make
your
lives
easier,
yeah
and-
and
you
know,
we're
we're
in
the
process
of
gathering
lots
of
different
integration
partnerships,
and
so
the
dx
style
could
be
do
one
of
those
yeah
that
is
basically
signaling
like
this
totally
makes
their
lives
easier.
C
Yeah
joe,
I
I
have
a
question
like
is:
is
it
tooling
beneficial
for
product
development
or
is
it?
Is
this
beneficial
for
the
geek
styles
infrastructure
like
yeah.
J
And
yeah
that
that's
a
great
question,
so
it
is
for
product
development.
This
actually
makes
first
off
integrating
several
different
protocols,
a
lot
easier,
because
the
user
flow
around
integrating
them
is
no
longer.
You
know
see
if
they
have
a
javascript
sdk.
Add
that
figure
out
how
to
use
it
and
then
now,
all
of
a
sudden,
you
know,
like
your
application,
is
bloated.
J
The
user
flow
of
integrating
a
web3
api
is
now
you
just
add
the
web
through
api
client
to
your
browser
application,
and
then
you
query
their
endpoint.
Let's
say
it's
api.mesa.eth
and
then
the
query
may
be,
you
know,
create
new
pool,
or
you
know,
cast
a
vote
on
this,
and
so
that
that's
one
benefit
is
that
it's
a
lot
easier
to
integrate
and
it
also
doesn't
bloat
your
applications.
J
So
these
different
schemes,
one
of
the
big
problems
here,
though,
is
that
when
you
publish
a
scheme,
the
ui
has
to
be
rebuilt
in
order
to
facilitate
that
functionality
of
interacting
with
that
scheme
with
web3
api.
Since
these
wasm
modules
are
downloaded
at
runtime,
the
application
can
be
built
once
and
then
made
so
that
it
can
have
dynamic
ui
based
off
these
various
different
features,
and
so
this
would
be
interesting
for
dao
applications.
J
This
would
be
interesting
for
interesting
for
any
other
type
of
protocol
like,
for
instance,
a
wi-fi
strategy
that
you
want
some
semblance
of
what's
happening
on
chain
from
these
various
different
like
published
contracts
being
represented
in
the
ui
without
having
to
like
constantly
maintain
the
ui.
So
it
really
helps
the
horizontal
scalability
of
ecosystems,
but
yeah
that
that
use
case
takes
a
little
bit
more
imagination
to
really
grasp.
C
J
The
stuff
anymore,
if
if
by
online
you
mean
the
the
api
being
present
on
ipfs,
then
yes,
and
so,
but
but
there
is
no
server
that
is
required
for
this.
It's
strictly
just
a
package
that
is
running
within
the
client.
J
Right
yeah,
that's
that's!
How
it
works
is
that
these
packages,
all
the
web3
api
package,
is,
is
a
graphql
schema,
which
is
your
you
know,
your
interface
for
the
api
and
then
behind.
That
is
these
web
assembly
modules
and
these
webassembly
modules
get
downloaded
and
run
inside
the
application,
and
so
it's
completely
decentralized.
There
is
no
backing
service
of
any.
J
J
Yeah
and
then
you
know
just
to
reiterate
the
reason
why
this
is
cool
is
because
it's
dynamic,
you
know
you,
you
can
now
download
this
at
runtime
and
then
the
biggest
point
is
that
it's
multi-platform,
so
you
can
use
this
in
python,
go
c-sharp.
You
know
javascript
whatever.
J
Yeah,
so
I
I
do
think
yes,
it
does
make
developing
dapps
ten
times
easier,
because
now,
interacting
with
web3
protocols
like
uniswap
or
mesa,
becomes
the
same
as
let's
say,
querying
a
web
to
api,
it's
just
simple,
graphql
or
rest
queries
and
and
then
more
benefits
come
around
when
you
think
of,
like
you
know
more
advanced
dap
development
scenarios,
where
let's
say
you
have
an
aggregation,
dap
like
zurion
or
zapper,
those
adapts
become
really
bloated
as
they
interact
with
more
and
more
protocols.
J
This
is
not
the
case
with
web3
api,
because
again
these
logic
modules
are
being
downloaded
at
runtime.
The
same
way
like
you
know,
you
can
have
postman
interact
with
any
web
web
2
service
and
postman
isn't
a
huge
bloated
application
right.
It's
just
using
like
this
standard
protocol,
so
the
same
rules
apply
here
and
and
and
then
like.
The
last
big
thing
is
dynamic
applications
which
I
won't
go
through
the
effort
of
explaining
again
but
like
that's
another
big
use
case
that
we
haven't
really
seen
in
web3,
that's
totally
possible.
J
Yes,
yeah,
I'm
just
going
to
add
that
I
think
that
it's
really
helpful
for
if
you
are
primarily
focused
on
authoring
next
level
protocols
like
let's
say
you
know,
let's
say,
for
instance,
you
wanted
to
incentivize
the
usage
of
let's
say
a
uniswap
fork
that
has
some
augmentation
to
it
to
make
it
better
than
uniswap.
J
In
order
to
get
people
to
use
this
today,
you
would
have
to
say:
hey
use
our
app
like
go
to
this
endpoint
use
our
application
instead
of
uniswap.org,
but
with
web3
apis,
it's
much
simpler
to
be
able
to
basically
make
a
incentivized
campaign
around
application
developers.
Integrating
your
protocol
so
basically
saying
hey.
Zapper.
Add
this
to
your
add
this
to
your
application
and
then
we'll
you
know,
pro
rata
rewards
you
based
on
users
of
the
of
the
web3
api.
J
So
so
so
it
that's
like
you
know,
a
future
feature
set
that
we're
planning
on
really
focusing
on
is
this
whole
concept
of
application
mining
where
protocol
developers
can
remain
protocol
developers,
they
simply
publish
these
great
contracts
and
these
great
web
3
apis
and
then
application
developers
just
freely
integrate
them
and
they're
incentivized
to
do
so.
So
that's
that's
a
future
use
case,
but
but
yeah
it.
It
makes
the
integration
of
protocols
much
simpler.
E
Yeah
to
also
answer
that
question,
I
guess
we
don't
know,
because
we
don't
know
what
the
dx
dials
focus
is
right
now,
but
the
whole
idea.
What
we're
trying
to
do
right
now
is
get
like
a
couple
key
like
launch
partners
together.
That
think
this
would
be
useful
to
their
ecosystem
or
their
stack,
and
then
we
want
to
work
really
closely
with
those
teams
to
like
build
your
first
web
through
api.
Like
let's
say
in
the
next
five
months,
we
would
like,
as
the
alpha
gets
released
at
the
end
of
this
year.
E
We
would
start
like
working
with
you
to
be
like
okay,
where's.
What's
the
low
hanging
fruit,
what's
the
best
way,
you
can
try
this
out
first
and
then
like
we
would
do
the
heavy
lifting
of
like
building
it,
but
it
would
be
for
one
of
your
services
or
one
of
your
protocols
or
daps
and
so
yeah
it's.
This
is
just
the
start
of
figuring
out.
E
If
that
interest
is
there,
and
if
so,
we'd
want
to
like
just
have
like
a
continuous
thing
going
on
like
every
other
week,
figuring
out,
like
updating
you
on
what's
been
built
and
making
sure
that,
like
seems
useful,
because
we
just
don't
want
to
build
this
like
in
a
cave,
we
want
to
be
building
it
with
the
the
projects
that
will
be
using
it.
So
yeah
we
don't
know,
but
we
want
to
figure
that
out
with
you,
that's
my
answer.
B
So
I
suppose
three
api
could
be
useful
in
like
incentivizing
more
development
on
top
of
the
dx1
protocol.
I
suppose
we
could
think
about.
Maybe
what
that
would
mean
for
like
omen
or
or
doses
protocol
as
well,
I'm
not
as
I'm
not
sure.
Maybe
I
would
think
d
swap.
B
Maybe
is
the
one
that
makes
the
most
sense,
and
I
think
the
other
angle
would
be
if
dx
now
gets
around
to
like
some
kind
of
a
like
zap
or
instagram,
but
for
dx
style
products
like
if
we
have
kind
of
one
dashboard
for
dx
down
products,
then
maybe
this
helps
make
that
more
efficient
right
like
more.
J
B
That's
why
I
think
dxf,
because
I
think,
having
I
think,
that's
more
likely
to
be
integrated
into
other
protocols
like
some.
The
ability
to
you
know
create
kx,
swap
pools
and
trade
on
them.
I
suppose
you
know,
I
don't
know,
I
mean
that's
just
me
kind
of
guessing
I
mean
gnosis
protocol
or
or
the
conditional
token
framework
may
also
make
sense
at
some
point,
but
I
think
people
have
already.
You
can
already
see
that
a
lot
of
dapps
have
already
interacted
with
uniswap.
H
J
Yeah
that
works
yeah
totally,
so
that's
kind
of
like
the
big
reason
of
why
we're
standing
up
the
dow
in
the
fundraiser
so
that
we
can
spend
time
getting
it
to
a
really
solid
alpha
and
in
that
alpha.
All
of
these
networks,
like
ethereum,
like
let's
say,
zk,
sync
or
xdi,
will
be
treated
just
as
another
web
3
api
module
and
they
can
interact
with
each
other.
So,
for
instance,
the
rails
web3
api
module
may
include.
J
I'm
I'm
not
sure
what
layer
2
is
using,
but
let's
say
like
a
zk
sync
or
something
like
that
like
so
it
could
just
include
that
that
external
web
web
3
api
module
and
then
signing
you
know
would
be
happening.
Let's
say
with
metamask
or
something
like
that.
But
yes
like
you
could
definitely
use
other
layer
twos,
and
so
so.
This
is
equally
beneficial
for
app
developers
as
it
is
for
protocol
developers
as
it
is
for
network
developers
to
be
able
to
get.
J
You
know
your
things
used
in
different
protocols
and
different
apps,
so
yeah
it's
it's
kind
of
like
a
an
operating
system
for
peer-to-peer
modules
like
peer-to-peer
like
peer-to-peer,
client-side
micro
services.
I
guess
you
could
say,
but
that's
like
you
know,
technical
verbiage
but
yeah.
H
J
100,
yep
and,
and
one
of
the
big
features
with
the
web3hub
that
we're
adding
is
the
ability
to
have
these
dashboards
that
are
just
generated
ui
from
these
web
three
queries,
and
so
in
this
you
could
create
a
dx
dial
dashboard,
which
has
its
governance,
its
proposals,
the
dx,
swap,
you
know
all
of
the
open.
Like
omen
markets,
you
know,
like
all
the
dx
protocols
in
one
single
interface,
and
you
don't
have
to
create
this
interface,
it's
being
generated
for
you.
J
All
you
have
to
do
is
just
author,
the
queries
that
interact
with
your
various
different
protocols
so
yeah
like
it
it
it
just
goes
to
show
like
when
you
make
things
dynamic.
When
you
make
things
based
off
of
us
like
an
easy
to
understand,
schema
like
graphql,
you
can
now
generate
these
really
nice
uis
that
are
great
aggregations
for
lots
of
different
things.
H
If
I
could
ask,
maybe
one
more
just
curious
on
your
thoughts
on
the
current
status
of
of
the
graph
and
and
their
their
decentralization
path,
and
also
like
just
struggles
that
they've
had
something
that
I've
been
getting
all
sorts
of
signals
from
everywhere.
So
I'm
curious
what
what
you
think
about
that.
J
Yeah
so,
first
and
foremost,
this
is
a
complementary
project
to
the
graph.
This
does
not
replace
what
they
are
doing.
This
is
strictly
an
add-on,
so
the
graph
is
still
used.
Let's
say
for
historical
data.
This
would
just
be
used
for
client-side
logic.
H
J
Okay
yeah,
so
I
I'm
not
necessarily
sure
you
know
I
don't
know
if
their
model
will
do
well
in
the
long
run.
I
think
that
there's
definitely
going
to
need
to
be
multiple
competing
models
to
figure
out
what
the
best
token
economics
are
for
this.
This
query
problem
that
they're
trying
to
solve,
and
so
for
web3
api.
As
far
as
it's
concerned,
subgraphs
are
used
as
just
an
add-on
to
a
web3
api.
So
if
another
computing
solution
comes
out,
you
could
just
as
easily
use
that
in
in
replace
of
the
subgraph.
J
Like
you,
you,
you
can
map
those
graphql
queries
to
something
else
like
you
know
so,
yeah,
like
you
yeah,
so.
E
Yeah,
just
don't
want
to
take
up
more
time,
because
I
know
this
probably
closes
in
two
minutes.
You
guys
want
to
close
out,
but
if,
if
this
is
interesting,
we
can
come
back
or
people
can
reach
us
reach
out
individually.
I
think
jordan
and
I
are
both
in
the
in
the
dxo
key
base
and
yeah.
I
can
like
drop
our
handles
here.
I
don't
know
if
anyone
has
better
ideas
for
next
steps.
J
Yeah
and
thanks
again
for
giving
us
the
floor
for
so
long
and
sorry
for
filibustering
if
we
did
but
yeah
this
is.
This
is
really
great.
We're
really
excited
about
the
collaboration.
J
Yeah,
so
so
for
right
now,
what
we're
doing
is
we're
like
signing
on
different
integration
partnerships
and
what
that
means
is
that
there's
this
non-binding
mou
document,
a
memorandum
of
understanding,
it's
basically
a
signaling
document
that
just
says
that,
like
there
is
good
faith
partnership
between
these
two
organizations,
and
so
if
the
dxtile
passed
this
mou
as
a
proposal,
it
would
effectively
sign
it
and
ratify
it.
Saying
that,
like
you
know,
the
dx
die
was
able
to
advertise
and
promote
web3
api.
J
The
same
way
that
web3
api
is
able
to
advertise
and
promote
dx
style
as
a
partnership,
and
this
partnership
is
for
launch
partners
for
different
integration
partners,
and
so
we've
been
talking
to
you
know:
people
like,
for
instance,
gnosis
to
be
able
to
get
them
signed
on
so
yeah
yeah.
That's
that
that's
where
it
is
right
now
is
getting
lots
of
different
launch
partners.
B
I
think
whether
or
not
gnosis
is
involved
is
relevant
to
because
I
mean
the
two
live
products
now
are
built
on
gnosis
smart
contract
protocols,
so
yeah.
J
E
G
Dope,
all
right
thanks
guys,
yup
thanks,
see
ya.
Thank
you
later.
I
know
we're
at
the
hour.
I
can
go
another
10
minutes.
If
you
guys
are
down.
All
I
wanted
to
bring
up
was
just
the
air
table
that
I'm
starting
to
update
more
with.
I
don't
know
if
you
guys
are
able
to
see
it,
but
it's
got
like
marketing
tasks
and
I'm
kind
of
toying
with
putting
bounties
on
there.
G
So
everyone
sees
like
like
many
projects
that
everyone's
handling,
at
least
in
the
marketing
department,
it's
mostly
stuff
by
me
and
mike,
and
I'm
starting
to
put
bounties
on
there
just
to
see
like
if
it
looks
better
than
google
docs,
so
you'll
have
a
place
to
see
like
what
like
what
we're
doing.
G
That's
that's
sort
of
it
and
I
I've
got
matt
bartlett
working
on
one
of
them
just
putting
together
all
the
content
pieces
that
have
ever
come
out
in
the
extent
and
putting
them
in
the
categories
for
each
each
product
and
maybe
having
that
as
a
place
for
like
when
we
update
the
website
to
have
all
the
content
pieces
for
for
each
product.
G
All
right
guys
cool
thanks
for
coming
on.
Shall
we
adjourn
this.