►
From YouTube: DXdev Weekly Sync [2023-02-07]
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).
A
Weekly
developer
call
7th
of
February
2023,
and
today
we
are
going
to
you
to
do
the
usual
run-up
over
the
Exile
projects
to
see
what
happens
in
the
last
week
and
I
also
am
going
to
present
something
I'll
be
working
on
for
the
past
yeah
I
think
for
the
past
three
weeks
more
than
working
on
I've
been
thinking
a
lot
on
how
to
implement
it
and
I
finally
did
I
had
an
open
pool
requesting
the
exact
contracts
and
I
think
it.
A
It
turned
out
been
something
pretty
cool
like
a
very
good
hug,
so
I'm
going
to
be
presenting
it
today.
Also
it's
a
create
a
true
deployer,
but
let's
leave
that
for
the
last
first,
let's
go
over
the
Excel
projects,
I
think
yeah
medicine
yeah
wrote
no
Ross
is
Ross
is
not
here
because
he
has
traveled.
B
C
Sure
yeah
so
we're
in
the
final
set
of
migrating,
the
hooks
to
a
stock
craft.
We
have
I
think
one
or
two
hooks
left,
so
that's
been
smooth.
C
We
now
have.
We
can
now
show
who
voted
on
the
proposals
that
was
very
requested,
got
three
new
pages
treasury
permissions
and
members
all
depending
on
this,
so
graph,
well,
except
treasury.
But
the
other
depends
on
the
Socrative
implementation.
C
D
C
C
Well,
not
like
a
fresh
coat
of
paint.
We
are
taking
a
little
more
time
to
get
this
release
done,
but
yeah,
maybe
Debbie
releases
and
development.
You
can
understand
that.
A
A
Okay,
well
thanks,
you
know:
let's
move
to
the
next
one
that
will
be
swapper,
Adam
or
Frankie.
E
So
Nielsen
is
also
Nelson,
as
usual
is
working
on
zapping
contracts,
I'm
working
on
a
DCA
I'm
working
on
the
DCA
I
think
so
I
think
two
weeks
ago
we
demoed
this,
and
then
we
realized
that,
like
a
lot
of
things
that
are
kind
of
centralized,
because
the
way
we
are
this
is
that
you
have
like
a
bot
that
automates
all
the
things
to
you,
then
I
met
Felix
from
car
swap
at
a
Meetup,
and
then
he
suggested
using
something
called
an
I
said
standard
called
ERC
1271,
and
it's
actually
the
same
thing
that
Arjun
uses
for
verified
signature.
E
E
So
if
you're,
let's
say,
if
you're
every,
if
the
person
or
the
entity
that
has
the
submitted
a
cow
swap
order
and
if
it's
a
contract,
what
cow
does
is
that
they
call
a
message
called,
is
valid
signature
and
this
valve
signatures
they're,
going
to
pass
you
to
things
which
I
think
is
the
message
hash
and
then
the
signature.
So
the
next
attack
I
believe
it
could
be
anything.
So
this
could
be
the
order
digest
in
case
of
car
shop
and
then
the
signature.
And
then
what
did
what
your
contract
does
is
verifies
it.
E
And
then
you
can
have
all
sort
of
conditions
you
want
so
in
in
our
case,
I
think.
The
one
we're
really
curious
about
is
the
receiver,
because
this
can
be
anything
and
I,
don't
think
we're
going
to
implement
like
the
amount,
because
that
can
be
like
too
much
gas
gas
to
consume
on
the
contract.
But
we
just
want
to
make
sure
that
the
receiver
is
the
one
that
is
the
who
is
the
person
who
deployed
the
contract.
So
that's
the
thing
we're
currently
working
on
and
then
other
things
we're
also
aiming
for
like
a
release.
E
I
think
we've
been
promising
you
and
we've
been
hashing
this
for
a
long
time,
but
bank
is
trying
to
get
the
beta
19
out
soon.
There's
like
a
lot
of
things
going
on
there,
so
I
think
that's
everything
for
this
week
Allah.
He
can
fill
me
in
if
I
forgot
anything.
D
B
A
That
you
are
you're
seeing
that
you're
using
1271.
yeah,
that's
a
standardized
way
to
verifying
is
a
very
heavy
way
right,
because
the
smart
contract
cannot
sign
anything.
But
it's
a
way
to
canal.
Like
agree.
Okay,
a
user
can
verify
that
this
is
a
valid
signature
from
a
contract
and
also
from
an
ethereum
or
an
account.
E
Yeah
I
think
if
you
go
back
to
the
exact
documentation
for
this
ERC,
it's
mainly
for
organosis,
safe,
but
also
Arjun
is
using
it.
So
I
think
like
this
is
a
big
thing
in
account
abstraction
Realm,.
A
B
A
Okay,
awesome,
then
we
can
move
to
the
next
one.
That
will
be
carrot.
Do
we
have
Diego
or
someone
from
carrot
here.
A
A
A
E
D
D
Not
technically
but
I
mean
we
just
had
a
call
with
Federico
and
Sky
last
week,
just
going
through
what
is
contained
in
the
first
release
of
carrot
and
what
should
be
the
timelines
and
so
on.
So
we
are
looking
at
I
mean
Canada
team
is
working
on
different
features
separately,
I
mean
I,
think
we
are
trying
to
see
if
we
could
integrate
all
of
them
together
in
the
upcoming
weeks,
and
then
we
will
see
yeah
how
well
it
is
integrated
together
and
it
is
working
together.
D
But
apart
from
that,
I
haven't
seen.
Canada
I
haven't
I
haven't
been
spending
a
lot
of
time
on
Karen
this
month:
okay,
yeah,
okay,
hopefully.
A
B
A
Okay,
positive
well
I
have
to
work
on
the
better
description
here
of
the
of
the
pull
request,
but
basically
this
is
the
request
that
they
create
to
deployer,
and
the
idea
is
to
ensure
that
we
can
be.
We
can
have
a
same
the
same.
How
can
we
say
the
same.
A
Contract
on
every
Network,
sorry,
okay,
the
same
deployment,
smart
contract
on
every
Network
and
this
smart
contract.
We
will
be
able
to
use
it
as
entry
point
to
do
public
or
private
deployments.
Public
deployment
is
what
we
have
been
doing
so
far
with
the
which
is
you
tell
the
deployer,
hey
deployed
this
byte
code
and
use
this
salt
and
it's
going
to
generate
a
deterministic
address.
A
Does
it
we
can
use
that
address
everywhere,
but
that
can
be
that
can
be
exploited
publicly
because,
for
example,
let's
say
that
we
are
interested
only
on
deploying
on
like
a
magnet
and
nosy
chain,
and
we
deployed
The
Guild
on
mainnet
and
oxygen
and
it
can
be
someone
else
can
go
and
can
publicly
deploy
it
on
arbitrol
right
or
any
other
ethereum
etvm
ebm
network.
So,
okay,
that
happens
and
the
contract
setups
on
the
initialized
metal,
when
the
contract
is
a
let's
say,
establish.
A
E
A
They've
asked
how
how
do
we
prove?
How
do
we
make
sure
that
we
that
the
address
can
be
deployed,
that
the
same
smart
contract
can
be
deployed
on
other
words,
and
we
have
control
over
it?
My
initial
response
was
what
we
deployed
from
an
ethereum
account
and
that's
it.
We
can
ensure
that
this
private
kit,
this
private
key,
can
be
the
only
and
sole
deployer
of
these
smart
contracts.
A
But
the
idea
here
was
to
use
a
Crea,
a
creature
deployer,
so
I
had
to
combine
the
deployment
using
enforcing
the
message,
dot,
sender
or
the
ethereum
account
that
is
going
to
be
used
to
make
deployment
on
a
deployer
contract,
so
I
have
a
private
key
of
this
account
and
I
use
this
to
call
the
employer
contract
and
deploy
this
contract,
and
the
only
way
to
recreate
the
the
address
of
the
contractors
employee
is
to
have
access
to
my
ethereum
account.
So
the
primary
deployment
is
done
using
the
white
called
plus
the
employer
address.
D
A
A
A
So
what
we
do
is
we
send
funds
to
this
transaction
where
we
don't
have
control,
but
we
can
execute
I
mean
we
sent
funds
to
the
address
that
will
execute
the
transaction
and
we
execute-
and
this
is
what
we
did
on
nosy
chain
and
on
sepolia
with
Milton
yesterday,
for
example,
we
baked
we
built
in
transaction
that
is
going
to
be
executed
from
this
address,
where
we
don't
have
the
private
key
and
we
send
enough
funds
to
cover
the
thus
cause
for
the
create
to
deployer
to
create
this
employer
smart
contract.
A
A
The
way
the
then
later,
the
way
the
addresses
are
generated
or
are
calculated
the
address
that
smart
contract
is
going
to
have
the
sender
or
the
deployer
of
of
the
summer
countries
being
is
being
taken
in
count
so
having
this
smart
contract
they
create
to
deployer.
Being
the
same
address
is
very
important,
because
this
is
the
entry
point
for
this
determininity
calculation.
If
this
address
is
not
the
same,
you
won't
have
the
same
smart
contracts
employed
with
the
same
address
from
these
ones.
A
D
A
That
we
have
this
smart
contract
that
uses
other
two
smart
contracts,
one
from
private
and
one
from
public
deployments.
If
you
want
to
deploy
a
public
contract
using
the
code,
you
can
also
set
the
initialize
call
data.
So
if
this
is
different,
that
0x0
is
going
to
call
the
contract
as
soon
as
it's
being
created.
This
is
very
helpful
because
I
can
create
a
smart
contract
and
then
initialize
it
right
away.
We
have
tests
for
this.
A
D
A
A
A
The
code
to
I-
don't
remember,
that's
it,
the
private
one
doesn't
receive.
The
salt
is
Hash
the
sender,
and
this
is
where
we
use
something
very
interesting.
We
use
the
DX
origin,
so
the
TX
origin
is
something
that
you
shouldn't
use.
This
is
not
safe
to
use.
You
should
be
very
careful
on
how
do
you
use
it,
because
the
TX
origin
is
the
original
sender
of
the
of
the
transaction.
A
This
is
always
an
ethereum
record.
This
cannot
be
in
a
smart
contract,
so
we
hash
the
sender
which
is
going
to
be
the
TX
origin,
always
in
athenum
account
the
account
that
is
going
to
execute
these
display.
Deployer
and
the
private
deployer
has
only
the
function
deployed
where
it's
going
to
again
receive
the
DX
origin.
So
you
see
here
we
are
on
another
contract
that
is
being
called
by
this
contract,
but
the
TX
origin
is
always
the
same
is
going
to
be
always
the
same.
Ethereum
account
important
thing
here.
A
B
A
B
A
Deployment
these
contracts
made
to
create
two,
and
what
it's
going
to
do
is
going
to
use
it's
going
to
calculate
the
address
by
hashing.
These
address
the
code
that
we
are
sending
and
the
salt
the
only
way
to
change
the
result.
The
only
way
to
specify
the
salt
is
by
crashing
DX
Collision,
which
is
a
ethereum
account,
so
there
is
no
way
to
specify
another
result.
This
is
not
an
arbitrary
way
to
set
this
out.
The
only
way
to
change
the
salt
is
by
doing
the
deployment
from
other
algories.
A
So
here
you
have
complete
control
and
I
know
that,
from
my
ethereum
account
a
I'm
going
to
call
the
deployer,
B
and
I'm
going
to
have
the
address
C
deployed
and
this
address
see
won't
be
able
to
be
replicated
without
my
ethereum
account
a,
and
this
will
be
a
way
where
we
can
deploy
the
same.
Let's
say:
give
contracts
right
on
mainnet
no
see
chain,
arbitrum
optimism,
any
other
evm
network
that
supports,
create
you.
A
So
this
is
an
extension
over
the
current
creature
deployer,
where
we
were
using
the
deploy
public
and-
and
this
is
deployed
private-
it's
a
very
hacky
solution,
but
based
on
all
the
research
and
everything
I
did,
it
should
work
it's
still
on
on
experimental.
A
A
Any
in
any
project
on
on
ethereum
or
anyone
can
use
the
create
to
deployer
I'm
going
to
create
the
geese
later
saying
this
is
the
creator
address
it's
on
these
networks
and
you
can
go
and
you
can
deploy
a
public
or
a
private
demand
contract
in
anytime?
You
want
me
one.
The
main
idea
for
this
is
to
later
integrate
it
on
Navi
right
where
we
are
going
to
deploy.
A
A
Maybe
we
don't
want
to
show
a
guild
that
is
going
to
be
dealing
with
I,
know
products
or
child
pornography
like
it
can
happen
right,
so
we
don't
want
to
show
that,
but
we
can
identify
the
guild
that
have
been
deployed
here
by
listening
to
the
white
called
hash
that
was
used
or.
A
I
think
this
wasn't
too
heavy
on
the
technical
side,
and
it
was
not
that
hard
to
understand
it
might
be
complex,
but
what
we
have
tested
for
it
and
right
now
is
working
and
we
are
going
to
be
yeah
testing
and
reviewing
it
I'm
going
to
share
the
poor
requests
on
the
development
channel.
Everyone
is
important
to
go
on.
Reviewing,
try,
try
to
break
it.
It
will
be
awesome
if
someone
can
break
it
and
create
the
same
at
the
idea
to
break
this.
A
D
A
B
Skype,
hey
yeah,
that's
this
sounds
cool
and
it
sounds
it's
a
little
complex
for
me,
but
a
question
high
level,
so
I
know
that
there
is
a
plan
to
eventually
have
more
of
a
factory
for
deploying
our
our
guilds,
so
that
would
work
that
looks
a
lot
more
like
the
factory
that
noses
safe
has
across
different
chains.
They
have
the
same
Factory,
which
allows
you
to
like
do
stuff
related
to
this.
Is
this?
B
A
D
A
You
see
the
equipment.
The
thing
is
that
you
will
need
to
do
more
work
on
the
client
side
right
on
on
on
your
side,
to
make
sure
that
you're
going
to
send
the
right
configuration
to
agree
to
deploy
it
later.
A
We
can
have
like
a
let's
say,
a
guild
Factory
where
you
just
say
this
is
the
type
of
kill
that
I
want
to
deploy,
and
this
is
the
configuration
that
I
want
to
use,
and
this
smart
contract
can
take
care
of
making
sure
that
it's
going
to
make
the
right
call
to
the
create
to
deployer
so
having
a
factory,
will
simplify
and
will
help
the
process.
But
it's
not
actually
needed
so.
B
Later
I
guess
I
understand
that
it's
not
actually
needed
I
guess,
but
for
like
most
even
developers
in
the
space
like
having
the
factory
like,
for
example,
if
there's
a
factory
I
can
figure
out
as
a
non-dev
how
to
deploy
a
guild
like
through
etherscan.
If
there's
no
Factory
like
I
can't
do
it,
and
so
there's
a
lot
of
people
like
that.
I
think
that
that's
why
I
think
a
factory
is
so
important
because
without
it
a
lot
of
people
get
or
feel
lost,
I
think,
oh.
A
Yeah
yeah
yeah
I:
when
is
when
it,
when
I
mean
it's
not
made,
I
mean
technically
need
right,
but
from
the
user
side
yeah,
it
might
I
mean
sounds
like
in
it.
Right
sounds
like
something
that
would
be
very
cool
and
it
won't
add
a
lot
of
complexity
and
yeah.
It
would
be,
it
would
be
great.
Actually,
this
is
something
that
the
DX
Gob
team
can
later
spawn
and
and
work
and
create
any
Factory
they
want.
This
is
the
I
mean
the
creature
deployer?
A
My
goal
here
was
to
make
something
that
would
be
very
flexible
that
can
be
used
with
anything
right
later.
You
can.
You
can
build
the
factory
over
it
by
the
Creator
deployer.
It
needs
to
be
something
solid.
That
allows
you
to
again.
This
is
the
new
feature
that
I
haven't
seen
on
any
other
deployer
or
any
other
Singleton
Factory
like
they
have,
and
they
have
been
quite
popular
I
haven't
seen
this
around.
This
is
like
this
is
something
new.
A
This
is
a
khaki
way
that
I
figured
out
how
we
can
we
can
do
a
play
with
deployment.
Of
course,
it
is
still
like
if
you
lose
a
private
key
that
you're
using
to
for
the
private
deployment.
That's
it
your
fact.
You
can
get
attacked,
but
you
can
still
be
in
control
if
you
make
sure
that
your
private
key
is
being
kept,
secure
and
and
yeah
yeah
add
in
a
factory
again,
it
will
be
awesome.