►
From YouTube: DXdev Weekly Sync [2023-01-24]
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
C
Presenting
the
sapping
contracts,
what
we
have
the
work
that
has
been
there
has
been
done.
They
are
so
far
by
the
contractors
that
we
had
working
for
us
the
last
year.
What
was
the
name
of
the
con?
The
contractors
yeah
Oscar
from
right.
C
D
Yeah
I,
don't
think,
there's
a
ton
Beyond
last
time.
The
data
migration
data
architecture,
migration
is
going
well
and
we're
moving
on
to
the
subgraph
support
now,
which
is
actually
utilizing
the
the
new
architecture.
So
we're
able
to
switch
between
data
fetching
models
and
all
that
is
going
well.
We've
got
a
few
design
changes
as
well,
which
is
quite
nice
to
be
to
be
implementing
where
you
can
know
because
of
the
subgraph.
D
It's
a
bunch
of
additional
pages
and
features,
like
members
view
permission,
View
and
seeing
individual
votes
on
our
proposal.
So
that's
all
very
nice
and
I
think
that's.
D
On
oh
well,
we
had
our
release
as
well
at
the
start
of
this
week,
yeah
the
release
the
release,
notes
on
discard
on
GitHub
and
on
the
DX
gov
keybus
chats.
So
that's
live
at
app.projectaview.heath,
dot
level
version,
2.4,
yeah
I
think
that's
everything.
Okay,.
D
D
Probably
bug
fixes
which
now
makes
the
streaming
contracts
work
properly,
so
it
wasn't
technically
part
of
the
release
because
we
can
do
additional
contracts
editions
today
without
doing
a
release
because
it
uses
subdomains
from
ens,
which
is
another
cool
thing,
but
the
the
thing
we've
been
using
this
week
and
actually
we
just
executed
one
yesterday-
is
streaming
from
langope,
so
we're
using
their
vesting
contracts
for
streaming
payments
to
match
just
made
a
reports
for
yesterday
for
streaming.
D
6000
wrap
text
die
across
two
months
and
you
did
it
and
then
today
executed
that
to
get
I
guess
just
under
a
month's
pay
and
then,
if
he
wants
to
tomorrow,
you
can
get
another
day's
worth
of
pay
which
is
cool
and
so
we're
setting
up
the
rest
of
the
team's
streams
as
well
today
and
yeah.
That's
probably
my
favorite
there's
a
lot
of
good
quality
of
life
updates
in
there,
though,
if
you
want
to
read
the
changelog.
A
B
C
There
is
going
to
be
minted
at
burn
from
the
Dow
itself
and
both
of
the
tokens,
the
DFC
State
token
or
contract.
This
is
something
that
fair
is
working
on
right
now.
We
don't
have
it
ready
to
share,
but
it's
going
to
be
very
soon
the
DFC
State
and
the
reputation
token.
Both
of
them
are
going
to
be
calling
back
the
voting
power
talk
and
this
voting
power
token
is
going
to
have.
We
are
going
to
be
able
to
configure.
C
Reputation
and
dxc
stake
to
get
a
final
voting
power
that
is
going
to
be
used
for
their
governance.
So
this
is
what
we
have
been
working.
We
are
going
to
have
pull
requests
created
today
with
the
first
version
of
the
contracts
right.
We
are
going
to
hide
today.
Right,
yes,
say:
CC,
okay,
yeah
I'm,
hearing
see
from
the
background.
So,
if
not
today,
tomorrow
yeah
we
are
going
to
be
sharing
it
in
the
development
Channel.
It's
a
very
important,
my
son.
C
So
this
is
going
to
be
part
of
the
dxr
contracts,
the
Exile
contract,
2.1
version,
and
we
still
need
to
specify
the
Milestone
and
the
and
the
features
that
we
aim
to
add
on
the
next
on
the
next
contract
release.
But
it
will
be
mainly
this
governance,
2.0
right,
the
governor
2.0,
both
in
power
formulas
and
a
smart
contract,
and
then
on
the
next
version
of
the
on
the
on
the
next
release.
C
The
idea
will
be
to
add
the
Boating
machine,
with
multiple
options
and
and
a
scheme
with
multiple
options,
but
for
now
we
are
going
to
type
we
are
going
to
try
to
keep
the
next
version
of
2.0
of
the
Excel
contracts,
2.1
focus
on
the
governor
2.0
implementation.
That
is
again
the
combination
of
reputation
and
DXE
yeah
to
get
the
final
vote
in
power
that
it
will
be
used
for
Goblin
assist
for
our
governance
system.
C
No
okay,
let's
do
carrot,
then
we
can
lip
swapper
for
the
last,
because
nursing
is
going
to
be
presenting
something
software
related.
So
let's
do
carrot
next
and
we
have
the
over
here.
C
C
No
I
know
Lucifer's
no
fair
Binky
anything
or
we
should
wait
for
the
album
to
give
an
update
on
the
development
Channel.
F
B
Okay,
just
to
add
to
Augusta,
to
just
add
to
thank
you
so
in
the
carrot
Channel,
which
anyone
here
you
can
be
in
it.
If
you
want
there's
a
dock,
there's
a
breakdown
of
the
original
post
that
Federico
made
when
he
set
out
to
start
creating
current
V1,
that's
obviously
a
little
outdated,
and
so
there
may
be
some
changes
to
what
has
been
built
and
what's
focused
on
and
so
venky
and
well.
The
carrot
Guild
like
ideally
is
gonna
provide.
B
What
this
initial
version
is
so
that
everyone
here
in
you
know,
devs
plus
everyone
else
can
have
the
same
yeah
the
same
initial
product
in
our
heads
as
we
think
about
how
to
begin
using
it,
how
to
share
it
with
other
communities
and
and
the
plan,
and
so
then,
in
that
doc.
B
Also
in
the
our
Channel
there's
some
rough
timeline,
which
is
just
an
initial
draft
of
what
timing
could
look
like
and
then,
if
we
can,
if
anyone
wants
to
make
any
changes
to
that,
that's
that's,
but
that's
just
to
get
everyone
on
the
same
page
in
terms
of
like
how
we
could
you
know
how
it
would
roll
out
over
the
next
few
months
and
then
ex
and
then
span
from
expand
from
there
and
like
what
some
goals
would
be
over
the
course
of
the
year
and
then
there's
some
and
then
the
other.
B
The
other
piece
is
be
like
most
of
our
products
like
Davi
like
we
did
with
swapper
like
carrot,
will
be
we'll
have
like
an
initial
version
and
obviously
the
a
really
important
part
is
to
learn
the
feedback
of
users.
So
users
will
be
a
lot
of
DX
Dao
Community
products,
using
it
getting
feedback
and
then
other
communities
and
getting
all
that
feedback
and
then
being
able
to
iterate
and
either
add
things
that
are
missing
or
fix
things
that
aren't
working
and
that
kind
of
fits
in
with
that
would
fit.
B
That
would
go
in
parallel
to
the
to
the
to
like
the
Strategic
timeline.
I
think
so
check
that
doc
out.
If
you
have
any
comments,
you
can
add
it.
If
you
have
any,
if
you
want
to
chat
about
it,
we
can
all
chat
about
it,
but
that's
to
like
help
align
everyone's
understanding
of
of
how
carrot
will
carrot
V1
will
come
into
existence.
I
think
so.
Take
a
look
at
that
doc.
B
E
Sure
for
swapper
we
have
onboarded
Nielsen.
As
you
guys
know,
we
had
a
car
with
a
new
ranking
and
then
we
decided
you
know
like
a
lot
of
things
going
on
on
the
contract
side.
So
we
immediately
start
working
on
the
zapping
contracts
actually
did
before
we
officially
onboarded
them,
because
so
that's
so
that's
that
I'm
personally
working
on
a
new
product
I'm,
not
sure
if
we're
going
to
call
out
a
new
product
or
not.
E
But
it's
like
a
part
of
a
initiative
within
swapper
that
does
like
dollar
cost
averaging
built
on
top
of
a
cow.
So
the
main
architecture
like
super
simple,
you
have
like
a
factory
contract
and
then
you
have
like
a
vault
proxy
user
comes
in
and
then
they
deposit,
like,
let's
say,
like
eight
thousand
dollars
worth
of
usdc.
E
This
goes
into
default
and
then
there's
like
a
bot
that
does
the
DC
ink
with
them.
So
there's
like
a
server
setting
and
there's
like
a
on
chain.
The
cool
thing
about
the
engine
stuff
is
like
the
user,
have
the
full
authority
of
a
different,
so
they
can
always
like
withdraw
their
tokens
in
case
they
feel
like
they
want
to
cancel
or
they
just
feel
unsafe,
and
that
will
trigger
like
the
cancellation
of
the
entire
thing
and
that
would
destroy
the
Vault
itself,
but
I
think
I
can
probably
demo
it.
E
Next
week
it's
like
I
I
showed
a
few
screenshots
to
lanky
and
then
said,
but
yeah
we're
gonna
see
how
this
goes.
There's
also
a
mono
repo
on
impeccable
HQ,
it's
private
right
now,
but
I
can,
if
you're
a
member
of
the
organization
on
GitHub,
you
should
have
access
to
it
and
then,
like
the
team,
are
still
working
on
like
some
of
the
fixes
fundament
order.
E
We
have
like
one
inch
integration
coming
but
not
like.
We
don't
have
like
a
release
pipeline
just
yet,
and
then
I'll
probably
give
it
a
new
song.
Yes,
probably
more
exciting
things.
C
Yeah
sorry
regarding
the
the
cows
have
limited
or
the
orders
what
other
regions
are.
We
are
we
find
there
issues
yeah,
like
you,
you
mentioned
fixing
something
regarding
cows.
E
So
basically,
there
are
a
few
things
other
than
like
the
ux
itself,
so
you
have
like
a
lot
of
so
you
have
like
if
you,
if
you
want
to
switch
between
the
pro
mode
and
then
the
simple
mode,
you
have
like
a
lot
of
things
losing
so
you
deform
itself
we
set,
so
we
we
decided
to
move
a
the
state
higher
up
in
the
reacting
component
tree.
So
the
context
I
think
there's
also
another
thing:
Leonardo
is
working
on
it,
but
I
can't
recall
right
now.
Leonardo
do
you
know
what
it?
A
A
That
too,
like
when
you
enter
on
limit
orders
You
by
default,
have
one
percent
price
increase
on
the
sell
amount.
So
if
you
go
and
exchange
by
the
default
value,
you
will
earn
one
percent
more
than
the
market
price.
A
No,
no!
It's
the
default
market
price
on
limit
orders,
so
you
go
to
limit
orders.
It
has
by
default,
one
percent
increase
on
the
on
the
on
the
limit
order
price
and
you
can
use
the
market
price.
That's
the
price
that
other
markets
give
you
or
you
can
change
to
another
price
like
10,
more
or
10
percent,
less
yeah!
C
Okay,
try
it
on
swapper.site,
okay,.
D
F
Sure,
hello,
everyone
so
devia
here
is
to
talk
about
a
little
bit
about
what
the
sapi
controls
are
well.
I
have
been
working
on
with
them,
so
for
everyone
that
doesn't
know
the
sapier
contracts,
the
sub
contracts
to
a
very
simple
job,
which
is
when
you
want
to
provide
liquidity
or
remove
liquidity
from
an
exchange.
F
So
the
idea
of
these
sub
contract
is
to
make
it
easier
for
the
users,
so
you
can
just
provide
one
token
and
the
contract
of
the
necessary
swaps
to
get
the
50
50
rate
on
the
two
tokens
of
the
tools
you
actually
want
to
open
and
then
provides
a
liquidity,
takes
a
small
fee
for
the
job
and
gives
the
lp
tokens
back
to
their
to
the
to
the
user.
F
F
F
I
did
was,
to
like
add
those
tests
and
refer
to
a
few
things,
thanks
Augusto
for
the
link
and
then
after
doing
that,
there
is
one
change
left
I'm
having
issues
the
usct
UCT
contracts
have
a
specific
allow
allowance
change
constraints
where,
in
order
to
change
the
the
approval
amount,
the
approved
amount
or
the
allowance,
you
first
have
to
set
it
to
zero,
and
then
you
can
actually
change
it.
F
That's
to
prevent
an
attack
Vector
on
many
erc20
right
now,
but
so
because
of
that
I
have
some
testing
using
the
usdt
constructs
to
make
sure
our
our
implementation
works
with
them,
because
it's
not
the
only
token
that
has
this
restriction
and
having
some
issues,
some
errors,
doing
data
specific
unit
testing.
So
that's
the
only
commit
missing
on
the
refactor
pull
request,
which
is
the
first
one
you
will
see
on
the
link.
I
will
suggest
posts.
F
Another
two
things
I've
been
working
on,
which
are
the
two
other
pull
requests
you
see
there
one
is
we
used
to
have,
or
we
have
currently
Boolean
parameter
when
you
sap
in
so
when
you
provide
the
liquidity
that,
after
doing
the
exchange
and
providing
the
liquidities,
there
could
be
some
procedural
tokens
still
remaining
within
the
contract
that
actually
belong
to
user.
F
F
F
So
the
I
was.
This
idea
was
to
swap
the
Boolean
to
minimum
amount
of
tokens.
So
when
you
step
in
you
can
say:
okay,
if
the
threshold
is
above,
this
Mark
of
tokens
I
want
them.
If
it's
not
just
leave
them
on
the
contract
code,
it
doesn't,
it
doesn't
compensate
for
the
extra
gas
to
transfer
the
tokens
back
to
my
account.
So
there
is
no
point
in
doing
it.
F
F
But
let's
say,
benefits
on
the
partnership
side
is
the
affiliate
feeds.
So,
what's
now
in
the
current
concurrent
version
of
the
contract,
is
you.
E
F
An
affiliate
split,
a
fixed
affiliate,
speed
for
everyone,
and
then
you
can
add
addresses
that
will
get
this
affiliate
fees,
so
that
has
some
limitations.
The
first
one
being
you're
gonna
have
two
different
affiliates
with
different
splits
and
the
second
one
is
like
it's
taking
the
fee
directly
from
the
protocol
fee,
so
yeah,
it's
more
limited.
So
the
another
proposed
idea
where
I
used
to
that
I
developed
was
to
First.
F
Have
this
affiliate
fees
taken
from
the
total
amount
instead
of
the
instead
of
the
actual
current
protocol
fees,
so
it
can
be
sent
to
anything
below
the
protocol
fees,
so
it
cannot
be
higher,
but
that
gives
us
more
flexibility
on
what
can
be
extracted.
What
can
be
set?
F
F
Those
are
three
pairs
you
see
available
now
and
another
thing
I'm
working
on
is
called
injury,
doing
research
on
how
to
integrate
Unity
and
nearly
any
other
two
tokens
pools,
because
it's
more
than
two,
then
it
will
be
more
complex.
But
the
idea
is
to
create
a
common
interface
for
liquidity
protocols,
like
essentially
in
liquidity
protocols.
You
can
do
flops
and
provide
liquidity
in
and
out
or
oily
green
tea
or
take
liquids
out.
F
So
the
idea
is
to
build
a
common
interface
that
the
subcontracts
can
use
and
then
have
specific
implementations
of
those
of
that
interface
on
very
small
Constructor.
Its
only
job
is
to
receive
the
calls
from
the
subcontracts
and
understand
each
product
each
protocol,
specifics.
Let's
say
we
have
a
contract
that
has
the
adequity,
the
Swap
and
the
remote
liquidity
functions
implemented
for
initial
B2,
which
is
what
the
currently
current
subcontract
does.
F
It
uses
Universe
V2,
but
we
can
also
have
dnb3
implementation
in
another
contract
using
the
same
common
interface
and
that
what
that
allows
us
is
to
add
more
dexes
that
can
be
univ
2
unit,
3
or
whatever
implementations
of
the
interface
we
we
do
and
then,
when
we
add
the
new
decks,
we
just
specify
what
what
kind
of
protocol
it
is.
F
University
I
know
money
swap
from
180
with
blue,
whatever
balance
at
least
two
token
pools,
and
that
will
mainly
allow
us
to
have
one
implementation
that
we
don't
really
have
to
update.
If
we
want
to
implement
an
alligator,
because
you
only
deployed
this
small
implementation
on
new
contracts
and
then
you
add
it
to
the
current
Lexus
list
and
it
should
work
out
of
the
box
if
the
if
the
implementation
is
right.
F
So
that's
the
idea,
that's
why
I'm
currently
doing
research
on
and
I
have
like
the
main
design,
at
least
on
paper
and
after
I,
get
some
feedback
for
it
and
I
will
start
the
development.
Any
questions.
C
The
main
thing
will
be
regarding
unib3
that
we
have
something
called
Texas
right,
like
a
taxi.
C
F
Yeah
absolutely
like
I
think
right
now,
because
of
legal
reasons.
There
are
no
other
university
implementation,
but
not
long
in
a
couple
of
months.
We
will
see
many
but
yeah
I
mean
I,
say
in
unisa,
but
I
can
actually
be
used
on
on
any
other
implementation
of
of
the
three.
We
just
need.
The
the
router
and
the
factory
addresses
I.
C
F
The
the
challenges
here
are
because
of
how
the
liquidity
Works
in
uni,
you
I
mean
Unity.
You
provide
you
just
spray
liquidity
and
it's
a
very
straightforward
process
on
the
unib3.
You
have
six
minute.
Mark
sticks
where
you
can
provide
a
great
different,
specific
range
of
price
and
yeah
that
that's
the
main
challenge
like
we
need
to
be
able
to
add
the
like
to
to
be
flexible
enough.
F
So
we
can
have
all
the
parameters
in
when
I
use
in
interacts
with
with
the
separate
contracts,
but
I
mean
it
can
be
done
as
far
as
the
research
has
done,
skills
but
we'll
see.
C
Okay,
cool
yeah.
That
would
be
very
interesting
to
see
how
how
it
is
implemented
very
interesting
and
see
how
feasible
will
be
to
use
it,
because
what
functionalities
are
we
going
to
lose
for
unib3
migrating
this
rubber?
This
wrapper
that
can
be
used
to
work
with
unib2
Integrations
as
well
so
yeah.
That
would
be
very
interesting
to
see
regarding
the
the
purpose
of
national
I'm
already
reviewing
them.
C
C
The
affiliate
fees,
let's
see,
does
it
change
on
the
structure
of
how
the
fish
affiliate
fees
work
and
yeah
later
it
will
be
good
also
to
see
what's
the
timeline
or
start
integrating
these
these
contracts,
as
well
in
in
swaba
I.
Guess
we
can
have
that
the
answer
to
the
question
in
a
few
weeks
and
see
how
it's
going
to
affect
swapper
roadmap
and
if
it
makes
sense
to
put
more
energy
and
work
in
supporting
University
from
the
right
from
as
soon
as
it
starts
being
used
by
other
exchanges.
C
C
B
C
B
C
Nelson
anyone
else
has
any
question
for
Nelson
or.